| Summary: | Only slotmove supports version handlers, move should also. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Cort <linuxgeek> |
| Component: | Eclasses | Assignee: | PMS/EAPI <pms> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | enhancement | CC: | ciaran.mccreesh, cycoone, gentoo, jmbsvicetto, p, ulm |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
mee too It's fixed in CVS. Wait an hour or so before doing a sync again. To fix your system, replace /usr/portage/profiles/updates/2Q-2009 with the contents of the file in CVS which is found here: http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/profiles/updates/2Q-2009 Reopening to reassign to dev-portage. me2 @Josh and everyone else who is using the same mirrors: when a package changes category, we declare it in /usr/portage/profiles/updates/ file, with an entry saying move app/foo misc/foo. In this case we did a partial move of >=kde-base/konq-plugins-4 to kde-misc/konq-plugins. We wanted to declare it to portage in the above files, but then we realized that portage doesn't support >= in move, only in slotmove. We reverted the commit in about 5 minutes, i guess we are very unlucky that this hit some mirrors. As Thomas Cort said, to fix, either resync in a couple of hours, or fix it manually by editing /usr/portage/profiles/updates/2Q-2009 file and removing the move >=kde-base/konq-plugins-4 kde-misc/konq-plugins line. This bug is now a portage bug to support version handlers for move. Thanks and accept my apologies for the mess :) Thanks for clearing that up. :) *** Bug 272004 has been marked as a duplicate of this bug. *** a good bug report is nearly as good as not making the error. Good Job. *** Bug 272080 has been marked as a duplicate of this bug. *** Can we change the syntax of the updates files? They are not EAPI specific. Adding dev-portage to CC: Portage should handle malformed lines more gracefully, e.g. output an error message and ignore the line. It _shouldn't_ go haywire and block any further actions. When filing bugs that are really about portage we should start with the dev-portage@ alias vs going directly to PMS. Prove the idea with portage and other PM's will pick them up in due time. You mean "start using it in the tree, breaking everyone who isn't using Portage, and then rush to try to get it documented and standardised later, then when doing so realise the way it's been implemented isn't perfect but that we can't come up with a better solution now that it's already being used"? No progress since several years. Reopen only if you have a complete proposal how to achieve this, including a transition plan. |
I get an "InvalidPackageName: >=kde-base/konq-plugins-4" error when "Performing Global Updates: /usr/portage/profiles/updates/2Q-2009" Reproducible: Always Steps to Reproduce: 1. emerge --sync Actual Results: ... Performing Global Updates: /usr/portage/profiles/updates/2Q-2009 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' #='/var/db update' @='/var/db move' s='/var/db SLOT move' %='binary move' S='binary SLOT move' p='update /etc/portage/package.*' ......................... ERROR: Malformed update entry 'move >=kde-base/konq-plugins-4 kde-misc/konq-plugins' Traceback (most recent call last): File "/usr/bin/emerge", line 40, in <module> retval = _emerge.emerge_main() File "//usr/lib64/portage/pym/_emerge/__init__.py", line 15118, in emerge_main return action_sync(settings, trees, mtimedb, myopts, myaction) File "//usr/lib64/portage/pym/_emerge/__init__.py", line 12861, in action_sync if portage._global_updates(trees, mtimedb["updates"]): File "//usr/lib64/portage/pym/portage/__init__.py", line 7914, in _global_updates moves = vardb.move_ent(update_cmd) File "//usr/lib64/portage/pym/portage/dbapi/vartree.py", line 165, in move_ent raise InvalidPackageName(cp) InvalidPackageName: >=kde-base/konq-plugins-4 Expected Results: No error Now emerge --sync doesn't work anymore.... ainsworth ~ # emerge --sync Performing Global Updates: /usr/portage/profiles/updates/2Q-2009 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' #='/var/db update' @='/var/db move' s='/var/db SLOT move' %='binary move' S='binary SLOT move' p='update /etc/portage/package.*' ......................... ERROR: Malformed update entry 'move >=kde-base/konq-plugins-4 kde-misc/konq-plugins' Traceback (most recent call last): File "/usr/bin/emerge", line 40, in <module> retval = _emerge.emerge_main() File "//usr/lib64/portage/pym/_emerge/__init__.py", line 14830, in emerge_main if portage._global_updates(trees, mtimedb["updates"]): File "//usr/lib64/portage/pym/portage/__init__.py", line 7914, in _global_updates moves = vardb.move_ent(update_cmd) File "//usr/lib64/portage/pym/portage/dbapi/vartree.py", line 165, in move_ent raise InvalidPackageName(cp) InvalidPackageName: >=kde-base/konq-plugins-4 and `emerge --info` fails too :) ainsworth ~ # emerge --info Performing Global Updates: /usr/portage/profiles/updates/2Q-2009 (Could take a couple of minutes if you have a lot of binary packages.) .='update pass' *='binary update' #='/var/db update' @='/var/db move' s='/var/db SLOT move' %='binary move' S='binary SLOT move' p='update /etc/portage/package.*' ......................... ERROR: Malformed update entry 'move >=kde-base/konq-plugins-4 kde-misc/konq-plugins' Traceback (most recent call last): File "/usr/bin/emerge", line 40, in <module> retval = _emerge.emerge_main() File "//usr/lib64/portage/pym/_emerge/__init__.py", line 14830, in emerge_main if portage._global_updates(trees, mtimedb["updates"]): File "//usr/lib64/portage/pym/portage/__init__.py", line 7914, in _global_updates moves = vardb.move_ent(update_cmd) File "//usr/lib64/portage/pym/portage/dbapi/vartree.py", line 165, in move_ent raise InvalidPackageName(cp) InvalidPackageName: >=kde-base/konq-plugins-4 ainsworth ~ #