Your message dated Wed, 17 Aug 2011 14:20:14 +0200 with message-id <4E4BB1FE.60403@debian.org> and subject line Closing has caused the Debian Bug report #635593, regarding qa.debian.org: PTS shows incorrect latest upstream version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 635593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635593 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: qa.debian.org: PTS shows incorrect latest upstream version
- From: Ben Finney <ben+debian@benfinney.id.au>
- Date: Wed, 27 Jul 2011 21:14:59 +1000
- Message-id: <8739hs5618.fsf@benfinney.id.au>
Package: qa.debian.org Severity: normal The ‘python-coverage’ package has a ‘debian/watch’ file. This configuration allows ‘uscan’ to correctly report the latest upstream version: ===== $ uscan --verbose --report -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: opts="uversionmangle=s/(\d)([a-z]\d+)$/$1~$2/" http://pypi.python.org/packages/source/c/coverage/coverage-(.+).tar.gz -- Found the following matching hrefs: coverage-3.0.1.tar.gz coverage-3.0.tar.gz coverage-3.0b3.tar.gz coverage-3.1.tar.gz coverage-3.1b1.tar.gz coverage-3.2.tar.gz coverage-3.2b1.tar.gz coverage-3.2b2.tar.gz coverage-3.2b3.tar.gz coverage-3.2b4.tar.gz coverage-3.3.1.tar.gz coverage-3.3.tar.gz coverage-3.4.tar.gz coverage-3.4b1.tar.gz coverage-3.4b2.tar.gz coverage-3.5.tar.gz coverage-3.5b1.tar.gz Newest version on remote site is 3.5, local version is 3.4 => coverage-3.5.tar.gz already in package directory -- Scan finished ===== The PTS page <URL:http://packages.qa.debian.org/p/python-coverage.html> disagrees though: ===== A new upstream version is available: 3.5~b1, you should consider packaging it. ===== The PTS is evidently using the watch file's version mangling (that's how the ‘~’ is introduced), but is comparing the resulting version string incorrectly and coming up with a wrong value for the latest version. The correct “new upstream version” at this point in time is not “3.5~b1” but instead is “3.5”, as correctly determined by ‘uscan’. The PTS should use the same comparison algorithm in order to get the same result. -- \ “Nullius in verba” (“Take no-one's word for it”) —motto of the | `\ Royal Society, since 1663-06-30 | _o__) | Ben Finney <ben@benfinney.id.au>
--- End Message ---
--- Begin Message ---
- To: 635593-done@bugs.debian.org
- Subject: Closing
- From: Giovanni Mascellani <gio@debian.org>
- Date: Wed, 17 Aug 2011 14:20:14 +0200
- Message-id: <4E4BB1FE.60403@debian.org>
This bug appears to be fixed, since now the PTS says last version is 3.5, as determined by uscan (version 3.5b1 is still available on the repository anyway, so this is not an apparent fix caused by a disappeared beta version). If you still experience the problem, please reopen the bug. Giovanni. -- Giovanni Mascellani <mascellani@poisson.phc.unipi.it> Pisa, Italy Web: http://poisson.phc.unipi.it/~mascellani Jabber: g.mascellani@jabber.org / giovanni@elabor.homelinux.orgAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---