Re: [gentoo-user] Re: Update circle
On Saturday, 1 September 2018 11:35:49 BST Wols Lists wrote: > On 01/09/18 10:39, Peter Humphrey wrote: > >> I wish there was a portage option that said "don't give up, just emerge > >> > >> > what you can". > > > > There is: --keep-going > > There isn't ... > > "keep going" says "don't stop once you've started". What I want is > "start anyway". > > If emerge hits a load of dependency conflicts, it refuses to start > emerging. Instead of giving up, I want it to emerge anything that > doesn't conflict. Ah, now I understand. -- Regards, Peter.
Re: [gentoo-user] Re: Update circle
On 01/09/18 10:39, Peter Humphrey wrote: >> I wish there was a portage option that said "don't give up, just emerge >> > what you can". > There is: --keep-going > There isn't ... "keep going" says "don't stop once you've started". What I want is "start anyway". If emerge hits a load of dependency conflicts, it refuses to start emerging. Instead of giving up, I want it to emerge anything that doesn't conflict. Cheers, Wol
Re: [gentoo-user] Re: Update circle
On Saturday, 1 September 2018 09:35:46 BST Wol's lists wrote: > On 23/08/18 11:25, Adam Carter wrote: > > The machine is actually a server, which just sat in a corner doing > > its > > job perfectly. That's one of the reasons it wasn't updated: if it > > ain't > > broken, don't fix it. > > > > Any system that is not getting software updates is broken to some > > degree, just in a subtle way. > > > > Trimming your /var/lib/portage/world file and removing the trimmed > > packages can make the update less painful. I sometimes remove non-system > > packages I want, then reinstall again later to get through difficult > > upgrades. > > Bit late to the party, but yes this is normally my approach. > > If emerge lists a bunch of packages it thinks it can build, I explicitly > just update them (on several occasions that has "miraculously" cleared > the conflicts and the next global emerge just roars away). > > I wish there was a portage option that said "don't give up, just emerge > what you can". There is: --keep-going > If there are conflicts on something that doesn't appear crucial to the > system, I just "emerge -C" it, and make a note to put it back later. > > My current home system is like this one, well out of date, but I'm > planning to replace not fix it, because it's a multi-user system and > *relies* on kdm which has, iirc, been deprecated and is not in kde5. > Upgrading that is a task I do NOT fancy ... :-) Yes, the recommended replacement is sddm, which I'm having problems with at the moment, as in the thread "KDE reboot not preserving running applications" -- Regards, Peter.
Re: [gentoo-user] Re: Update circle
On 23/08/18 11:25, Adam Carter wrote: The machine is actually a server, which just sat in a corner doing its job perfectly. That's one of the reasons it wasn't updated: if it ain't broken, don't fix it. Any system that is not getting software updates is broken to some degree, just in a subtle way. Trimming your /var/lib/portage/world file and removing the trimmed packages can make the update less painful. I sometimes remove non-system packages I want, then reinstall again later to get through difficult upgrades. Bit late to the party, but yes this is normally my approach. If emerge lists a bunch of packages it thinks it can build, I explicitly just update them (on several occasions that has "miraculously" cleared the conflicts and the next global emerge just roars away). I wish there was a portage option that said "don't give up, just emerge what you can". If there are conflicts on something that doesn't appear crucial to the system, I just "emerge -C" it, and make a note to put it back later. My current home system is like this one, well out of date, but I'm planning to replace not fix it, because it's a multi-user system and *relies* on kdm which has, iirc, been deprecated and is not in kde5. Upgrading that is a task I do NOT fancy ... :-) Cheers, Wol
Re: [gentoo-user] Re: Update circle
On 08/23/2018 10:27 AM, Grant Edwards wrote: > On 2018-08-22, Zoltán Kócsi wrote: >> I have a Gentoo machine, which has not been updated for a while. Quite >> a long while, actually. > >> It seems that I'm kind of stuck. Wiping the disk and rebuilding the >> system from scratch is absolutely not an option, the existing (and >> running) system must be updated somehow. > > Doing a reinstall will probably be far less work and less disruption > for the machines user's. You don't have to "wipe the disk" to do a > re-install. Yeah. I would suggest after the back up then you simply clone the disk and perform the re-install on another computer or in a VM so that you can fiddle with things and then just swap out the drives vs having down-time for your users potentially for days if something goes wrong on the actual server. It is what I do for situations like this and it works great.
[gentoo-user] Re: Update circle
On 2018-08-22, Zoltán Kócsi wrote: > I have a Gentoo machine, which has not been updated for a while. Quite > a long while, actually. > It seems that I'm kind of stuck. Wiping the disk and rebuilding the > system from scratch is absolutely not an option, the existing (and > running) system must be updated somehow. Doing a reinstall will probably be far less work and less disruption for the machines user's. You don't have to "wipe the disk" to do a re-install. -- Grant Edwards grant.b.edwardsYow! You were s'posed at to laugh! gmail.com
Re: [gentoo-user] Re: Update circle
> > The machine is actually a server, which just sat in a corner doing its > job perfectly. That's one of the reasons it wasn't updated: if it ain't > broken, don't fix it. > Any system that is not getting software updates is broken to some degree, just in a subtle way. Trimming your /var/lib/portage/world file and removing the trimmed packages can make the update less painful. I sometimes remove non-system packages I want, then reinstall again later to get through difficult upgrades.
Re: [gentoo-user] Re: Update circle
On Wed, 22 Aug 2018 15:17:58 +0100 (Nuno Silva) wrote: > [...] > The biggest hurdle in your case is that you need to update tar. Do > what was already mentioned elsewhere in the thread, fetch the older > EAPI 5 ebuild, put it in the local overlay and let portage grab that. Thanks, I will try to do that. > [...] > Some recent issues were a change in the C++ ABI and the build system > change in certain X11-related packages that pulls python3 as a build > dependency. The machine is actually a server, which just sat in a corner doing its job perfectly. That's one of the reasons it wasn't updated: if it ain't broken, don't fix it. But the important thing is that it has no X11, pretty much nothing apart from the basic system and a handful of network daemons. Now it needs one more daemon and that started the whole exercise. Thanks, Regards, Zoltan
[gentoo-user] Re: Update circle
On 2018-08-22, Zoltán Kócsi wrote: > I have a Gentoo machine, which has not been updated for a while. Quite > a long while, actually. > > Now I needed to install a package, and I did so. It went up, no > problem. Except that it relies on a newer version of openrc than > what's on the system. From here it's all downhill: > > emerge openrc: > - Fails, as the current portage is EAPI 5 (whatever that is), thus all > EAPI 6 packages are masked. Must upgrade portage. > > emerge portage: > - Fails, as it needs tar-1.30 and the installed tar is 1.27. Must update > tar. > > emerge tar: > - Fails, as tar-1.30 needs EAPI 6. Must upgrade portage. > > It seems that I'm kind of stuck. Wiping the disk and rebuilding the > system from scratch is absolutely not an option, the existing (and > running) system must be updated somehow. > > I would appreciate any advice, I'm in complete darkness about the > internal workings of portage (would be happy to find some detailed docs > about that, by the way, preferably in PDF). > > Thanks in advance, > > Zoltan First, and before anything else: it can be done. You will have to deal with issues that are perhaps a bit more complex than the usual conflicts and issues that show up once in a while even on a stable system which is updated frequently. But it's definitely not impossible. The biggest hurdle in your case is that you need to update tar. Do what was already mentioned elsewhere in the thread, fetch the older EAPI 5 ebuild, put it in the local overlay and let portage grab that. If you're lucky, that might be the only problem you'll have. If you're not so lucky, you will have a couple packages that were since removed from the tree, and which must be either uninstalled or added to a local overlay and adjusted as required. (Because they might depend on older versions of other packages which do not exist anymore.) You will probably find some actual bugs too, for example, some packages may fail because their dependencies are not correct. When was the last time this system was fully updated/upgraded? (Not the last time you synced the tree, but the last time you did emerge -DuN world or the like.) This might be useful to figure out which issues are you going to find. Some recent issues were a change in the C++ ABI and the build system change in certain X11-related packages that pulls python3 as a build dependency. -- Nuno Silva
