I'm using portage-2.0.49. I've noticed that when a package is renamed after a sync (today example was app-misc/Welcome2L --> app-misc/welcome2l), what portage does is basically: mv /var/db/pkg/app-misc/Welcome2L-xxx /var/db/pkg/app-misc/welcome2l-xxx This is enough from portage point of view, but disturbes utilities like 'qpkg', which are based on the names of the ebuilds that are in in the db. For instance, after the above described move, I still get: # qpkg -nc -I Welcome app-misc/Welcome2L which is no more a valid pkg name. This is an issue that qpkg or other such scripts output some wrong pkg names, because one can sometimes use this output to feed an emerge command, or things like that. I will submit a small patch which adds ebuild renaming to the move_ent function. Reproducible: Always Steps to Reproduce:
Created attachment 16560 [details, diff] portage-2.0.49--rename_ebuilds.patch patch is against portage.py from portage-2.0.49.
Patch doesn't apply, and portage doesn't use the ebuild.
