[pkgcore] #244: unmerge-orphans feature ignored
pkgcore
----------------------+-------------------
Reporter: bldewolf | Owner:
Type: defect | Status: new
Priority: normal | Milestone: 0.6+
Component: pkgcore | Version: 0.6.4
Keywords: |
----------------------+-------------------
It appears that the unmerge-orphans feature is ignored by pmerge when
uninstalling packages. This causes pmerge to exhibit potentially
disastrous behavior when compared to emerge.
For example, when upgrading to openrc, some of the files owned by openrc
were previously part of baselayout. If baselayout is upgraded, important
modified files in /etc are removed, such as /etc/conf.d/hostname and
/etc/conf.d/net, which could potentially prevent the host from getting on
the network on its next boot (when openrc does get installed, it places
the default versions of these files, thus somewhat circumventing the
intended behavior of CONFIG_PROTECT).
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/244>
pkgcore <http://www.pkgcore.org/trac/pkgcore>
pkgcore package manager
pkgcore
-----------------------+-------------------
Type: defect | Status: new
Priority: normal | Milestone: 0.6+
Component: pkgcore | Version: 0.6.4
-----------------------+-------------------
Comment (by bldewolf):
The title is misleading, actually. I think this may just be that
CONFIG_PROTECT is ignored during an unmerge, which is poor behavior. The
behavior of emerge and the description of unmerge-orphans implies that
CONFIG_PROTECT'ed files should never be removed on unmerge, but pmerge
does so anyway.
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/244#comment:1>
pkgcore
-----------------------+-------------------
Type: defect | Status: new
Priority: normal | Milestone: 0.6+
Component: pkgcore | Version: 0.6.4
-----------------------+-------------------
Comment (by ferringb):
unmerge-orphans is on by default (it was a pkgcore feature first after all
;); CONFIG_PROTECT likely isn't the cause either, although please paste
the output of pinspect portageq envvar CONFIG_PROTECT{,_MASK}.
guessing the upgrade pathway just sucks, but lets see...
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/244#comment:2>
pkgcore
-----------------------+-------------------
Type: defect | Status: new
Priority: normal | Milestone: 0.6+
Component: pkgcore | Version: 0.6.4
-----------------------+-------------------
Comment (by bldewolf):
{{{
# pinspect portageq envvar CONFIG_PROTECT{,_MASK}
('/etc',)
('/etc/env.d', '/etc/gconf')
}}}
The effect of an unmerge and an upgrade appear to be the same (files that
should be config protected are not).
And sorry for bungling the title of this ticket. :)
--
Ticket URL: <http://www.pkgcore.org/trac/pkgcore/ticket/244#comment:3>