On Sun, Apr 12, 2009 at 12:16:24PM -0500, Raphael Geissert wrote: > Jan Hauke Rahm wrote: > [...] > > > > And if a proper string comparison will pe possible some time it should > > still warn about a policy version which is too high. If I upload a > > package now with standards-version 4.0.0 the PTS should definitely warn > > about it, too, imho (and not simply suggest a downgrade of course :)). > > Already checked by lintian: > > E: asedriveiiie source: invalid-standards-version 3.6.3 > W: csound-doc source: timewarp-standards-version (2004-01-26 < 2008-06-04) ...which implies that people always check their packages properly.[1] But as Dato already correctly pointed out, PTS is not the right place for checks like that. My point was just that *if* there is any "complex" version comparison *then* it should also deal with timewarp-standards-versions. [1] People building packages in a chroot and checking them with lintian from testing (or even ubuntu) would see that 3.7.3 is outdated and they should update to 3.8.0. Then they remember some mail on d-d-a but don't remember the version... was it 3.8.1 or 3.9.0? ah, wth I just take 3.9.0. Sure, this is a bad mistake but people... :)
Attachment:
signature.asc
Description: Digital signature