On Tue, Dec 16, 2014 at 02:45:47PM +0000, Steve McIntyre wrote: >On Mon, Dec 15, 2014 at 01:38:34PM -0600, D. Jared Dominguez wrote: >> >>Once you test against unstable's efibootmgr, Peter Jones (upstream) >>can help us try to triage this bug more. > >Same behaviour using current upstream head - see the comments in >upstream's issue tracker: > >https://github.com/vathpela/efibootmgr/issues/21 >https://github.com/vathpela/efivar/issues/11
And after some discussion with Peter in IRC, he agrees with my proposed fix. We're still using the legacy EFI access path here, which may explain why nobody else has been reporting this. He's pushed a fix for efivar issue#11 above, and I can confirm that it fixes all my reported problems. I'd strongly recommend we take that ASAP! Also, it's probably worth spending time to see why we're not using the new non-legacy efivarfs path yet. I'm guessing it's just that nobody has looked into it yet, but it's probably a bit too big a change to make for Jessie right now. :-/ -- Steve McIntyre, Cambridge, UK. st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
