The 2.1.5 packages have made their way into bookworm, and my system is
now happily running kernel 5.18 with ZFS.
I'm no expert, but since these packages are in 'contrib' I suspect
they don't have the ability to block package upgrades in 'main'.
On Sun, Jun 19, 2022 at 5:51 AM Chris Putnam wrote:
>
> Apologies if this question is well-answered, but why isn't this package
> holding back the kernel to 5.17? I
Building python-apt 2.3.0 also fails with the same error, so I suspect
the cause is in libapt-pkg, not libqapt.
r place for the userspace firmware
loader to find it.
--
Kevin P. Fleming
Senior Software Engineer
Digium, Inc.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
4 matches
Mail list logo