Upgrading glibc in current: what I did and what should I have done?
by hazel from LinuxQuestions.org on (#5FGH8)
This is not a story about a disaster, merely a mild annoyance. But I do feel that I missed a trick somewhere and hope someone here will tell me what I should have done.
I have a partial Slackware-current system on /dev/sda10, which I regard as my new Slackware-15. I installed glibc-multilib on it because I will eventually need 32-bit glibc for my printer. I have the multilib repo uncommented in slackpkgplus.conf and I also have glibc blacklisted because I hoped this would force slackpkg to use the multilib version for updating (which turned out not to be the case).
Early this morning I did a monthly update and noticed that this included glibc. I've never had to do a glibc update in Slackware before (I assume it never happens in a release version) and so I was ultra-cautious. I unchecked glibc and did the update without it.
Then I ran slackpkg upgrade-all again. The ncurses interface now showed only one package, the normal glibc. At the bottom I could see a line of text with two packages named: glibc and glibc-multilib. Obviously it was the second one I wanted but only the first showed up in ncurses. So I said yes and it upgraded smoothly but my multilib setup is gone. Not that that's a problem; I'll reinstall it down the line when we finally have a stable release. But obviously I did something wrong because I didn't get the result I really wanted. So what should I have done?
I have a partial Slackware-current system on /dev/sda10, which I regard as my new Slackware-15. I installed glibc-multilib on it because I will eventually need 32-bit glibc for my printer. I have the multilib repo uncommented in slackpkgplus.conf and I also have glibc blacklisted because I hoped this would force slackpkg to use the multilib version for updating (which turned out not to be the case).
Early this morning I did a monthly update and noticed that this included glibc. I've never had to do a glibc update in Slackware before (I assume it never happens in a release version) and so I was ultra-cautious. I unchecked glibc and did the update without it.
Then I ran slackpkg upgrade-all again. The ncurses interface now showed only one package, the normal glibc. At the bottom I could see a line of text with two packages named: glibc and glibc-multilib. Obviously it was the second one I wanted but only the first showed up in ncurses. So I said yes and it upgraded smoothly but my multilib setup is gone. Not that that's a problem; I'll reinstall it down the line when we finally have a stable release. But obviously I did something wrong because I didn't get the result I really wanted. So what should I have done?