[Pkg-dspam-misc] DSPAM packages

[Julien Valroff]

Le dimanche 18 juil. 2010 à 15:04:27 (+0200), Matthijs Möhlmann a écrit :
> Date: Sun, 18 Jul 2010 15:04:27 +0200
> From: Matthijs Möhlmann <matthijs at cacholong.nl>
> To: julien at kirya.net
> CC: pkg-dspam-misc at lists.alioth.debian.org
> Subject: Re: [Pkg-dspam-misc] DSPAM packages
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 07/18/2010 02:42 PM, Julien Valroff wrote:
> > Le dimanche 18 juil. 2010 à 11:43:01 (+0200), Matthijs Möhlmann a écrit :
> >> Date: Sun, 18 Jul 2010 11:43:01 +0200
> >> From: Matthijs Möhlmann <matthijs at cacholong.nl>
> >> To: pkg-dspam-misc at lists.alioth.debian.org
> >> Subject: Re: [Pkg-dspam-misc] DSPAM packages
> >>
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> On 07/17/2010 08:34 AM, Julien Valroff wrote:
> >>> Hi,
> >>>
> >>> The 3.9.1 release is being prepared upstream, it should be released in
> >>> August or September if no major bug is found in the meantime. I would
> >>> like to see this version uploaded to experimental as soon as it is
> >>> released. I am hence extensively testing the packages in the
> >>> experimental branch in our svn repo. I would appreciate if someone could
> >>> review them in the meantime.
> >>> Also, I would like to test them with piuparts, to avoid any major issue
> >>> when users will upgrade from the old 3.6.8 still in unstable - any hint
> >>> on how to run these tests with such a large bunch of packages?
> >>>
> >>> The packages are also tested by various users, as they are publicly
> >>> available in my personal repository (it seems most Debian users get
> >>> these packages sooner or later, as upstream even recommend using them
> >>> instead of the outdated official packages).
> >>>
> >>> Kurt also stated he was working on getting RC bugs fixed in the 3.6.8
> >>> version. Any news on this? If nothing happens, don't you think 3.9.1
> >>> could be directly uploaded to unstable?
> >>>
> >>> Cheers,
> >>> Julien
> >>>
> >>
> >> Hello Julien,
> > 
> > Hi Matthijs,
> > 
> >> Good to hear that 3.9.1 is being prepared. The current version in the
> >> trunk is at this moment 3.6.8 ?
> >>
> >> Is there any reason not to update the trunk instead of
> >> branches/experimental ?
> > 
> > Kurt was (is?) working on fixing RC bugs in the old 3.6.8 in trunk, I didn't
> > want to interfer with his work.
> > 
> > I had understood the plan was to upload a fixed 3.6.8 to unstable, while the 3.9
> > series would be uploaded to experimental at first.
> > 
> 
> I see several pending bugs in the bugtracker, Kurt can you explain if we
> need to upload 3.6.8 to fix the RC bugs or that we should upload 3.9.1
> straight away ?
> 
> >> If you can update to the current version you
> >> have in the experimental branch I'm willing to upload them.
> > 
> > I'll give it a try, though I'm more comfortable with git.
> > 
> > Does anybody has any objection?
> > 
> 
> Ah well, it can also be first uploaded to experimental so it can get
> tested by more people. But I was in the understanding that an upload was
> needed.

I think I have tagged most of these bugs, thinking the packages would be uploaded...
 
> Which branch is the 'latest and greatest' ? branches/development?

I have removed development, experimental is the latest source, tested with current
upstream GIT which is 3.9.1 RC1 (not yet published).

> Then I'll go and will do some testing.

Thanks, that would help a lot, as I still do not understand why there are so many 
conflicts. trunk hasn't been modified since I have created the branch, the contents 
should simply been replaced.

Cheers,
Julien

-- 
Julien Valroff <julien at kirya.net>
http://www.kirya.net
GPG key: 4096R/290D20C5 
092F 4CB5 5F19 E006 1CFD  B489 D32B 8D66 290D 20C5