Bug 485740 – =app-portage/eix-0.29.3 - Moved /etc/eixrc to /etc/eixrc.backup.0000 but there is no postinst message about that move.

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Bruce Hill 2013-09-23 13:52:08 UTC]

eix-0.29.3 removed the file /etc/eixrc for system-wide defaults without notification. That probably should have been done in a postinst message? The only way I knew of a change is when my status line choice in urxvt broke.

I read in /var/log/portage/elog/app-portage\:eix-0.29.3\:20130913-092213.log

Installation of a directory is blocked by a file:
  '/etc/eixrc'
This file will be renamed to a different name:
  '/etc/eixrc.backup.0000'

But after the upgrade there was nothing detected by "dispatch-conf".

[Comment 1 Bruce Hill 2013-09-23 14:21:38 UTC]

Also noticed that in /etc/eixrc/00-eixrc there is a typo in the title of the file.

mingdao@workstation ~ $ head -n1 /etc/eixrc/00-eixrc
# /etc/eixrc/00-eirc

should be /etc/eixrc/00-eixrc (r was omitted)

[Comment 2 Martin Väth 2013-09-23 15:07:04 UTC]

Since the move is done by portage this is a dupe of bug 471132.
I do not think that there is a reasonable solution without extending pms.

I will leave this bug open for a while so that other people running into it can see it, but later I will close a duplicate.

(The typo will be fixed with the next commit if I don't forget)

[Comment 3 Bruce Hill 2013-09-23 16:02:57 UTC]

Why would there not be a postinst message so that users know about the change?

[Comment 4 Martin Väth 2013-09-23 17:15:19 UTC]

(In reply to Bruce Hill from comment #3)
> Why would there not be a postinst message so that users know about the
> change?

It makes no sense in the ebuild: Portage reports about the move. Other package managers (paludis) do not move. Moreover, it would be an eternal message (or at least eternal code if the message is made conditional) in the ebuild, not only for this eix version but also for all future ones.

[Comment 5 Bruce Hill 2013-09-23 17:33:47 UTC]

(In reply to Martin Väth from comment #4)
> (In reply to Bruce Hill from comment #3)
> > Why would there not be a postinst message so that users know about the
> > change?
> 
> It makes no sense in the ebuild: Portage reports about the move. Other
> package managers (paludis) do not move. Moreover, it would be an eternal
> message (or at least eternal code if the message is made conditional) in the
> ebuild, not only for this eix version but also for all future ones.

Sorry I didn't know that. Where does portage report about the move? I found out when I started investigating after my vt's title broke.

[Comment 6 Martin Väth 2013-09-24 06:59:20 UTC]

The portage message is shown in the first comment of bug 471132

[Comment 7 Michael Weber (RETIRED) 2017-02-10 00:19:22 UTC]

no longer in tree