View previous topic :: View next topic |
Author |
Message |
telex4 l33t
Joined: 21 Sep 2002 Posts: 704 Location: Reading, UK
|
Posted: Fri Jul 23, 2004 10:51 am Post subject: |
|
|
Evangelion wrote: | telex4 wrote: |
Anyone have any submissions for the name of the next release? We've done Kindergarten, Klassroom and Kollege... |
My Guess: Akademy. You know it makes sense |
Well the 3.3final release will be called aKademy There will be a RC before then... |
|
Back to top |
|
|
Jakub Guru
Joined: 04 Oct 2003 Posts: 377 Location: Warsaw, Poland
|
Posted: Fri Jul 23, 2004 4:09 pm Post subject: |
|
|
Get ready.. set... emerge! |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Fri Jul 23, 2004 4:42 pm Post subject: |
|
|
I could of put it on my other host but I figured I'd let spymac handle the little load it might generate. Spymac is pretty slow in general anyways.
I see the official ebuild are out now, time to try to track down the problem with kdepim. I couldn't get it to compile last night, it kept saying it couldn't find lartskde or it wasn't defined. |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Fri Jul 23, 2004 4:59 pm Post subject: |
|
|
Ok I'm still getting the error when I try to emerge kdepim.
Code: | make: *** No rule to make target `-lartskde', needed by `kalarm/kalarm'. Stop.
|
Unsermake is on so not much usefull info to look back at. I'm going to try it with unsermake off since I haven't tried that yet. |
|
Back to top |
|
|
Phemt Apprentice
Joined: 05 Apr 2003 Posts: 242
|
Posted: Fri Jul 23, 2004 6:17 pm Post subject: |
|
|
!!! ERROR: kde-base/kdebase-3.3.0_beta2 failed.
!!! Function inherit, Line 1102, Exitcode 1
!!! died sourcing /usr/portage/eclass/kde-dist.eclass in inherit()
aux_get(): (0) Error in kde-base/kdebase-3.3.0_beta2 ebuild. (1)
Check for syntax error or corruption in the ebuild. (--debug)
emerge: create(): aux_get() error on kde-base/kdebase-3.3.0_beta2; aborting...
i get this error |
|
Back to top |
|
|
Shadowline n00b
Joined: 18 Sep 2003 Posts: 14
|
Posted: Fri Jul 23, 2004 6:35 pm Post subject: |
|
|
Calculating world dependencies \/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 160: unexpected EOF while looking for matching `"'
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 175: syntax error: unexpected end of file
!!! ERROR: x11-themes/baghira-deco-0.4_pre failed.
!!! Function inherit, Line 1102, Exitcode 1
!!! died sourcing /usr/portage/eclass/kde.eclass in inherit()
aux_get(): (0) Error in x11-themes/baghira-deco-0.4_pre ebuild. (1)
Check for syntax error or corruption in the ebuild. (--debug)
...done!
>>> emerge (1 of 9) kde-base/kdetoys-3.3.0_beta2 to /
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 160: unexpected EOF while looking for matching `"'
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 175: syntax error: unexpected end of file
!!! ERROR: kde-base/kdetoys-3.3.0_beta2 failed.
!!! Function inherit, Line 1102, Exitcode 1
!!! died sourcing /usr/portage/eclass/kde.eclass in inherit()
Gee, I guess I got a error to add also..... any ideas ? |
|
Back to top |
|
|
Phemt Apprentice
Joined: 05 Apr 2003 Posts: 242
|
Posted: Fri Jul 23, 2004 6:40 pm Post subject: |
|
|
Shadowline wrote: | Calculating world dependencies \/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 160: unexpected EOF while looking for matching `"'
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 175: syntax error: unexpected end of file
!!! ERROR: x11-themes/baghira-deco-0.4_pre failed.
!!! Function inherit, Line 1102, Exitcode 1
!!! died sourcing /usr/portage/eclass/kde.eclass in inherit()
aux_get(): (0) Error in x11-themes/baghira-deco-0.4_pre ebuild. (1)
Check for syntax error or corruption in the ebuild. (--debug)
...done!
>>> emerge (1 of 9) kde-base/kdetoys-3.3.0_beta2 to /
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 160: unexpected EOF while looking for matching `"'
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.eclass: line 175: syntax error: unexpected end of file
!!! ERROR: kde-base/kdetoys-3.3.0_beta2 failed.
!!! Function inherit, Line 1102, Exitcode 1
!!! died sourcing /usr/portage/eclass/kde.eclass in inherit()
Gee, I guess I got a error to add also..... any ideas ? |
mmm..same here..guess we will have to wait for an emerge sync that correct the problem |
|
Back to top |
|
|
Phemt Apprentice
Joined: 05 Apr 2003 Posts: 242
|
Posted: Fri Jul 23, 2004 7:12 pm Post subject: |
|
|
mmm...everything it's now ok again after a sync |
|
Back to top |
|
|
yog-sothoth n00b
Joined: 23 Jul 2004 Posts: 1
|
Posted: Fri Jul 23, 2004 7:17 pm Post subject: Still problems here after a sync |
|
|
but... it probably just hasn't propagated to the repository I'm using.
In the meantime, for others that don't have an updated copy yet, the error is easily fixed:
On line 91 of /usr/portage/eclass/kde.eclass change the line:
myconf="$myconf `use_with arts`
to:
myconf="$myconf `use_with arts`" |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Fri Jul 23, 2004 7:29 pm Post subject: |
|
|
I just checked my kde.eclass and it doesn't have any reference to arts in it.
I finally got kdepim to emerge, I disabled unsermake and it compiled ok. Just have kdeutils left and everything will be updated except games, edu, and sdk. |
|
Back to top |
|
|
himpierre l33t
Joined: 31 Aug 2002 Posts: 867 Location: Berlin
|
Posted: Fri Jul 23, 2004 8:10 pm Post subject: |
|
|
Everything compiled fine here on my amd64 in 64bit.
Thanks caleb.
t. |
|
Back to top |
|
|
Shadowline n00b
Joined: 18 Sep 2003 Posts: 14
|
Posted: Fri Jul 23, 2004 9:01 pm Post subject: |
|
|
a sync fixed my problem.... |
|
Back to top |
|
|
UclaBob Tux's lil' helper
Joined: 22 Oct 2002 Posts: 83
|
Posted: Fri Jul 23, 2004 9:36 pm Post subject: |
|
|
An emerge sync shows the following Kde 3.3 Beta 2 ebuilds:
Code: | [ebuild N ] kde-base/arts-1.3.0_beta2
[ebuild N ] kde-base/kdelibs-3.3.0_beta2
[ebuild N ] kde-base/kdebase-3.3.0_beta2 |
Since I have all of KDE installed, should I wait for the rest of the packages before emerging ? |
|
Back to top |
|
|
Jakub Guru
Joined: 04 Oct 2003 Posts: 377 Location: Warsaw, Poland
|
Posted: Fri Jul 23, 2004 9:42 pm Post subject: |
|
|
As far as I can tell, all (or almost all) of them are there. Maybe check the /usr/portage/kde-base directories for specific ebuilds.
Moreover, they are listed here:
http://packages.gentoo.org/
so they should be available. |
|
Back to top |
|
|
UclaBob Tux's lil' helper
Joined: 22 Oct 2002 Posts: 83
|
Posted: Fri Jul 23, 2004 9:59 pm Post subject: |
|
|
Yeah, oddly enough I have all of the ebuilds in the /usr/portage directories....however, I don't know why only some would show up after an emerge sync |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Fri Jul 23, 2004 10:14 pm Post subject: |
|
|
It could be that those are the only packages in your world file? Either that or some of them got masked by something.
What does the following show?
Code: | emerge arts kdelibs kdebase kdemultimedia kdenetwork kdegraphics kdeaccessibility kdeartwork kdeadmin kdepim kdeaddons kdeutils -vp
|
|
|
Back to top |
|
|
Phemt Apprentice
Joined: 05 Apr 2003 Posts: 242
|
Posted: Sat Jul 24, 2004 4:41 am Post subject: |
|
|
have some problems with kdemultimedia...it didn't compiled juk (I HAVE taglib installed) and didn't find ogg/vorbis support.
I use gcc 3.4.1 but with alpha, beta1 cvs and 3.2.x I didn't have this problem so I guess it's not gcc. |
|
Back to top |
|
|
Phemt Apprentice
Joined: 05 Apr 2003 Posts: 242
|
Posted: Sat Jul 24, 2004 5:27 am Post subject: |
|
|
Phemt wrote: | have some problems with kdemultimedia...it didn't compiled juk (I HAVE taglib installed) and didn't find ogg/vorbis support.
I use gcc 3.4.1 but with alpha, beta1 cvs and 3.2.x I didn't have this problem so I guess it's not gcc. |
tried to emerge again taglib, libogg, vorbis-tools and kdemultimedia..still no juk |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Sat Jul 24, 2004 5:46 am Post subject: |
|
|
These are the only dependencies that would seem to be needed by juk.
media-libs/taglib
media-sound/cdparanoia
media-sound/trm
encode media-sound/lame
flac media-libs/flac
oggvorbis media-libs/libvorbis
alsa media-libs/alsalib
You might try re-emerging all of them, and musicbrainz too if you don't have it. It goes along with trm. |
|
Back to top |
|
|
p h a n t n00b
Joined: 29 May 2003 Posts: 56 Location: Berlin, Germany
|
Posted: Sat Jul 24, 2004 7:34 am Post subject: |
|
|
I cant restore maximized windows anymore
It's very strange, since it only happens with one specific user account (my main one unfortunately). I have already deleted all previous kde config files in ~, thus started "configuring from scratch again" - no luck. Does anyone experience the same behaviour? When I click the restore button nothing happens and the windows remain maximized. A right click on the title bar shows me a greyed [x] Maximize which can't be changed. |
|
Back to top |
|
|
JLP Tux's lil' helper
Joined: 13 Sep 2003 Posts: 143 Location: Slovenia
|
Posted: Sat Jul 24, 2004 8:07 am Post subject: |
|
|
I compile from CVS and I also have a similar problem. I can restore windows just fine. But Fullscreen mode doesn't work correctly for me in any application. It goies into FS just fine but when I try to get out of it it just remains in FS.
Oh and I have a problem with KOragnizer crashing even before it starts up. In libthread_db.so.1.
And playing notification sounds very quickly just freezes my whole machine completely
That is about it. Other things work very well. _________________ Live long and prosper! |
|
Back to top |
|
|
Raoul_Duke l33t
Joined: 15 Dec 2002 Posts: 694 Location: Caerdydd, Wales
|
Posted: Sat Jul 24, 2004 8:54 am Post subject: |
|
|
Is it a good idea to have the beta builds in the '~x86' arch?
I don't want to run two versions of KDE but i also don't want to have all the ebuilds showing up on my 'emerge -uDvp world'
Is there a good reason why they're not masked?
ps. i'm not complaining, just curious _________________ www.iamthepenguin.com |
|
Back to top |
|
|
Jakub Guru
Joined: 04 Oct 2003 Posts: 377 Location: Warsaw, Poland
|
Posted: Sat Jul 24, 2004 8:58 am Post subject: |
|
|
Well I certainly have them masked . Maybe you unmasked them? (in /etc/portage/package.unmask)?
EDIT: Hmm, now that's strange, I can see the line:
Code: |
KEYWORDS="~x86 ~amd64"
|
in the ebuilds. But I *think* when I did emerge -u world they didn't show up (they did after I put them in package.unmask). Now I'm majorly confused. |
|
Back to top |
|
|
Raoul_Duke l33t
Joined: 15 Dec 2002 Posts: 694 Location: Caerdydd, Wales
|
Posted: Sat Jul 24, 2004 9:04 am Post subject: |
|
|
Jakub wrote: | Well I certainly have them masked . Maybe you unmasked them? (in /etc/portage/package.unmask)?
EDIT: Hmm, now that's strange, I can see the line:
Code: |
KEYWORDS="~x86 ~amd64"
|
in the ebuilds. But I *think* when I did emerge -u world they didn't show up (they did after I put them in package.unmask). Now I'm majorly confused. |
I certainly don't remember unmasking them.....weird _________________ www.iamthepenguin.com |
|
Back to top |
|
|
Jakub Guru
Joined: 04 Oct 2003 Posts: 377 Location: Warsaw, Poland
|
Posted: Sat Jul 24, 2004 9:19 am Post subject: |
|
|
There's something I don't understand and I would be glad if someone could explain this to me.
I've always thought a package is either in the x86 arch or in the unstable ~x86 arch (and will show up in emerge -u world if you have the appropriate ACCEPT_KEYWORDS option in your /etc/make.cong) OR it is hard-masked and then, well, it doesn't have the KEYWORDS part in the ebuild and it won't show in emerge -u world (in order to install it, you have to either point emerge to a specific ebuild file or unmask it in package.unmask).
So could someone who's more competent clarify this for me? If the betas are not hard-masked, I would also be very interested why it's so (after all, they could potentially be very unstable, with some grave, not yet discovered bugs). |
|
Back to top |
|
|
|