Bug#211660: don't add stricter checks short before release
Package: dpkg
Version: 1.10.13
Severity: grave
The last changes to dpkg makes unreleated packages FBFTS (well, as
much unrelated as a package can be to a major toolchain piece), and is
a policy violation.
Generally, it's ok to add stricter checks. But the uploads where on
2003-09-16 and 2003-09-17, both _after_ the last change date for the
toolchain, see
http://lists.debian.org/debian-devel-announce/2003/debian-devel-announce-200308/msg00010.html
How do you expect us to release sarge when introducing FBFTS after the
last minute and without warning on d-d-a? dpkg fails now if there is
no space between the package name and the () for the version (example:
"glibc(>>2.0)" don't work any more).
Also this change is a policy violation. According to policy:
| Whitespace may appear at any point in the version specification
| subject to the rules in Syntax of control files, Section 5.1, and must
| appear where it's necessary to disambiguate; it is not otherwise
| significant.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
Reply to: