Anything that pertains to Portage
- Sagely Hen
- Posts: 8092
- Joined: Sat Mar 10, 2007 5:40
- Location: United Kingdom
Recently, when I "emerge -u" any package, the number of config files reported at the end of the emerge as needing to be updated is one greater than the actual number of modified config files. For example:
Code: Select all
* IMPORTANT: 3 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
localhost / # find /etc -iname '._cfg????_*'
localhost / #
Notice in the above example that emerge told me that 3 config files in /etc have to be updated but in fact the find command only found 2 modified config files.
This phenomenon only started recently. Is anyone else experiencing this?
- Technological Hen
- Posts: 331
- Joined: Tue Aug 22, 2006 23:56
- Location: Northeastern Ohio
I observed the same problem in Sabayon v3.4a after updating to portage v18.104.22.168. Since installing Sabayon v3.4e I've avoided portage v22.214.171.124 and have had no problems. "emerge --help config" works in v126.96.36.199, as does the "find /etc -iname '._cfg????_*'"
It's obvious that the latest version of portage has a few bugs.
Former Sabayon user (2005 - 2013) and current Arch user.
I liked Sabayon until it switched to Rigo and becoming the gentoo equivalent of Ubuntu. Extreme browsing? Extreme gaming? Extreme work? Extreme development? Like, totally gnarly, dude!
- Old Dear Hen
- Posts: 742
- Joined: Mon Jul 09, 2007 20:29
- Location: Mobile, AL, USA
Yep, I've noticed the same problem also.
- Growing Hen
- Posts: 162
- Joined: Wed Oct 04, 2006 18:12
- Location: Germany