Adeodato Simó wrote:
> * Martin Schulze [Thu, 06 Jan 2005 16:49:21 +0100]:
>
> > Please
> > . update the package in sid
> > . mention the CVE id from the subject in the changelog
> > . tell me the version number of the fixed package
> > . use priority=high
> > . no need to upload into sarge directly, except the version in
> > sid is not meant to go into testing
>
> I recommend that you don't wait for the unstable package to be
> uploaded, since we need to hold it up until the latest kdebase and
> arts packages are built on all arches (#98 and #88 in the sparc queue,
> #18 and #14 in mipsel, the m68k buildd that picked kdebase is "fast").
I won't wait unless I get a notice.
> Of course, you may want to mail us just before the stable security
> update happens, in case we're ready to go then. Is there an ETA for it
> already?
It depends how fast packages are built on our 11 architectures and
if there are problems. For example, on i386 I just noticed:
Checking kdelibs3_2.2.2-13.woody.13_i386.deb against stable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Files in second .deb but not in first
-------------------------------------
/usr/lib/libgmcop.la
/usr/lib/libgmcop.so
/usr/lib/libgmcop.so.0
/usr/lib/libgmcop.so.0.0.0
I have no idea where this library comes from.
Regards,
Joey
--
There are lies, statistics and benchmarks.
Please always Cc to me when replying to me on the lists.
