kde 3.4rc1 is out!

Message

StringCheesian · Post by **StringCheesian** » Sun Feb 27, 2005 3:18 am

firephoto wrote:I renamed all of beta2* to rc1 in my local/portage/kde-base/ [...]

Did you have to edit the kdelibs-3.4.0_beta2 ebuild? It's got this in it (line 8):

MY_PV=3.3.92

firephoto · Post by **firephoto** » Sun Feb 27, 2005 3:25 am

StringCheesian wrote:
firephoto wrote:I renamed all of beta2* to rc1 in my local/portage/kde-base/ [...]
Did you have to edit the kdelibs-3.4.0_beta2 ebuild? It's got this in it (line :
Code: Select all
MY_PV=3.3.92

No because kdelibs*rc1 is already in portage.

You have to digest ALL the ebuilds (300+ for everything) so unless there's some way to do them all easily it means one by one on the command line or with abeni.

fuji · Post by **fuji** » Sun Feb 27, 2005 4:11 am

Just off the top of my head, but would this work?
`find /usr/portage/kde-base -iname '*rc1.ebuild' -exec /usr/sbin/ebuild {} digest \;`

firephoto · Post by **firephoto** » Sun Feb 27, 2005 4:23 am

I knew it was possible but never tried to figure it out.

fuji wrote:Just off the top of my head, but would this work?
`find /usr/portage/kde-base -iname '*rc1.ebuild' -exec /usr/sbin/ebuild {} digest \;`

Works like a dream. I just adjusted it to my /usr/local/portage, did a test on a specific directory, worked, backed off to all of kde-base, works great it seems.

Code: Select all

# find /usr/local/portage/kde-base -iname '*rc1.ebuild' -exec /usr/sbin/ebuild {} digest \;
>>> Generating digest file...
<<< kdeutils-3.3.90.tar.bz2
<<< kdeutils-3.3.90-3.3.91.tar.xdelta
<<< kdeutils-3.3.91-3.3.92.tar.xdelta
<<< kdeutils-3.3.92-3.4.0-rc1.tar.xdelta
<<< kdeutils-3.4.0-rc1.tar.bz2
>>> Generating manifest file...
<<< ChangeLog
<<< metadata.xml
<<< ark-3.4.0_rc1.ebuild
<<< files/digest-ark-3.4.0_rc1
>>> Computed message digests.

>>> Generating digest file...
>>> Generating manifest file...
<<< kde-3.3.2.ebuild
<<< kde-3.4.0_rc1.ebuild
<<< ChangeLog
<<< kde-3.2.3.ebuild
<<< metadata.xml
<<< kde-3.3.1.ebuild
<<< files/digest-kde-3.4.0_rc1
<<< files/digest-kde-3.2.3
<<< files/digest-kde-3.3.1
<<< files/digest-kde-3.3.2
>>> Computed message digests.

>>> Generating digest file...
<<< kdeutils-3.3.90.tar.bz2
<<< kdeutils-3.3.90-3.3.91.tar.xdelta
<<< kdeutils-3.3.91-3.3.92.tar.xdelta
<<< kdeutils-3.3.92-3.4.0-rc1.tar.xdelta
<<< kdeutils-3.4.0-rc1.tar.bz2
>>> Generating manifest file...
<<< ChangeLog
<<< metadata.xml
<<< kdf-3.4.0_rc1.ebuild
<<< files/digest-kdf-3.4.0_rc1
>>> Computed message digests.

>>> Generating digest file...
<<< kdebase-3.3.90.tar.bz2
<<< kdebase-3.3.90-3.3.91.tar.xdelta
<<< kdebase-3.3.91-3.3.92.tar.xdelta
<<< kdebase-3.3.92-3.4.0-rc1.tar.xdelta
<<< kdebase-3.4.0-rc1.tar.bz2
>>> Generating manifest file...
<<< kdm-3.4.0_rc1.ebuild
<<< ChangeLog
<<< metadata.xml
<<< files/kde.pam
<<< files/agent-shutdown.sh
<<< files/kde-np.pam
<<< files/agent-startup.sh
<<< files/digest-kdm-3.4.0_rc1
...
..
.
:)

Could of saved me lots of clicks earlier but I didn't have too many packages to digest. Thanks a lot, will come in handy when I make a set of kde "snapshot" ebuilds for my overlay.

younker · Post by **younker** » Sun Feb 27, 2005 5:07 am

I've emerged kde 3.4beta2, and I found the menu not worked as my expection, I choose to show prefrence menu from kcontrol, but I can't see the menu item in kmenu, I hope rc1 will resolve these problem.

Phemt · Post by **Phemt** » Sun Feb 27, 2005 10:39 am

someone who has a working overlay from kdebase?

It would be very apprecied

blaster999 · Post by **blaster999** » Sun Feb 27, 2005 10:45 am

younker wrote:I've emerged kde 3.4beta2, and I found the menu not worked as my expection, I choose to show prefrence menu from kcontrol, but I can't see the menu item in kmenu, I hope rc1 will resolve these problem.

Yes, it is a known problem - I posted it to kde bugzilla, and they told me it's fixed in CVS, so rc1 does not have this issue.

Gaspode · Post by **Gaspode** » Sun Feb 27, 2005 12:43 pm

fuji wrote:Just off the top of my head, but would this work?
`find /usr/portage/kde-base -iname '*rc1.ebuild' -exec /usr/sbin/ebuild {} digest \;`

Why not simply use emerge --digest? For some reason, most people don't seem to know that option for emerge... this will automatically digest all packages during the emerge.

Merlin-TC · Post by **Merlin-TC** » Sun Feb 27, 2005 3:30 pm

Any news on when the rest of the ebuilds will be out? Right now it's only arts and kdelibs isn't it?

_hephaistos_ · Post by **_hephaistos_** » Sun Feb 27, 2005 3:58 pm

Merlin-TC wrote:Right now it's only arts and kdelibs isn't it?

yes... unfortunately

elsenator · Post by **elsenator** » Sun Feb 27, 2005 4:00 pm

Merlin-TC wrote:Any news on when the rest of the ebuilds will be out? Right now it's only arts and kdelibs isn't it?

Yes, it is. I'm quite sure they are working to get them done right now... But i guess it might take a while before it's up in the repository. We'll just have to wait.

firephoto · Post by **firephoto** » Sun Feb 27, 2005 4:21 pm

Gaspode wrote:
fuji wrote:Just off the top of my head, but would this work?
`find /usr/portage/kde-base -iname '*rc1.ebuild' -exec /usr/sbin/ebuild {} digest \;`
Why not simply use emerge --digest? For some reason, most people don't seem to know that option for emerge... this will automatically digest all packages during the emerge.

That seems to work too and my guess to why it's unknown is...

Code: Select all

~ # emerge --help | grep -ie digest
~ #

The only mention of digest comes up in the man:ebuild page. Thanks for the tip though it does work out better than digesting ALL the ebuilds.

I got the thinkpad updated to rc1, it only has arts, libs, base on it though.

Corny · Post by **Corny** » Sun Feb 27, 2005 7:06 pm

What's up with the ebuilds? It didn't took them so long with the betas, or is it just me and my impatiency?

Are there problems with the RC1?

firephoto · Post by **firephoto** » Sun Feb 27, 2005 7:38 pm

*edit The official ebuilds are out, see below. edit*

Phlogiston · Post by **Phlogiston** » Sun Feb 27, 2005 9:09 pm

why waiting?

They are out now!!!

*happy* compiling

the only problem:

Code: Select all

[nomerge      ] kde-base/kde-i18n-3.4.0_beta2  +arts -debug -kdeenablefinal -xinerama
[ebuild     UD]  kde-base/kdelibs-3.4.0_beta2 [3.4.0_rc1] +alsa +arts +cups -debug -doc -jpeg2k -kdeenablefinal -kerberos -openexr +spell +ssl +tiff -xinerama 0 kB

I think copying and renaming this ebuild should work, but I'm wondering why always the i18n ebuild is missing on kde releases???

firephoto · Post by **firephoto** » Sun Feb 27, 2005 9:27 pm

They unsplit all the konqueror-plugins so now it seems to be all or nothing for them. I hope that means the stupid rellinks bar doesn't pop up all the time still.

Maybe there was some breakage due to the split of the konqueror-plugins?

kdepim packages seem to be emerging now but they're not all there yet.

Phlogiston · Post by **Phlogiston** » Sun Feb 27, 2005 9:38 pm

Phlogiston. wrote: I think copying and renaming this ebuild should work, but I'm wondering why always the i18n ebuild is missing on kde releases???

Unfortunately this does not work here:

Code: Select all

config.pl: fast created 297 file(s).
config.status: creating config.h

Good - your configure finished. Start make now

WARNING: use unsermake instead of make or use a wrapper script, e.g. makeobj!!!
unsermake all
make: unsermake: Kommando nicht gefunden
make: *** [all] Fehler 127

!!! ERROR: kde-base/kde-i18n-3.4.0_rc1 failed.
!!! Function kde_src_compile, Line 166, Exitcode 2
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, NOT this status message.

Any hint?

I also merged unsermake:

Code: Select all

ARNING: use unsermake instead of make or use a wrapper script, e.g. makeobj!!!
unsermake all
ACCESS DENIED  unlink:    /usr/kde/unsermake/utilities.pyc
ACCESS DENIED  open_wr:   /usr/kde/unsermake/utilities.pyc
ACCESS DENIED  unlink:    /usr/kde/unsermake/handlerbase.pyc
ACCESS DENIED  open_wr:   /usr/kde/unsermake/handlerbase.pyc
ACCESS DENIED  unlink:    /usr/kde/unsermake/target.pyc
ACCESS DENIED  open_wr:   /usr/kde/unsermake/target.pyc
ACCESS DENIED  unlink:    /usr/kde/unsermake/program.pyc
ACCESS DENIED  open_wr:   /usr/kde/unsermake/program.pyc
all.am does not exist!
make: *** [all] Fehler 1

^PsYcHo · Post by **^PsYcHo** » Sun Feb 27, 2005 10:40 pm

Packages.gentoo. is looking real beautiful with rc1 all over the place

iverson0881 · Post by **iverson0881** » Sun Feb 27, 2005 10:46 pm

Looks like they did a little typo with lm_sensors package.

Code: Select all

emerge -uDavt world

These are the packages that I would merge, in reverse order:

Calculating world dependencies        er
emerge: there are no ebuilds to satisfy "sys-apps/lm-sensors".


!!! Problem with ebuild kde-base/kde-meta-3.4.0_rc1
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.

should've read "sys-apps/lm_sensors" .

firephoto · Post by **firephoto** » Sun Feb 27, 2005 11:19 pm

lm sensors changed their name today in portage, - to a _.

The konq-plugins*rc1 ebuild is incorrect, it's an old copy of the ark-plugins ebuild with the new name. the konq-plugins*beta2 ebuild is correct for the new combined way.

Still a few packages missing but I think I have my system up to date now.

Lokheed · Post by **Lokheed** » Sun Feb 27, 2005 11:55 pm

firephoto wrote:lm sensors changed their name today in portage, - to a _.

The konq-plugins*rc1 ebuild is incorrect, it's an old copy of the ark-plugins ebuild with the new name. the konq-plugins*beta2 ebuild is correct for the new combined way.

Still a few packages missing but I think I have my system up to date now.

I am wondering if they got rid of the various plugins and are just going with this one ebuild? That would suck as I only want a few plugins and not all. I will wait till all the packages arrive...more than a couple are still missing.

Also did you file a bug report for the konq-plugins error?

EDIT: I saw your post above that they indeed got rid of the various plugins...to bad.

iverson0881 · Post by **iverson0881** » Sun Feb 27, 2005 11:56 pm

I found that "ksysguard-3.4.0_rc1" is the problem. It has the incorrect "-" instead of "_"

Should I report this into the bug or do devs look at this post?

Lokheed · Post by **Lokheed** » Mon Feb 28, 2005 12:01 am

iverson0881 wrote:I found that "ksysguard-3.4.0_rc1" is the problem. It has the incorrect "-" instead of "_"

Should I report this into the bug or do devs look at this post?

Report it please.

firephoto · Post by **firephoto** » Mon Feb 28, 2005 12:02 am

Lokheed wrote:
firephoto wrote:lm sensors changed their name today in portage, - to a _.

The konq-plugins*rc1 ebuild is incorrect, it's an old copy of the ark-plugins ebuild with the new name. the konq-plugins*beta2 ebuild is correct for the new combined way.

Still a few packages missing but I think I have my system up to date now.
I am wondering if they got rid of the various plugins and are just going with this one ebuild? That would suck as I only want a few plugins and not all. I will wait till all the packages arrive...more than a couple are still missing.

Also did you file a bug report for the konq-plugins error?

I filed a bug, probably a few others too that will show up with the ebuilds. I have one system that I'm waiting for the official ebuilds to all show up then I'll emerge world on it and check everything out good with the ebuilds.

iverson0881 if you've tracked down the problem for sure I'd file a bug, make sure it's reported to the kde team, it's in the guided report.

iverson0881 · Post by **iverson0881** » Mon Feb 28, 2005 12:04 am

bug is here:
http://bugs.gentoo.org/show_bug.cgi?id=83506