Summary: | vmware-workstation-5.5.1-19175-r4 requires ~vmware-modules-1.0.0.13, but emerge world attempts to upgrade it | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Francois Chenier <belgix_oz> |
Component: | New packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | vmware+disabled |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 137422 | ||
Attachments: |
emerge --info
vmware-workstation-5.5.1.19175-r4.ebuild emerge --debug --pretend |
Description
Francois Chenier
2006-08-04 18:52:58 UTC
Hi Francois, You're correct, vmware-workstation-5.5.1-19175-r4 requires ~vmware-modules-1.0.0.13 and won't work with later versions, and you're also correct that portage should *not* be automatically upgrading this. Is this bug that portage is trying to upgrade you to vmware-modules-1.0.0.15? If that's the case please post as much more useful information as you can, such as what emerge command you're trying, any special settings in /etc/portage/package.* relating to vmware, whether you have any overlays that might be influencing vmware, things like that... I have presently installed on my laptop vmware-modules-1.0.0.13 vmware-workstation-5.5.1.19175-r4 which are working fine together. If I pretend to 'emerge world' I have this ... ***** belgix@edinburgh ~ $ emerge -p world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild U ] app-emulation/vmware-modules-1.0.0.15 [1.0.0.13] Unless I mask manually vmware-modules-1.0.0.15 in /etc/portage/package.mask, portage will upgrade automatically vmware-modules tomorrow morning at my next world update. Hmmm, that's is weird. I'll have a chat with portage guys and see if they can help me figure it out... Sorry for the spam, but someone reminded me to check whether you've got --deep or --update set as defaults for your emerge command? Please check your aliases, and also emerge --info to see if they're set anywhere. If so, it might be related to bug #13632... Created attachment 93502 [details]
emerge --info
Nothing unusual in my emerge --info (see attachment).
I just have ACCEPT_KEYWORD="~x86" and nothing specific to overlays in my /etc/make.conf file.
(TESTED) As expected, adding =app-emulation/vmware-modules-1.0.0.15 in my package.mask file fix my problem.
Created attachment 93506 [details]
vmware-workstation-5.5.1.19175-r4.ebuild
Just a question. Can you tell me why line 39 is
~app-emulation/vmware-modules-1.0.0.13
and not
=app-emulation/vmware-modules-1.0.0.13
in this ebuild ?
Ok, I'm gonna throw this over to the portage guys, to see if one of them can tell whether this is a known duplicate, or something else... In answer to your question, it's ~<version> rather than =<version> so that it still accepts <version>-r1 and <version>-r2, etc. Please attach emerge --pretend --debug output for the command that behaves improperly. Created attachment 93576 [details]
emerge --debug --pretend
Normally,
vmware-workstation-5.5.1.19175-r4
should block vmware-modules-1.0.0.15 because
vmware-workstation-5.5.1.19175-r4 requires =vmware-modules-1.0.0.13
Relevant info from the attachment ...
Parent: None
Depstring: app-emulation/vmware-workstation
Candidates: ['app-emulation/vmware-workstation']
ebuild: app-emulation/vmware-workstation-5.5.1.19175-r4
Exiting... None
Parent: None
Depstring: app-emulation/vmware-modules
Candidates: ['app-emulation/vmware-modules']
ebuild: app-emulation/vmware-modules-1.0.0.15
Parent: ebuild / app-emulation/vmware-modules-1.0.0.15 merge
Depstring: x11-misc/shared-mime-info kernel_linux? ( virtual/linux-sources ) kernel_linux? ( virtual/modutils ) sys-app$Candidates: ['sys-apps/sed', 'sys-apps/module-init-tools', 'sys-kernel/vanilla-sources', 'x11-misc/shared-mime-info', '$ ebuild: sys-apps/sed-4.1.5
ebuild: sys-apps/module-init-tools-3.2.2-r1
ebuild: sys-kernel/vanilla-sources-2.6.18_rc3
ebuild: x11-misc/shared-mime-info-0.18-r1
ebuild: sys-apps/portage-2.1.1_pre4-r3
Exiting... ebuild / app-emulation/vmware-modules-1.0.0.15 merge
Exiting... None
(In reply to comment #9) > Parent: None > Depstring: app-emulation/vmware-modules > Candidates: ['app-emulation/vmware-modules'] > ebuild: app-emulation/vmware-modules-1.0.0.15 The "Parent: None" indicates that app-emulation/vmware-modules is in your world set or it's pulled in as a PDEPEND of some package. Most likely, you have it listed in /var/lib/portage/world. > The "Parent: None" indicates that app-emulation/vmware-modules is in your
> world set or it's pulled in as a PDEPEND of some package. Most likely, you
> have it listed in /var/lib/portage/world.
>
I see nothing wrong with this. Both packages are installed in my laptop.
(In reply to comment #11) > I see nothing wrong with this. Both packages are installed in my laptop. If it's in the world set, you're going to experience bug #13632. There's no need to have it in the world set if it's a dep of another package. *** This bug has been marked as a duplicate of 13632 *** Yes, quite similar behavior but w/o using --deep switch. BTW, I will mask vmware-modules-1.0.0.15 in my package.mask to fix this issue. The "fix" is to remove vmware-modules from your world file. It shouldn't ever be there. I'll be sure to update anything that mentions merging the modules to use --oneshot... Nevermind... it already says to use --oneshot... =] |