Bug#301799: kernel-tree-2.6.11: new upstream source available: 2.6.11.6
- To: Horms <horms@verge.net.au>, 301799@bugs.debian.org
- Cc: Henrique de Moraes Holschuh <hmh@debian.org>
- Subject: Bug#301799: kernel-tree-2.6.11: new upstream source available: 2.6.11.6
- From: Sven Luther <sven.luther@wanadoo.fr>
- Date: Mon, 4 Apr 2005 12:41:33 +0200
- Message-id: <[🔎] 20050404104133.GA24894@pegasos>
- Reply-to: Sven Luther <sven.luther@wanadoo.fr>, 301799@bugs.debian.org
- In-reply-to: <20050330150816.GA17299@verge.net.au>
- References: <20050328131020.GA14336@khazad-dum.debian.net> <20050330084607.GF24363@verge.net.au> <20050330131718.GD8417@khazad-dum.debian.net> <20050330140454.GA16427@verge.net.au> <20050330142719.GK8417@khazad-dum.debian.net> <20050330145015.GA16952@verge.net.au> <20050330145527.GO8417@khazad-dum.debian.net> <20050330150816.GA17299@verge.net.au>
On Thu, Mar 31, 2005 at 12:08:18AM +0900, Horms wrote:
> On Wed, Mar 30, 2005 at 11:55:27AM -0300, Henrique de Moraes Holschuh wrote:
> > On Wed, 30 Mar 2005, Horms wrote:
> > > > It is much more user-friendly, and it readly provides information on the
> > > > most up-to-date tree it was synced with, in aptitude/dselect/synaptic...
> > >
> > > Yes, but the problem is that each time it changes backages
> > > have to go through a NEW cycle.
> >
> > I assume you mean for the binary packages? I was only paying attention to
> > the kernel-source, kernel-patch and kernel-tree packages...
>
> To follow the current naming convention, I believe that they
> all would have to go through new, and also would not be
> an upgrade path, but a fresh install for users.
No, the packages would still be kernel-*-2.6.11, but the version number would
be 2.6.11.6-<debianversion>, yiedling stuff like :
kernel-source-2.6.11_2.6.11.6-1_all.deb
Which is ok, and doesn't trigger NEW. I vote for that.
Friendly,
Sven Luther
Reply to: