Re: FC 34, broken glibc
Howdy, I thought of a solution that didn't require a re-installation. There's a handy command in /bin named rpm2cpio. I fed the glibc rpms to this program and passed the stream to cpio. Out popped several directories that were stored into by the rpm command except that these dirs went to the current directory. I copied the files to each of it's designated target. This is kinda iffy since some rpms run pre and post scriptlets. I took a gamble and it appears to have worked. Just in case I ran dnf distro-sync to get "real" package installation. That worked as well. This message is from my fc34 system... The problem appears to be resolved. Thanks to all you terrific helpers for your thougts and help. Best regards... and STAY SAFE! George... On Friday, December 11, 2020, 7:28:55 AM PST, Matthew Miller wrote: On Fri, Dec 11, 2020 at 03:24:14PM +, George R Goffe wrote: > I have a fc31 live system booted and am looking for a statically linked > bash because chroot fails... no libgc. Sigh... The commands rpm and the > others rpm might run during an (re)install would probably need to be > statically linked in as well. You might be able to install busybox and get that to be helpful. But I don't think we have a statically-linked RPM anymore. Personally, I'd rsync /home to a backup device and reinstall the whole thing. -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
On Fri, Dec 11, 2020 at 03:24:14PM +, George R Goffe wrote: > I have a fc31 live system booted and am looking for a statically linked > bash because chroot fails... no libgc. Sigh... The commands rpm and the > others rpm might run during an (re)install would probably need to be > statically linked in as well. You might be able to install busybox and get that to be helpful. But I don't think we have a statically-linked RPM anymore. Personally, I'd rsync /home to a backup device and reinstall the whole thing. -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
Matthew, Thanks for your appreciation. In my fumbling attempt to get "dnf distro-sync" to work I removed the one rpm that was holding things up (glibc*-20*). OUCH! This was the exact thing I was afraid of... not afraid enough it seems. Now I have a totally non funcional system. Argh. I did this in 2001 to a Solaris system... got the fear and the vaccination... Sigh. The vaccination apparently wore off. I have a fc31 live system booted and am looking for a statically linked bash because chroot fails... no libgc. Sigh... The commands rpm and the others rpm might run during an (re)install would probably need to be statically linked in as well. Do you have any ideas on how I can recover from this... preferably without reinstalling the system. Best regards, George... On Thursday, December 10, 2020, 4:26:03 PM EST, Matthew Miller wrote: On Thu, Dec 10, 2020 at 08:55:11PM +, George R Goffe via test wrote: > Thanks VERY MUCH to everyone who helped with this. And thanks for undertaking the adventure of running Rawhide. :) We're looking at turning on some of the gating infrastructure we have in place but dormant to make it a little safer to do so in the future. -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
On Thu, Dec 10, 2020 at 08:55:11PM +, George R Goffe via test wrote: > Thanks VERY MUCH to everyone who helped with this. And thanks for undertaking the adventure of running Rawhide. :) We're looking at turning on some of the gating infrastructure we have in place but dormant to make it a little safer to do so in the future. -- Matthew Miller Fedora Project Leader ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
Adam, Removing fprintd did the trick! I'll have to do a "distro-sync" to get the glibc stuff cleaned up. Thanks VERY MUCH to everyone who helped with this. Best regards, George... On Thursday, December 10, 2020, 12:48:43 PM PST, George R Goffe wrote: Adam, I did all the glibc stuff you wrote about but that didn't solve the problem. I have removed fprintd and will try again... and report here... Thanks, George... On Thursday, December 10, 2020, 11:23:00 AM PST, Adam Williamson wrote: On Thu, 2020-12-10 at 19:04 +, George R Goffe wrote: > Adam, > > Where do "we" get the downgrade version of glibc? > > I'm "live" with FC31 on my now sadly broken FC34 rawhide system. Hey, George. So the login/su bugs are actually in fprintd, not glibc. There *is* a bug in glibc, though, that showed up in the same compose - that bug means that secondary group memberships don't work any more. So: two bugs, two packages, one compose. The bad packages are glibc-2.32.9000-19.fc34 and fprintd-1.90.6-1.fc34 . There should be fixed versions of both now: fprintd-1.90.7-1.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656747 glibc-2.32.9000-20.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656956 you can get these from koji with the `koji` CLI tool, `koji download- build --arch=x86_64 --arch=noarch glibc-2.32.9000-20.fc34` for e.g. It will download *all* the subpackages, so do it in a dir with a bit of space. Then you can do "dnf update *.rpm" to update. Hope that helps! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
Adam, I did all the glibc stuff you wrote about but that didn't solve the problem. I have removed fprintd and will try again... and report here... Thanks, George... On Thursday, December 10, 2020, 11:23:00 AM PST, Adam Williamson wrote: On Thu, 2020-12-10 at 19:04 +, George R Goffe wrote: > Adam, > > Where do "we" get the downgrade version of glibc? > > I'm "live" with FC31 on my now sadly broken FC34 rawhide system. Hey, George. So the login/su bugs are actually in fprintd, not glibc. There *is* a bug in glibc, though, that showed up in the same compose - that bug means that secondary group memberships don't work any more. So: two bugs, two packages, one compose. The bad packages are glibc-2.32.9000-19.fc34 and fprintd-1.90.6-1.fc34 . There should be fixed versions of both now: fprintd-1.90.7-1.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656747 glibc-2.32.9000-20.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656956 you can get these from koji with the `koji` CLI tool, `koji download- build --arch=x86_64 --arch=noarch glibc-2.32.9000-20.fc34` for e.g. It will download *all* the subpackages, so do it in a dir with a bit of space. Then you can do "dnf update *.rpm" to update. Hope that helps! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
Adam, Thanks for your help. I'm downloading now. Will report results "here" asap. Best regards, George... On Thursday, December 10, 2020, 11:23:00 AM PST, Adam Williamson wrote: On Thu, 2020-12-10 at 19:04 +, George R Goffe wrote: > Adam, > > Where do "we" get the downgrade version of glibc? > > I'm "live" with FC31 on my now sadly broken FC34 rawhide system. Hey, George. So the login/su bugs are actually in fprintd, not glibc. There *is* a bug in glibc, though, that showed up in the same compose - that bug means that secondary group memberships don't work any more. So: two bugs, two packages, one compose. The bad packages are glibc-2.32.9000-19.fc34 and fprintd-1.90.6-1.fc34 . There should be fixed versions of both now: fprintd-1.90.7-1.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656747 glibc-2.32.9000-20.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656956 you can get these from koji with the `koji` CLI tool, `koji download- build --arch=x86_64 --arch=noarch glibc-2.32.9000-20.fc34` for e.g. It will download *all* the subpackages, so do it in a dir with a bit of space. Then you can do "dnf update *.rpm" to update. Hope that helps! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: FC 34, broken glibc
On Thu, 2020-12-10 at 19:04 +, George R Goffe wrote: > Adam, > > Where do "we" get the downgrade version of glibc? > > I'm "live" with FC31 on my now sadly broken FC34 rawhide system. Hey, George. So the login/su bugs are actually in fprintd, not glibc. There *is* a bug in glibc, though, that showed up in the same compose - that bug means that secondary group memberships don't work any more. So: two bugs, two packages, one compose. The bad packages are glibc-2.32.9000-19.fc34 and fprintd-1.90.6-1.fc34 . There should be fixed versions of both now: fprintd-1.90.7-1.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656747 glibc-2.32.9000-20.fc34 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1656956 you can get these from koji with the `koji` CLI tool, `koji download- build --arch=x86_64 --arch=noarch glibc-2.32.9000-20.fc34` for e.g. It will download *all* the subpackages, so do it in a dir with a bit of space. Then you can do "dnf update *.rpm" to update. Hope that helps! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
FC 34, broken glibc
Adam, Where do "we" get the downgrade version of glibc? I'm "live" with FC31 on my now sadly broken FC34 rawhide system. Best regards, George... On Wednesday, December 9, 2020, 8:04:23 PM PST, test-requ...@lists.fedoraproject.org wrote: ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
