Fedora for WSL

I may be hair-brained to do this, but I've put together an installer for Fedora on WSL. It mostly follows the procedures that had been much talked about in a blog post about running Fedora 33 in the WSL2, but it uses the direct installer rather than the manual side-loads. It also will install

[Bug 1905190] biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

https://bugzilla.redhat.com/show_bug.cgi?id=1905190 Fedora Release Engineering changed: What|Removed |Added CC|

Re: Upgrade to Fedora 34 broke the boot menu.

On Sat, May 8, 2021 at 3:51 PM Björn Persson wrote: > > Chris Murphy wrote: > > Does /etc/default/grub contain > > GRUB_ENABLE_BLSCFG=false > > ? > > No, it says "GRUB_ENABLE_BLSCFG=true". > > > There have been two big GRUB changes and if you followed them without > > any intervention or

[Bug 1958573] New: perl-YAML-LibYAML-0.83 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1958573 Bug ID: 1958573 Summary: perl-YAML-LibYAML-0.83 is available Product: Fedora Version: rawhide Status: NEW Component: perl-YAML-LibYAML Keywords: FutureFeature, Triaged

Re: Upgrade to Fedora 34 broke the boot menu.

Alexander Ploumistos wrote: > Have you looked in /boot/loader/entries/ ? I don't know how they get > created, but a couple of times I've had some extra entries after an > upgrade - nothing older than Fedora N-2 though. It contains files that seem to match the menu entries I should get, none of

Re: Upgrade to Fedora 34 broke the boot menu.

Chris Murphy wrote: > Does /etc/default/grub contain > GRUB_ENABLE_BLSCFG=false > ? No, it says "GRUB_ENABLE_BLSCFG=true". > There have been two big GRUB changes and if you followed them without > any intervention or customizations, you get upgraded correctly. If you > make customizations or opt

[Bug 1958569] New: perl-PDL-2.047 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1958569 Bug ID: 1958569 Summary: perl-PDL-2.047 is available Product: Fedora Version: rawhide Status: NEW Component: perl-PDL Keywords: FutureFeature, Triaged

Re: Upgrade to Fedora 34 broke the boot menu.

On Sat, May 8, 2021 at 11:36 AM Chris Murphy wrote: > > If you have BLS disabled, enable it. Recreate /boot/grub2/grub.cfg > (this is now the correct location on UEFI and BIOS). If you've > accidentally stepped on the forwarding /boot/efi/EFI/fedora/grub.cfg If you have accidentally done

Re: Upgrade to Fedora 34 broke the boot menu.

Oh and you can delete any stale *conf files you find in /boot/loader/entries/. That will remove them from the GRUB menu. If you want the rescue kernel+initramfs updated you can just remove them as well. They'll be replaced the next time the kernel is updated, or you can reinstall a kernel. --

Re: Upgrade to Fedora 34 broke the boot menu.

On Sat, May 8, 2021 at 6:52 AM Björn Persson wrote: > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. Does /etc/default/grub

Re: Upgrade to Fedora 34 broke the boot menu.

On Sat, May 8, 2021 at 6:37 PM Björn Persson wrote: > > Tomasz Torcz wrote: > > Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > > Grub complains about not finding some theme files, and then

Re: Upgrade to Fedora 34 broke the boot menu.

Tomasz Torcz wrote: > Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > Grub complains about not finding some theme files, and then displays a > > Missing theme files sounds like >

Re: Upgrade to Fedora 34 broke the boot menu.

Neal Gompa wrote: > On Sat, May 8, 2021 at 8:53 AM Björn Persson wrote: > > > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > > Grub complains about not finding some theme files, and then displays a > > menu with two kernels from Fedora 29 and a rescue entry from Fedora

Re: Upgrade to Fedora 34 broke the boot menu.

Dnia Sat, May 08, 2021 at 02:51:31PM +0200, Björn Persson napisał(a): > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a Missing theme files sounds like

Re: Upgrade to Fedora 34 broke the boot menu.

On Sat, May 8, 2021 at 8:53 AM Björn Persson wrote: > > I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now > Grub complains about not finding some theme files, and then displays a > menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. > If I choose one of the

Re: F35 Change: Broken RPATH will fail rpmbuild (System-Wide Change proposal)

* Ben Cotton: > Another problem of a hardcoded RPATH is security. When an ELF object > contains an RPATH pointed to a directory not managed by the system, > where some malicious actor has write permissions to, it's relatively > easy to execute arbitrary code. > > Performance can be also affected,

Fedora-Rawhide-20210508.n.0 compose check report

No missing expected images. Compose FAILS proposed Rawhide gating check! 1 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 7/133 (aarch64), 7/194 (x86_64) New failures (same test not failed in

Upgrade to Fedora 34 broke the boot menu.

I used yum system-upgrade to upgrade from Fedora 32 to Fedora 34. Now Grub complains about not finding some theme files, and then displays a menu with two kernels from Fedora 29 and a rescue entry from Fedora 28. If I choose one of the Fedora 29 entries, then Grub unsurprisingly fails to find the

Fedora-IoT-35-20210508.0 compose check report

No missing expected images. Failed openQA tests: 3/16 (x86_64), 2/15 (aarch64) Old failures (same test failed in Fedora-IoT-35-20210507.0): ID: 882496 Test: x86_64 IoT-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/882496 ID: 882498 Test: x86_64

Re: F35 Change: Broken RPATH will fail rpmbuild (System-Wide Change proposal)

On Sat, May 08, 2021 at 12:44:32PM +0100, Richard W.M. Jones wrote: > Some random questions about this: > > - How many existing packages are affected? Can this be analyzed and > the maintainers notified? There's a list of packages at:

Fedora rawhide compose report: 20210508.n.0 changes

OLD: Fedora-Rawhide-20210507.n.0 NEW: Fedora-Rawhide-20210508.n.0 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 3 Dropped packages:0 Upgraded packages: 68 Downgraded packages: 1 Size of added packages: 2.84 MiB Size of dropped packages:0 B

Re: F35 Change: Broken RPATH will fail rpmbuild (System-Wide Change proposal)

Some random questions about this: - How many existing packages are affected? Can this be analyzed and the maintainers notified? - If I want to analyze my own packages to see if they contain rpaths, is it sufficient to run this? chrpath --list --keepgoing | grep RUNPATH I ran that on

Fedora-Cloud-34-20210508.0 compose check report

No missing expected images. Failed openQA tests: 1/8 (x86_64) Old failures (same test failed in Fedora-Cloud-34-20210507.0): ID: 882098 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/882098 Soft failed openQA tests: 1/8 (aarch64) (Tests

Fedora-Cloud-32-20210508.0 compose check report

No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20210507.0): ID: 882082 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL:

Re: Self Introduction: Rémi Lauzier

On 5/2/21 11:21 PM, remilauzier via devel wrote: Hello fellow fedoreans, My name is Rémi Lauzier. He, Him. I am 29 years old. I am passionate about computer and video games. I am the developer of a rust program call Rudo.

Fedora-Cloud-33-20210508.0 compose check report

No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-33-20210507.0): ID: 881896 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: