On Sun, 2012-06-03 at 14:56 +0100, Ben Hutchings wrote: > On Sun, 2012-06-03 at 01:50 -0500, Jonathan Nieder wrote: > > Ben Hutchings wrote: > > > > > We would certainly like to do this, but we want to find a way to do so > > > while properly tracking bugs that may apply to both the old 'linux-2.6' > > > and the new 'linux'. > > > > Based on experience of the git-core -> git renaming: > > > > The only downside I know of is that you have to look at both > > src:linux-2.6 and src:linux to find the full list of known bugs. As > > long as src:linux-2.6 exists in a maintained version, the maintainer > > info is still fine (and if that breaks, we can pester owner@). To > > move a bug to the new package: > > > > reassign 94324832 src:linux 3.2.20-1 > > found 94324832 linux-2.6/2.6.32-29 > > found 94324832 linux-2.6/3.2.12-1 > > > > Debbugs uses the changelogs of the current package in stable and > > unstable (I don't remember if it uses testing and oldstable too or > > not) to understand found/fixed information, so the version graph, > > testing migration, and other version-associated magic would work fine. > > What, including changes in the source package name? Yes, this seems to work just fine: <http://bugs.debian.org/675817>. > > I wouldn't mind just making the switch, as long as the bug script is > > updated to match at the same time. > > Then let's do it. -- Ben Hutchings Knowledge is power. France is bacon.
Attachment:
signature.asc
Description: This is a digitally signed message part