Re: Some fixed warnings still showing up on lintian.d.o
Quoting Russ Allbery ([EMAIL PROTECTED]): Rather than try to poke at it too much, I've just updated lintian to the latest version on lintian.d.o and started a full archive run. It should be fixed (with various other improvements in the reports) by sometime tomorrow. Well: http://lintian.debian.org/ Forbidden You don't have permission to access / on this server. Apache/1.3.33 Server at lintian.debian.org Port 80 http://lintian.debian.org/reports/Tdebian-changelog-file-uses-obsolete-national-encoding.html Not Found The requested URL /reports/Tdebian-changelog-file-uses-obsolete-national-encoding.html was not found on this server. Apache/1.3.33 Server at lintian.debian.org Port 80 I'm afraid somethign is b0rken somewhere:) signature.asc Description: Digital signature
Re: Some fixed warnings still showing up on lintian.d.o
Quoting Russ Allbery ([EMAIL PROTECTED]): Forbidden You don't have permission to access / on this server. Apache/1.3.33 Server at lintian.debian.org Port 80 This works correctly now that the scan of the archive is finished. OK, I was suspecting something like that but I didn't imagine this would take so long..:-) http://lintian.debian.org/reports/Tdebian-changelog-file-uses-obsolete-national-encoding.html This will work correctly as soon as the Apache server on gluck is restarted to pick up the redirect. The new canonical URL is: http://lintian.debian.org/reports/tags/debian-changelog-file-uses-obsolete-national-encoding.html Clicking on the package will show the package's full lintian report and the package version, which reveals that, for example, xcin2.3 is version 2.3.04.3-3.1, indicating that lintian.d.o hasn't seen your update yet. And that: gluck:/org/ftp.debian.org/ftp/project/trace cat ftp-master.debian.org Wed Feb 13 08:00:02 UTC 2008 is because the archive on gluck hasn't been updated since you uploaded your package. Why that might be, I have no idea. Hmmm, that actually explains why lintian.d.o sometimes reports that it didn't see any change from one day to anotherwhich I noticed while working on this. So, I now have to find out what updates the archive on gluck and nag some people about this to happen on a regular basis. signature.asc Description: Digital signature
Re: Some fixed warnings still showing up on lintian.d.o
Christian Perrier [EMAIL PROTECTED] writes: Quoting Russ Allbery ([EMAIL PROTECTED]): Forbidden You don't have permission to access / on this server. Apache/1.3.33 Server at lintian.debian.org Port 80 This works correctly now that the scan of the archive is finished. OK, I was suspecting something like that but I didn't imagine this would take so long..:-) The old web pages would have been available while it worked, if I hadn't screwed up. Or if I'd thought to regenerate them while lintian chugged away (although by the time I realized I'd accidentally deleted the pages, it was mostly done). Sorry about that. It takes about a day and a half for poor gluck to make it all the way through the i386 archive. Hmmm, that actually explains why lintian.d.o sometimes reports that it didn't see any change from one day to anotherwhich I noticed while working on this. So, I now have to find out what updates the archive on gluck and nag some people about this to happen on a regular basis. I should similarly figure out how to request that Apache be reloaded, since apparently just using an .htaccess file for the redirect of the tags URLs (which I thought would work) doesn't. The new version of lintian now installed on lintian.d.o will at least tell you what version of the package it checked if you go to the maintainer page, which helps a lot in figuring out what's going on with this sort of thing. It will also tell you if anyone is overriding a tag. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some fixed warnings still showing up on lintian.d.o
Christian Perrier [EMAIL PROTECTED] writes: Quoting Russ Allbery ([EMAIL PROTECTED]): Rather than try to poke at it too much, I've just updated lintian to the latest version on lintian.d.o and started a full archive run. It should be fixed (with various other improvements in the reports) by sometime tomorrow. Well: http://lintian.debian.org/ Forbidden You don't have permission to access / on this server. Apache/1.3.33 Server at lintian.debian.org Port 80 This works correctly now that the scan of the archive is finished. http://lintian.debian.org/reports/Tdebian-changelog-file-uses-obsolete-national-encoding.html This will work correctly as soon as the Apache server on gluck is restarted to pick up the redirect. The new canonical URL is: http://lintian.debian.org/reports/tags/debian-changelog-file-uses-obsolete-national-encoding.html Clicking on the package will show the package's full lintian report and the package version, which reveals that, for example, xcin2.3 is version 2.3.04.3-3.1, indicating that lintian.d.o hasn't seen your update yet. And that: gluck:/org/ftp.debian.org/ftp/project/trace cat ftp-master.debian.org Wed Feb 13 08:00:02 UTC 2008 is because the archive on gluck hasn't been updated since you uploaded your package. Why that might be, I have no idea. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some fixed warnings still showing up on lintian.d.o
Christian Perrier [EMAIL PROTECTED] writes: Hell dear lintian maintainer(s), I'm currently working to fix debian-changelog-file-uses-obsolete-national-encoding. (a lenny release goal) My work tool is, among others, the http://lintian.debian.org/reports/Tdebian-changelog-file-uses-obsolete-national-encoding.html page I recently NMU'ed several packages but some of them still shown up on the page, namely slashem and xcin2.3 Is there a reason for this which I would be unaware of? It looks like a lintian problem. It's not picking up the latest versions of those packages for some reason. I think something went wrong with the lintian runs a few days back. Rather than try to poke at it too much, I've just updated lintian to the latest version on lintian.d.o and started a full archive run. It should be fixed (with various other improvements in the reports) by sometime tomorrow. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
