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

Bug#922184: marked as done (Stretch-backports linux-image-cloud-amd64 broken)

Your message dated Tue, 26 Mar 2019 23:36:14 +0100
with message-id <20190326223612.bxaixpezuzv2bede@debian.org>
and subject line Re: Stretch-backports linux-image-cloud-amd64 broken
has caused the Debian Bug report #922184,
regarding Stretch-backports linux-image-cloud-amd64 broken
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.)


-- 
922184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922184
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-cloud-amd64
Severity: critical

In stretch-backports the  linux-image-cloud-amd64 package depends upon  linux-image-4.19.0-0.bpo.2-cloud-amd64 however that package is not available

See https://packages.debian.org/stretch-backports/linux-image-cloud-amd64

There does seem to be an unsigned version at https://packages.debian.org/stretch-backports/linux-image-4.19.0-0.bpo.2-cloud-amd64-unsigned

--- End Message ---
--- Begin Message --- 
Hi,

On Wed, Feb 13, 2019 at 11:01:18AM +1100, Dean Hamstead wrote:
> Package: linux-image-cloud-amd64
> Severity: critical
> 
> In stretch-backports the  linux-image-cloud-amd64 package depends upon  linux-image-4.19.0-0.bpo.2-cloud-amd64 however that package is not available
> 
> See https://packages.debian.org/stretch-backports/linux-image-cloud-amd64
> 
> There does seem to be an unsigned version at https://packages.debian.org/stretch-backports/linux-image-4.19.0-0.bpo.2-cloud-amd64-unsigned
> 

The signed version was uploaded to stretch-backports shortly after this bug
was filed.

Thanks,

Ivo

--- End Message ---
Reply to: