Your message dated Wed, 16 Feb 2022 13:18:45 +0100
with message-id <18082961.OrvFop5N7Y@bagend>
and subject line Re: raspi-firmware: keep 1.20220120+ds-1 out of testing a bit 
longer
has caused the Debian Bug report #1005845,
regarding raspi-firmware: keep 1.20220120+ds-1 out of testing a bit longer
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 ow...@bugs.debian.org
immediately.)


-- 
1005845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi-firmware
Version: 1.20220120+ds-1
Severity: grave

Hi,

This is a 'dummy' RC bug to prevent version 1.20220120+ds-1 from transitioning 
to testing. Just now on IRC we identified a bug which I don't consider RC in 
itself, but the upstream issue tracker indicate various issue with the latest 
firmware, especially https://github.com/raspberrypi/firmware/issues/1688

https://github.com/raspberrypi/firmware/commit/
9c04ed2c1ad06a615d8e6479806ab252dbbeb95a could be a potential fix.

Once we're confident enough that it should work, this bug can be closed so that 
the package can transition to testing.

Cheers,
  Diederik

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


--- End Message ---
--- Begin Message ---
On 16 Feb 2022 00:16:23 +0100 Diederik de Haas <didi.deb...@cknow.org> wrote:
> Package: raspi-firmware
> Version: 1.20220120+ds-1
> Severity: grave
> 
> This is a 'dummy' RC bug to prevent version 1.20220120+ds-1 from
> transitioning to testing.

It looks like I was too late as it did transition to testing, so closing this 
bug again.
The bug I mentioned earlier was bug #1005846 and that bug mentions an upstream 
commit which fixed the reported issue, so a new upstream version should fix 
that.

Cheers,
  Diederik

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


--- End Message ---

Reply via email to