You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by da...@chaosreigns.com on 2011/10/14 20:22:56 UTC
Monthly tested unofficial Ubuntu releases of SpamAssassin
The official spamassasin release process drives me nuts, so I set up almost
completely automated monthly releases for Ubuntu.
Packages in this PPA have been tested at least by me on my server for a
month: https://launchpad.net/~spamassassin/+archive/spamassassin-monthly
The version I'm currently in the process of testing can be found here:
https://launchpad.net/~spamassassin/+archive/spamassassin-test
The testing versions come, once a month, from the daily build PPA:
https://launchpad.net/~spamassassin/+archive/spamassassin-daily
It's as easy to use as:
sudo add-apt-repository ppa:spamassassin/spamassassin-monthly
sudo apt-get update
sudo apt-get install spamassassin
And as easy to un-do as:
sudo ppa-purge ppa:spamassassin/spamassassin-monthly
The SpamAssassin Project Management Committee seems to need to make
everything as much work as possible. These monthly releases take almost no
work. I was already running trunk (the unreleased development version)
via the -daily PPA since April, and it's incredibly reliable. And there
are at least a couple other developers on the dev list running trunk
on production servers. So I think that, in combination with running
the test versions myself, will make it pretty easy for me to notice any
problems quickly enough to avoid propagating them to the -monthly PPA.
So the only work involved is, once a month, a few mouse clicks to copy
the contents of the -test PPA to the -monthly PPA, and from the -daily
PPA to the -monthly PPA.
Today is the first time I finished testing a build for a month.
If you use this, I'd appreciate if you told me. And of course, I'd
appreciate others testing the -test PPA.
There was supposed to be an official SpamAssassin version 3.4.0 Release
Candidate of what's currently in trunk, two weeks ago. It's going
incredibly badly.
The reason these releases are Ubuntu specific is because Ubuntu is what I
use, and Ubuntu has set up an excellent public build system (launchpad.net).
There are daily official snapshots of trunk (not releases):
http://cvs.apache.org/snapshots/spamassassin/
I think it would be fun to try to do something more official involving
similar monthly release tarballs. Part of the problem with that is
launchpad doesn't have a way to do automated imports from tarballs.
More info on building from trunk:
http://wiki.apache.org/spamassassin/DownloadFromSvn
--
"The whole aim of practical politics is to keep the populace alarmed --
and hence clamorous to be led to safety -- by menacing it with an endless
series of hobgoblins, all of them imaginary." - H. L. Mencken
http://www.ChaosReigns.com
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 11/14/2011 1:42 PM, Alex wrote:
>> The official spamassasin release process drives me nuts, so I set up almost
>> completely automated monthly releases for Ubuntu.
> Just wondering if someone is maintaining equivalent fedora RPMS?
>
> Also, looks like Warren isn't updating spamtips.org any longer?
I think Warren is pretty busy right now with graduate school. He'll
come up for air soon and keep fighting the bastard spammers.
regards,
KAM
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by Alex <my...@gmail.com>.
> The official spamassasin release process drives me nuts, so I set up almost
> completely automated monthly releases for Ubuntu.
Just wondering if someone is maintaining equivalent fedora RPMS?
Also, looks like Warren isn't updating spamtips.org any longer?
Thanks,
Alex
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by Karsten Bräckelmann <gu...@rudersport.de>.
> > > SpamAssassin 3.4.0 release candidate 1 is now 45 days overdue.
> >
> > We're moving towards a very nice release and I'm less worried about
> > the 9/30 goal if we didn't have such great movement on tickets
> > going. I certainly haven't forgotten!
>
> I know. I really appreciate all the work you've done recently. The
> momentum is great. And I agree that getting stuff fixed is more important
> in the short term than getting a releases out. But it bothers me how
> hard it is to get out an official release.
The date was a plan, not a commitment.
As with most Open Source projects, releases will be done when they're
ready. Neither asking when that'll be, nor constant nagging will get one
any closer to a release.
I'd appreciate if you would stop dropping a line like that every second
post. It's not helpful. Thank you for your cooperation.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 11/14/2011 5:54 PM, darxus@chaosreigns.com wrote:
> Not entirely sure what you're asking. sa-update has always worked. I
> considered mentioning the stuff about trunk not getting properly
> generated scores until recently, but obviously I didn't (
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6644 ). I have
> not been doing rules separately. These packages contain a snapshot of
> rules I pulled via sa-update on 2011-05-25, just to satisfy the
> existing Debian packaging. Maybe I should be clearer that I expect
> people to use sa-update.
I didn't consider the use of sa-update that distrubuted rules without
scores as "working".
>
> I know. I really appreciate all the work you've done recently. The
> momentum is great. And I agree that getting stuff fixed is more important
> in the short term than getting a releases out. But it bothers me how
> hard it is to get out an official release.
It bothers me too but I'm less worried about that than putting out a
good product. Improving documentation and streamlining the process is
needed.
Plus, we could likely have beers and a healthy debate about
long-term-server distributions vs. bleeding edge stuff. I'm far more
leaning towards the LTS concept than the latter.
For example, one of the things I think is dumb about eBay is the
arbitrary bidding deadline that leads to sniping. In a real auction, a
new bid would add more time to the auction indefinitely as long as
people are willing to bid.
In our case, as long as we have movement on bugs and nothing major to
justify the release, it makes some sense to keep rolling back the
deadline to get things into the release. We don't get a bonus for
releasing more versions ;-)
So right now, please focus on tickets because the 9/30 is a goal not a
deadline. But I think we are getting very close!
Regards,
KAM
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by da...@chaosreigns.com.
On 11/14, Kevin A. McGrail wrote:
> >I still haven't seen any problems running trunk since I began in April.
> Out of interest, have you been doing rules separately or are you now
> able to update with sa-update under trunk?
Not entirely sure what you're asking. sa-update has always worked. I
considered mentioning the stuff about trunk not getting properly generated
scores until recently, but obviously I didn't
( https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6644 ).
I have not been doing rules separately. These packages contain a snapshot
of rules I pulled via sa-update on 2011-05-25, just to satisfy the
existing Debian packaging. Maybe I should be clearer that I expect people
to use sa-update.
> > SpamAssassin 3.4.0 release candidate 1 is now 45 days overdue.
>
> We're moving towards a very nice release and I'm less worried about
> the 9/30 goal if we didn't have such great movement on tickets
> going. I certainly haven't forgotten!
I know. I really appreciate all the work you've done recently. The
momentum is great. And I agree that getting stuff fixed is more important
in the short term than getting a releases out. But it bothers me how
hard it is to get out an official release.
> Next thing on my plate is getting the DNS changes done to test the
> ipv6-only mirror/sa-update.
Excellent.
> I haven't looked at the curl/wget version of sa-update and wonder if
> we ripped all of LWP out which breaks sa-update on windows...
Don't think so: "If an external program is not available, fall back to LWP;"
- https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6654#c11
--
"Hermes will help you get your wagon unstuck, but only if you push on it."
- Greek Alphabet Oracle
http://www.ChaosReigns.com
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
> I still haven't seen any problems running trunk since I began in April.
Out of interest, have you been doing rules separately or are you now
able to update with sa-update under trunk?
> SpamAssassin 3.4.0 release candidate 1 is now 45 days overdue.
We're moving towards a very nice release and I'm less worried about the
9/30 goal if we didn't have such great movement on tickets going. I
certainly haven't forgotten!
Next thing on my plate is getting the DNS changes done to test the
ipv6-only mirror/sa-update.
I haven't looked at the curl/wget version of sa-update and wonder if we
ripped all of LWP out which breaks sa-update on windows...
Regards,
KAm
Re: Monthly tested unofficial Ubuntu releases of SpamAssassin
Posted by da...@chaosreigns.com.
Second monthly tested release is now available:
https://launchpad.net/~spamassassin/+archive/spamassassin-monthly
I still haven't seen any problems running trunk since I began in April.
Added builds for the next release of Ubuntu, 12.04 Precise Pangolin.
Most interesting change in the last month:
------------------------------------------------------------------------
r1199081 | mmartinec | 2011-11-07 21:52:16 -0500 (Mon, 07 Nov 2011) | 18 lines
Bug 6655: sa-update might DOS mirrors if TMPDIR unwritable
Bug 6654: Make sa-update and its infrastructure usable over IPv6
- the LWP perl module does not support IPv6 and is hard to trick properly
to use IO::Socket::INET6 in place of IO::Socket::INET (e.g., doesn't
handle multihomed (like dual-stack) hosts). Instead, add code to use
one of the external programs (curl, wget, fetch) to download rules files
and mirrors file, and make LWP module optional. If an external program
is not available, fall back to LWP;
- preserve .tar.gz, .sha1 and .asc files if rules installation fails,
so that a subsequent attempt does not download these files again,
as long as their size and creation time match the server
(this task is handled by curl, wget, or fetch);
- improve debug logging;
------------------------------------------------------------------------
SpamAssassin 3.4.0 release candidate 1 is now 45 days overdue.
Current monthly release: 3.4.0-0~16196, November 14 2011
First monthly release: 3.4.0-0~16013, October 14 2011
On 10/14, darxus@chaosreigns.com wrote:
> The official spamassasin release process drives me nuts, so I set up almost
> completely automated monthly releases for Ubuntu.
>
> Packages in this PPA have been tested at least by me on my server for a
> month: https://launchpad.net/~spamassassin/+archive/spamassassin-monthly
>
> The version I'm currently in the process of testing can be found here:
> https://launchpad.net/~spamassassin/+archive/spamassassin-test
>
> The testing versions come, once a month, from the daily build PPA:
> https://launchpad.net/~spamassassin/+archive/spamassassin-daily
>
> It's as easy to use as:
>
> sudo add-apt-repository ppa:spamassassin/spamassassin-monthly
> sudo apt-get update
> sudo apt-get install spamassassin
>
> And as easy to un-do as:
>
> sudo ppa-purge ppa:spamassassin/spamassassin-monthly
>
>
> The SpamAssassin Project Management Committee seems to need to make
> everything as much work as possible. These monthly releases take almost no
> work. I was already running trunk (the unreleased development version)
> via the -daily PPA since April, and it's incredibly reliable. And there
> are at least a couple other developers on the dev list running trunk
> on production servers. So I think that, in combination with running
> the test versions myself, will make it pretty easy for me to notice any
> problems quickly enough to avoid propagating them to the -monthly PPA.
>
> So the only work involved is, once a month, a few mouse clicks to copy
> the contents of the -test PPA to the -monthly PPA, and from the -daily
> PPA to the -monthly PPA.
>
> Today is the first time I finished testing a build for a month.
>
> If you use this, I'd appreciate if you told me. And of course, I'd
> appreciate others testing the -test PPA.
>
> There was supposed to be an official SpamAssassin version 3.4.0 Release
> Candidate of what's currently in trunk, two weeks ago. It's going
> incredibly badly.
>
>
> The reason these releases are Ubuntu specific is because Ubuntu is what I
> use, and Ubuntu has set up an excellent public build system (launchpad.net).
>
>
> There are daily official snapshots of trunk (not releases):
> http://cvs.apache.org/snapshots/spamassassin/
These have been removed.
> I think it would be fun to try to do something more official involving
> similar monthly release tarballs. Part of the problem with that is
> launchpad doesn't have a way to do automated imports from tarballs.
> More info on building from trunk:
> http://wiki.apache.org/spamassassin/DownloadFromSvn
--
"One armed student or teacher could have stopped the killer, but all
died obeying the rules."
- http://www.olegvolk.net/gallery/technology/arms/yourkid0181.jpg.html
http://www.ChaosReigns.com