On Wed, Dec 21, 2011 at 09:39:20PM +0100, Philipp Kern wrote: > Pierre, > > am Wed, Dec 21, 2011 at 07:14:36PM +0100 hast du folgendes geschrieben: > > It's a bug that isn't "fixed" by any package because it was a bogus > > upload in experimental, that is fixed because the 3.7.0 has been > > rerolled. It's transient, and doesn't warrant a Close in the 3.7.0 > > changelog that doesn't even "come" from the same git branch at all. It > > made no sense. (when I rolled the snapshot tarball for experimental I > > ran autoconf without the --copy flag and it had symlinks instead of > > copies of the autocrap stuff). > > ok, if the new upload doesn't have the old experimental changelog in > it, it won't be affecting experimental anymore anyway and you could > indeed just close it, but… > > > I've closed this bug because it's just spurious, and never existed in > > the unstable branches. > > we're tracking more than unstable in the BTS, though. So I would've > waited until a fixed package hits experimental, I guess.
the experimental package was a pre 3.7.0 release, which has been released and uploaded to unstable, the experimental package will go away and I don't plan any experimental upload for a long time. But okay, next time I'll close from the changelog, I thought it made more sense, it wasn't a lapse, I made it on purpose to avoid cluttering the changelog with orthogonal stuff :) -- ·O· Pierre Habouzit ··O madco...@debian.org OOO http://www.madism.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
