[gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Roy Wright]

Howdy,

kde-4.3 is now unmasked for ~x86.  Whooooop!

But it is looking like a non-trivial upgrade.  :(

When I installed kde-4.2, I followed the advice of unmasking portage  
and using sets.  Also followed the recommendation to use -kdeprefix.   
Further I removed kde-3.5 and added a mask on kdelibs-3.5 to help keep  
3.5 off of the system.

So for the kde-4.3 upgrade, it looks like this is what will be  
necessary:

1) grab the sets again from the kde-testing overlay and put them in / 
etc/portage/sets (assumption is to do a replace).
2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
3) merge kde-4.3 using: emerge -av @kde-4.3
4) recustomize kde as the ~/.kde will not be migrated

Am I on the right track?

TIA,
Roy

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dirk Heinrichs]

[-- Attachment #1: Type: Text/Plain, Size: 576 bytes --]

Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:

> So for the kde-4.3 upgrade, it looks like this is what will be
> necessary:
>
> 1) grab the sets again from the kde-testing overlay and put them in /
> etc/portage/sets (assumption is to do a replace).
> 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> 3) merge kde-4.3 using: emerge -av @kde-4.3
> 4) recustomize kde as the ~/.kde will not be migrated
>
> Am I on the right track?

No.

1) They're in portage.
2) No need to unmerge anything (except one or two blockers).
4) Worked just fine here.

HTH...

	Dirk

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

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dirk Heinrichs]

[-- Attachment #1: Type: Text/Plain, Size: 187 bytes --]

Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:

> 2) No need to unmerge anything (except one or two blockers).

However, you can unmerge 4.2.x, if you like to.

Bye...

	Dirk

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

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Helmut Jarausch]

On 16 Aug, Dirk Heinrichs wrote:
> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
> 
>> 2) No need to unmerge anything (except one or two blockers).
> 
> However, you can unmerge 4.2.x, if you like to.
> 

How to do that in a simple way?

Unfortunately, 
emerge --unmerge kde-base/kde-meta:4.2
only unmerges the meta package itself.

Thanks for a hint ( I'm afraid of any kde updates
since they always have created more headaches than any
other package or set of packages )

-- 
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alan McKinnon]

On Wednesday 26 August 2009 09:25:55 Helmut Jarausch wrote:
> On 16 Aug, Dirk Heinrichs wrote:
> > Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
> >> 2) No need to unmerge anything (except one or two blockers).
> >
> > However, you can unmerge 4.2.x, if you like to.
>
> How to do that in a simple way?
>
> Unfortunately,
> emerge --unmerge kde-base/kde-meta:4.2
> only unmerges the meta package itself.

Also remove all occurrences of kde-4.2 packages in the world file, then run 
emerge --depclean to get rid of the resulting orphaned deps.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dale]

Helmut Jarausch wrote:
> On 16 Aug, Dirk Heinrichs wrote:
>   
>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
>>
>>     
>>> 2) No need to unmerge anything (except one or two blockers).
>>>       
>> However, you can unmerge 4.2.x, if you like to.
>>
>>     
>
> How to do that in a simple way?
>
> Unfortunately, 
> emerge --unmerge kde-base/kde-meta:4.2
> only unmerges the meta package itself.
>
> Thanks for a hint ( I'm afraid of any kde updates
> since they always have created more headaches than any
> other package or set of packages )
>
>   

Not tested but should work.  Use the -p option to make sure.

Unmerge kde-meta:4.2
emerge --depclean -p

If that looks good, remove the -p.  It should only remove kde:4.2 and
what depends on it.  If you wait a while, I may be about to do this. 
I'm doing the same thing as you.  This DSL is soooooo cool.  :-) 

Dale

:-)  :-) 

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Helmut Jarausch]

On 26 Aug, Dale wrote:
> Helmut Jarausch wrote:
>> On 16 Aug, Dirk Heinrichs wrote:
>>   
>>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
>>>
>>>     
>>>> 2) No need to unmerge anything (except one or two blockers).
>>>>       
>>> However, you can unmerge 4.2.x, if you like to.
>>>
>>>     
>>
>> How to do that in a simple way?
>>
>> Unfortunately, 
>> emerge --unmerge kde-base/kde-meta:4.2
>> only unmerges the meta package itself.
>>
>> Thanks for a hint ( I'm afraid of any kde updates
>> since they always have created more headaches than any
>> other package or set of packages )
>>
>>   
> 
> Not tested but should work.  Use the -p option to make sure.
> 
> Unmerge kde-meta:4.2
> emerge --depclean -p
> 
> If that looks good, remove the -p.  It should only remove kde:4.2 and
> what depends on it.  If you wait a while, I may be about to do this. 
> I'm doing the same thing as you.  This DSL is soooooo cool.  :-) 
> 

I have difficulties doing so. 'emerge --depclean' requires a recent
emerge --update --newuse --deep @system @world
which tries to update kde, as well.
I'm just trying to mask all kde-base packages, then doing emerge
--update --newuse --deep @system @world

Still, quite tedious.
Helmut.

-- 
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dale]

Helmut Jarausch wrote:
> On 26 Aug, Dale wrote:
>   
>> Helmut Jarausch wrote:
>>     
>>> On 16 Aug, Dirk Heinrichs wrote:
>>>   
>>>       
>>>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
>>>>
>>>>     
>>>>         
>>>>> 2) No need to unmerge anything (except one or two blockers).
>>>>>       
>>>>>           
>>>> However, you can unmerge 4.2.x, if you like to.
>>>>
>>>>     
>>>>         
>>> How to do that in a simple way?
>>>
>>> Unfortunately, 
>>> emerge --unmerge kde-base/kde-meta:4.2
>>> only unmerges the meta package itself.
>>>
>>> Thanks for a hint ( I'm afraid of any kde updates
>>> since they always have created more headaches than any
>>> other package or set of packages )
>>>
>>>   
>>>       
>> Not tested but should work.  Use the -p option to make sure.
>>
>> Unmerge kde-meta:4.2
>> emerge --depclean -p
>>
>> If that looks good, remove the -p.  It should only remove kde:4.2 and
>> what depends on it.  If you wait a while, I may be about to do this. 
>> I'm doing the same thing as you.  This DSL is soooooo cool.  :-) 
>>
>>     
>
> I have difficulties doing so. 'emerge --depclean' requires a recent
> emerge --update --newuse --deep @system @world
> which tries to update kde, as well.
> I'm just trying to mask all kde-base packages, then doing emerge
> --update --newuse --deep @system @world
>
> Still, quite tedious.
> Helmut.
>
>   

It may not work but then again it might.  emerge --depclean -p
kde-meta:4.2 .

Dale

:-)  :-)

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Helmut Jarausch]

On 26 Aug, Dale wrote:
> Helmut Jarausch wrote:
>> On 26 Aug, Dale wrote:
>>   
>>> Helmut Jarausch wrote:
>>>     
>>>> On 16 Aug, Dirk Heinrichs wrote:
>>>>   
>>>>       
>>>>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
>>>>>
>>>>>     
>>>>>         
>>>>>> 2) No need to unmerge anything (except one or two blockers).
>>>>>>       
>>>>>>           
>>>>> However, you can unmerge 4.2.x, if you like to.
>>>>>
>>>>>     
>>>>>         
>>>> How to do that in a simple way?
>>>>
>>>> Unfortunately, 
>>>> emerge --unmerge kde-base/kde-meta:4.2
>>>> only unmerges the meta package itself.
>>>>
>>>> Thanks for a hint ( I'm afraid of any kde updates
>>>> since they always have created more headaches than any
>>>> other package or set of packages )
>>>>
>>>>   
>>>>       
>>> Not tested but should work.  Use the -p option to make sure.
>>>
>>> Unmerge kde-meta:4.2
>>> emerge --depclean -p
>>>
>>> If that looks good, remove the -p.  It should only remove kde:4.2 and
>>> what depends on it.  If you wait a while, I may be about to do this. 
>>> I'm doing the same thing as you.  This DSL is soooooo cool.  :-) 
>>>
>>>     
>>
>> I have difficulties doing so. 'emerge --depclean' requires a recent
>> emerge --update --newuse --deep @system @world
>> which tries to update kde, as well.
>> I'm just trying to mask all kde-base packages, then doing emerge
>> --update --newuse --deep @system @world
>>
>> Still, quite tedious.
>> Helmut.
>>
>>   
> 
> It may not work but then again it might.  emerge --depclean -p
> kde-meta:4.2 .

This gives

>>> No packages selected for removal by depclean

Helmut.

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alan McKinnon]

On Wednesday 26 August 2009 11:23:32 Helmut Jarausch wrote:
> On 26 Aug, Dale wrote:
> > Helmut Jarausch wrote:
> >> On 16 Aug, Dirk Heinrichs wrote:
> >>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
> >>>> 2) No need to unmerge anything (except one or two blockers).
> >>>
> >>> However, you can unmerge 4.2.x, if you like to.
> >>
> >> How to do that in a simple way?
> >>
> >> Unfortunately,
> >> emerge --unmerge kde-base/kde-meta:4.2
> >> only unmerges the meta package itself.
> >>
> >> Thanks for a hint ( I'm afraid of any kde updates
> >> since they always have created more headaches than any
> >> other package or set of packages )
> >
> > Not tested but should work.  Use the -p option to make sure.
> >
> > Unmerge kde-meta:4.2
> > emerge --depclean -p
> >
> > If that looks good, remove the -p.  It should only remove kde:4.2 and
> > what depends on it.  If you wait a while, I may be about to do this.
> > I'm doing the same thing as you.  This DSL is soooooo cool.  :-)
>
> I have difficulties doing so. 'emerge --depclean' requires a recent
> emerge --update --newuse --deep @system @world
> which tries to update kde, as well.
> I'm just trying to mask all kde-base packages, then doing emerge
> --update --newuse --deep @system @world
>
> Still, quite tedious.
> Helmut.

Run emerge -avuND world and unmerge the blockers, then emerge -avuND world and 
let portage take care of the updates.

KDE-4.3 introduced some new packages and moved others around. Portage does not 
know how to deal with this.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dirk Heinrichs]

[-- Attachment #1: Type: Text/Plain, Size: 398 bytes --]

Am Mittwoch 26 August 2009 09:25:55 schrieb Helmut Jarausch:
> On 16 Aug, Dirk Heinrichs wrote:
> > Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs:
> >> 2) No need to unmerge anything (except one or two blockers).
> >
> > However, you can unmerge 4.2.x, if you like to.
>
> How to do that in a simple way?

paludis --uninstall --with-unused-dependencies "=kde-base/*:4.2"

Bye...

	Dirk

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

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alan McKinnon]

On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > So for the kde-4.3 upgrade, it looks like this is what will be
> > necessary:
> >
> > 1) grab the sets again from the kde-testing overlay and put them in /
> > etc/portage/sets (assumption is to do a replace).
> > 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > 4) recustomize kde as the ~/.kde will not be migrated
> >
> > Am I on the right track?
>
> No.
>
> 1) They're in portage.

He's asking about the set files, not the ebuilds.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Volker Armin Hemmann]

On Sonntag 16 August 2009, Alan McKinnon wrote:
> On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> > Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > > So for the kde-4.3 upgrade, it looks like this is what will be
> > > necessary:
> > >
> > > 1) grab the sets again from the kde-testing overlay and put them in /
> > > etc/portage/sets (assumption is to do a replace).
> > > 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > > 4) recustomize kde as the ~/.kde will not be migrated
> > >
> > > Am I on the right track?
> >
> > No.
> >
> > 1) They're in portage.
>
> He's asking about the set files, not the ebuilds.

and you don't copy the set files.

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alan McKinnon]

On Sunday 16 August 2009 21:46:02 Volker Armin Hemmann wrote:
> On Sonntag 16 August 2009, Alan McKinnon wrote:
> > On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> > > Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > > > So for the kde-4.3 upgrade, it looks like this is what will be
> > > > necessary:
> > > >
> > > > 1) grab the sets again from the kde-testing overlay and put them in /
> > > > etc/portage/sets (assumption is to do a replace).
> > > > 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > > > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > > > 4) recustomize kde as the ~/.kde will not be migrated
> > > >
> > > > Am I on the right track?
> > >
> > > No.
> > >
> > > 1) They're in portage.
> >
> > He's asking about the set files, not the ebuilds.
>
> and you don't copy the set files.

Which set files does one not copy, and why?

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Volker Armin Hemmann]

On Sonntag 16 August 2009, Alan McKinnon wrote:
> On Sunday 16 August 2009 21:46:02 Volker Armin Hemmann wrote:
> > On Sonntag 16 August 2009, Alan McKinnon wrote:
> > > On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> > > > Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > > > > So for the kde-4.3 upgrade, it looks like this is what will be
> > > > > necessary:
> > > > >
> > > > > 1) grab the sets again from the kde-testing overlay and put them in
> > > > > / etc/portage/sets (assumption is to do a replace).
> > > > > 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > > > > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > > > > 4) recustomize kde as the ~/.kde will not be migrated
> > > > >
> > > > > Am I on the right track?
> > > >
> > > > No.
> > > >
> > > > 1) They're in portage.
> > >
> > > He's asking about the set files, not the ebuilds.
> >
> > and you don't copy the set files.
>
> Which set files does one not copy, and why?

you don't copy any set files because there is no reason to do so?

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alan McKinnon]

On Sunday 16 August 2009 23:09:41 Volker Armin Hemmann wrote:
> On Sonntag 16 August 2009, Alan McKinnon wrote:
> > On Sunday 16 August 2009 21:46:02 Volker Armin Hemmann wrote:
> > > On Sonntag 16 August 2009, Alan McKinnon wrote:
> > > > On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> > > > > Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > > > > > So for the kde-4.3 upgrade, it looks like this is what will be
> > > > > > necessary:
> > > > > >
> > > > > > 1) grab the sets again from the kde-testing overlay and put them
> > > > > > in / etc/portage/sets (assumption is to do a replace).
> > > > > > 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > > > > > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > > > > > 4) recustomize kde as the ~/.kde will not be migrated
> > > > > >
> > > > > > Am I on the right track?
> > > > >
> > > > > No.
> > > > >
> > > > > 1) They're in portage.
> > > >
> > > > He's asking about the set files, not the ebuilds.
> > >
> > > and you don't copy the set files.
> >
> > Which set files does one not copy, and why?
>
> you don't copy any set files because there is no reason to do so?

And if the changes between kde-4.2 and kde-4.3 DO require changes to the set 
files to build everything, then what should one do? Not copy the files and 
live with the omission/breakage?

Set files do not ship with a --sync, the user must either get them from 
somewhere or create them himself. And additions to 4.3 are not present in 4.2, 
so I don't understand your position. Seems to me that copying working set 
files from somewhere is a requirement in this case, especially if the user 
uses versioned set files.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Volker Armin Hemmann]

On Sonntag 16 August 2009, Alan McKinnon wrote:
> On Sunday 16 August 2009 23:09:41 Volker Armin Hemmann wrote:
> > On Sonntag 16 August 2009, Alan McKinnon wrote:
> > > On Sunday 16 August 2009 21:46:02 Volker Armin Hemmann wrote:
> > > > On Sonntag 16 August 2009, Alan McKinnon wrote:
> > > > > On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> > > > > > Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > > > > > > So for the kde-4.3 upgrade, it looks like this is what will be
> > > > > > > necessary:
> > > > > > >
> > > > > > > 1) grab the sets again from the kde-testing overlay and put
> > > > > > > them in / etc/portage/sets (assumption is to do a replace). 2)
> > > > > > > unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > > > > > > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > > > > > > 4) recustomize kde as the ~/.kde will not be migrated
> > > > > > >
> > > > > > > Am I on the right track?
> > > > > >
> > > > > > No.
> > > > > >
> > > > > > 1) They're in portage.
> > > > >
> > > > > He's asking about the set files, not the ebuilds.
> > > >
> > > > and you don't copy the set files.
> > >
> > > Which set files does one not copy, and why?
> >
> > you don't copy any set files because there is no reason to do so?
>
> And if the changes between kde-4.2 and kde-4.3 DO require changes to the
> set files to build everything, then what should one do? Not copy the files
> and live with the omission/breakage?
>
> Set files do not ship with a --sync, the user must either get them from
> somewhere or create them himself. And additions to 4.3 are not present in
> 4.2, so I don't understand your position. Seems to me that copying working
> set files from somewhere is a requirement in this case, especially if the
> user uses versioned set files.

you install kde-testing. Suddenly you have all the set files needed. you have 
all the unmask files needed. You have all keyword files needed.

And the overlay is not that big.

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Roy Wright]

On Aug 16, 2009, at 4:33 PM, Volker Armin Hemmann wrote:

> On Sonntag 16 August 2009, Alan McKinnon wrote:
>> On Sunday 16 August 2009 23:09:41 Volker Armin Hemmann wrote:
>>> On Sonntag 16 August 2009, Alan McKinnon wrote:
>>>> On Sunday 16 August 2009 21:46:02 Volker Armin Hemmann wrote:
>>>>> On Sonntag 16 August 2009, Alan McKinnon wrote:
>>>>>> On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
>>>>>>> Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
>>>>>>>> So for the kde-4.3 upgrade, it looks like this is what will be
>>>>>>>> necessary:
>>>>>>>>
>>>>>>>> 1) grab the sets again from the kde-testing overlay and put
>>>>>>>> them in / etc/portage/sets (assumption is to do a replace). 2)
>>>>>>>> unmerge kde-4.2 using: emerge --unmerge @kde-4.2
>>>>>>>> 3) merge kde-4.3 using: emerge -av @kde-4.3
>>>>>>>> 4) recustomize kde as the ~/.kde will not be migrated
>>>>>>>>
>>>>>>>> Am I on the right track?
>>>>>>>
>>>>>>> No.
>>>>>>>
>>>>>>> 1) They're in portage.
>>>>>>
>>>>>> He's asking about the set files, not the ebuilds.
>>>>>
>>>>> and you don't copy the set files.
>>>>
>>>> Which set files does one not copy, and why?
>>>
>>> you don't copy any set files because there is no reason to do so?
>>
>> And if the changes between kde-4.2 and kde-4.3 DO require changes  
>> to the
>> set files to build everything, then what should one do? Not copy  
>> the files
>> and live with the omission/breakage?
>>
>> Set files do not ship with a --sync, the user must either get them  
>> from
>> somewhere or create them himself. And additions to 4.3 are not  
>> present in
>> 4.2, so I don't understand your position. Seems to me that copying  
>> working
>> set files from somewhere is a requirement in this case, especially  
>> if the
>> user uses versioned set files.
>
> you install kde-testing. Suddenly you have all the set files needed.  
> you have
> all the unmask files needed. You have all keyword files needed.
>
> And the overlay is not that big.
>
I've been avoiding overlays (been bit a few times) and just running a  
testing (~x86) system.

The first blocker is kde-menu-icons-4.2.4 which looks like it is  
replaced by kdebase-menu-icons-4.3.0, but here's what happens when  
attempting to unmerge kde-menu-icons-4.2.4:

royw-gentoo portage # emerge --unmerge kde-menu-icons
Not unmerging package kde-base/kde-menu-icons-4.2.4 as it is
still referenced by the following package sets:
     kdebase


 >>> No packages selected for removal by unmerge

That's what started me looking for how to do the upgrade.

Went ahead and added the kde-testing overlay.  Then moved /etc/portage/ 
kde and /etc/portage/sets to /tmp.  This allowed "emerge -uDNav world"  
to not have any stoppers.

So it looks like the kde-4.3 upgrade is still tightly coupled to the  
kde-testing overlay.

Thank you,
Roy

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dirk Heinrichs]

[-- Attachment #1: Type: Text/Plain, Size: 418 bytes --]

Am Montag 17 August 2009 00:12:33 schrieb Roy Wright:

> So it looks like the kde-4.3 upgrade is still tightly coupled to the  
> kde-testing overlay.

No, it's not. I don't have the kde-testing overlay and update went smooth, 
except for the blockers you mentioned, but they were solved by simply 
uninstallind these ebuilds. The differences are:

1) I don't use sets.
2) I use paludis.

Bye...

	Dirk

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

Re: [gentoo-user] [solved] upgrading ~x68 kde-4.2 to kde-4.3 question

[Roy Wright]

On Aug 16, 2009, at 5:12 PM, Roy Wright wrote:

> Went ahead and added the kde-testing overlay.  Then moved /etc/ 
> portage/kde and /etc/portage/sets to /tmp.  This allowed "emerge - 
> uDNav world" to not have any stoppers.

Using the overlay for the new sets solved the upgrading.

The new features seem very problematic, for example assigning  
wallpaper to activities just doesn't work and just using activities  
seem to make the desktop extremely flaky.  Some plasmoids (like  
calendar) can be dragged from a panel to the desktop but some (like  
calculator) can not.  Then the upgrade re-enabled the stupid desktop  
search which maxes a core forever (at least an hour which is when I  
disabled it).  Also had to change the plasmoid theme back to oxygen  
from the new air.  Surprisingly the rest of my customized environment  
seemed to have survived the upgrade...

Thanks everyone!

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Dirk Heinrichs]

[-- Attachment #1: Type: Text/Plain, Size: 562 bytes --]

Am Sonntag 16 August 2009 23:18:40 schrieb Alan McKinnon:

> And if the changes between kde-4.2 and kde-4.3 DO require changes to the
> set files to build everything, then what should one do? Not copy the files
> and live with the omission/breakage?

I maybe wrong here, but aren't the sets in kde-testing just examples, which 
are equivalent to what to get with the meta ebuilds? And, they're not in 
portage, so they are not needed at all to install kde. So no, not copying them 
will not cause any breakage, using them may do so.

Bye...

	Dirk

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

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alex Schuster]

Roy Wright writes:

> kde-4.3 is now unmasked for ~x86.  Whooooop!

I'm also happy, and I want to upgrade soon. I hope many of those little 
annoyances I experience will be fixed.

> But it is looking like a non-trivial upgrade.  :(

Yeah.

> When I installed kde-4.2, I followed the advice of unmasking portage
> and using sets.  Also followed the recommendation to use -kdeprefix.
> Further I removed kde-3.5 and added a mask on kdelibs-3.5 to help keep
> 3.5 off of the system.
>
> So for the kde-4.3 upgrade, it looks like this is what will be
> necessary:
>
> 1) grab the sets again from the kde-testing overlay and put them in /
> etc/portage/sets (assumption is to do a replace).

I did that, too, but got errors from portage (Error during set creation: 
Redefinition of set...). Looks like the sets are found in the kde-testing 
overlay, so I removed them from /etc/portage/sets, and all was fine. Coool.

> 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2

Not really necessary I heard.
But: I am still using the dreaded kdeprefix use flag. It sounded like a good 
idea to use it, and I would also like to have different minor KDE versions 
alongside. Okay, it's hard to maintain, I understand it will be dropped.
Now, do I REALLY REALLY have to unmerge all @kde-4.2 first, remove the 
kdeprefix use flag, and proceed to step 3?

> 3) merge kde-4.3 using: emerge -av @kde-4.3

Hopefully this runs through. If it takes a night, it's okay, but if it stops 
in the middle, I have no KDE for a while. And I need much of the stuff in 
there, like the wallet with its passwords.

What about this: I update my system's backup (I'm using rdiff-backup), 
chroot into the backup, sudo to my account, and issue startkde. Could I get 
a running KDE 4.2? Then I would have time to install 4.3.

> 4) recustomize kde as the ~/.kde will not be migrated

I really hope I can just copy .kde4.2 to .kde4 and all (okay, most) settings 
will be kept. I think it just _should_ work. Customizing all over again 
every time a new KDE arrives would be no good.

	Wonko

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[John H. Moe]

Alex Schuster wrote:
> Roy Wright writes:
>
>   
>> kde-4.3 is now unmasked for ~x86.  Whooooop!
>>     
>
> I'm also happy, and I want to upgrade soon. I hope many of those little 
> annoyances I experience will be fixed.
>
>   
>> But it is looking like a non-trivial upgrade.  :(
>>     
>
> Yeah.
>
>   
>> When I installed kde-4.2, I followed the advice of unmasking portage
>> and using sets.  Also followed the recommendation to use -kdeprefix.
>> Further I removed kde-3.5 and added a mask on kdelibs-3.5 to help keep
>> 3.5 off of the system.
>>
>> So for the kde-4.3 upgrade, it looks like this is what will be
>> necessary:
>>
>> 1) grab the sets again from the kde-testing overlay and put them in /
>> etc/portage/sets (assumption is to do a replace).
>>     
>
> I did that, too, but got errors from portage (Error during set creation: 
> Redefinition of set...). Looks like the sets are found in the kde-testing 
> overlay, so I removed them from /etc/portage/sets, and all was fine. Coool.
>
>   
>> 2) unmerge kde-4.2 using: emerge --unmerge @kde-4.2
>>     
>
> Not really necessary I heard.
> But: I am still using the dreaded kdeprefix use flag. It sounded like a good 
> idea to use it, and I would also like to have different minor KDE versions 
> alongside. Okay, it's hard to maintain, I understand it will be dropped.
> Now, do I REALLY REALLY have to unmerge all @kde-4.2 first, remove the 
> kdeprefix use flag, and proceed to step 3?
>
>   
>> 3) merge kde-4.3 using: emerge -av @kde-4.3
>>     
>
> Hopefully this runs through. If it takes a night, it's okay, but if it stops 
> in the middle, I have no KDE for a while. And I need much of the stuff in 
> there, like the wallet with its passwords.
>
> What about this: I update my system's backup (I'm using rdiff-backup), 
> chroot into the backup, sudo to my account, and issue startkde. Could I get 
> a running KDE 4.2? Then I would have time to install 4.3.
>
>   
>> 4) recustomize kde as the ~/.kde will not be migrated
>>     
>
> I really hope I can just copy .kde4.2 to .kde4 and all (okay, most) settings 
> will be kept. I think it just _should_ work. Customizing all over again 
> every time a new KDE arrives would be no good.
>
> 	Wonko
>
>
>   

Well, I don't know about necessary, but on my box, when I tried to
update from kde-meta:4.2 to kde-meta:4.3, there were a few blockers that
wouldn't let it go through, so I ended up unmerging 4.2, then emerging
4.3 (which took about 4-6 hours, but I have distcc set up between two
boxes, so that probably sped things up).  However, I seem to remember
that the blockers were with PyQt, Python and eselect-python; I hadn't
thought about it, cause I'm still not THAT experienced with Linux in
general, and Gentoo in particular, but the Python update was a Big Deal,
so perhaps updating Python before the KDE upgrade would have been a good
idea.  :-P  Granted though, I didn't use sets, so it may be a bit
different for you.

Oh, and I didn't touch my .kde or .kde4 folders during this process, and
as far as I can tell, it's still using all of my customizations...

--==**==--
John Moe

Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question

[Alex Schuster]

John H. Moe writes:

> Alex Schuster wrote:
> > Roy Wright writes:

> >> 4) recustomize kde as the ~/.kde will not be migrated
> >
> > I really hope I can just copy .kde4.2 to .kde4 and all (okay, most)
> > settings will be kept. I think it just _should_ work. Customizing all
> > over again every time a new KDE arrives would be no good.

> Well, I don't know about necessary, but on my box, when I tried to
> update from kde-meta:4.2 to kde-meta:4.3, there were a few blockers that
> wouldn't let it go through, so I ended up unmerging 4.2, then emerging
> 4.3 (which took about 4-6 hours, but I have distcc set up between two
> boxes, so that probably sped things up).  However, I seem to remember
> that the blockers were with PyQt, Python and eselect-python; I hadn't
> thought about it, cause I'm still not THAT experienced with Linux in
> general, and Gentoo in particular, but the Python update was a Big Deal,
> so perhaps updating Python before the KDE upgrade would have been a good
> idea.  :-P  Granted though, I didn't use sets, so it may be a bit
> different for you.

Yes, emerge -p @kde-4.3 shows now problems. Maybe it's because of using 
sets, or I already have resolved the blockers, as I already had trouble with 
PyQt and such.

> Oh, and I didn't touch my .kde or .kde4 folders during this process, and
> as far as I can tell, it's still using all of my customizations...

This sounds good.

	Wonko