On 2/21/22 17:18, Stan Johnson wrote:
> In my experience, installation of either sysvinit-core or systemd
> requires that the other be removed, so I don't think I can use sysvinit
> with systemd installed. But since libsystemd0 is a separate package, it
> should be enough for fwupd to require libsy
On 2/21/22 4:57 AM, John Paul Adrian Glaubitz wrote:
>
>
>> On Feb 21, 2022, at 10:52 AM, Frank Scheiner wrote:
>>
>> Small update...
>>
>> Well, looks like these two dependencies are not the cause. But checking
>> the differences between the "fwupd" package in buster ([2]) and bullseye
>> ([3]
> On Feb 21, 2022, at 10:52 AM, Frank Scheiner wrote:
>
> Small update...
>
> Well, looks like these two dependencies are not the cause. But checking
> the differences between the "fwupd" package in buster ([2]) and bullseye
> ([3]) there is a dependency on "libsystemd0" that is not included
Small update...
On 21.02.22 10:22, Frank Scheiner wrote:
On 20.02.22 23:37, Stan Johnson wrote:
So there must have been a change in fwupd somewhere between version
1.7.4-1 and 1.7.5-3 that causes it to now require systemd. Please let me
know where I should report the issue.
[1] lists two depe
Hi Stan, Rick,
spotted this by chance.
On 20.02.22 23:37, Stan Johnson wrote:
And now:
# dpkg --list | grep -w fwupd
ii fwupd 1.7.5-3powerpcFirmware update daemon
So there must have been a change in fwupd somewhere between version
1.7.4-1 and 1.7.5-3 that causes it to now require sys
5 matches
Mail list logo
