Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

2021-02-18 Thread Steve McIntyre
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

Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

2021-02-18 Thread Paul Gevers
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

Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

2021-02-17 Thread Limonciello, Mario
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

Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

2021-02-17 Thread Paul Gevers
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,