Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Michel Le Bihan
erCould not parse device path: > > > > Invalid > > > > argument > > > > error trace: > > > > /build/efivar-yvRv8P/efivar-37/src/include/efivar/efivar- > > > > dp.h:1208 > > > > efidp_is_valid(): invalid device p

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Michel Le Bihan
t; From: Michel Le Bihan > > Sent: Monday, July 27, 2020 11:25 AM > > To: Limonciello, Mario; 963...@bugs.debian.org > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with > > "Could not > > parse device path: Invalid argument" > >

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Limonciello, Mario
Message- > > > From: Michel Le Bihan > > > Sent: Monday, July 27, 2020 12:16 PM > > > To: Limonciello, Mario; 963...@bugs.debian.org > > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with > > > "Could not > >

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Michel Le Bihan
: Invalid argument ``` Michel Le Bihan Le lundi 27 juillet 2020 à 15:28 +, Limonciello, Mario a écrit : > > -Original Message- > > From: Michel Le Bihan > > Sent: Sunday, July 26, 2020 2:58 PM > > To: 963...@bugs.debian.org > > Subject: Bug#963475: lib

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Kevin Locke
On Mon, 2020-07-27 at 18:24 +0200, Michel Le Bihan wrote: > Le lundi 27 juillet 2020 à 15:28 +, Limonciello, Mario a écrit : >>> On Sun, 2020-07-26 at 14:58, Michel Le Bihan wrote: >>> What's preventing the upstream fix from being applied to this >>> package? >> >> I personally can't

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Limonciello, Mario
Limonciello, Mario; 963...@bugs.debian.org > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not > parse device path: Invalid argument" > > > [EXTERNAL EMAIL] > > It was efibootmgr and efivar master. > > Le lund

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Limonciello, Mario
> -Original Message- > From: Michel Le Bihan > Sent: Sunday, July 26, 2020 2:58 PM > To: 963...@bugs.debian.org > Subject: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not > parse device path: Invalid argument" > > > [EXT

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-27 Thread Limonciello, Mario
ichel Le Bihan > > Le lundi 27 juillet 2020 à 15:28 +, Limonciello, Mario a écrit : > > > -Original Message- > > > From: Michel Le Bihan > > > Sent: Sunday, July 26, 2020 2:58 PM > > > To: 963...@bugs.debian.org > > > Subject: Bug#963475: libe

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-07-26 Thread Michel Le Bihan
Hello, What's preventing the upstream fix from being applied to this package? Michel Le Bihan

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-06-27 Thread Francesco Poli
On Mon, 22 Jun 2020 08:46:14 +0200 Francesco Poli (wintermute) wrote: [...] > I searched the web and found a github [issue], that claims the > problem is in efivar, mentioning a [commit] that is supposed > to fix it. > But it seems to me that the [code] currently in Debian unstable > does not

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

2020-06-22 Thread Francesco Poli (wintermute)
Package: libefivar1 Version: 37-2.1 Severity: important Hello! One week ago I had no issues in running: $ efibootmgr -v but today, I get: $ efibootmgr -v BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001, Boot* debianCould not parse device path: Invalid argument Please