Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[kde-testing] and [kde-crazy] KDE4 overlays thread (part 2)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 5, 6, 7 ... 28, 29, 30  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
mkyral
Apprentice
Apprentice


Joined: 06 May 2007
Posts: 152
Location: Czech Republic

PostPosted: Sun Oct 26, 2008 8:27 pm    Post subject: Reply with quote

Well, I have installed 4.1.71 and no playground-plasma installed, I re-emerged all plasma thinks, but plasma still crashes :-(

Code:

Object::connect: No such signal TaskManager::TaskItem::changed()
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
ksmserver: Fatal IO error: client killed
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 137 requests (135 known processed) with 0 events remaining.
kded4: Fatal IO error: client killed
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 20 requests (8 known processed) with 0 events remaining.
ICE default IO error handler doing an exit(), pid = 6036, errno = 0

Code:

[21:20:00 root@gool marian]# eix -Ic plasma
[I] kde-base/kdeplasma-addons (4.1.71(4.2)[1]@26.10.2008): Extra Plasma applets and engines.
[I] kde-base/libplasma (4.1.71(4.2)[1]@26.10.2008): Plasma: KDE desktop framework
[I] kde-base/plasma-apps (4.1.71(4.2)[1]@26.10.2008): Additional Applets for Plasma
[I] kde-base/plasma-workspace (4.1.71(4.2)[1]@26.10.2008): Plasma: KDE desktop framework
[I] kde-base/libplasmaclock [1] (4.1.71(4.2)@26.10.2008): A library for KDE desktop applications
[1] "kde-crazy" /usr/local/portage/layman/kde-crazy
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Sun Oct 26, 2008 11:57 pm    Post subject: Reply with quote

Okay. I see kde-crazy in layman now. Thanks. I will remove the other two overlays. Any reason for this juggling of the names?
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Mon Oct 27, 2008 2:45 am    Post subject: Reply with quote

Let me get this straight. :roll:
If we were happily running along using the kdesvn-portage overlay, we now need to remove it and our entire current kdesvn installation, and essentially start over from scratch with
Code:
layman -a kde-crazy

and set it up correctly in /etc/portage with symlinks to the new layman/kde-crazy files, which will be explained in the kde-crazy overlay?

And this will get us back to using kdesvn in portage, as before with sets, keywords, etc., but just in a new overlay?

How about a quick step by step rundown of the correct procedure?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental
Back to top
View user's profile Send private message
tampakrap
Retired Dev
Retired Dev


Joined: 27 Nov 2007
Posts: 71
Location: Prague, Czech Republic

PostPosted: Mon Oct 27, 2008 6:54 am    Post subject: Reply with quote

Let me solve your questions.
Kdesvn-portage overlay closed because we wanted to move live ebuilds and snapshots to kde-testing which is the official kde-herd overlay. Now those ebuilds are being reviewed by the kde-herd, so we gain better communication with the other kde versions (4.X and 3.5), with the official eclasses and we added new features like the kdeprefix useflag. But because the kde-herd wanted to have "stable" ebuilds to kde-testing, they created kde-crazy overlay (which is also an official kde-herd overlay) but with highly experimental ebuilds. I don't know the status of snapshots (i think they are ready) but live ebuilds are not ready yet. I hope they will be tomorrow.
There will also be a kde-live-guide to kde.gentoo.org but we will write it after we finish the ebuilds. so stay tuned. we will try to make transition as much easy and normal as we can.
Back to top
View user's profile Send private message
scarabeus
Developer
Developer


Joined: 25 Oct 2008
Posts: 95
Location: Europe/Prague

PostPosted: Mon Oct 27, 2008 7:03 am    Post subject: Reply with quote

tampakrap wrote:
Let me solve your questions.
Kdesvn-portage overlay closed because we wanted to move live ebuilds and snapshots to kde-testing which is the official kde-herd overlay. Now those ebuilds are being reviewed by the kde-herd, so we gain better communication with the other kde versions (4.X and 3.5), with the official eclasses and we added new features like the kdeprefix useflag. But because the kde-herd wanted to have "stable" ebuilds to kde-testing, they created kde-crazy overlay (which is also an official kde-herd overlay) but with highly experimental ebuilds. I don't know the status of snapshots (i think they are ready) but live ebuilds are not ready yet. I hope they will be tomorrow.
There will also be a kde-live-guide to kde.gentoo.org but we will write it after we finish the ebuilds. so stay tuned. we will try to make transition as much easy and normal as we can.


Well tampakrap put it corectly but I might add that biggest benefit for you will be usage of the same eclasses that will be in the main tree.
What does it mean?
Global eclass updates will be applied for all kde versions at once.
What else it means that we support it?
If something break in one version of kde4 it is more likely to be fixed in all versions.
About guide, If you use some basic logic you can use as starters guide for 4.1 (http://www.gentoo.org/proj/en/desktop/kde/kde4-guide.xml)
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Mon Oct 27, 2008 9:42 am    Post subject: Reply with quote

All this sounds great, and I'm not complaining, and maybe I'm just misunderstanding, but from the above two posts I can't figure out where regular kdesvn live (not kdesvn snapshots) is going to wind up.

In "kde-crazy," "kde-testing," or a new overlay called "kde-live"?

One statement refers to kde-testing having "stable" ebuilds, and another refers to moving live ebuilds to testing. I was under the impression that kdesvn was always "experimental," which is referenced to as kde-crazy. So, bottom line is, I'm unclear on this stuff. :roll:

I'll anxiously await the new stuff, but not-to-worry, I'll play with my Paludis kdesvn partition and/or my Arch Linux kdesvn install until then. :)
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental
Back to top
View user's profile Send private message
tampakrap
Retired Dev
Retired Dev


Joined: 27 Nov 2007
Posts: 71
Location: Prague, Czech Republic

PostPosted: Mon Oct 27, 2008 12:31 pm    Post subject: Reply with quote

apparently i was not clear enough
kde-testing is supposed to have ebuilds that are going to be transferred to portage. no live ebuilds, no snapshots. this is the overlay that is safe to use, as it won't break your current gentoo-kde installation.
kde-crazy is going to host live ebuilds (what you called kdesvn) snapshots, and maybe other experimental ebuilds. This is a highly experimental overlay and we do not guarantee that it won't break. After all, current users of kde live ebuilds already now that :wink:
Currently live ebuilds are still under development in kde-crazy and i hope tomorrow to be finished. Personally i'm in a little hurry preparing those ebuilds as i want to install them to my new toshiba qosmio!!!
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Mon Oct 27, 2008 2:16 pm    Post subject: Reply with quote

Quote:
I don't know the status of snapshots (i think they are ready)


The kde-meta:4.2 ebuild is not there yet and there are no sets for portage only paludis.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Mon Oct 27, 2008 4:29 pm    Post subject: Reply with quote

tampakrap,
Thanks for the clarification, however I'm still not completely clear on this. :lol:

As I've always understood it, "snapshots" and regular "kdesvn" are two completely different things, in that "kdesvn" is the ongoing trunk and you can update at any time day or night, and "snapshots" are daily or weekly "frozen" updates done once a day or week, and when you install these you are getting the state of the trunk at the time.

Thus, if you wanted to update with snapshots, you would need to wait until the next day, or week, when that specific "snapshot" is taken, and then made available.

Is that incorrect?

So when you say
Quote:
kde-crazy is going to host live ebuilds (what you called kdesvn) snapshots

I'm not exactly sure what this means. :) I assume what you mean by "live ebuilds" is what we were doing in kdesvn-portage, but then the added "snapshots" term seems to mean something else, at least according to my understanding of what a kde "snapshot" is.

In any case, I wish to keep up my kdesvn installations, as I've found it much better than any "staitic" kde-4.x.x release I've ever tried, at least until kde-4.2.1 is officially in ~x86.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Mon Oct 27, 2008 4:39 pm    Post subject: Reply with quote

Snapshots are the 4.1.69 ... releases. These are snapshots of the svn tree created by the kde team every so often.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
tampakrap
Retired Dev
Retired Dev


Joined: 27 Nov 2007
Posts: 71
Location: Prague, Czech Republic

PostPosted: Mon Oct 27, 2008 4:42 pm    Post subject: Reply with quote

kde-crazy is going to host live ebuilds (what you called kdesvn) and snapshots <-- i find it clear :P

yes, snapshots are updated once a week and live ebuilds are updated every minute
Personally i use kde-3.5 in my main desktop and won't switch until kde-4.2 comes out kdevelop, amarok and k3b release stable versions. But in my testing machines i have kde-4.X and live ebuilds
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Mon Oct 27, 2008 5:23 pm    Post subject: Reply with quote

Yes, but the "and" wasn't there to clearly qualify that the snapshots were going to be in addition to the kdesvn live ebuilds. That was the source of my misunderstanding of what you meant.

Thanks for clearing this up, and I'm really looking forward to this new setup. :) All of us wanting to keep running kdesvn in portage really appreciate all the great work you guys do.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental


Last edited by wrc1944 on Tue Oct 28, 2008 8:01 am; edited 1 time in total
Back to top
View user's profile Send private message
Mafteah
Apprentice
Apprentice


Joined: 30 May 2003
Posts: 265
Location: IL

PostPosted: Tue Oct 28, 2008 5:41 am    Post subject: Reply with quote

Someone got digikam emerged?
_________________
http://www.mafteah.co.il
Back to top
View user's profile Send private message
tampakrap
Retired Dev
Retired Dev


Joined: 27 Nov 2007
Posts: 71
Location: Prague, Czech Republic

PostPosted: Tue Oct 28, 2008 1:00 pm    Post subject: Reply with quote

wrc1944 wrote:
Yes, but the "and" wasn't there to clearly qualify that the snapshots were going to be in addition to the kdesvn live ebuilds. That was the source of my misunderstanding of what you meant.


my "i find it clear" sentence was meant to be just a joke :)

We may finish the merge today cross your fingers
Back to top
View user's profile Send private message
reavertm
Developer
Developer


Joined: 05 Feb 2004
Posts: 264
Location: Wrocław

PostPosted: Tue Oct 28, 2008 4:40 pm    Post subject: Reply with quote

I'm going to got this thread to be renamed to [kde-testing] and [kde-crazy] KDE4 overlays support thread (part2) - any objections? :)
updated info will be available here soon
_________________
Maciek
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Tue Oct 28, 2008 8:49 pm    Post subject: Reply with quote

reavertm wrote:
Quote:
I'm going to got this thread to be renamed to [kde-testing] and [kde-crazy] KDE4 overlays support thread (part2) - any objections? :)
updated info will be available here soon
I guess that sounds fine to me, however, I'm wondering why "testing" which I thought was supposed to have ebuilds that are going to be transferred to portage. no live ebuilds, no snapshot, and "crazy" which was going to be for "live" and snapshots of kdesvn trunk would be in the same thread.

I would think having kdesvn live and perhaps kdesvn trunk snapshots in a single thread dedicated only to them only would keep it better organized, as problems coming up in svn trunk often have little relevance for people not running svn. I know in the last year I've had trouble keeping track all the threads and posts involving kde4, with both x.x.x releases and svn in the same thread.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental
Back to top
View user's profile Send private message
letchideslandes
Apprentice
Apprentice


Joined: 21 Nov 2004
Posts: 197
Location: Landes France

PostPosted: Wed Oct 29, 2008 1:10 pm    Post subject: Reply with quote

Hello

I just switch from kde-9999 to kde-snapshot (4.1.71), but there's not ebuild and snapshot package for kde-l10n. Is there a plan to do it or may i wait for for kde-4.2 release ? (sorry i'm french).
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Wed Oct 29, 2008 1:42 pm    Post subject: Reply with quote

tampakrap wrote:
Quote:
We may finish the merge today cross your fingers

I got the kde-crazy overlay, but looking at /usr/local/portage/layman/kde-crazy/Documentation/TODO it seems like it's not quite ready yet.

Is that correct, and will we have a little run-down posted here on how to correctly move from kdesvn-portage to kde-crazy?

Or, is all the info we need going to be in /usr/local/portage/layman/kde-crazy/Documentation/kde4-guide.xml?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental


Last edited by wrc1944 on Wed Oct 29, 2008 1:48 pm; edited 1 time in total
Back to top
View user's profile Send private message
tampakrap
Retired Dev
Retired Dev


Joined: 27 Nov 2007
Posts: 71
Location: Prague, Czech Republic

PostPosted: Wed Oct 29, 2008 1:47 pm    Post subject: Reply with quote

live ebuilds and snapshots now available in kde-crazy overlay! guide coming in a while :)
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Wed Oct 29, 2008 2:10 pm    Post subject: Reply with quote

Is it difficult (or breaks some rules...) to make a docs only ebuild for kdelibs? I mean the the kdelibs code emerges in a few minutes (ccache installed) but then the docs take a very long time to build and I do not want to rebuild them for every snapshot upgrade. I guess I could just disable the docs but sometimes I actually look at these...
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
mkyral
Apprentice
Apprentice


Joined: 06 May 2007
Posts: 152
Location: Czech Republic

PostPosted: Wed Oct 29, 2008 9:22 pm    Post subject: Reply with quote

Huh,
does anybody know, what does it mean?

Code:

[22:13:48 root@nbmkyral package.mask]# emerge -uavtDN world
--- Invalid atom in /etc/portage/package.unmask: @kdeaccessibility-4.2
--- Invalid atom in /etc/portage/package.mask: @kdeaccessibility-4.1
 * Overlay eclasses override eclasses from PORTDIR:
 *
 *   '/usr/local/portage/layman/arcon/eclass/bzr.eclass'
 *   '/usr/local/portage/layman/kde-crazy/eclass/kde4-base.eclass'
 *   '/usr/local/portage/layman/kde-crazy/eclass/kde4-functions.eclass'
 *   '/usr/local/portage/layman/kde-crazy/eclass/kde4-meta.eclass'
 *
 * It is best to avoid overriding eclasses from PORTDIR because it will
 * trigger invalidation of cached ebuild metadata that is distributed with
 * the portage tree. If you must override eclasses from PORTDIR then you
 * are advised to add FEATURES="metadata-transfer" to /etc/make.conf and to
 * run `emerge --regen` after each time that you run `emerge --sync`. Set
 * PORTAGE_ECLASS_WARNING_ENABLE="0" in /etc/make.conf if you would like to
 * disable this warning.

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

Calculating dependencies... done!
[nomerge      ] kde-base/kwin-3.5.10  USE="kdehiddenvisibility xcomposite -debug"  [0]
[blocks b     ]  =kde-base/kdebase-3.5* ("=kde-base/kdebase-3.5*" is blocking kde-base/kdeprint-3.5.10, kde-base/kmenuedit-3.5.10, kde-base/kcminit-3.5.10, kde-base/ksplashml-3.5.10, kde-base/konsole-3.5.10, kde-base/knetattach-3.5.10, kde-base/libkonq-3.5.10, kde-base/kcontrol-3.5.10, kde-base/kdialog-3.5.10, kde-base/kreadconfig-3.5.10, kde-base/kdebase-startkde-3.5.10-r4, kde-base/ksysguard-3.5.10, kde-base/kdm-3.5.10, kde-base/kdcop-3.5.10, kde-base/konqueror-3.5.10, kde-base/kate-3.5.10, kde-base/kscreensaver-3.5.10, kde-base/kstart-3.5.10, kde-base/ksmserver-3.5.10, kde-base/kdebase-data-3.5.10, kde-base/kfind-3.5.10, kde-base/kdebase-kioslaves-3.5.10-r1, kde-base/khotkeys-3.5.10, kde-base/khelpcenter-3.5.10, kde-base/kdepasswd-3.5.10, kde-base/kwin-3.5.10, kde-base/kicker-3.5.10, kde-base/kcheckpass-3.5.10, kde-base/kdesktop-3.5.10, kde-base/kdesu-3.5.10, kde-base/kpersonalizer-3.5.10)
[nomerge      ] kde-misc/kio-sysinfo-1.8.2  USE="kdeenablefinal%* xinerama -arts -debug (-branding%)"  [1=>2]
[nomerge      ]  kde-base/kdebase-3.5.9-r4  USE="cups hal kdeenablefinal kdehiddenvisibility ldap opengl pam samba xcomposite xinerama -arts -branding -debug -ieee1394 -java -joystick -lm_sensors -logitech-mouse -openexr -xscreensaver"  [0]
[blocks b     ]   kde-base/kmenuedit:3.5 ("kde-base/kmenuedit:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/kmenuedit-3.5.10  USE="kdehiddenvisibility -debug"  [0]
[blocks b     ]   kde-base/kdm:3.5 ("kde-base/kdm:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/kdm-3.5.10  USE="kdehiddenvisibility pam -debug"  [0]
[blocks b     ]   kde-base/ksysguard:3.5 ("kde-base/ksysguard:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/ksysguard-3.5.10  USE="kdehiddenvisibility -debug -lm_sensors"  [0]
[blocks b     ]   kde-base/konsole:3.5 ("kde-base/konsole:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/konsole-3.5.10  USE="kdehiddenvisibility -debug"  [0]
[blocks b     ]   kde-base/knetattach:3.5 ("kde-base/knetattach:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/knetattach-3.5.10  USE="kdehiddenvisibility -debug"  [0]
[blocks b     ]   kde-base/kdepasswd:3.5 ("kde-base/kdepasswd:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/kdepasswd-3.5.10  USE="kdehiddenvisibility -debug"  [0]
[blocks b     ]   kde-base/kscreensaver:3.5 ("kde-base/kscreensaver:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/kscreensaver-3.5.10  USE="kdehiddenvisibility opengl -arts -debug"  [0]
[blocks b     ]   kde-base/kstart:3.5 ("kde-base/kstart:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[uninstall    ]    kde-base/kstart-3.5.10  USE="kdehiddenvisibility -debug"  [0]
.......
[ebuild     U ] sys-kernel/linux-headers-2.6.27-r2 [2.6.26] 3,509 kB [0]
[blocks B     ] kde-base/kdebase-startkde:3.5 ("kde-base/kdebase-startkde:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdesu:3.5 ("kde-base/kdesu:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/ksmserver:3.5 ("kde-base/ksmserver:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kcheckpass:3.5 ("kde-base/kcheckpass:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdebase-data:3.5 ("kde-base/kdebase-data:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdebase-kioslaves:3.5 ("kde-base/kdebase-kioslaves:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/khotkeys:3.5 ("kde-base/khotkeys:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdesktop:3.5 ("kde-base/kdesktop:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/khelpcenter:3.5 ("kde-base/khelpcenter:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kwin:3.5 ("kde-base/kwin:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdebase ("kde-base/kdebase" is blocking kde-base/kdelibs-3.5.10-r2)
[blocks B     ] kde-base/kpersonalizer:3.5 ("kde-base/kpersonalizer:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kfind:3.5 ("kde-base/kfind:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/libkonq:3.5 ("kde-base/libkonq:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kcminit:3.5 ("kde-base/kcminit:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] =kde-base/kdebase-3.5* ("=kde-base/kdebase-3.5*" is blocking kde-base/kdeprint-3.5.10, kde-base/kmenuedit-3.5.10, kde-base/kcminit-3.5.10, kde-base/ksplashml-3.5.10, kde-base/konsole-3.5.10, kde-base/knetattach-3.5.10, kde-base/libkonq-3.5.10, kde-base/kcontrol-3.5.10, kde-base/kdialog-3.5.10, kde-base/kreadconfig-3.5.10, kde-base/kdebase-startkde-3.5.10-r4, kde-base/ksysguard-3.5.10, kde-base/kdm-3.5.10, kde-base/kdcop-3.5.10, kde-base/konqueror-3.5.10, kde-base/kate-3.5.10, kde-base/kscreensaver-3.5.10, kde-base/kstart-3.5.10, kde-base/ksmserver-3.5.10, kde-base/kdebase-data-3.5.10, kde-base/kfind-3.5.10, kde-base/kdebase-kioslaves-3.5.10-r1, kde-base/khotkeys-3.5.10, kde-base/khelpcenter-3.5.10, kde-base/kdepasswd-3.5.10, kde-base/kwin-3.5.10, kde-base/kicker-3.5.10, kde-base/kcheckpass-3.5.10, kde-base/kdesktop-3.5.10, kde-base/kdesu-3.5.10, kde-base/kpersonalizer-3.5.10)
[blocks B     ] kde-base/kdialog:3.5 ("kde-base/kdialog:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kate:3.5 ("kde-base/kate:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kreadconfig:3.5 ("kde-base/kreadconfig:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdcop:3.5 ("kde-base/kdcop:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/konqueror:3.5 ("kde-base/konqueror:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kicker:3.5 ("kde-base/kicker:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kcontrol:3.5 ("kde-base/kcontrol:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/ksplashml:3.5 ("kde-base/ksplashml:3.5" is blocking kde-base/kdebase-3.5.9-r4)
[blocks B     ] kde-base/kdeprint:3.5 ("kde-base/kdeprint:3.5" is blocking kde-base/kdebase-3.5.9-r4)
Total: 125 packages (106 upgrades, 2 downgrades, 6 new, 5 in new slots, 6 reinstalls, 8 uninstalls), Size of downloads: 277,190 kB
Conflict: 34 blocks (25 unsatisfied)


Putting
Code:
<=kde-base/kdelibs-3.5.10
<=kde-base/kdebase-3.5.10
into package.mask helps, but I would like to know what happen.
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Wed Oct 29, 2008 10:45 pm    Post subject: Reply with quote

I tried one last kdesvn-portage update today, but on kdebase-svn I kept running into plasma clock and plasma workspace problems, apparently which couldn't be solved, at least by me. :? :lol: I figured the overlay itself was now getting obsolete, since trying to sync said it's already up-to-date, and I hadn't sync'd in a week. I guess it's no longer being worked on, due to the new kde-crazy coming online.

Therefore, I sync'd the kde-crazy overlay I just got earlier today (it had some updates since this morning), and setup a new /etc/portage with symlinks to the /usr/local/portage/layman/kde-crazy/Documentation/ stuff.

I'm currently doing an emerge @kdebase-live, which seems to be going OK. I was running kdesvn-portage, and did NOT remove all the recently installed 9999 packages, but did do a layman -d kdesvn-portage. The 9999 packages are getting updated from kdesvn trunk. Kdelibs is at 877650 and compiling right now, so things seem normal so far. I was too impatient to remove all my svn-src distfiles. :lol:

Anyone else successfully installed with kde-crazy yet? Any problems I will run into?

Anyone tried koffice-live? That would really be nice.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3231
Location: Gainesville, Florida

PostPosted: Thu Oct 30, 2008 1:29 am    Post subject: Reply with quote

Hmmmm- On kde-crazy, plasma-workspace is still failing:
Code:
Scanning dependencies of target kdeinit_plasma_qgv
[ 69%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/backgrounddialog.o
[ 69%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/dashboardview.o
[ 70%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/desktopcorona.o
[ 70%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/desktopview.o
sip: Unable to find file "framesvg.sip"
make[2]: *** [plasma/scriptengines/python/sip/sipplasmapart0.cpp] Error 1
make[1]: *** [plasma/scriptengines/python/CMakeFiles/python_module_PyKDE4_plasma.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 70%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/main.o

Then at the end:

[ 73%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/__/common/plasmaappletitemmodel.o
[ 74%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/appadaptor.o
[ 74%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/ksmserver_interface.o
[ 74%] Building CXX object plasma/shells/desktop/CMakeFiles/kdeinit_plasma_qgv.dir/kdeinit_plasma_qgv_automoc.o
Linking CXX shared library ../../../lib/libkdeinit4_plasma.so
[ 74%] Built target kdeinit_plasma_qgv
make: *** [all] Error 2
 *
 * ERROR: kde-base/plasma-workspace-9999 failed.


Will try removing src-svn kdebase, and getting a fresh kdebase svn checkout. Any other ideas?

UPDATE:

Hmmm.. With this probably unwise hack, I got plasma-workspace to compile and install. I didn't remove svn-src, but in /usr/portage/distfiles/svn-src/KDE/kdebase/kdebase/workspace/plasma/scriptengines/python/CMakeLists.txt, I commented out this line:
Code:
if (PythonSupport_FOUND)
#  macro_optional_add_subdirectory(python)
endif (PythonSupport_FOUND)

Hope nothing weird happens on rebooting kde, :roll: but for now guess I'll try some more kde-crazy kde-live sets.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.0.14-gentoo USE=experimental
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Thu Oct 30, 2008 8:09 am    Post subject: Reply with quote

kdepimlibs-4.1.71 is failing for me right before the merge:

Code:
>>> Completed installing kdepimlibs-4.1.71 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/                         

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment
   usr/lib64/kde4/kabc_net.so                               
   usr/lib64/kde4/kcal_local.so                             
   usr/lib64/kde4/kio_sieve.so                               
   usr/lib64/kde4/kio_nntp.so                               
   usr/lib64/kde4/kcm_mailtransport.so                       
   usr/lib64/kde4/kcm_kresources.so                         
   usr/lib64/kde4/kio_pop3.so                               
   usr/lib64/kde4/kabc_ldapkio.so                           
   usr/lib64/kde4/kio_imap4.so                               
   usr/lib64/kde4/kabc_directory.so                         
   usr/lib64/kde4/kabcformat_binary.so                       
   usr/lib64/kde4/kio_ldap.so                               
   usr/lib64/kde4/kcal_localdir.so                           
   usr/lib64/kde4/kabc_file.so                               
   usr/lib64/kde4/kio_mbox.so                               
   usr/lib64/kde4/kio_smtp.so                               
   usr/lib64/libkcal.so.4.2.0                               
   usr/lib64/libkabc_file_core.so.4.2.0                     
   usr/lib64/libqgpgme.so.1.0.1                             
   usr/lib64/libgpgme++-pthread.so.2.0.0                     
   usr/lib64/libkimap.so.4.2.0                               
   usr/lib64/libkabc.so.4.2.0                               
   usr/lib64/libktnef.so.4.2.0                               
   usr/lib64/libkblog.so.4.2.0                               
   usr/lib64/libakonadi-kde.so.4.2.0                         
   usr/lib64/libkpimidentities.so.4.2.0                     
   usr/lib64/libsyndication.so.4.2.0                         
   usr/lib64/libkpimutils.so.4.2.0                           
   usr/lib64/libakonadi-kmime.so.4.2.0                       
   usr/lib64/libgpgme++.so.2.0.0                             
   usr/lib64/libkresources.so.4.2.0                         
   usr/lib64/libkmime.so.4.2.0                               
   usr/lib64/libmailtransport.so.4.2.0                       
   usr/lib64/libakonadi-kabc.so.4.2.0                       
   usr/lib64/libkxmlrpcclient.so.4.2.0                       
   usr/lib64/libkldap.so.4.2.0                               
injecting /usr/kde/4.2/lib64/libakonadi-kde.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libakonadi-kde.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libkpimutils.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/     
injecting /usr/kde/4.2/lib64/libkpimutils.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/ 
injecting /usr/kde/4.2/lib64/libkresources.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/     
injecting /usr/kde/4.2/lib64/libkresources.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libsyndication.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/   
injecting /usr/kde/4.2/lib64/libsyndication.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libmailtransport.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/ 
injecting /usr/kde/4.2/lib64/libmailtransport.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libkabc.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/             
injecting /usr/kde/4.2/lib64/libkabc.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/         
injecting /usr/kde/4.2/lib64/libkpimidentities.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/   
injecting /usr/kde/4.2/lib64/libkpimidentities.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libktnef.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/             
injecting /usr/kde/4.2/lib64/libktnef.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/         
injecting /usr/kde/4.2/lib64/libkldap.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/             
injecting /usr/kde/4.2/lib64/libkldap.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/         
injecting /usr/kde/4.2/lib64/libakonadi-kabc.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/     
injecting /usr/kde/4.2/lib64/libakonadi-kabc.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/ 
injecting /usr/kde/4.2/lib64/libgpgme++.so.2 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/           
injecting /usr/kde/4.2/lib64/libgpgme++.so.2.0.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/       
injecting /usr/kde/4.2/lib64/libkabc_file_core.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/   
injecting /usr/kde/4.2/lib64/libkabc_file_core.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libkmime.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/             
injecting /usr/kde/4.2/lib64/libkmime.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/         
injecting /usr/kde/4.2/lib64/libkimap.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/             
injecting /usr/kde/4.2/lib64/libkimap.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/         
injecting /usr/kde/4.2/lib64/libqgpgme.so.1 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/           
injecting /usr/kde/4.2/lib64/libqgpgme.so.1.0.1 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/       
injecting /usr/kde/4.2/lib64/libgpgme++-pthread.so.2 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/   
injecting /usr/kde/4.2/lib64/libgpgme++-pthread.so.2.0.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/
injecting /usr/kde/4.2/lib64/libkcal.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/               
injecting /usr/kde/4.2/lib64/libkcal.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/           
injecting /usr/kde/4.2/lib64/libakonadi-kmime.so.4 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/     
injecting /usr/kde/4.2/lib64/libakonadi-kmime.so.4.2.0 into /var/tmp/portage/kde-base/kdepimlibs-4.1.71/image/ 
* checking 869 files for package collisions                                                                     
 *                                                                                                             
 * ERROR: kde-base/kdepimlibs-4.1.71 failed.                                                                   
 * Call stack:                                                                                                 
 * ebuild.sh, line   49:  Called pkg_preinst                                                                   
 * environment, line 3034:  Called subversion_pkg_preinst                                                       
 * environment, line 3576:  Called subversion_wc_info ''                                                       
 * environment, line 3597:  Called subversion__get_repository_uri ''                                           
 * environment, line 3413:  Called die                                                                         
 * The specific snippet of code:                                                                               
 * die "${ESVN}: ESVN_REPO_URI (or specified URI) is empty.";                                                   
 * The die message:                                                                                             
 * subversion: ESVN_REPO_URI (or specified URI) is empty.                                                       
 *                                                                                                             
 * If you need support, post the topmost build error, and the call stack if relevant.                           
 * A complete build log is located at '/var/tmp/portage/kde-base/kdepimlibs-4.1.71/temp/build.log'.             
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/kdepimlibs-4.1.71/temp/environment'.   
 * This ebuild used the following eclasses from overlays:                                                       
 * /usr/local/portage/layman/kde-crazy/eclass/kde4-base.eclass                                                 
 * /usr/local/portage/layman/kde-crazy/eclass/kde4-functions.eclass                                             
 * This ebuild is from an overlay: '/usr/local/portage/layman/kde-crazy/'                                       
 *                                                                                                             
!!! FAILED preinst: 1

 * GNU info directory index is up-to-date.

_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
uraes
Tux's lil' helper
Tux's lil' helper


Joined: 28 Nov 2002
Posts: 120
Location: Estonia

PostPosted: Thu Oct 30, 2008 8:46 am    Post subject: Reply with quote

drescherjm wrote:
kdepimlibs-4.1.71 is failing for me right before the merge:

It seesms to me, that now all kde-crazy packages are failing when ">>> Installing" phaze begins, for example I get:

Code:

...
>>> Installing kde-base/kate-4.1.71
* checking 90 files for package collisions
 *
 * ERROR: kde-base/kate-4.1.71 failed.
 * Call stack:
 * ebuild.sh, line   49:  Called pkg_preinst
 * environment, line 3245:  Called subversion_pkg_preinst
 * environment, line 3784:  Called subversion_wc_info ''
 * environment, line 3805:  Called subversion__get_repository_uri ''
 * environment, line 3621:  Called die
 * The specific snippet of code:
 * die "${ESVN}: ESVN_REPO_URI (or specified URI) is empty.";
 * The die message:
 * subversion: ESVN_REPO_URI (or specified URI) is empty.
...


For some reason is emerge trying to do smth with subversion. I found also one older thread ([SOLVED] mythtv-themes-0.20.2_p14301 fails to emerge), but really no solution...[/url]
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3 ... 5, 6, 7 ... 28, 29, 30  Next
Page 6 of 30

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum