Bug#636010: [linux-2.6] Please rename source to linux

2012-06-03 Thread Jonathan Nieder
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.

I wouldn't mind just making the switch, as long as the bug script is
updated to match at the same time.

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120603065040.GA3973@burratino



Bug#636010: [linux-2.6] Please rename source to linux

2012-06-03 Thread Ben Hutchings
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?

 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.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


signature.asc
Description: This is a digitally signed message part


Bug#636010: [linux-2.6] Please rename source to linux

2012-06-03 Thread Ben Hutchings
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.


signature.asc
Description: This is a digitally signed message part


Bug#636010: [linux-2.6] Please rename source to linux

2012-06-02 Thread Ben Hutchings
On Sat, 2011-07-30 at 10:14 +0200, Clara Gnos wrote:
 Package: linux-2.6
 Severity: wishlist
 
 To use the name linux-2.6 for the source package is quite misleading. Maybe 
 it 
 is better to drop this -2.6 appendix and use the name linux as Linus Torvalds 
 does since the release of 3.0 [1].
 
 [1] https://lkml.org/lkml/2011/7/20/371

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'.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


signature.asc
Description: This is a digitally signed message part


Bug#636010: [linux-2.6] Please rename source to linux

2011-07-30 Thread Clara Gnos
Package: linux-2.6
Severity: wishlist

To use the name linux-2.6 for the source package is quite misleading. Maybe it 
is better to drop this -2.6 appendix and use the name linux as Linus Torvalds 
does since the release of 3.0 [1].

[1] https://lkml.org/lkml/2011/7/20/371


--- System information. ---
Architecture: amd64
Kernel:   Linux 3.0.0-1-amd64

Debian Release: wheezy/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.debian.org 
  500 testing ftp.debian.org 
1 experimentalwww.debian-multimedia.org 
1 experimentalftp.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.







-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2393079.zvltut6...@sven-desktop.home.narfation.org