Bug#818382: tracker.debian.org: False positive: "Problems while searching for new upstream version"
Package: tracker.debian.org Followup-For: Bug #818382 The problem reported in this bug seems to be particularly prevalent for upstream sources hosted on github.com. I imagine there's a temporary access problem at the time UDD tries to connect. If that's the case can it be marked to try again after say 5 minutes rather than waiting a whole day or week? Packages just in my list currently affected: golang-github-anacrolix-dms golang-github-anacrolix-ffprobe golang-github-anacrolix-missinggo golang-github-huandu-xstrings packmol pytest-mpi python-bumps python-dmsh python-periodictable python-pypathlib qutip sasview sphinx-click superlu-dist apbs armci-mpi avogadro golang-github-azure-azure-pipeline-go golang-github-roaringbitmap-roaring hypre pyfftw scalapack xhtml2pdf All on github.com. Curiously avogadrolibs is fine, hosted by the same github user as avogadro. Can UDD uscan access to github.com be made more robust? Not clear from this bug, is there already a patch available to help with the problem? Drew
Bug#818382: tracker.debian.org: False positive: "Problems while searching for new upstream version"
Package: tracker.debian.org Severity: normal Hi, For at least some packages, there's a consistent false positive when running uscan (e.g. https://tracker.debian.org/pkg/s3ql): | uscan had problems while searching for a new upstream version: | No upstream tarball downloaded. No further processing with mk_origtargz As far as I can tell, uscan didn't actually have any problems here. Best, -Nikolaus
Bug#818382: tracker.debian.org: False positive: "Problems while searching for new upstream version"
On Thu, Mar 17, 2016 at 09:37:57AM +0100, Raphael Hertzog wrote: > Osamu, can fix this too? Just to be sure, I tested for other versions: devscripts 2.16.1: $ uscan --dehs --report 2>/dev/null s3ql 2.15+dfsg 2.15+dfsg 2.17.1+dfsg https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.17.1.tar.bz2 newer package available Not downloading upstream package: s3ql-2.17.1.tar.bz2 Looks good for me. devscripts 2.15.10: $ uscan --dehs --report 2>/dev/null s3ql 2.15+dfsg 2.15+dfsg 2.17.1+dfsg https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.17.1.tar.bz2 newer package available Successfully downloaded package s3ql-2.17.1.tar.bz2 SKIP Checking OpenPGP signature (by request). This is problematic. --report downloads package
Bug#818382: tracker.debian.org: False positive: "Problems while searching for new upstream version"
Hi, On Thu, Mar 17, 2016 at 09:37:57AM +0100, Raphael Hertzog wrote: > Hi, > > On Wed, 16 Mar 2016, Nikolaus Rath wrote: > > For at least some packages, there's a consistent false positive when > > running uscan (e.g. https://tracker.debian.org/pkg/s3ql): > > > > | uscan had problems while searching for a new upstream version: > > | No upstream tarball downloaded. No further processing with mk_origtargz > > > > As far as I can tell, uscan didn't actually have any problems here. > > We get the data from UDD which gets it from uscan itself via "uscan > --dehs". > > uscan had major changes recently... see https://bugs.debian.org/815980 > for some of the recent issues. > > This warning can be useful when you use uscan interactively but it really > should not be displayed with --dehs. Yes we don't want to download > anything, it's normal... all --dehs output goes to STDOUT all other output including verbose output goes to STDERR if --dehs is used. So use 2>/dev/null. Having verbose output available for -dehs is really good for debug etc. In script, invoke uscan with 2>/dev/null I have already killed almost all verbose output in VCS. So default output is readuced much more for VCS stable-bpo 2.16.1~bpo8+1 testing 2.16.1 These did not address all the regressions caused by the major changes happened at 2.15.10 > Osamu, can fix this too? PENDING FIXES are [ Osamu Aoki ] * uscan: + Print proper warnings for bad rules. Closes: #814049 + Fix glitches around rules such as "s<...> <...>g" and add their tests. + Reactivate --no-verbose mode. Closes: #815645 + Fix --destdir for version 4. Closes:#814686 + Always use uscan_warn and uscan_die. + Die if the action script fails. Closes: #810976 For --dehs, "Always use uscan_warn and uscan_die" is important. I guess we need to wait for James McCoy to upload new version. As for the current VCS code: $ uscan --dehs --report 2>/dev/null s3ql 2.15+dfsg 2.15+dfsg 2.17.1+dfsg https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.17.1.tar.bz2 newer package available Not downloading upstream package: s3ql-2.17.1.tar.bz2 Status report good. No warnings to indicate there were no scanning errors. So I see no problerm. Osamu
Bug#818382: tracker.debian.org: False positive: "Problems while searching for new upstream version"
Hi, On Wed, 16 Mar 2016, Nikolaus Rath wrote: > For at least some packages, there's a consistent false positive when > running uscan (e.g. https://tracker.debian.org/pkg/s3ql): > > | uscan had problems while searching for a new upstream version: > | No upstream tarball downloaded. No further processing with mk_origtargz > > As far as I can tell, uscan didn't actually have any problems here. We get the data from UDD which gets it from uscan itself via "uscan --dehs". uscan had major changes recently... see https://bugs.debian.org/815980 for some of the recent issues. This warning can be useful when you use uscan interactively but it really should not be displayed with --dehs. Yes we don't want to download anything, it's normal... Osamu, can fix this too? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
