On Sunday 17 February 2008 17:22, Raphael Geissert wrote: > Scott Kitterman wrote: > > On Sunday 17 February 2008 15:41, Raphael Geissert wrote: > >> Please note that this situation often occurs when the maintainer didn't > >> make the watch file strip some +VCSrevNNNNN that was added to the Debian > >> Version. > >> > >> If nobody objects I'll start filling (in an automated way since there > >> are no false positives) reports on the 307 source packages which report > >> a Debian upstream version higher than Upstream version by the watch > >> file. > > > > I disagree. You list my package: > > > > Scott Kitterman <[EMAIL PROTECTED]> > > pysubnettree > > > > The reason this package is in the state it's in is that upstream uploaded > > a new version of the package without changing the released version number > > so a > > fake version number was needed. While suboptimal, there is no bug in the > > watch file. > > If Debian's 0.11+1-1 is upstream's 0.11 why not just strip the '+1' using > dversionmangle? > That's in my POV the bug. > I think rewriting watch files for one time events is a mistake. If this were a permanent feature of the version numbering I would agree. I suppose the easiest solution for me to not be bothered about this would be to remove the watch file on the next upload.
Scott K -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
