Hi, Guillem Jover wrote: > On Mon, 2015-08-24 at 11:00:18 +0300, Riku Voipio wrote: > > These obsolete urls are already checked with duck[1][2]. I > > think what would make sense would be to make lintian recommend > > duck. Then lintian can run duck if it has been installed. > > I was aware of duck, but as stated by Jakub, that is a non-option for > lintian. In addition many of these URLs are (or were at the time) > still reachable, but might disappear in the near future, and we know > beforehand that they are obsolete, so I think they are really good > candidates for a lintian check, because the just require a string > match instead of a network check.
Yep, one more for which I filed a bug report (#797815) today: freshmeat.net / freecode.com I'll think about such a test for working but known to be legacy URLs. What about the tag name "legacy-url-in-packaging"? Or rather "obsolete-url-in-packaging"? Niels: Which existing check would be best to add such a check? I'd check at least debian/control, debian/copyright, debian/watch, and debian/upstream/metadata (plus variants). Maybe fields.pm? debian/copyright doesn't necessarily need to have fields (i.e. if not in DEP5 format) and debian/watch doesn't have fields either... Maybe split up the test using the same data file (I'd name it data/*/obsolete-sites) and then using it in fields.pm, watch-file.pm and copyright-file.pm separately? But where to check debian/upstream/metadata and friends then? So far my data file looks like this: ---8<--- # Known obsolete websites / hosters who closed down or have frozen # content, one hostname per line. Subdomains will be matched, too. code.google.com gitorious.org codehaus.org freshmeat.net freecode.com --->8--- Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE