| 1 |
On Mon, May 4, 2009 at 2:55 PM, Dan Johansson <Dan.Johansson@×××.nu> wrote: |
| 2 |
> On Sunday 03 May 2009, Duncan wrote: |
| 3 |
>> Dan Johansson <Dan.Johansson@×××.nu> posted |
| 4 |
>> 200905031107.24458.Dan.Johansson@×××.nu, excerpted below, on Sun, 03 May |
| 5 |
>> |
| 6 |
>> 2009 11:07:17 +0200: |
| 7 |
>> > I noticed that emerge wanted to downgrade my |
| 8 |
>> > app-emulation/vmware-modules-1.0.0.15-r2 |
| 9 |
>> > |
| 10 |
>> > # emerge --update --deep --verbose --reinstall changed-use world |
| 11 |
>> > --pretend |
| 12 |
>> > |
| 13 |
>> > These are the packages that would be merged, in order: |
| 14 |
>> > |
| 15 |
>> > Calculating dependencies... done! |
| 16 |
>> > [ebuild U ] dev-perl/XML-Parser-2.36 [2.34-r1] 0 kB [?=>0] [ebuild |
| 17 |
>> > UD] app-emulation/vmware-modules-1.0.0.15-r2 [1.0.0.23] 0 kB [0] |
| 18 |
>> > |
| 19 |
>> > Total: 2 packages (1 upgrade, 1 downgrade), Size of downloads: 0 kB |
| 20 |
>> > |
| 21 |
>> > I really don't get it |
| 22 |
>> |
| 23 |
>> It's likely that your current version has been masked, for some reason. |
| 24 |
>> Try this to find out why: |
| 25 |
>> |
| 26 |
>> emerge --pretend =app-emulation/vmware-modules-1.0.0.23 |
| 27 |
>> |
| 28 |
>> That should tell you why it can't remerge that version, spitting out the |
| 29 |
>> comment from package.mask or otherwise telling you what's wrong |
| 30 |
>> (keywords, blocker, whatever). |
| 31 |
>> |
| 32 |
>> FWIW, it lets me pretend-install that version here, but I don't have |
| 33 |
>> VMWare installed (it's proprietaryware which I don't do) so whatever |
| 34 |
>> blocker there might be I'm not seeing, and if the mask was just added in |
| 35 |
>> the last 24-36 hours or so, I'd not see it either as I've not synced in |
| 36 |
>> that time. |
| 37 |
> No it's not the vmware-modules ebuild - it's not masked or keyworded. |
| 38 |
> # emerge --pretend =app-emulation/vmware-modules-1.0.0.23 |
| 39 |
> |
| 40 |
> These are the packages that would be merged, in order: |
| 41 |
> |
| 42 |
> Calculating dependencies... done! |
| 43 |
> [ebuild R ] app-emulation/vmware-modules-1.0.0.23 |
| 44 |
> |
| 45 |
> I think it's a change in the vmware-server ebuild - without version change |
| 46 |
> (:-( |
| 47 |
> |
| 48 |
> # grep vmware-modules /usr/portage/app-emulation/vmware-server/*.ebuild |
| 49 |
> ~app-emulation/vmware-modules-1.0.0.15 |
| 50 |
> !<app-emulation/vmware-modules-1.0.0.15 |
| 51 |
> !>=app-emulation/vmware-modules-1.0.0.16 |
| 52 |
> |
| 53 |
> The !>=...1.0.0.16 must be a new addition in the last one to two weeks. Before |
| 54 |
> that this was not a problem. |
| 55 |
> |
| 56 |
> If the devs think that 1.0.0.23 is a bad idea then OK I'll downgrade.... |
| 57 |
|
| 58 |
I suggest using the vmware overlay... it seems to be much more |
| 59 |
up-to-date, especially when vmware-modules gets updated after a new |
| 60 |
kernel, etc. I'm using it and haven't run into this problem. |
Archives