[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"
To
:
963475@bugs.debian.org
Subject
: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"
From
: Michel Le Bihan <
michel@lebihan.pl
>
Date
: Sun, 26 Jul 2020 21:57:48 +0200
Message-id
: <
[🔎]
b01cb1db68d4ad9729110161434c61a91e95d922.camel@lebihan.pl
>
Reply-to
: Michel Le Bihan <
michel@lebihan.pl
>,
963475@bugs.debian.org
References
: <159280837411.2657.582930654109743839.reportbug@crunch>
Hello, What's preventing the upstream fix from being applied to this package? Michel Le Bihan
Reply to:
debian-efi@lists.debian.org
Michel Le Bihan (on-list)
Michel Le Bihan (off-list)
Follow-Ups
:
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"
From:
"Limonciello, Mario" <Mario.Limonciello@dell.com>
Prev by Date:
shim-helpers-i386-signed_1+15+1533136590.3beb971+7+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Next by Date:
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"
Previous by thread:
shim-helpers-i386-signed_1+15+1533136590.3beb971+7+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Next by thread:
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"
Index(es):
Date
Thread