On Thu, May 17, 2012 at 08:49:37AM +0900, Charles Plessy wrote: > Hi Andreas, > > Le Wed, May 16, 2012 at 10:18:32AM +0200, Andreas Tille a écrit : > > > > 2012-05-16 10:08:39,177 - WARNING - (120): praat has upstream file but no > > references in UDD > > 2012-05-16 10:08:53,233 - WARNING - (120): mlv-smile has upstream file but > > no references in UDD > > 2012-05-16 10:08:58,503 - WARNING - (120): gbrowse has upstream file but no > > references in UDD > > 2012-05-16 10:09:17,422 - WARNING - (120): abyss has upstream file but no > > references in UDD > > Obsolete VCS URL in the Umegaya database; fixed with the following commands. > > umegaya-adm -p praat -d > curl http://upstream-metadata.debian.net/praat/ping > umegaya-adm -p mlv-smile -d > curl http://upstream-metadata.debian.net/mlv-smile/ping > umegaya-adm -p gbrowse -d > curl http://upstream-metadata.debian.net/gbrowse/ping > umegaya-adm -p abyss -d > curl http://upstream-metadata.debian.net/abyss/ping
I wonder whether there might be a chance to detect this obsoleteness somehow automatically. Currently we have a quite restricted set of packages which can be maintained manually. But once we have more packages this certainly will not scale. I wonder whether it makes sense for Umegaya to inspect VCSes directly. When dealing with the machine-readable files for prospective packages I was able to detect several broken Vcs strings without much trouble. > > 2012-05-16 10:08:48,704 - WARNING - (120): libhmsbeagle has upstream file > > but no references in UDD > > In Umegaya today. > > > > 2012-05-16 10:09:01,685 - WARNING - (120): snap has upstream file but no > > references in UDD > > This package is available in experimental only, and Umegaya depends on > debcheckout > to find the VCS URL, so I added a deb-src line for experimental in > blends.debian.net, Makes sense. > which hosts upstream-metadata.debian.net, and refreshed the URL by simply > deleting the package. > > umegaya-adm -p snap -d > curl http://upstream-metadata.debian.net/snap/ping > > Strangely, upstream-metadata.debian.net does not display information, nor > gives > error message in Apache's log. I need to investigate why. But snap's > upstream > and copyright files are is in the file pool. > > > > 2012-05-16 10:09:17,960 - WARNING - (120): r-bioc-edger has upstream file > > but no references in UDD > > Wrong VCS URL in the source package. I corrected the source package, and > registered the URL by hand in Umegaya. > > umegaya-adm -p r-bioc-edger -d > umegaya-adm -p r-bioc-edger -k YAML-URL -v > git://git.debian.org/debian-med/r-bioc-edger.git > curl http://upstream-metadata.debian.net/r-bioc-edger/ping Seems it might make sense if I stretch the Vcs verification code also to existing packages in the porspective packages investigation. This could be a reasonable QA means. > > 2012-05-16 10:09:19,473 - WARNING - (120): r-cran-genabel has upstream file > > but no references in UDD > > It was never loaded before because our tasks files still refered to its old > name, r-other-genabel (corrected). Thanks for fixing this. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120517071448.gc2...@an3as.eu
