as I said, I can try. Test PCs could be an old 386 Laptop with 524MB Ram (only LXDE), or a fast 64bit Laptop, I think there also should run an i686 workstation.
Kind regards
-----Ursprüngliche Mitteilung-----
Von: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
An: For testing and quality assurance of Fedora releases <test@xxxxxxxxxxxxxxxxxxxxxxx>
Verschickt: Fr, 20 Mai 2016 10:05 pm
Betreff: TPM prevents grub menu, scratch build request
[Bug 1334075] TPM prevents grub menu, drops to grub rescue; BIOS settings no help https://bugzilla.redhat.com/show_bug.cgi?id=1334075 This is not a blocker since it's i686, but there is a willing tester with affected hardware who can test the recent patch submitted for this bug. Is anyone able/willing to put up a scratch build? And if that goes well get it into u-t before freeze? I can do it locally but I know diddly squat about how to package stuff within the Fedora build system. -- Chris Murphy -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
Von: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
An: For testing and quality assurance of Fedora releases <test@xxxxxxxxxxxxxxxxxxxxxxx>
Verschickt: Fr, 20 Mai 2016 10:05 pm
Betreff: TPM prevents grub menu, scratch build request
[Bug 1334075] TPM prevents grub menu, drops to grub rescue; BIOS settings no help https://bugzilla.redhat.com/show_bug.cgi?id=1334075 This is not a blocker since it's i686, but there is a willing tester with affected hardware who can test the recent patch submitted for this bug. Is anyone able/willing to put up a scratch build? And if that goes well get it into u-t before freeze? I can do it locally but I know diddly squat about how to package stuff within the Fedora build system. -- Chris Murphy -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx