Summary: | /etc/portage/package.use : no update after package move | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | CC: | stian |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
![]() This would be a user-error. You can make any virtual-entries here of your own-wish that does not really exists. However, when a profile-change renames a packes, does it upgrade this file? net-www/tomcat might be a valid package. The package was moved from net-www to www-servers. So I think portage should update the files in /etc/portage/. That I agree on. Change the summary to affect that issue instead, and reopen the bug. Sure you didn't ignore/skip an etc-update? Reopended with new summary @Stian: done @Marius: there is no .cfg* file tfoerste@nhh221 ~ $ ls -al /etc/portage/ total 20 drwxr-xr-x 3 root portage 58 Feb 14 11:10 . drwxr-xr-x 91 root root 8192 Feb 15 09:56 .. -rw-r--r-- 1 root root 265 Feb 6 18:00 package.keywords -rw-r--r-- 1 root root 90 Feb 14 11:10 package.use drwxrwsr-x 2 root portage 6 Oct 21 12:52 sets tfoerste@nhh221 ~ $ Portage does update the files. It creates ._cfg* entries for any matching file in /etc/portage/ that will then be picked up by etc-update or dispatch-conf. If this did not happen, you are either using an old portage or you ignored the update. |