Bug 478726 – difficulties with the 2.2.0_alpha190

• Status: VERIFIED FIXED
• Product: Portage Development

[Description Mike Hiretsky 2013-07-30 04:49:02 UTC]

portage-2.2.0_alpha190.ebuild contains code which creates
"/etc/portage/repos.conf/._cfg0000_gentoo.conf" in spite of existence
of the file /etc/portage/repos.conf/gentoo.conf. Can you
disable the creating ._cfg0000 file
if /etc/portage/repos.conf/gentoo.conf already exists.

We use portage throught "git" and portage update has broke "emerge --sync".

[Comment 1 Zac Medico 2013-07-30 04:55:41 UTC]

You are free to discard or modify /etc/portage/repos.conf/._cfg0000_gentoo.conf as necessary to fit your needs. So, I don't see a reason to change anything about the portage ebuild.

[Comment 2 Mike Hiretsky 2013-07-30 06:06:27 UTC]

Automatic using of dispatch-conf with "use new" option by default will break "emerge --sync". 
Our distribute Calculate Linux based by Gentoo provides utilities for automatic stage building. Some users are using this will have problem.
The question is: Can you disable creating ._cfg at the existsing gentoo.conf or disabling can cause problems and we disable creating throught profile.bashrc?

[Comment 3 Zac Medico 2013-07-30 06:20:16 UTC]

(In reply to Mike Hiretsky from comment #2)
> Automatic using of dispatch-conf with "use new" option by default will break
> "emerge --sync". 

You're supposed to review the ._cfg updates before accepting them. Why would you blindly accept the config update?

> Our distribute Calculate Linux based by Gentoo provides utilities for
> automatic stage building. Some users are using this will have problem.

Can't you just explain to them that they need to review the config updates?

> The question is: Can you disable creating ._cfg at the existsing gentoo.conf
> or disabling can cause problems and we disable creating throught
> profile.bashrc?

I guess it's probably safe to disable the ._cfg creation if the file already exists. However, I'm curious about the reasons why people would want to blindly accept config updates.

[Comment 4 Mike Hiretsky 2013-07-30 06:45:06 UTC]

(In reply to Zac Medico from comment #3)

> You're supposed to review the ._cfg updates before accepting them. Why would
> you blindly accept the config update?
> Can't you just explain to them that they need to review the config updates?

Typically, users do not pay attention to the config update that users did not change. Therefore, they will apply it blindly.

[Comment 5 Mike Hiretsky 2013-07-30 06:54:18 UTC]

As alternate disabling: transfer sync-type from /usr/share/portage/config/repos.conf instead hard value "rsync".

[Comment 6 Zac Medico 2013-07-30 07:09:29 UTC]

In 2.1.13.2 and 2.2.0_alpha191 it skips creating the .cfg file if /etc/portage/repos.conf/gentoo.conf exists.

[Comment 7 Zac Medico 2013-07-30 18:39:55 UTC]

I've also updated the ebuild to detect git:// in the SYNC variable and set sync-type = git in that case.

[Comment 8 Mike Hiretsky 2013-07-31 06:59:35 UTC]

Thanks, everything works.