Hi Christian, On Tue, May 03, 2005 at 11:16:04PM +0200, Christian Hammers wrote: > As suggested by todays freeze announcement (juhuu!) I hereby tell you of an > uploaded a bugfix for Quagga to t-p-u as unstable will get the new upstream > release 0.99.1 tomorrow which may or may not be suiteable but is at least > not important for Sarge. > quagga (0.98.3-6) testing-proposed-updates; urgency=high > * Removed "Recommends kernel-image-2.4" as aptitude then > installes a kernel-image for an arbitrary architecture as long > as it fullfill that recommendation which can obviously fatal > at the next reboot :) Also it is a violation of the policy > which mandates a reference to real packages (thanks to Holger Levsen). > Closes: #307281 > $ interdiff -z quagga_0.98.3-5.diff.gz quagga_0.98.3-6.diff.gz | diffstat > changelog | 11 +++++++++++ > control | 1 - > 2 files changed, 11 insertions(+), 1 deletion(-) $ cat queue/reject/quagga_0.98.3-6_i386.reason Rejected: quagga-doc_0.98.3-6_all.deb: old version (0.98.3-5) in unstable <= new version (0.98.3-6) targeted at testing-proposed-updates. Rejected: quagga_0.98.3-6_i386.deb: old version (0.98.3-5) in unstable <= new version (0.98.3-6) targeted at testing-proposed-updates. Rejected: quagga_0.98.3-6.dsc: old version (0.98.3-5) in unstable <= new version (0.98.3-6) targeted at testing-proposed-updates. $ As you can see, if you have different versions of the package in testing and unstable, the version uploaded to t-p-u must have a version number >> testing and << unstable. Perhaps it would be easier to hold off on uploading 0.99.1 for a few more days, and let 0.98.3-6 get in through unstable? Thanks, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature