[EPEL-devel] Fedora EPEL 9 updates-testing report

2023-12-27 Thread updates
The following Fedora EPEL 9 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7ff32fc746 podman-tui-0.15.0-2.el9 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-b698d8c031 proftpd-1.3.8b-1.el9 5

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/28/23 00:04, Samuel Sieb wrote: On 12/27/23 08:20, Sandro wrote: I added `level` and `num-devices` to all entries in mdadm.conf and rebooted. It didn't change anything. Manual assembly still freezes the system as well. You need to also update the initramfs using dracut or the modified

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Samuel Sieb
On 12/27/23 15:12, Samuel Sieb wrote: On 12/27/23 06:05, Sandro wrote: I could you use some help with ${SUBJECT}. I posted the details in discussion [1], but have yet to receive a response. I thought maybe folks on the list may have an idea. I'm kinda lost as to where this is going wrong.

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Samuel Sieb
On 12/27/23 06:05, Sandro wrote: I could you use some help with ${SUBJECT}. I posted the details in discussion [1], but have yet to receive a response. I thought maybe folks on the list may have an idea. I'm kinda lost as to where this is going wrong. Feel free to reply either on discussion

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Samuel Sieb
On 12/27/23 08:20, Sandro wrote: I added `level` and `num-devices` to all entries in mdadm.conf and rebooted. It didn't change anything. Manual assembly still freezes the system as well. You need to also update the initramfs using dracut or the modified mdadm.conf won't be available at boot.

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 22:48, pgnd wrote: without seeing all the details, unfound superblocks aren't good. But isn't the information `mdadm --examine` prints coming from the superblock stored on the device? The magic number, that this command reports, matches what was expected (a92b4efc). I can access

intent to hand over or orphan several scientific packages and their build requirements

2023-12-27 Thread Dominik 'Rathann' Mierzejewski
Hello! I intend to hand over primary maintainership of the following packages or orphan them if nobody steps up: arpack chemtool cp2k elpa inchi python-colorspacious python-fypp python-GridDataFormats python-gsd python-kaitaistruct python-mmtf python-mrcfile python-Pympler tachyon wxmacmolplt

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 17:36, Sandro wrote: I'll try with a F39 live ISO as well. If nothing else, it could confirm the issue to be with/in F39. I did that. Right after boot only one of the arrays was assembled. In /proc/mdstat is was listed as "active (auto-read-only)" and the component devices

[Bug 2255994] perl-YAML-1.31 is available

2023-12-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2255994 --- Comment #2 from Upstream Release Monitoring --- Created attachment 2006122 --> https://bugzilla.redhat.com/attachment.cgi?id=2006122=edit Update to 1.31 (#2255994) -- You are receiving this mail because: You are on the CC list for

[Bug 2255994] New: perl-YAML-1.31 is available

2023-12-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2255994 Bug ID: 2255994 Summary: perl-YAML-1.31 is available Product: Fedora Version: rawhide Status: NEW Component: perl-YAML Keywords: FutureFeature, Triaged

[Bug 2255994] perl-YAML-1.31 is available

2023-12-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2255994 --- Comment #1 from Upstream Release Monitoring --- Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-t5efr8_l/perl-YAML.spec']' returned

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 17:28, pgnd wrote: WAG? https://www.urbandictionary.com/define.php?term=wild%20ass%20guess ;) I should have guessed... I added `level` and `num-devices` to all entries in mdadm.conf and rebooted. It didn't change anything. Manual assembly still freezes the system as well.

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 17:03, pgnd wrote: also make sure your drivers are in the initrd lsinitrd | grep -Ei "kernel/drivers/md/raid" -rw-r--r-- 1 root root10228 Nov 15 19:00 usr/lib/modules/6.6.8-200.fc39.x86_64/kernel/drivers/md/raid0.ko.xz -rw-r--r-- 1 root root35376 Nov 15

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 17:10, pgnd wrote: If it works, I'd still wonder why md54 comes up fine. That entry is also missing `level` and `num-devices`. 1st WAG ? WAG? /dev/md/54 is 'just' raid1, without an atypical spare It's not. It's a raid5 without any spare just like md5. Only difference

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 16:47, pgnd wrote: i explicitly add the level= num-devices i've had issues long ago with mis-assembly that that cured. whether it's STILL a problem, i don't know; all my array spec contain contain these, and don't cause harm. it's now SOP here. i'd at least

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 15:14, pgnd wrote: what's the output of: mdadm -Es cat /etc/mdadm.conf # mdadm -Es ARRAY /dev/md/5 metadata=1.1 UUID=39295d93:e5a75797:b72287f3:51563755 name=urras.penguinpee.nl:5 ARRAY /dev/md/1 metadata=1.1 UUID=4a2c44b5:25f2a6c9:0e7f6cae:37a8a9cc

Re: Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
On 12/27/23 15:05, Sandro wrote: I could you use some help with ${SUBJECT}. I posted the details in discussion [1], but have yet to receive a response. I thought maybe folks on the list may have an idea. I'm kinda lost as to where this is going wrong. Feel free to reply either on discussion or

Re: F40 Change Proposal: Enable IPv4 Address Conflict Detection (Self-Contained)

2023-12-27 Thread Chris Adams
Once upon a time, Beniamino Galvani said: > In practice, it's a bit more complex than that. network-online.target > is emitted after all NM connections succeed. The meaning of "success" > depends on properties "ipv4.may-fail" and "ipv6.may-fail" of the > connection profile. Normally they are both

Troubleshooting MD RAID assembly not working after upgrade to F39

2023-12-27 Thread Sandro
I could you use some help with ${SUBJECT}. I posted the details in discussion [1], but have yet to receive a response. I thought maybe folks on the list may have an idea. I'm kinda lost as to where this is going wrong. Feel free to reply either on discussion or here. I'd appreciate any help I

[Bug 2255972] New: perl-Math-BigInt-GMP-1.6014 is available

2023-12-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2255972 Bug ID: 2255972 Summary: perl-Math-BigInt-GMP-1.6014 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Math-BigInt-GMP Keywords: FutureFeature,

Fedora rawhide compose report: 20231227.n.0 changes

2023-12-27 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20231226.n.0 NEW: Fedora-Rawhide-20231227.n.0 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 5 Dropped packages:0 Upgraded packages: 34 Downgraded packages: 0 Size of added packages: 167.59 KiB Size of dropped packages:0

[Bug 2255963] New: perl-Math-BigInt-FastCalc-0.5016 is available

2023-12-27 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2255963 Bug ID: 2255963 Summary: perl-Math-BigInt-FastCalc-0.5016 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Math-BigInt-FastCalc Keywords:

Re: F40 Change Proposal: Enable IPv4 Address Conflict Detection (Self-Contained)

2023-12-27 Thread Beniamino Galvani
On Thu, Dec 21, 2023 at 10:35:45AM -0600, Chris Adams wrote: > Once upon a time, Beniamino Galvani said: > > network-scripts do [1]: > > > > /sbin/arping -c 2 -w ${ARPING_WAIT:-3} -D -I ${REALDEVICE} ${ipaddr[$idx]} > > > > which waits 2 seconds by default. > > Ahh, sorry, that's what I get