Summary: | emerge xine-lib requires manual unmerge of previous version | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Per Cederberg <per> |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | axxo |
Priority: | High | ||
Version: | 1.4_rc2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 4698 | ||
Bug Blocks: |
you get this message already from ebuild. Well, my point was that the ebuild shouldn't push this on to the user. All other ebuilds uninstall /after/ a sucessful emerge. If the emerge fails for some other reason, the user will end up without any version of xine-lib installed, which is annoying at best. Is there a good reason for xine-lib being different from other libraries? a) it's not stable b) it's itself a beta would be fixed if xine-lib gets stable *** Bug 27296 has been marked as a duplicate of this bug. *** wrangler Moving to SLOT=1. Closes #19409. |
When performing a "emerge -u xine-ui" I get an error that requires me to manually unmerge the previous version of xine-lib. I already have version 0.9.13-r2 of xine-lib installed, which was the stable version when I updated xine-ui previously. Reproducible: Always Steps to Reproduce: emerge -C xine-lib emerge =xine-lib-0.9.13-r2 emerge -u xine-lib Actual Results: The following error message is presented: >>> md5 ;-) xine-lib-1-beta10.tar.gz >>> Unpacking source... >>> Unpacking xine-lib-1-beta10.tar.gz to /var/tmp/portage/xine-lib-1_beta10/work >>> Source unpacked. * Please uninstall older xine libraries. * The compilation cannot procede. !!! ERROR: media-libs/xine-lib-1_beta10 failed. !!! Function src_compile, Line 52, Exitcode 0 !!! (no error message) Expected Results: The standard ebuild behaviour seems to be uninstalling /after/ a successful installation of the new version. By performing a "emerge -C xine-lib" before the update, this problem disappears.