Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary
On Thu, Feb 18, 2021 at 09:32:24AM +0100, Paul Gevers wrote: >Hi Limonciello, > >On 18-02-2021 07:15, Limonciello, Mario wrote: >> I don't have the power to manually run it. So there is nothing I can do. >> With the new 1.5.6-1 upload someone will need to manually run it again. > >I recognize what you say. However, *in my opinion* you can't just upload >the unsigned package without securing that the signing will happen ASAP, >with such tight dependencies. Users of unstable should expect that their >system breaks once in a while, but that's not by design but because bugs >happen. Being able to not update because of transitions is to be >expected and we don't have an alternative. But that's different from >what I read in this bug, where something else got updated and then the >fwupd set breaks without warning. We're in a bind here - by now I was hoping/assuming that we'd have the signing queue running automatically. I've just prodded in #debian-ftp to ask people to run the queue. -- Steve McIntyre, Cambridge, UK.st...@einval.com "War does not determine who is right - only who is left." -- Bertrand Russell
Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary
Hi Limonciello, On 18-02-2021 07:15, Limonciello, Mario wrote: > I don't have the power to manually run it. So there is nothing I can do. > With the new 1.5.6-1 upload someone will need to manually run it again. I recognize what you say. However, *in my opinion* you can't just upload the unsigned package without securing that the signing will happen ASAP, with such tight dependencies. Users of unstable should expect that their system breaks once in a while, but that's not by design but because bugs happen. Being able to not update because of transitions is to be expected and we don't have an alternative. But that's different from what I read in this bug, where something else got updated and then the fwupd set breaks without warning. If unstable doesn't work for you, how about using experimental? You can upload there much more freely and once stuff is ready (including making sure the signing can happen ASAP) you upload to unstable. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary
Paul, I don't have the power to manually run it. So there is nothing I can do. With the new 1.5.6-1 upload someone will need to manually run it again. Get Outlook for Android<https://aka.ms/ghei36> From: Paul Gevers Sent: Thursday, February 18, 2021, 00:09 To: 973...@bugs.debian.org Subject: Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary Hi Mario, LOn Mon, 16 Nov 2020 16:01:34 + "Limonciello, Mario" wrote: > As @Steve McIntyre mentions, it's a manual process to kick off the re-signing. > It needs to be done when 1.5.1-2 is ready to migrate. There's users of unstable too. In my opinion, if you can't relax the constraints, you'll have to kick it off as soon as it's needed in unstable, not when it's ready to migrate. Paul
Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary
Hi Mario, LOn Mon, 16 Nov 2020 16:01:34 + "Limonciello, Mario" wrote: > As @Steve McIntyre mentions, it's a manual process to kick off the re-signing. > It needs to be done when 1.5.1-2 is ready to migrate. There's users of unstable too. In my opinion, if you can't relax the constraints, you'll have to kick it off as soon as it's needed in unstable, not when it's ready to migrate. Paul OpenPGP_signature Description: OpenPGP digital signature
