[gentoo-user] Portage wants KDE4, I don't

[gentoo-user] Portage wants KDE4, I don't

[Nikos Chantziaras]

I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my 
KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any 
options other than removing portage 2.1.6_rc1 again?

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Nikos Chantziaras wrote:
> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my 
> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any 
> options other than removing portage 2.1.6_rc1 again?

On a similar note, what's the justification of having KDE4 in the same 
tree as KDE3?  It's a different package altogether.  It would have made 
more sense to have them in "kde4-base/*" etc.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[sebasmagri]

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

On Tue, Nov 25, 2008 at 03:18:11PM +0200, Nikos Chantziaras wrote:
> Nikos Chantziaras wrote:
>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my 
>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any options 
>> other than removing portage 2.1.6_rc1 again?
>
> On a similar note, what's the justification of having KDE4 in the same tree 
> as KDE3?  It's a different package altogether.  It would have made more 
> sense to have them in "kde4-base/*" etc.
>
Hi!

kde3 and kde4 are slotted, so I don't think it's necessary to have
just-another-category for kde4... At last, kde4 is kde too...
in any case kde4 is willing to be installed without removing kde3...

From my point of view it's impossible that portage upgrades kde3 to
kde4, if you really never unmasked or keyworded any kde stuff, then it's
in the ~arch tree and it would not be installable for you rigth now...
Portage do what you want it to do... Give a deep look to your portage
configuration files and fill a bug if there is really a portage issue...

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

sebasmagri@gmail.com wrote:
> On Tue, Nov 25, 2008 at 03:18:11PM +0200, Nikos Chantziaras wrote:
>> Nikos Chantziaras wrote:
>>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my 
>>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any options 
>>> other than removing portage 2.1.6_rc1 again?
>> On a similar note, what's the justification of having KDE4 in the same tree 
>> as KDE3?  It's a different package altogether.  It would have made more 
>> sense to have them in "kde4-base/*" etc.
>>
> Hi!
> 
> kde3 and kde4 are slotted, so I don't think it's necessary to have
> just-another-category for kde4... At last, kde4 is kde too...
> in any case kde4 is willing to be installed without removing kde3...
> 
> From my point of view it's impossible that portage upgrades kde3 to
> kde4, if you really never unmasked or keyworded any kde stuff

I didn't unmask nor keyword any *KDE4* stuff.  Only KDE3.  Previous 
portage was happy with that.  The new portage is not.  I have dozens of 
packages in package.keywords that look like this:

kde-base/kdelibs

Now portage wants to install the 4.1 versions of all those.  The 
previous portage did not; I had to tell it to keyword the 4.1 versions 
if I wanted that.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Sebastián Magrí]

El mar, 25-11-2008 a las 16:17 +0200, Nikos Chantziaras escribió:
> sebasmagri@gmail.com wrote:
> > On Tue, Nov 25, 2008 at 03:18:11PM +0200, Nikos Chantziaras wrote:
> >> Nikos Chantziaras wrote:
> >>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my 
> >>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any options 
> >>> other than removing portage 2.1.6_rc1 again?
> >> On a similar note, what's the justification of having KDE4 in the same tree 
> >> as KDE3?  It's a different package altogether.  It would have made more 
> >> sense to have them in "kde4-base/*" etc.
> >>
> > Hi!
> > 
> > kde3 and kde4 are slotted, so I don't think it's necessary to have
> > just-another-category for kde4... At last, kde4 is kde too...
> > in any case kde4 is willing to be installed without removing kde3...
> > 
> > From my point of view it's impossible that portage upgrades kde3 to
> > kde4, if you really never unmasked or keyworded any kde stuff
> 
> I didn't unmask nor keyword any *KDE4* stuff.  Only KDE3.  Previous 
> portage was happy with that.  The new portage is not.  I have dozens of 
> packages in package.keywords that look like this:
> 
> kde-base/kdelibs
> 
> Now portage wants to install the 4.1 versions of all those.  The 
> previous portage did not; I had to tell it to keyword the 4.1 versions 
> if I wanted that.
> 
> 
Check the slots you used unmasking kde3 stuff... there is maybe the
explanation...

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Dmitry S. Makovey]

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

On November 25, 2008, Nikos Chantziaras wrote:
> I didn't unmask nor keyword any *KDE4* stuff.  Only KDE3.  Previous
> portage was happy with that.  The new portage is not.  I have dozens of
> packages in package.keywords that look like this:
>
> kde-base/kdelibs

in which case portage did exactly what you've asked it to. You should've 
mentioned either which specific versions you're unmasking/keywording or 
slots. Either way it's not a bug it's a true feature.

> Now portage wants to install the 4.1 versions of all those.  The
> previous portage did not; I had to tell it to keyword the 4.1 versions
> if I wanted that.

It exhibits proper behavior, what's wrong with that? I'd be surprised if I ran 
system with blanket keyworded kde builds (no slot or version mentioning) and 
portage wouldn't suggest KDE4 install. KDE4 is a successor of KDE3 so it's 
all correct. The fact that you've enabled ~arch builds without consideration 
for future implications doesn't constitute fault on part of portage, sorry. I 
would suggest now and in the future either specify slot or version of package 
you're unmasking unless you *really* know what you're doing.

P.S.
KDE3 and KDE4 would live happily alongside each other as long as you have 
USE="kdeprefix" specified in /etc/make.conf .

-- 
Dmitry Makovey
Web Systems Administrator
Athabasca University
(780) 675-6245

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Dmitry S. Makovey wrote:
> On November 25, 2008, Nikos Chantziaras wrote:
>> I didn't unmask nor keyword any *KDE4* stuff.  Only KDE3.  Previous
>> portage was happy with that.  The new portage is not.  I have dozens of
>> packages in package.keywords that look like this:
>>
>> kde-base/kdelibs
> 
> in which case portage did exactly what you've asked it to. You should've 
> mentioned either which specific versions you're unmasking/keywording or 
> slots. Either way it's not a bug it's a true feature.

I can see that now.  I assumed it's not the right behavior because 
portage-2.1.4.5 did not pull KDE 4.  Having:

   kde-base/kdelibs

in keywords only keyworded the KDE 3 package.  I'm not sure why.  Maybe 
it was looking at what I have installed and used that slot only instead 
of every available slot.  The new portage keywords all slots, installed 
or not.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Stroller]

On 25 Nov 2008, at 14:17, Nikos Chantziaras wrote:
> ...
> I didn't unmask nor keyword any *KDE4* stuff.  Only KDE3.

I can't help wondering if that's your problem. You unmasked KDE on  
your own machine... now in the main tree KDE 3 is no longer masked,  
but KDE 4 is available (so your machine thinks you wanted it  
unmasked). I would try removing *everything* KDE-related from /etc/ 
portage/package* & trying `emerge -pv world` again.

Stroller.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Dmitry S. Makovey]

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

On November 25, 2008, Stroller wrote:
> On 25 Nov 2008, at 14:17, Nikos Chantziaras wrote:
> > ...
> > I didn't unmask nor keyword any *KDE4* stuff.  Only KDE3.
>
> I can't help wondering if that's your problem. You unmasked KDE on
> your own machine... now in the main tree KDE 3 is no longer masked,
> but KDE 4 is available (so your machine thinks you wanted it
> unmasked). I would try removing *everything* KDE-related from /etc/
> portage/package* & trying `emerge -pv world` again.

if Nikos is after 3.5.10 he needs it to be unmasked as it's in ~arch just as 
KDE4 is ;)

-- 
Dmitry Makovey
Web Systems Administrator
Athabasca University
(780) 675-6245

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Portage wants KDE4, I don't

[Volker Armin Hemmann]

On Tuesday 25 November 2008, Nikos Chantziaras wrote:
> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
> options other than removing portage 2.1.6_rc1 again?

/etc/portage/package.mask

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Volker Armin Hemmann wrote:
> On Tuesday 25 November 2008, Nikos Chantziaras wrote:
>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
>> options other than removing portage 2.1.6_rc1 again?
> 
> /etc/portage/package.mask

So you're saying I must spend 1 hour to mask all the stuff?  (Not 
joking, the list is big, I have to do "emerge -av world" each time and 
see the package, mask it, emerge again, mask it, emerge again, mask it, 
ad infinitum.  This is not funny :P)

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Zsitvai János]

On Tue, Nov 25, 2008 at 3:18 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> So you're saying I must spend 1 hour to mask all the stuff?  (Not joking,
> the list is big, I have to do "emerge -av world" each time and see the
> package, mask it, emerge again, mask it, emerge again, mask it, ad
> infinitum.  This is not funny :P)

eix -C kde-|grep "\[[IU]\]"|awk -F" " '{print $2 ":4.1"}' >
/etc/portage/package.mask/kde4

You might need to mask media-sound/amarok:4.1 as well, but that's
hardly an hour's work.

On a related note, paludis calculates and lists all blockers at once,
not one-by-one.

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Zsitvai János wrote:
> On Tue, Nov 25, 2008 at 3:18 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
>> So you're saying I must spend 1 hour to mask all the stuff?  (Not joking,
>> the list is big, I have to do "emerge -av world" each time and see the
>> package, mask it, emerge again, mask it, emerge again, mask it, ad
>> infinitum.  This is not funny :P)
> 
> eix -C kde-|grep "\[[IU]\]"|awk -F" " '{print $2 ":4.1"}' >
> /etc/portage/package.mask/kde4

package.mask is a file here, not a directory.


> On a related note, paludis calculates and lists all blockers at once,
> not one-by-one.

I don't have paludis.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Arttu V.]

On 11/25/08, Nikos Chantziaras <realnc@arcor.de> wrote:
> Zsitvai János wrote:
>> On Tue, Nov 25, 2008 at 3:18 PM, Nikos Chantziaras <realnc@arcor.de>
>> wrote:
>>> So you're saying I must spend 1 hour to mask all the stuff?  (Not joking,
>>> the list is big, I have to do "emerge -av world" each time and see the
>>> package, mask it, emerge again, mask it, emerge again, mask it, ad
>>> infinitum.  This is not funny :P)
>>
>> eix -C kde-|grep "\[[IU]\]"|awk -F" " '{print $2 ":4.1"}' >
>> /etc/portage/package.mask/kde4
>
> package.mask is a file here, not a directory.

Maybe you should use existing, old portage features: slots.

Add ":3.5" to the end of all those "kde-base/"-starting lines in
package.keywords, and you'll accept unstable from slot 3.5 but not
from 4.1 (current kde4 slot). You probably can use
match/search-and-replace within your favourite text editor to get it
to the end of all those lines without doing it manually.

Your lines will look like this (but with slot 3.5 instead of 4.1):

kde-base/superkaramba:4.1

Yes, that's the way they suggest unmasking stuff when testing out kde4 ... :)

Slots <3 <3 <3

-- 
Arttu V.

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Arttu V. wrote:
> On 11/25/08, Nikos Chantziaras <realnc@arcor.de> wrote:
>> Zsitvai János wrote:
>>> On Tue, Nov 25, 2008 at 3:18 PM, Nikos Chantziaras <realnc@arcor.de>
>>> wrote:
>>>> So you're saying I must spend 1 hour to mask all the stuff?  (Not joking,
>>>> the list is big, I have to do "emerge -av world" each time and see the
>>>> package, mask it, emerge again, mask it, emerge again, mask it, ad
>>>> infinitum.  This is not funny :P)
>>> eix -C kde-|grep "\[[IU]\]"|awk -F" " '{print $2 ":4.1"}' >
>>> /etc/portage/package.mask/kde4
>> package.mask is a file here, not a directory.
> 
> Maybe you should use existing, old portage features: slots.
> 
> Add ":3.5" to the end of all those "kde-base/"-starting lines in
> package.keywords, and you'll accept unstable from slot 3.5 but not
> from 4.1 (current kde4 slot).

Thank you.  It's funny though that portage-2.1.4.5 somehow kept the 4.1 
slot out of the way even though I didn't specify a slot in 
package.keywords.  That's why I assumed there's some bug here.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Zsitvai János]

On Tue, Nov 25, 2008 at 3:54 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> package.mask is a file here, not a directory.

You could either tack the output to the end of your package.mask with
>>, or rename the current package.mask, mkdir package.mask, and move
it in there.

Or just copypaste this line:
eix -C kde-|grep "\[[IU]\]"|awk -F" " '{print $2 ":4.1"}' >>
/etc/portage/package.mask

It does assume that you have eix installed.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Etaoin Shrdlu]

On Tuesday 25 November 2008, 15:54, Nikos Chantziaras wrote:
> Zsitvai János wrote:
> > On Tue, Nov 25, 2008 at 3:18 PM, Nikos Chantziaras <realnc@arcor.de> 
wrote:
> >> So you're saying I must spend 1 hour to mask all the stuff?  (Not
> >> joking, the list is big, I have to do "emerge -av world" each time
> >> and see the package, mask it, emerge again, mask it, emerge again,
> >> mask it, ad infinitum.  This is not funny :P)
> >
> > eix -C kde-|grep "\[[IU]\]"|awk -F" " '{print $2 ":4.1"}' >
> > /etc/portage/package.mask/kde4
>
> package.mask is a file here, not a directory.

It can also be a directory. See man portage for the details.

/etc/portage/
              Any  file in this directory that begins with "package." can 
be more than just a flat file.  If it is a directory, then all the files 
in that directory will be summed together as if it were a single file.

(and, btw, adapting the above to the case where package.mask is a single 
file is very easy)

Re: [gentoo-user] Portage wants KDE4, I don't

[Dmitry S. Makovey]

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

On November 25, 2008, Nikos Chantziaras wrote:
> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
> options other than removing portage 2.1.6_rc1 again?

1st of all, I'm running 2.2.x versions of portage and never had KDE4 magically 
unmasked. You'd better check your setup. I do realize that 2.2.x is not 
2.1.6_rc1, but what I mean - it must be either a bug in portage or your 
setup. Find where the problem originates. Do you have ~arch KDE3 ? I suppose 
you don't run ~arch branch, right?

-- 
Dmitry Makovey
Web Systems Administrator
Athabasca University
(780) 675-6245

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Portage wants KDE4, I don't

[Dale]

Dmitry S. Makovey wrote:
> On November 25, 2008, Nikos Chantziaras wrote:
>   
>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
>> options other than removing portage 2.1.6_rc1 again?
>>     
>
> 1st of all, I'm running 2.2.x versions of portage and never had KDE4 magically 
> unmasked. You'd better check your setup. I do realize that 2.2.x is not 
> 2.1.6_rc1, but what I mean - it must be either a bug in portage or your 
> setup. Find where the problem originates. Do you have ~arch KDE3 ? I suppose 
> you don't run ~arch branch, right?
>
>   

I am using portage-2.2_rc15 and I have unstable KDE 3 but nothing KDE
4.  I actually tested KDE 4 once and had to unmask all the KDE 4 stuff
to get it.

I agree, there is something fishy about his/her setup.  I think that if
this happened to anyone else, someone would have spoke up by now.  I'll
sync in a little bit and test mine to be sure tho.

Dale

:-)  :-)

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Dale wrote:
> Dmitry S. Makovey wrote:
>> On November 25, 2008, Nikos Chantziaras wrote:
>>   
>>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
>>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
>>> options other than removing portage 2.1.6_rc1 again?
>>>     
>> 1st of all, I'm running 2.2.x versions of portage and never had KDE4 magically 
>> unmasked. You'd better check your setup. I do realize that 2.2.x is not 
>> 2.1.6_rc1, but what I mean - it must be either a bug in portage or your 
>> setup. Find where the problem originates. Do you have ~arch KDE3 ? I suppose 
>> you don't run ~arch branch, right?
> 
> I am using portage-2.2_rc15 and I have unstable KDE 3 but nothing KDE
> 4.  I actually tested KDE 4 once and had to unmask all the KDE 4 stuff
> to get it.
> 
> I agree, there is something fishy about his/her setup.  I think that if
> this happened to anyone else, someone would have spoke up by now.  I'll
> sync in a little bit and test mine to be sure tho.

No, not unmasked but keyworded.  We've figured it out by now.  It was 
because KDE4 was getting masked automatically by EAPI2 which stable 
portage doesn't support.  As soon as portage was upgraded, no masking 
anymore due to EAPI and hence KDE4 got pulled-in.

Re: [gentoo-user] Re: Portage wants KDE4, I don't

[Dale]

Nikos Chantziaras wrote:
> Dale wrote:
>> Dmitry S. Makovey wrote:
>>> On November 25, 2008, Nikos Chantziaras wrote:
>>>  
>>>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
>>>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
>>>> options other than removing portage 2.1.6_rc1 again?
>>>>     
>>> 1st of all, I'm running 2.2.x versions of portage and never had KDE4
>>> magically unmasked. You'd better check your setup. I do realize that
>>> 2.2.x is not 2.1.6_rc1, but what I mean - it must be either a bug in
>>> portage or your setup. Find where the problem originates. Do you
>>> have ~arch KDE3 ? I suppose you don't run ~arch branch, right?
>>
>> I am using portage-2.2_rc15 and I have unstable KDE 3 but nothing KDE
>> 4.  I actually tested KDE 4 once and had to unmask all the KDE 4 stuff
>> to get it.
>>
>> I agree, there is something fishy about his/her setup.  I think that if
>> this happened to anyone else, someone would have spoke up by now.  I'll
>> sync in a little bit and test mine to be sure tho.
>
> No, not unmasked but keyworded.  We've figured it out by now.  It was
> because KDE4 was getting masked automatically by EAPI2 which stable
> portage doesn't support.  As soon as portage was upgraded, no masking
> anymore due to EAPI and hence KDE4 got pulled-in.
>
>
>

Well, I noticed this on mine.  I thought I had unmasked KDE 3.5 but
after going and looking, I have not.  I have portage-2.2_rc16 currently
installed and it appears autounmask does not work well with it.

This may at some point help the OP but can help me at the moment.  How
does one unmask ALL the KDE 3 packages but not the KDE 4 stuff?  I ask
that as in what command would list those to copy to packages.unmask or
add them to it.

I think whoever writes code for autounmask needs to get a gently nudge. 
It doesn't seem to like the latest portage.  I'm not complaining and I
know I am running unstable packages.  Just thinking he may not know that
his code just got borked.  :-O

I eagerly await the day one can keyword/unmask kde-meta and it
automatically unmasks all its friends.  I'm not sure how good that day
will be but it is a thought.

Dale

:-)  :-) 

Re: [gentoo-user] Portage wants KDE4, I don't

[Mike Williams]

On Tuesday 25 November 2008 13:08:40 Nikos Chantziaras wrote:
> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
> options other than removing portage 2.1.6_rc1 again?

The KDE4 ebuilds need EAPI 2 support in the package manager, portage 2.1.4.5 
does not implement EAPI 2, portage 2.1.6_rc1 proabably does (2.2 certainly 
does).
You either need to mask all the kde4 ebuilds, or keyword only the 3.5 SLOT 
versions.

-- 
Mike Williams

[gentoo-user] Re: Portage wants KDE4, I don't

[Nikos Chantziaras]

Mike Williams wrote:
> On Tuesday 25 November 2008 13:08:40 Nikos Chantziaras wrote:
>> I decided to give portage 2.1.6_rc1 a try.  Now it wants to upgrade my
>> KDE3 to KDE4.  I never unmasked or keyworded any KDE4 stuff.  Any
>> options other than removing portage 2.1.6_rc1 again?
> 
> The KDE4 ebuilds need EAPI 2 support in the package manager, portage 2.1.4.5 
> does not implement EAPI 2, portage 2.1.6_rc1 proabably does (2.2 certainly 
> does).
> You either need to mask all the kde4 ebuilds, or keyword only the 3.5 SLOT 
> versions.

Ah, that was the thing I missed. EAPI2. Guess that mystery is solved now ;D