Re: [gentoo-user] Update After A Year
Tamas Sarga wrote: Hi, I moved from my flat a year ago, and now I' went back. At my temporary place I wasn't be able to reach the internet, so I didn't update the system. Now I'd like to update it. Should I do anything special in addition to an emerge -e system; emerge -e world? Are there anything I should attend to? TIA, Tamas Sarga emerge --sync then hope for the best with the emerge -uvDN world. Don't forget to search the forums for any problems you run into. Most of them will be answered by now I would think. I'm sure you will run into at least a few issues. You may want to just update portage after you do the sync up then update world. A new portage should update better. Hope it goes well. Dale :-) :-) -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Update After A Year
On Thursday 10 January 2008, Tamas Sarga wrote: Hi, I moved from my flat a year ago, and now I' went back. At my temporary place I wasn't be able to reach the internet, so I didn't update the system. Now I'd like to update it. Should I do anything special in addition to an emerge -e system; emerge -e world? Are there anything I should attend to? Generally you can just emerge -uND world and we done with it. But life isn't always so simple. I can think of a few updates in the last while that were problematic, but I think they were all more than a year ago: Xorg 6.x - 7.x - there's wiki pages for that at gentoo-wiki.com gcc-3.3.x - 3.4.x - check gentoo.org/docs for the full info glibc-2.3 - 2.4 - there was something about that too, I forget... The update to python-2.5 had a specific procedure (?) And there was a portage update as well with a change in on-disk format. This one caught me, as an upgrade path was maintained for several versions, then dropped. My upgrade fell in that window. But that was way back in the early 2.0 versions, I think you will be safe. Oddly, kde-3.5.7 to 3.5.8 recently was a pain for me. I hadn't updated in two months and the first emerge world failed about 8 times, all on kde stuff. It felt as if the DEPENDS were evaluated in the wrong order as emerge --resume --skipfirst allowed it to continue. Then I would emerge world again with less failures, and do it again. IIRC it took 4 runs thorough, but once it was done everything did seem to work correctly. With long intervals between updates like you have here, I prefer to make a quickpkg of vital system stuff (gcc, glibc, python, portage, bash) as a safety measure, then run emerge -pvuND system and update those vital packages manually - the reason is to force me to look at the portage output and not miss important messages. Then emerge the rest of system followed by the rest of world. It's the long way round but it gives me the warm fuzzy safety net feeling. -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Update After A Year
On Thu, 10 Jan 2008 12:57:57 +0200, Alan McKinnon wrote: Generally you can just emerge -uND world and we done with it. But life isn't always so simple. I can think of a few updates in the last while that were problematic, but I think they were all more than a year ago: The expat upgrade was less than a year ago for stable systems. I'd go with emerge -auvDN system and check the output carefully before opting to proceed. I'd also make sure that ELOG is correctly set up in make.conf so you don't miss any important massages. After updating system, it would be prudent to run revdep-rebuild before moving onto the rest of world. emerge -e is pointless, portage is quite capable of determining what needs to be updated, and reemerging everything just creates noise and confusion that could make it harder to deal with any potential problems. -- Neil Bothwick Any connection between your reality and mine is purely coincidental. signature.asc Description: PGP signature
Re: [gentoo-user] Update After A Year
It's been much less than a year since I've updated last, however I'm experiencing problems updating my system. First off, I have Gentoo 2007.0 installed on an AMD64 X2 3800+ (SMP kernel.) I cannot upgrade PAM from 0.99.8.1-r1 to 0.99.9.0. The output of trying to do so is the following: emerge pam Calculating dependencies... done! Verifying ebuild Manifests... Emerging (1 of 1) sys-libs/pam-0.99.9.0 to / * Linux-PAM-0.99.9.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ...[ ok ] * checking Linux-PAM-0.99.9.0.tar.bz2 ;-) ...[ ok ] * * Your current setup is using one or more of the following modules, * that are not built or supported anymore: * pam_pwdb, pam_radius, pam_timestamp, pam_console * If you are in real need for these modules, please contact the maintainers * of PAM through http://bugs.gentoo.org/ providing information about its * use cases. * Please also make sure to read the PAM Upgrade guide at the following URL: * http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml * 'emerge --search pam' returns the following (I'm only going to include the actual listing for pam, and not all the other stuff it lists to keep the list short) * sys-libs/pam Latest version available: 0.99.9.0 Latest version installed: 0.99.8.1-r1 Size of files: 887 kB Homepage: http://www.kernel.org/pub/linux/libs/pam/ Description: Linux-PAM (Pluggable Authentication Modules) License: PAM I've followed the Linux-PAM upgrade guide, which didn't mention what to do in the event that those modules were used. http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml There is a forum discussion on this matter, however none of the modules appear in /etc/pam.d/ files... I don't know enough about PAM and Gentoo to know if running a PAMless system would cause problems, I have been using linux for a while, but I am relatively new to Gentoo (and yes, I realize that PAM is not exclusive to Gentoo...) I've tried the #gentoo channel on FreeNode and after an hour of asking and waiting, was unable to receive an answer. Any help would be appriciated. Thanks! Hal Martin Neil Bothwick wrote: On Thu, 10 Jan 2008 12:57:57 +0200, Alan McKinnon wrote: Generally you can just emerge -uND world and we done with it. But life isn't always so simple. I can think of a few updates in the last while that were problematic, but I think they were all more than a year ago: The expat upgrade was less than a year ago for stable systems. I'd go with emerge -auvDN system and check the output carefully before opting to proceed. I'd also make sure that ELOG is correctly set up in make.conf so you don't miss any important massages. After updating system, it would be prudent to run revdep-rebuild before moving onto the rest of world. emerge -e is pointless, portage is quite capable of determining what needs to be updated, and reemerging everything just creates noise and confusion that could make it harder to deal with any potential problems.
Re: [gentoo-user] Update After A Year
On 10 Jan 2008, at 23:45, Hal Martin wrote: ... * Your current setup is using one or more of the following modules, * that are not built or supported anymore: * pam_pwdb, pam_radius, pam_timestamp, pam_console ... I'm not sure if I should be replying to this, as it kinda looks like a thread hijack, but: $ equery b `grep -l -ie pwdb -ie radius -ie timestamp -ie console / etc/pam.d/*` [ Searching for file(s) /etc/pam.d/login in *... ] sys-apps/shadow-4.0.18.1-r1 (/etc/pam.d/login) $ Stroller.
Re: [gentoo-user] Update After A Year
On 11 Jan 2008, at 01:17, Stroller wrote: On 10 Jan 2008, at 23:45, Hal Martin wrote: ... * Your current setup is using one or more of the following modules, * that are not built or supported anymore: * pam_pwdb, pam_radius, pam_timestamp, pam_console ... I'm not sure if I should be replying to this, as it kinda looks like a thread hijack, but: $ equery b `grep -l -ie pwdb -ie radius -ie timestamp -ie console /etc/pam.d/*` [ Searching for file(s) /etc/pam.d/login in *... ] sys-apps/shadow-4.0.18.1-r1 (/etc/pam.d/login) $ Ooops! Pressed send too hastily! I assumed that there'd be an update available to shadow which would fix this, but looking closer at the output of `grep -l -ie pwdb -ie radius -ie timestamp -ie console /etc/pam.d/*` it seems that the line containg `pam_console.so` is commented out on my system: # If you want to enable pam_console, uncomment the following line # and read carefully README.pam_console in /usr/share/doc/pam* #sessionoptionalpam_console.so So the question arises, did you uncomment it? Or is your sys-apps/shadow just older than mine? What does `grep -l -ie pwdb -ie radius -ie timestamp -ie console /etc/ pam.d/* actually say on your machine? Stroller.
Re: [gentoo-user] Update After A Year
Stroller wrote: Ooops! Pressed send too hastily! I assumed that there'd be an update available to shadow which would fix this, but looking closer at the output of `grep -l -ie pwdb -ie radius -ie timestamp -ie console /etc/pam.d/*` it seems that the line containg `pam_console.so` is commented out on my system: # If you want to enable pam_console, uncomment the following line # and read carefully README.pam_console in /usr/share/doc/pam* #sessionoptionalpam_console.so So the question arises, did you uncomment it? Or is your sys-apps/shadow just older than mine? What does `grep -l -ie pwdb -ie radius -ie timestamp -ie console /etc/pam.d/* actually say on your machine? I will also participate on this thread hijack (but Hal, don't hijack anymore. It makes your mom angry!) I would actually check more than just /etc/pam.d/* if you don't find it there because it's possible for mail servers or web servers to use these things the old way too! -- Randy Barlow http://electronsweatshop.com -- gentoo-user@lists.gentoo.org mailing list
