[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#547903: marked as done (linux-image-amd64 broken dependencies (again))

Your message dated Sat, 03 Oct 2009 23:22:59 +0100
with message-id <1254608579.2395.16.camel@localhost>
and subject line Re: linux-image-amd64 broken dependencies (again)
has caused the Debian Bug report #547903,
regarding linux-image-amd64 broken dependencies (again)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
547903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547903
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 2.6.30+20

Not a bug and this is an unmet dependency, so it will probably get
closed.  But it's the 3rd consecutive kernel release that has broken
this package in the identical way.  New kernel released, last kernel
removed from sid package list, pointer package (at least amd64 version
linux-image-amd64) is left with unmet dependency.  Isn't there something
that can be done about this in future?  It makes base systems install
without a kernel, which is pretty grave imo =(

... Sigh, sorry I know you work hard to get bug fixes out and updates to
sid which is appreciated, sorry to be the pest here.

-jmd
 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4447 (20090922) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

--- End Message ---
--- Begin Message --- 
Version: 2.6.30+21

On Tue, 2009-09-22 at 09:52 -0400, Joseph M. Deming wrote:
> Package: linux-image-amd64
> Version: 2.6.30+20
> 
> Not a bug and this is an unmet dependency, so it will probably get
> closed.  But it's the 3rd consecutive kernel release that has broken
> this package in the identical way.

In order to allow for multiple upstream versions of Linux in the same
suite, as in etch, we must have separate source packages for Linux
itself (linux-2.6, linux-2.6.x) and for the 'latest version'
metapackages (linux-latest-2.6).

Due to the nature of the autobuilder network, we cannot ensure that
these arrive in the archive precisely in sync for all architectures.
But I acknowledge we could do a better job of actually uploading around
the same time.

> New kernel released, last kernel
> removed from sid package list, pointer package (at least amd64 version
> linux-image-amd64) is left with unmet dependency.  Isn't there something
> that can be done about this in future?  It makes base systems install
> without a kernel, which is pretty grave imo =(
[...]

d-i should not have this problem.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

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


--- End Message ---
Reply to: