Am 12.07.23 um 18:11 schrieb Josh Triplett:
My understanding was that that error happens *unconditionally* whether
there's a RAID device on the system or not, and that that bug is fixed
by depending on libblockdev-mdraid3 (which seems fine). But if I'm
understanding the upstream issue correctly,
On Wed, 12 Jul 2023 13:14:47 +0200 Michael Biebl wrote:
> Am 12.07.23 um 11:14 schrieb Josh Triplett:
> > Package: libblockdev-mdraid3
> > Version: 3.0.1-1
> > Severity: normal
> > X-Debbugs-Cc: j...@joshtriplett.org
> >
> > Current udisks2 has a dependency on libblockdev-mdraid3, and
> >
Am 12.07.23 um 11:14 schrieb Josh Triplett:
Package: libblockdev-mdraid3
Version: 3.0.1-1
Severity: normal
X-Debbugs-Cc: j...@joshtriplett.org
Current udisks2 has a dependency on libblockdev-mdraid3, and
libblockdev-mdraid3 has a dependency on mdadm. This effectively makes
mdadm required on
Package: libblockdev-mdraid3
Version: 3.0.1-1
Severity: normal
X-Debbugs-Cc: j...@joshtriplett.org
Current udisks2 has a dependency on libblockdev-mdraid3, and
libblockdev-mdraid3 has a dependency on mdadm. This effectively makes
mdadm required on desktop systems.
As I understand it from
4 matches
Mail list logo