[gentoo-user] Portage just unmerged my openrc

[gentoo-user] Portage just unmerged my openrc

[Alan Mackenzie]

Hello, Gentoo.

Portage has just unmerged my openrc-0.34.11.  I didn't ask it to.  I'm
not very happy about this.

I did 

    # emerge -auND @world

, and after dealing with five packages, it just warned me that openrc
was a critical system package, then went ahead and unmerged it.

I presume that if I'd tried to reboot, I would have failed.  I've
manually emerged openrc again (version 0.42.1), and it looks like it
will work, but I haven't tried it yet.

What's up with Gentoo at the moment?  Uninstalling system critical
packages automatically is a big deal, and shouldn't happen.

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Portage just unmerged my openrc

[Rich Freeman]

On Tue, May 12, 2020 at 2:47 PM Alan Mackenzie <acm@muc.de> wrote:
>
> Portage has just unmerged my openrc-0.34.11.  I didn't ask it to.

Did you change any config files/etc recently?  You may have asked it
to without realizing it or intending to (computers are of course very
literal).

Full outputs on commands might also be useful to troubleshoot.

Even if you use systemd it is actually hard to get rid of openrc -
generally you have to mask it to force it to not install.

If you stuck it in package.provided or something like that then you
might get this result.  You can get portage to uninstall anything that
way, and of course the results on a reboot will not be pretty.

-- 
Rich

Re: [gentoo-user] Portage just unmerged my openrc

[Michael]

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

On Tuesday, 12 May 2020 19:47:21 BST Alan Mackenzie wrote:
> Hello, Gentoo.
> 
> Portage has just unmerged my openrc-0.34.11.  I didn't ask it to.  I'm
> not very happy about this.
> 
> I did
> 
>     # emerge -auND @world
> 
> , and after dealing with five packages, it just warned me that openrc
> was a critical system package, then went ahead and unmerged it.
> 
> I presume that if I'd tried to reboot, I would have failed.  I've
> manually emerged openrc again (version 0.42.1), and it looks like it
> will work, but I haven't tried it yet.
> 
> What's up with Gentoo at the moment?  Uninstalling system critical
> packages automatically is a big deal, and shouldn't happen.

I can't see how 'emerge -auND @world' would unmerge any package, let alone a 
@system package, without first emerging a later version.  Have you messed up 
with your make.profile symlink by any chance?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Portage just unmerged my openrc

[Alan Mackenzie]

Hello, Rich.

On Tue, May 12, 2020 at 15:02:23 -0400, Rich Freeman wrote:
> On Tue, May 12, 2020 at 2:47 PM Alan Mackenzie <acm@muc.de> wrote:

> > Portage has just unmerged my openrc-0.34.11.  I didn't ask it to.

> Did you change any config files/etc recently?  You may have asked it
> to without realizing it or intending to (computers are of course very
> literal).

My last change in /etc/portage was on 2020-04-25, to
package.accept-keywords.  I've emerged loads of times since then.  In
package.mask/openrc, I've had the following line since 2015:

    <sys-apps/openrc-0.13.0

.  This shouldn't do anything.

> Full outputs on commands might also be useful to troubleshoot.

I don't think I've got that any more.  I've had a look in
/var/log/emerge.log, and there's just records of which versions of
packages are emerged and unmerged and when, but not why or how.

> Even if you use systemd it is actually hard to get rid of openrc -
> generally you have to mask it to force it to not install.

I don't use systemd.

> If you stuck it in package.provided or something like that then you
> might get this result.  You can get portage to uninstall anything that
> way, and of course the results on a reboot will not be pretty.

I've grepped through all files in /etc/portage, but there's only the one
very old mention of openrc (see above) in them.

Might openrc-0.34.11 have been dependent on Python 2.7, and that's why
it was swept away?

I'm mystified, and somewhat unsettled.

> -- 
> Rich

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] Portage just unmerged my openrc

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]

Alan Mackenzie wrote:
> Hello, Rich.
>
> On Tue, May 12, 2020 at 15:02:23 -0400, Rich Freeman wrote:
>> On Tue, May 12, 2020 at 2:47 PM Alan Mackenzie <acm@muc.de> wrote:
>>> Portage has just unmerged my openrc-0.34.11.  I didn't ask it to.
>> Did you change any config files/etc recently?  You may have asked it
>> to without realizing it or intending to (computers are of course very
>> literal).
> My last change in /etc/portage was on 2020-04-25, to
> package.accept-keywords.  I've emerged loads of times since then.  In
> package.mask/openrc, I've had the following line since 2015:
>
>     <sys-apps/openrc-0.13.0
>
> .  This shouldn't do anything.


Actually, I think that does a lot.  Essentially, that masks any version
of openrc above that version.  Even that version is no longer in the
tree and no version below that is in the tree either.  This is what I
get here:


root@fireball / # equery list -p openrc
 * Searching for openrc ...
[-P-] [  ] sys-apps/openrc-0.41.2:0
[IP-] [  ] sys-apps/openrc-0.42.1:0
[-P-] [ -] sys-apps/openrc-9999:0
root@fireball / #


It would seem to me that openrc has been masked.  If that is meant to do
nothing, I'd remove it.  There is also a eix command that will search
for and list unneeded entries in those files.  I run it on occasion
myself, when I think about it or run into cruft that doesn't need to be
there anymore. 

Unless I'm reading that wrong, that could cause a problem.


Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 2394 bytes --]

Re: [gentoo-user] Portage just unmerged my openrc

[Matt Connell (Gmail)]

On 2020-05-12 14:36, Dale wrote:
> Actually, I think that does a lot.  Essentially, that masks any version
> of openrc above that version.

I believe you have it backwards, that should mask any version prior to 
(a version number less than) 0.13.0

> There is also a eix command that will search
> for and list unneeded entries in those files.I run it on occasion
> myself, when I think about it or run into cruft that doesn't need to be
> there anymore.

Can you share this?  I could definitely stand to clean up some portage 
cruft.
> Unless I'm reading that wrong, that could cause a problem.

I have this file as well, with no openrc problems.  I believe (without 
checking) that it is part of the stage3 install.

Re: [gentoo-user] Portage just unmerged my openrc

[Rich Freeman]

On Tue, May 12, 2020 at 3:25 PM Alan Mackenzie <acm@muc.de> wrote:
>
> Might openrc-0.34.11 have been dependent on Python 2.7, and that's why
> it was swept away?

openrc does not depend on python.  In any case, python-2.7 isn't going
anywhere right away anyway.

-- 
Rich

Re: [gentoo-user] Portage just unmerged my openrc

[Dale]

Matt Connell (Gmail) wrote:
> On 2020-05-12 14:36, Dale wrote:
>> Actually, I think that does a lot.  Essentially, that masks any version
>> of openrc above that version.
>
> I believe you have it backwards, that should mask any version prior to
> (a version number less than) 0.13.0

Ahh, I do sometimes get those backwards.  To me, it is a pointer or what
I use to indicate a action on my part, such as.  <big grin> or <smacks
forehead>


>
>> There is also a eix command that will search
>> for and list unneeded entries in those files.I run it on occasion
>> myself, when I think about it or run into cruft that doesn't need to be
>> there anymore.
>
> Can you share this?  I could definitely stand to clean up some portage
> cruft.

The command is:

eix-test-obsolete

If you are like me, it will spit out a whole lot of stuff.  Keep in
mind, some you may want to keep and will need to ignore but some you may
can remove.  Example.  I run unstable KDE.  However, if the version I'm
using is stable, it spits out that it is no longer needed.  Thing is,
when I sync later and a new unstable version is available, I need those
entries to be able to install the unstable version.  You just have to
look at what it says and recall why you have that entry to be sure you
want to remove it.


>> Unless I'm reading that wrong, that could cause a problem.
>
> I have this file as well, with no openrc problems.  I believe (without
> checking) that it is part of the stage3 install.
>
>
>


Since it no longer does anything, I'd remove it just to get rid of the
hit in searches.  After all, I don't think the devs will putting a
version that old back in the tree as a fix for anything.  ;-) 

Dale

:-)  :-)