[gentoo-user] Overlays & package.mask

[gentoo-user] Overlays & package.mask

[Hilco Wijbenga]

Hi all,

This morning I got

centaur ~ # emerge -vDuNp world

These are the packages that would be merged, in order:

Calculating dependencies... done!
<snip/>
[ebuild     UD] kde-base/pykde4-4.5.1 [4.5.1-r1] USE="semantic-desktop
(-aqua) -debug -doc -examples (-kdeenablefinal) (-kdeprefix)" 0 kB
[1=>0]
<snip/>

Total: 9 packages (7 upgrades, 1 downgrade, 1 reinstall), Size of
downloads: 10,550 kB
Portage tree and overlays:
 [0] /usr/portage
 [1] /var/lib/layman/kde

I decided that I did not want to go back to 4.5.1 so I added

=kde-base/pykde4-4.5.1

to /etc/portage/package.mask.

To my utmost surprise, I got the exact same result as before when
running the above emerge command again. I tried it with one of the
other upgrades mentioned and package.mask had the expected result.

So I'm confused. Why is package.mask not having any (apparent) effect
for pykde4? How do I prevent the downgrade?

Cheers,
Hilco

Re: [gentoo-user] Overlays & package.mask

[J. Roeleveld]

On Friday 10 September 2010 18:53:52 Hilco Wijbenga wrote:
> Hi all,
> 
> This morning I got
> 
> centaur ~ # emerge -vDuNp world
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> <snip/>
> [ebuild     UD] kde-base/pykde4-4.5.1 [4.5.1-r1] USE="semantic-desktop
> (-aqua) -debug -doc -examples (-kdeenablefinal) (-kdeprefix)" 0 kB
> [1=>0]
> <snip/>
> 
> Total: 9 packages (7 upgrades, 1 downgrade, 1 reinstall), Size of
> downloads: 10,550 kB
> Portage tree and overlays:
>  [0] /usr/portage
>  [1] /var/lib/layman/kde
> 
> I decided that I did not want to go back to 4.5.1 so I added
> 
> =kde-base/pykde4-4.5.1
> 
> to /etc/portage/package.mask.
> 
> To my utmost surprise, I got the exact same result as before when
> running the above emerge command again. I tried it with one of the
> other upgrades mentioned and package.mask had the expected result.
> 
> So I'm confused. Why is package.mask not having any (apparent) effect
> for pykde4? How do I prevent the downgrade?
> 
> Cheers,
> Hilco

Strange, I don't have pykde4-4.5.1-r1 at all.

What does "eix pykde4" say on your system?
On mine it says:
***
$ eix pykde4
[I] kde-base/pykde4
     Available versions:  
        (4.4)   ~4.4.1[3] 4.4.5 **4.4.9999!m!t[1] **4.4.9999!m!t[2]
        (4.5)   ~4.5.1 **4.5.9999!m!t[1]
        (live)  **9999!m!t[1] **9999!m!t[2]
        {akonadi aqua debug doc examples kdeenablefinal (+)kdeprefix semantic-
desktop}
     Installed versions:  4.4.5(4.4)(11:35:47 PM 08/13/2010)(semantic-desktop 
-aqua -debug -doc -examples -kdeenablefinal -kdeprefix)
     Homepage:            http://www.kde.org/
     Description:         Python bindings for KDE4

[1] "kde" /usr/portage/local/layman/kde
[2] layman/kde
[3] layman/sabayon

***

Hmm... why are there 2 "layman/kde" overlays?

--
Joost

Re: [gentoo-user] Overlays & package.mask

[Dale]

Hilco Wijbenga wrote:
> Hi all,
>
> This morning I got
>
> centaur ~ # emerge -vDuNp world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> <snip/>
> [ebuild     UD] kde-base/pykde4-4.5.1 [4.5.1-r1] USE="semantic-desktop
> (-aqua) -debug -doc -examples (-kdeenablefinal) (-kdeprefix)" 0 kB
> [1=>0]
> <snip/>
>
> Total: 9 packages (7 upgrades, 1 downgrade, 1 reinstall), Size of
> downloads: 10,550 kB
> Portage tree and overlays:
>   [0] /usr/portage
>   [1] /var/lib/layman/kde
>
> I decided that I did not want to go back to 4.5.1 so I added
>
> =kde-base/pykde4-4.5.1
>
> to /etc/portage/package.mask.
>
> To my utmost surprise, I got the exact same result as before when
> running the above emerge command again. I tried it with one of the
> other upgrades mentioned and package.mask had the expected result.
>
> So I'm confused. Why is package.mask not having any (apparent) effect
> for pykde4? How do I prevent the downgrade?
>
> Cheers,
> Hilco
>    

Do you have the package listed in the unmask or keyword file?  If so, it 
ignores the mask file.  Actually, I think it reads mask first then the 
others.

Hope that helps.

Dale

:-)  :-)

Re: [gentoo-user] Overlays & package.mask

[Hilco Wijbenga]

On 10 September 2010 10:25, J. Roeleveld <joost@antarean.org> wrote:
> Strange, I don't have pykde4-4.5.1-r1 at all.
>
> What does "eix pykde4" say on your system?
> On mine it says:
> ***
> $ eix pykde4
> [I] kde-base/pykde4
>     Available versions:
>        (4.4)   ~4.4.1[3] 4.4.5 **4.4.9999!m!t[1] **4.4.9999!m!t[2]
>        (4.5)   ~4.5.1 **4.5.9999!m!t[1]
>        (live)  **9999!m!t[1] **9999!m!t[2]
>        {akonadi aqua debug doc examples kdeenablefinal (+)kdeprefix semantic-
> desktop}
>     Installed versions:  4.4.5(4.4)(11:35:47 PM 08/13/2010)(semantic-desktop
> -aqua -debug -doc -examples -kdeenablefinal -kdeprefix)
>     Homepage:            http://www.kde.org/
>     Description:         Python bindings for KDE4
>
> [1] "kde" /usr/portage/local/layman/kde
> [2] layman/kde
> [3] layman/sabayon

[D] kde-base/pykde4
     Available versions:
        (4.4)   4.4.5 **4.4.9999!m!t[1]
        (4.5)   (~)4.5.1 **4.5.9999!m!t[1]
        (live)  **9999!m!t[1]
        {aqua debug doc examples kdeenablefinal (+)kdeprefix semantic-desktop}
     Installed versions:  4.5.1-r1(4.5){tbz2}[1](16:22:12
09/03/10)(semantic-desktop -aqua -debug -doc -examples -kdeenablefinal
-kdeprefix)
     Homepage:            http://www.kde.org/
     Description:         Python bindings for KDE4

[1] "kde" /var/lib/layman/kde

> Hmm... why are there 2 "layman/kde" overlays?

Looks like you need to remove that [1] overlay?

Re: [gentoo-user] Overlays & package.mask

[Hilco Wijbenga]

On 10 September 2010 10:25, Dale <rdalek1967@gmail.com> wrote:
> Do you have the package listed in the unmask or keyword file?  If so, it
> ignores the mask file.  Actually, I think it reads mask first then the
> others.

Ah! Yes, I do.

That explains why package.mask is being ignored, I guess, but I can't
think of a way yet to prevent the downgrade. Removing from
package.unmask just creates errors and adding 4.5.1-r1 didn't seem to
have any effect. Any ideas?

Re: [gentoo-user] Overlays & package.mask

[Paul Hartman]

On Fri, Sep 10, 2010 at 11:53 AM, Hilco Wijbenga
<hilco.wijbenga@gmail.com> wrote:
> So I'm confused. Why is package.mask not having any (apparent) effect
> for pykde4? How do I prevent the downgrade?

It's probably unmasked as well. I think unmask overrides mask.

As an alternative, you can try to eliminate pykde4 entirely by setting
these USE flags in your package.use:

kde-base/marble -python
kde-base/plasma-workspace -python
kde-base/superkaramba -python
kde-base/kdeadmin-meta -cups
kde-base/kdeutils-meta -cups

With those, I have no pykde4 at all. I'm not sure what functionality
may be lost due to it, but I've noticed nothing that I use missing.

Re: [gentoo-user] Overlays & package.mask

[Alan McKinnon]

Apparently, though unproven, at 18:53 on Friday 10 September 2010, Hilco 
Wijbenga did opine thusly:

> Hi all,
> 
> This morning I got
> 
> centaur ~ # emerge -vDuNp world
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> <snip/>
> [ebuild     UD] kde-base/pykde4-4.5.1 [4.5.1-r1] USE="semantic-desktop
> (-aqua) -debug -doc -examples (-kdeenablefinal) (-kdeprefix)" 0 kB
> [1=>0]
> <snip/>
> 
> Total: 9 packages (7 upgrades, 1 downgrade, 1 reinstall), Size of
> downloads: 10,550 kB
> Portage tree and overlays:
>  [0] /usr/portage
>  [1] /var/lib/layman/kde
> 
> I decided that I did not want to go back to 4.5.1 so I added
> 
> =kde-base/pykde4-4.5.1
> 
> to /etc/portage/package.mask.
> 
> To my utmost surprise, I got the exact same result as before when
> running the above emerge command again. I tried it with one of the
> other upgrades mentioned and package.mask had the expected result.
> 
> So I'm confused. Why is package.mask not having any (apparent) effect
> for pykde4? How do I prevent the downgrade?

Do you have the same entry in package.unmask?

unmask supercedes mask


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Overlays & package.mask

[Alex Schuster]

J. Roeleveld writes:

> Strange, I don't have pykde4-4.5.1-r1 at all.

I do.

> What does "eix pykde4" say on your system?
> On mine it says:
> ***
> $ eix pykde4
> [I] kde-base/pykde4
>      Available versions:
>         (4.4)   ~4.4.1[3] 4.4.5 **4.4.9999!m!t[1] **4.4.9999!m!t[2]
>         (4.5)   ~4.5.1 **4.5.9999!m!t[1]
>         (live)  **9999!m!t[1] **9999!m!t[2]
>         {akonadi aqua debug doc examples kdeenablefinal (+)kdeprefix
> semantic- desktop}
>      Installed versions:  4.4.5(4.4)(11:35:47 PM
> 08/13/2010)(semantic-desktop -aqua -debug -doc -examples
> -kdeenablefinal -kdeprefix)
>      Homepage:            http://www.kde.org/
>      Description:         Python bindings for KDE4
> 
> [1] "kde" /usr/portage/local/layman/kde
> [2] layman/kde
> [3] layman/sabayon
> 
> ***
> 
> Hmm... why are there 2 "layman/kde" overlays?

I'd check the layman setup. Does the path in /etc/layman/layman.cfg match 
the one you source at the bottom of make.conf?

	Wonko

Re: [gentoo-user] Overlays & package.mask

[Dale]

Hilco Wijbenga wrote:
> On 10 September 2010 10:25, Dale<rdalek1967@gmail.com>  wrote:
>    
>> Do you have the package listed in the unmask or keyword file?  If so, it
>> ignores the mask file.  Actually, I think it reads mask first then the
>> others.
>>      
> Ah! Yes, I do.
>
> That explains why package.mask is being ignored, I guess, but I can't
> think of a way yet to prevent the downgrade. Removing from
> package.unmask just creates errors and adding 4.5.1-r1 didn't seem to
> have any effect. Any ideas?
>
>    

Sounds like some things depend on that version being installed.  You may 
just have to go through them one by one and add them to the appropriate 
files.  I did this a few days ago with qt.  It's not fun but I don't 
know of a better way.

You may want to check into autounmask for future use.  At least that way 
you can just remove things that you no longer need, want or want to 
downgrade for some reason.

Dale

:-)  :-)

Re: [gentoo-user] Overlays & package.mask

[John Campbell]

On 09/10/2010 09:53 AM, Hilco Wijbenga wrote:
> Hi all,
> 
> So I'm confused. Why is package.mask not having any (apparent) effect
> for pykde4? How do I prevent the downgrade?

pykde4-4.5.1-r1 was removed from the repository, not masked.

In order to keep 4.5.1-r1 you need to obtain a copy of the ebuild and
add it to your local repository.

Re: [gentoo-user] Overlays & package.mask

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

On Fri, 10 Sep 2010 09:53:52 -0700, Hilco Wijbenga wrote:

> I decided that I did not want to go back to 4.5.1 so I added
> 
> =kde-base/pykde4-4.5.1
> 
> to /etc/portage/package.mask.
> 
> To my utmost surprise, I got the exact same result as before when
> running the above emerge command again. I tried it with one of the
> other upgrades mentioned and package.mask had the expected result.
> 
> So I'm confused. Why is package.mask not having any (apparent) effect
> for pykde4? How do I prevent the downgrade?

4.5.1-r1 was in the kde overlay, it is no longer there. That's why
portage wants to downgrade and no amount of unmasking will change that.
If you want to stay with -r1, copy the ebuild from /var/db/pkg to your
local overlay.


-- 
Neil Bothwick

Math and alcohol don't mix. Don't drink and derive.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Overlays & package.mask

[Hilco Wijbenga]

On 10 September 2010 11:40, Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
> On Fri, Sep 10, 2010 at 11:53 AM, Hilco Wijbenga
> <hilco.wijbenga@gmail.com> wrote:
>> So I'm confused. Why is package.mask not having any (apparent) effect
>> for pykde4? How do I prevent the downgrade?
>
> It's probably unmasked as well. I think unmask overrides mask.
>
> As an alternative, you can try to eliminate pykde4 entirely by setting
> these USE flags in your package.use:
>
> kde-base/marble -python
> kde-base/plasma-workspace -python
> kde-base/superkaramba -python
> kde-base/kdeadmin-meta -cups
> kde-base/kdeutils-meta -cups
>
> With those, I have no pykde4 at all. I'm not sure what functionality
> may be lost due to it, but I've noticed nothing that I use missing.

This seemed like the easiest solution especially since pykde4-4.5.1
doesn't even build. All's good now. :-)