Gentoo Archives: gentoo-user

From: Davyd McColl <davydm@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Heads Up - switching to profile 17.1 is not as easy as it sounds
Date: Tue, 11 Jun 2019 12:43:51
Message-Id: CAJjP=BsZJRvG+kva76x504=QFjCM3VZhGk6G_Xr04xi8arXa3A@mail.gmail.com
In Reply to: Re: [gentoo-user] Heads Up - switching to profile 17.1 is not as easy as it sounds by Rich Freeman
1 On Tue, 11 Jun 2019 at 14:23, Rich Freeman <rich0@g.o> wrote:
2
3 > On Tue, Jun 11, 2019 at 7:21 AM Davyd McColl <davydm@×××××.com> wrote:
4 > >
5 > > On Tue, 11 Jun 2019 at 12:34, Helmut Jarausch <jarausch@××××××.be>
6 > wrote:
7 > >>
8 > >> I had some trouble switching to the new profile 17.1.
9 > >> Following the advice in the news item didn't suffice.
10 > >>
11 > >
12 > > first off, `emerge -v1 /lib /lib32` didn't work out because I had an old
13 > library in there I
14 > > had to remove with `emerge --depclean` first. I also have an old install
15 > of sickbeard, which
16 > > I had to remove from world for the same reason: `emerge -v1 /lib /lib32`
17 > would just complain
18 > > about not being able to find an installable source (my words -- can't
19 > remember the original
20 > > terms), but it didn't really look like an error -- all green text.
21 >
22 > I've updated two hosts. One went very smoothly, but it is a fairly
23 > dedicated host. One had a few issues, and it has a LOT of history.
24 >
25 > I found that anything 32-bit tended to cause more trouble, and I had a
26 > few orphans as well. It wasn't a huge deal.
27 >
28 > I think a big part of that is that before I did ANYTHING I took a lot
29 > of steps to clean up. I ran depclean and revdep-rebuild as a start.
30 > I reviewed all the migration tool output and anything that looked
31 > non-essential was depcleaned. When I did the 32-bit rebuild anything
32 > that was giving me trouble was traced back to whatever pulled it in
33 > and depcleaned (I forget if I did that up-front or if I just deleted
34 > the offending library and depcleaned the rev dep later - obviously
35 > don't do that for anything you care about).
36 >
37 > On a more dedicated host/container/etc I suspect you won't have many
38 > issues, because you're not going to have a huge pile of legacy stuff
39 > lying around with complicated dependency relationships.
40 >
41 > Some of my rebuild and depclean issues were resolved with --backtrack
42 > and --with-bdeps=y.
43 >
44 > In general a good principle is that anytime you want to change
45 > profiles take some time to do some housekeeping. The less junk you
46 > have on your system, the less there is that can go wrong.
47 >
48 > On my one host I also took the opportunity to decide whether I REALLY
49 > needed wine. That is a TON of 32-bit stuff you otherwise probably
50 > don't need. After removing it you need to clean out package.use
51 > because we don't have soft USE dependencies yet.
52 >
53 > And of course before I did anything I took a zfs snapshot of my root
54 > filesystem which only contains the OS for the most part. So, if I ran
55 > into serious issues a rollback would probably have been a one-liner
56 > (I'm guessing that I'd do that from a rescue disk just to keep daemons
57 > with stuff in /var from going nuts).
58 >
59 > Overall it went better than I was anticipating actually. We haven't
60 > had a migration like this one in a while, but I do think that the
61 > risk-level of this one was a bit undersold. Restructuring all your
62 > libraries is obviously a risky task and while you shouldn't be
63 > alarmist it is something that has a lot of potential to go wrong. To
64 > be fair, the news item does say that you should do a backup.
65 >
66
67 I guess YMMV. I regularly:
68 - emerge --sync
69 - emerge --update --newuser --deep @world @preserved-rebuild -a
70 - emerge --depclean -a
71 (by regularly, I mean at least twice a week). If I uninstall anything, I
72 clean out
73 package.{use|accept_keywords|licence} where appropriate. AFAIK I followed
74 the news item pedantically, following it step-by-step until I got to
75 re-merging /lib32
76 & /usr/lib32, when things came a little unstuck.
77
78 Doesn't mean I'm couldn't miss something, just that I'm not leaving this
79 machine out-of-date for months at a time or expecting miracles. I also had
80 to ditch `wine-any` (for now, at least). I _do_, however, have abi_x86_32
81 set
82 on for */*, which speaks to your point about "mo' 32-bit, mo' problems". I
83 run
84 Steam, so I expect to find enough 32-bit dependencies that if I know that a
85 requirement for libfoo _always_ includes the 32-bit artifact, I might have
86 an
87 easier time with some game I got on Humble Bundle. I also do use a small
88 number of overlays, but try to keep that to a minimum as common sense tells
89 me that many overlays is a quick way to get into trouble. I'll only use an
90 overlay
91 if I _really_ want/need something (like dotnet core).
92
93 I appreciate all the help and experience available from this list
94 and would appreciate any input on my updating procedures above,
95 in particular, anything which would have made this transition smoother.
96
97 Mostly, I find portage to be very capable, though it's taken me quite a
98 while
99 to make heads-or-tails of the error output, but I'm getting better at it.
100 Coming
101 from Debian or a derivative for around 16 years, I truly appreciate Gentoo
102 and
103 the freedom it provides, not to mention the community and help that I've
104 received.
105
106 -d
107
108
109 > --
110 > Rich
111 >
112 >
113
114 --
115 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
116 If you say that getting the money is the most important thing
117 You will spend your life completely wasting your time
118 You will be doing things you don't like doing
119 In order to go on living
120 That is, to go on doing things you don't like doing
121
122 Which is stupid.
123
124 - Alan Watts
125 https://www.youtube.com/watch?v=-gXTZM_uPMY
126
127 *Quidquid latine dictum sit, altum sonatur. *

Replies