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
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
1, 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
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
> -Original Message-
> From: Matteo Settenvini On Behalf Of Matteo Settenvini
> Sent: Saturday, November 14, 2020 7:35
> To: 973...@bugs.debian.org
> Subject: Bug#973715: fwupd-amd64-signed holding off fwupd update results in
> segfaulting binary
>
> The probl
The problem suddenly become worse.
Now that fwupd 1.5.1 has landed in sid, and some dependencies
apparently changed, the fwupd-amd64-signed package holding off fwupd
upgrade and forcing it to stay at version 1.4.6-2, is breaking the
system:
nov 14 14:29:52 rosebud kernel: fwupd[11192]: segfault a
6 matches
Mail list logo
