On Thu, July 3, 2008 15:48, Frank Lichtenheld wrote: > On Thu, Jul 03, 2008 at 12:57:18PM +0200, Thijs Kinkhorst wrote: > >> On Tue, July 1, 2008 00:00, Frank Lichtenheld wrote: >> >>> Hmm, I can understand that some people don't want to see the >>> experimental changelog, and to fix that at some point might be nice, I >>> really don't see why you wouldn't want to have the newest version from >>> stable/testing/unstable? >> >> The PTS currently links to the changelog named "current": >> http://packages.debian.org/changelogs/pool/main/p/phpmyadmin/current/cha >> ngelog >> >> Which changelog would you expect to see when you click on that link >> from the PTS page? I would not expect to get the changelog for 'stable' >> then. > > No, but I also would not expect the stable version to be ever greater > than the unstable version. So maybe two broken assumptions together give a > valid one again ;)
Maybe I misunderstand you, but I'm not talking about a situation where the stable version is greater than the unstable version. I'm talking about the common situation where a package in stable is newer (of a more recent date) than the unstable one. Example: I have a package a which has a new upstream 1.2 that fixes a security issue. On the 1st of June I upload 1.2-1 to unstable. The 'current' changelog is now the changelog for 1.2-1. Stable has 0.9-2. On the 7th of June I upload version 0.9-2+etch1 to stable. The 'current' changelog is now the one from 0.9-2+etch1. > On a more serious note, I think the right solution is > to make the canonical changelog link something like > packages.debian.org/<suite>/<pkg>/changelog This is shorter and less > ambigous. Yes, that sounds like a good idea. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
