Bug#211660: don't add stricter checks short before release
tag 211660 -moreinfo
submitter 211660 email@example.com
* Adam Heath (firstname.lastname@example.org) [030919 18:21]:
> On Fri, 19 Sep 2003, Andreas Barth wrote:
> > 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).
> What package has that, so that I can use it to test?
You can test that with any package that use versioned dependencies.
However, my example is netpbm-free, and that failed autobuilding on
m68k because of this. (Note that I'm also doing an upload with one
more space, as I think it's really nicer to read - but there are other
packages out with the very same problem.)
> > 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.
> It's not a policy violation. It's just a normal bug in dpkg, that happens to
> affect other packages.
It _is_ a policy violation, because this programm fails for other
policy conforming programms on the interface that's described in
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C