[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Security updated versions in sid and amd64



Dear release team,

please consider binNMUing the packages (list below) for amd64 to avoid
different packages with the same version to exists on the debian
archives.


Hi,

as you might know amd64 has been added to the Debian archive. For this
Ftp-Master insisted on rebuilding every package of the archive. This
isn't such a bad idea but has some side effects.

One of those is that packages with a security update that have no
newer version in sid will be rebuild. Their version and filename will
match the packages on security.debian.org but their md5sums will
differ from the security announcements. This is anoying for anyone
doing security checks, breaks merging mirrors into a single repository
(like reprepro can do) and can cause apt-get to reinstall the package
on every single upgrade/dist-upgrade.

Since 3 of them are already rebuild and in the archive it is probably
impossible to import the old security builds instead even if we could
convince Ftp-Master to allow them in. So there are 2 solutions left
for this problem:

1) upload a new source (or NMU it)
2) binNMU the package

If you are aware of problems with binNMUing your package, e.g. a
strict versioned depends on a arch:all package of the same source,
please let the release team know about them and prepare a new source
upload asap.

In detail the following packages are affected:

antiword 0.35-2sarge1
graphviz 2.2.1-1sarge1 
gtkdiskfree 1.9.3-4sarge1 
ilohamail 0.8.14-0rc3sarge1 
ketm 0.0.6-17sarge1 
lynx 2.8.5-2sarge1 
mysql-dfsg 4.0.24-10sarge1 
replicator 3.1-sarge-1.5 
weex 2.6.1-6sarge1 

Thanks,
        Goswin



Reply to: