[debian-volatile] SA 3.2.3 available (for test purpose)

Tags:

Hi,

spamassassin 3.2.3-0.volatile1 is currently available in
etch-proposed/volatile. Before we accept it to etch/volatile i would
like to ask some experienced SysAdmins to do some (more extended testing
as we did) of the package and report back any problems you find to
.

As soon as we are convinced that SA 3.2.3 works as expected i will
move the package to etch/volatile and send an official announcement.

Greetings
Martin
--
[root@debian /root]# man real-life
No manual entry for real-life

--

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

[debian-volatile] SA 3.2.3 available (for test purpose)

This one time, at band camp, Martin Zobel-Helas said:
> Hi,
>
> spamassassin 3.2.3-0.volatile1 is currently available in
> etch-proposed/volatile. Before we accept it to etch/volatile i would
> like to ask some experienced SysAdmins to do some (more extended testing
> as we did) of the package and report back any problems you find to
> .
>
> As soon as we are convinced that SA 3.2.3 works as expected i will
> move the package to etch/volatile and send an official announcement.

Just my point of view - the upgrade from etch's spamassassin to this
version was easy. The only thing that required manual intervention was
enabling the various new features.
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------

[debian-volatile] SA 3.2.3 available (for test purpose)

* Stephen Gran [071105 14:51]:
> This one time, at band camp, Martin Zobel-Helas said:
> > Hi,
> >
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.
>
> Just my point of view - the upgrade from etch's spamassassin to this
> version was easy. The only thing that required manual intervention was
> enabling the various new features.

I agree, I installed this version from backports.org a few months ago,
and it seemed pretty painless.

Micah

--

[debian-volatile] SA 3.2.3 available (for test purpose)

Hi,

On Mon Nov 05, 2007 at 22:44:52 -0500, Micah Anderson wrote:
> * Stephen Gran [071105 14:51]:
> > This one time, at band camp, Martin Zobel-Helas said:
> > > Hi,
> > >
> > > spamassassin 3.2.3-0.volatile1 is currently available in
> > > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > > like to ask some experienced SysAdmins to do some (more extended testing
> > > as we did) of the package and report back any problems you find to
> > > .
> > >
> > > As soon as we are convinced that SA 3.2.3 works as expected i will
> > > move the package to etch/volatile and send an official announcement.
> >
> > Just my point of view - the upgrade from etch's spamassassin to this
> > version was easy. The only thing that required manual intervention was
> > enabling the various new features.
>
> I agree, I installed this version from backports.org a few months ago,
> and it seemed pretty painless.

backports.org != volatile.debian.org

Greetings
Martin
--
[root@debian /root]# man real-life
No manual entry for real-life

--

[debian-volatile] SA 3.2.3 available (for test purpose)

Hi,

On Mon Nov 05, 2007 at 22:44:52 -0500, Micah Anderson wrote:
> * Stephen Gran [071105 14:51]:
> > This one time, at band camp, Martin Zobel-Helas said:
> > > Hi,
> > >
> > > spamassassin 3.2.3-0.volatile1 is currently available in
> > > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > > like to ask some experienced SysAdmins to do some (more extended testing
> > > as we did) of the package and report back any problems you find to
> > > .
> > >
> > > As soon as we are convinced that SA 3.2.3 works as expected i will
> > > move the package to etch/volatile and send an official announcement.
> >
> > Just my point of view - the upgrade from etch's spamassassin to this
> > version was easy. The only thing that required manual intervention was
> > enabling the various new features.
>
> I agree, I installed this version from backports.org a few months ago,
> and it seemed pretty painless.

backports.org != volatile.debian.org

Greetings
Martin
--
[root@debian /root]# man real-life
No manual entry for real-life

--

[debian-volatile] SA 3.2.3 available (for test purpose)

* Stephen Gran [071105 14:51]:
> This one time, at band camp, Martin Zobel-Helas said:
> > Hi,
> >
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.
>
> Just my point of view - the upgrade from etch's spamassassin to this
> version was easy. The only thing that required manual intervention was
> enabling the various new features.

I agree, I installed this version from backports.org a few months ago,
and it seemed pretty painless.

Micah

--

SA 3.2.3 available (for test purpose)

Stephen Gran writes:

> Just my point of view - the upgrade from etch's spamassassin to this
> version was easy. The only thing that required manual intervention was
> enabling the various new features.

Being a bit impatient, I had installed SA 3.2.1 from lenny on an
otherwise pretty clean etch installation:

bjorn@canardo:~$ apt-cache policy spamassassin
spamassassin:
Installed: 3.2.1-1
Candidate: 3.2.1-1
Package pin: (not found)
Version table:
*** 3.2.1-1 750
650 http://ftp.no.debian.org lenny/main Packages
100 /var/lib/dpkg/status
3.1.7-2 750
700 http://ftp.no.debian.org etch/main Packages

Upgrading from this version to spamassassin 3.2.3-0.volatile1 worked
without any problems, and exactly as I expected.

bjorn@canardo:~$ apt-cache policy spamassassin
spamassassin:
Installed: 3.2.3-0.volatile1
Candidate: 3.2.3-0.volatile1
Package pin: (not found)
Version table:
*** 3.2.3-0.volatile1 750
100 /var/lib/dpkg/status
3.2.1-1 750
650 http://ftp.no.debian.org lenny/main Packages
3.1.7-2 750
700 http://ftp.no.debian.org etch/main Packages

Just in case anyone cares about that upgrade path...

Thanks a lot for supporting SA 3.2 in volatile!

Bjørn
--
I can't believe how ponderous you are

--

SA 3.2.3 available (for test purpose)

Bjørn Mork writes:

> bjorn@canardo:~$ apt-cache policy spamassassin
> spamassassin:
> Installed: 3.2.3-0.volatile1
> Candidate: 3.2.3-0.volatile1
> Package pin: (not found)
> Version table:
> *** 3.2.3-0.volatile1 750
> 100 /var/lib/dpkg/status
> 3.2.1-1 750
> 650 http://ftp.no.debian.org lenny/main Packages
> 3.1.7-2 750
> 700 http://ftp.no.debian.org etch/main Packages
>
>
> Just in case anyone cares about that upgrade path...

oops, I just read the volatile policy on http://www.debian.org/devel/debian-volatile/
and noticed that this probably violates it:

"The upgrade path from volatile to the next stable release needs to be
at least as easy as for the stable release; version numbers in
volatile must not be higher than those in testing, for instance."

I guess the best would be if there were a SA 3.2.3 release in testing
with a higher version number before introducing it in volatile.

Bjørn
--
Why, it's OK to run down Moonie people

--

SA 3.2.3 available (for test purpose)

Hi,

On Tue Nov 06, 2007 at 15:14:24 +0100, Bjørn Mork wrote:
> Bjørn Mork writes:
>
> > bjorn@canardo:~$ apt-cache policy spamassassin
> > spamassassin:
> > Installed: 3.2.3-0.volatile1
> > Candidate: 3.2.3-0.volatile1
> > Package pin: (not found)
> > Version table:
> > *** 3.2.3-0.volatile1 750
> > 100 /var/lib/dpkg/status
> > 3.2.1-1 750
> > 650 http://ftp.no.debian.org lenny/main Packages
> > 3.1.7-2 750
> > 700 http://ftp.no.debian.org etch/main Packages
> >
> >
> > Just in case anyone cares about that upgrade path...
>
> oops, I just read the volatile policy on http://www.debian.org/devel/debian-volatile/
> and noticed that this probably violates it:
>
> "The upgrade path from volatile to the next stable release needs to be
> at least as easy as for the stable release; version numbers in
> volatile must not be higher than those in testing, for instance."
>
>
> I guess the best would be if there were a SA 3.2.3 release in testing
> with a higher version number before introducing it in volatile.

due to ftp-master being down this has not happened yet. And also two
volatile team members are also release managers, so we are aware of
this. This was one of the reasons why i opened that thread here to fil
the gap between those two things happening.

Greetings
Martin
--
[root@debian /root]# man real-life
No manual entry for real-life

--

[debian-volatile] SA 3.2.3 available (for test purpose)

This one time, at band camp, Martin Zobel-Helas said:
> Hi,
>
> spamassassin 3.2.3-0.volatile1 is currently available in
> etch-proposed/volatile. Before we accept it to etch/volatile i would
> like to ask some experienced SysAdmins to do some (more extended testing
> as we did) of the package and report back any problems you find to
> .
>
> As soon as we are convinced that SA 3.2.3 works as expected i will
> move the package to etch/volatile and send an official announcement.

Just my point of view - the upgrade from etch's spamassassin to this
version was easy. The only thing that required manual intervention was
enabling the various new features.
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------

[debian-volatile] SA 3.2.3 available (for test purpose)

On Mon, 05 Nov 2007, Martin Zobel-Helas wrote:
> spamassassin 3.2.3-0.volatile1 is currently available in
> etch-proposed/volatile. Before we accept it to etch/volatile i would
> like to ask some experienced SysAdmins to do some (more extended testing
> as we did) of the package and report back any problems you find to
> .
>
> As soon as we are convinced that SA 3.2.3 works as expected i will
> move the package to etch/volatile and send an official announcement.

I wonder if spamassassin is volatile material? It certainly fits
backports.org (and I use the backport on production), but I have always
thought of volatile as something with exactly the same importance and
connotation as main.

Which means that, should a volatile spamassassin upgrade change ABIs, we
would also need to update amavisd-new, and anything else that links directly
to spamassassin perl modules...

It would feel weird to have amavisd-new in volatile. And it would be
extremely wrong to have anything in volatile *break* it and NOT have an
updated one available in volatile, so we would have to, should it happen.
The same is valid for any other package.

IMO, it is best to leave stuff like spamassassin out of volatile.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh

--

[debian-volatile] SA 3.2.3 available (for test purpose)

Hi,

On Tue Nov 06, 2007 at 08:30:46 +0000, Keith Edmunds wrote:
> On Mon, 5 Nov 2007 23:02:01 +0100, said:
>
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile.
>
> What's the repository URL for etch-proposed/volatile? I just Googled
> "etch-proposed/volatile" and got two hits, both of which were this
> announcement. I modified my existing source from etch/volatile to
> etch-proposed/volatile and got a 404. So, I'm happy to test it, but I need
> to know where to find it.

http://volatile.debian.org/debian-volatile/pool/volatile/main/s/spamassassin/spamassassin_3.2.3-0.volatile1_all.deb

--
[root@debian /root]# man real-life
No manual entry for real-life

--

[debian-volatile] SA 3.2.3 available (for test purpose)

On Tue, 2007-11-06 at 09:48 -0200, Henrique de Moraes Holschuh wrote:
> On Mon, 05 Nov 2007, Martin Zobel-Helas wrote:
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.
>
> I wonder if spamassassin is volatile material? It certainly fits
> backports.org (and I use the backport on production), but I have always
> thought of volatile as something with exactly the same importance and
> connotation as main.
>
> Which means that, should a volatile spamassassin upgrade change ABIs, we
> would also need to update amavisd-new, and anything else that links directly
> to spamassassin perl modules...
>
> It would feel weird to have amavisd-new in volatile.

I don't have strong feelings about it but amavisd-new is the one package
that I have always hoped to find in volatile.
but that's probably just because that would scratch MY itch.

> And it would be
> extremely wrong to have anything in volatile *break* it and NOT have an
> updated one available in volatile, so we would have to, should it happen.
> The same is valid for any other package.
>
> IMO, it is best to leave stuff like spamassassin out of volatile.
>
> --
> "One disk to rule them all, One disk to find them. One disk to bring
> them all and in the darkness grind them. In the Land of Redmond
> where the shadows lie." -- The Silicon Valley Tarot
> Henrique Holschuh
>

tinus

--

[debian-volatile] SA 3.2.3 available (for test purpose)

> On Mon, 05 Nov 2007, Martin Zobel-Helas wrote:
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.

On 06.11.07 09:48, Henrique de Moraes Holschuh wrote:
> I wonder if spamassassin is volatile material? It certainly fits
> backports.org (and I use the backport on production), but I have always
> thought of volatile as something with exactly the same importance and
> connotation as main.

Imho, SA fulfills the requirements for volatile without any problem. The
backports are here afaik for different reason.

> IMO, it is best to leave stuff like spamassassin out of volatile.

I disagree here.

--
Matus UHLAR - fantomas, ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95

--

SA 3.2.3 available (for test purpose)

Matus UHLAR - fantomas writes:
> On 06.11.07 09:48, Henrique de Moraes Holschuh wrote:
>> I wonder if spamassassin is volatile material? It certainly fits
>> backports.org (and I use the backport on production), but I have always
>> thought of volatile as something with exactly the same importance and
>> connotation as main.
>
> Imho, SA fulfills the requirements for volatile without any problem. The
> backports are here afaik for different reason.
>
>> IMO, it is best to leave stuff like spamassassin out of volatile.
>
> I disagree here.

AOL. spamassassin is one of the very few packages that needs to be
updated to _keep_ its functionality between stable releases, since spam
filtering rules lose their effect in time, and new rules often need new
software modules.

IMHO, this is exactly what volatile is for.

Bjørn
--
You're probably Moonie yourself

--

SA 3.2.3 available (for test purpose)

Matus UHLAR - fantomas writes:
> On 06.11.07 09:48, Henrique de Moraes Holschuh wrote:
>> I wonder if spamassassin is volatile material? It certainly fits
>> backports.org (and I use the backport on production), but I have always
>> thought of volatile as something with exactly the same importance and
>> connotation as main.
>
> Imho, SA fulfills the requirements for volatile without any problem. The
> backports are here afaik for different reason.
>
>> IMO, it is best to leave stuff like spamassassin out of volatile.
>
> I disagree here.

AOL. spamassassin is one of the very few packages that needs to be
updated to _keep_ its functionality between stable releases, since spam
filtering rules lose their effect in time, and new rules often need new
software modules.

IMHO, this is exactly what volatile is for.

Bjørn
--
You're probably Moonie yourself

--

[debian-volatile] SA 3.2.3 available (for test purpose)

> On Mon, 05 Nov 2007, Martin Zobel-Helas wrote:
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.

On 06.11.07 09:48, Henrique de Moraes Holschuh wrote:
> I wonder if spamassassin is volatile material? It certainly fits
> backports.org (and I use the backport on production), but I have always
> thought of volatile as something with exactly the same importance and
> connotation as main.

Imho, SA fulfills the requirements for volatile without any problem. The
backports are here afaik for different reason.

> IMO, it is best to leave stuff like spamassassin out of volatile.

I disagree here.

--
Matus UHLAR - fantomas, ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95

--

[debian-volatile] SA 3.2.3 available (for test purpose)

On Mon, 05 Nov 2007, Martin Zobel-Helas wrote:
> spamassassin 3.2.3-0.volatile1 is currently available in
> etch-proposed/volatile. Before we accept it to etch/volatile i would
> like to ask some experienced SysAdmins to do some (more extended testing
> as we did) of the package and report back any problems you find to
> .
>
> As soon as we are convinced that SA 3.2.3 works as expected i will
> move the package to etch/volatile and send an official announcement.

I wonder if spamassassin is volatile material? It certainly fits
backports.org (and I use the backport on production), but I have always
thought of volatile as something with exactly the same importance and
connotation as main.

Which means that, should a volatile spamassassin upgrade change ABIs, we
would also need to update amavisd-new, and anything else that links directly
to spamassassin perl modules...

It would feel weird to have amavisd-new in volatile. And it would be
extremely wrong to have anything in volatile *break* it and NOT have an
updated one available in volatile, so we would have to, should it happen.
The same is valid for any other package.

IMO, it is best to leave stuff like spamassassin out of volatile.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh

--

[debian-volatile] SA 3.2.3 available (for test purpose)

On 05.11.07 23:02, Martin Zobel-Helas wrote:
> spamassassin 3.2.3-0.volatile1 is currently available in
> etch-proposed/volatile. Before we accept it to etch/volatile i would
> like to ask some experienced SysAdmins to do some (more extended testing
> as we did) of the package and report back any problems you find to
> .
>
> As soon as we are convinced that SA 3.2.3 works as expected i will
> move the package to etch/volatile and send an official announcement.

is there any plan to push that into sarge volatile?

--
Matus UHLAR - fantomas, ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux is like a teepee: no Windows, no Gates and an apache inside...

--

[debian-volatile] SA 3.2.3 available (for test purpose)

This one time, at band camp, Matus UHLAR - fantomas said:
> On 05.11.07 23:02, Martin Zobel-Helas wrote:
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.
>
> is there any plan to push that into sarge volatile?

Not from my point of view. The versioned dependency tree is just too
large for me to feel comfortable that it won't break other things on
sarge. I'm not thrilled (I still have a sarge machine that does some
mail), but I think it's the right move from the perspective of the
volatile archive and it's impact on main. That's not to say some
interested person couldn't do an upload to backports.org or something
where the rules are a little laxer.
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------

[debian-volatile] SA 3.2.3 available (for test purpose)

This one time, at band camp, Matus UHLAR - fantomas said:
> On 05.11.07 23:02, Martin Zobel-Helas wrote:
> > spamassassin 3.2.3-0.volatile1 is currently available in
> > etch-proposed/volatile. Before we accept it to etch/volatile i would
> > like to ask some experienced SysAdmins to do some (more extended testing
> > as we did) of the package and report back any problems you find to
> > .
> >
> > As soon as we are convinced that SA 3.2.3 works as expected i will
> > move the package to etch/volatile and send an official announcement.
>
> is there any plan to push that into sarge volatile?

Not from my point of view. The versioned dependency tree is just too
large for me to feel comfortable that it won't break other things on
sarge. I'm not thrilled (I still have a sarge machine that does some
mail), but I think it's the right move from the perspective of the
volatile archive and it's impact on main. That's not to say some
interested person couldn't do an upload to backports.org or something
where the rules are a little laxer.
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------

[debian-volatile] SA 3.2.3 available (for test purpose)

On 05.11.07 23:02, Martin Zobel-Helas wrote:
> spamassassin 3.2.3-0.volatile1 is currently available in
> etch-proposed/volatile. Before we accept it to etch/volatile i would
> like to ask some experienced SysAdmins to do some (more extended testing
> as we did) of the package and report back any problems you find to
> .
>
> As soon as we are convinced that SA 3.2.3 works as expected i will
> move the package to etch/volatile and send an official announcement.

is there any plan to push that into sarge volatile?

--
Matus UHLAR - fantomas, ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux is like a teepee: no Windows, no Gates and an apache inside...

--

Syndicate content