KDE CVS/Subversion Split Ebuilds (Replies Part 1)

[Debentoo_Gao]

the QT-COPY version is 3 or 4 ?

[mario]

3

the QT-COPY version is 3 or 4 ?

[mario]

It's fully working in current svn, and I believe it somewhat works in 3.4 as well

Does anybody know how the 'Switch user' feature is supposed to work now? Some time ago, there was a $KDE_HOME/share/config/kdm/Xservers file, which now seems to be gone. Even if I put it back, kdm won't let me have more than one user logged in.

[Debentoo_Gao]

3

the QT-COPY version is 3 or 4 ?

Thanks,mario. But I got an error when I emerge kdelibs-7

Code: Select all

A  KDE/kdelibs/dnssd/domainbrowser.cpp
A  KDE/kdelibs/dnssd/remoteservice.cpp
A  KDE/kdelibs/dnssd/README
A  KDE/kdelibs/dnssd/sdevent.h
A  KDE/kdelibs/dnssd/domainbrowser.h
A  KDE/kdelibs/dnssd/remoteservice.h
A  KDE/kdelibs/dnssd/INSTALL
A  KDE/kdelibs/dnssd/configure.in.bot
A  KDE/kdelibs/dnssd/Makefile.am
A  KDE/kdelibs/dnssd/servicebase.cpp
A  KDE/kdelibs/dnssd/settings.kcfgc
A  KDE/kdelibs/COPYING.LIB

Fetching external item into 'KDE/kdelibs/admin'
 * Failed in /usr/portage/distfiles/svn-src/kde/trunk during "svn --non-interactive update KDE/kdelibs"

 !!! ERROR: kde-base/kdelibs-7 failed.
 !!! Function subversion_handle_error, Line 137, Exitcode 0
 !!! svn: PROPFIND request failed on '/home/kde/trunk/KDE/kde-common/admin'
 !!! If you need support, post the topmost build error, NOT this status message.

[superstoned]

3

the QT-COPY version is 3 or 4 ?

Thanks,mario. But I got an error when I emerge kdelibs-7

Code: Select all

A  KDE/kdelibs/dnssd/domainbrowser.cpp
A  KDE/kdelibs/dnssd/remoteservice.cpp
A  KDE/kdelibs/dnssd/README
A  KDE/kdelibs/dnssd/sdevent.h
A  KDE/kdelibs/dnssd/domainbrowser.h
A  KDE/kdelibs/dnssd/remoteservice.h
A  KDE/kdelibs/dnssd/INSTALL
A  KDE/kdelibs/dnssd/configure.in.bot
A  KDE/kdelibs/dnssd/Makefile.am
A  KDE/kdelibs/dnssd/servicebase.cpp
A  KDE/kdelibs/dnssd/settings.kcfgc
A  KDE/kdelibs/COPYING.LIB

Fetching external item into 'KDE/kdelibs/admin'
 * Failed in /usr/portage/distfiles/svn-src/kde/trunk during "svn --non-interactive update KDE/kdelibs"

 !!! ERROR: kde-base/kdelibs-7 failed.
 !!! Function subversion_handle_error, Line 137, Exitcode 0
 !!! svn: PROPFIND request failed on '/home/kde/trunk/KDE/kde-common/admin'
 !!! If you need support, post the topmost build error, NOT this status message.

getting this to work takes time, many re-tries and patience

try again; try to go to the place it went wrong and do it by hand (all info is in the error: go to the /usr/portage/etc/trunk folder and type "svn --non-inblablabla" and see what happens. fix it, and try again

[mario]

try again; try to go to the place it went wrong and do it by hand (all info is in the error: go to the /usr/portage/etc/trunk folder and type "svn --non-inblablabla" and see what happens. fix it, and try again

You shouldn't need to do that. Externals are disabled after at least a portion of the folder is created, so only 2 passes should suffice. If they don't, let me know, as there must be a bug in the code. I think the best solution would be to import keys, since the ebuilds are not supposed to be interactive to ask you to confirm certificates. I will look into key importation from the eclass.

[superstoned]

you know, mario, you're way cool! thanx for all you're doing for us

[alinv]

unsermake ebuild seems to have no source.

[Debentoo_Gao]

3

getting this to work takes time, many re-tries and patience

try again; try to go to the place it went wrong and do it by hand (all info is in the error: go to the /usr/portage/etc/trunk folder and type "svn --non-inblablabla" and see what happens. fix it, and try again

You shouldn't need to do that. Externals are disabled after at least a portion of the folder is created, so only 2 passes should suffice. If they don't, let me know, as there must be a bug in the code. I think the best solution would be to import keys, since the ebuilds are not supposed to be interactive to ask you to confirm certificates. I will look into key importation from the eclass.

sorry 4 my poor english understanding. could u tell me the way 2 go on my emerge ?

[mario]

just try emerging again. if that doesn't work, complain here again

3

getting this to work takes time, many re-tries and patience

try again; try to go to the place it went wrong and do it by hand (all info is in the error: go to the /usr/portage/etc/trunk folder and type "svn --non-inblablabla" and see what happens. fix it, and try again

You shouldn't need to do that. Externals are disabled after at least a portion of the folder is created, so only 2 passes should suffice. If they don't, let me know, as there must be a bug in the code. I think the best solution would be to import keys, since the ebuilds are not supposed to be interactive to ask you to confirm certificates. I will look into key importation from the eclass.

sorry 4 my poor english understanding. could u tell me the way 2 go on my emerge ?

[yagami]

Making all in taskbar
make[3]: Entering directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker/taskbar'
/usr/kde/devel/bin/kconfig_compiler ./taskbar.kcfg ./taskbarsettings.kcfgc; ret=$?; \
if test "$ret" != 0; then rm -f taskbarsettings.h ; exit $ret ; fi
make[3]: *** No rule to make target `../libkicker/kickerSettings.h', needed by `libtaskbar_la.all_cpp.cpp'. Stop.
make[3]: Leaving directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker/taskbar'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase'
make: *** [all] Error 2

this problem just wont go away.

the thing is that kcontrol/kicker needs ../kicker/libkicker compiled first to generate kickerSettings.h

i was able to compile kcontrol-7 , compiling the whole kdebase.

maybe you can do something with the split ebuilds ?!? ( i personnaly dunno if is such a good idea to split kde )

[mario]

Will be fixed - I noticed that myself as I am moving kde-i18n into kcontrol, I am testing what's necessary.

the thing is that kcontrol/kicker needs ../kicker/libkicker compiled first to generate kickerSettings.h

[mario]

If you want monolithic ebuilds, vote here:
https://developer.berlios.de/survey/sur ... rvey_id=97

[superstoned]

If you want monolithic ebuilds, vote here:
https://developer.berlios.de/survey/sur ... rvey_id=97

why would one want monolithic ebuilds???

[yagami]

If you want monolithic ebuilds, vote here:

its not that i think that monolithic ebuilds are better ... as long as we have -meta ebuilds , we are not missing on anything.

the problem is that i dont think kde is ready for that ... everything is so tightly integrated , and arent supposed to be used seperatly , i think ( used = compiled )

this would be really nice , split ebuilds , if we could use all kde using branch 3.4 or 3.5 or whatever , and then that special app would be trunk or HEAD.

since i like to test and try kopete HEAD , i would love a kde svn branch 3.4 and kopete HEAD ( note that i dont want kde stable release.... really , having been on branch 3.4 since kde 3.4 was released .... to me branches are the best , always stable and the first to receive stable bug fixs )

so , is there any way we could use a svn branch ebuild ?!? and maybe combine branch with trunk ?? that would rock !

[alinv]

If you want monolithic ebuilds, vote here:
https://developer.berlios.de/survey/sur ... rvey_id=97

Now, that I completed the transition?

My vote is no, but I wouldn't create an account on berlios.de for this. Wouldn't be a poll here a simpler way?

[mario]

Sorry, forget about it, I didn't know it requires an account. Anyone know how to create a poll here?

My vote is no, but I wouldn't create an account on berlios.de for this. Wouldn't be a poll here a simpler way?

[mario]

the thing is that kcontrol/kicker needs ../kicker/libkicker compiled first to generate kickerSettings.h

Fixed, gensync to update

[superstoned]

If you want monolithic ebuilds, vote here:

its not that i think that monolithic ebuilds are better ... as long as we have -meta ebuilds , we are not missing on anything.

the problem is that i dont think kde is ready for that ... everything is so tightly integrated , and arent supposed to be used seperatly , i think ( used = compiled )

this would be really nice , split ebuilds , if we could use all kde using branch 3.4 or 3.5 or whatever , and then that special app would be trunk or HEAD.

since i like to test and try kopete HEAD , i would love a kde svn branch 3.4 and kopete HEAD ( note that i dont want kde stable release.... really , having been on branch 3.4 since kde 3.4 was released .... to me branches are the best , always stable and the first to receive stable bug fixs )

so , is there any way we could use a svn branch ebuild ?!? and maybe combine branch with trunk ?? that would rock !

well, i'm running these ebuilds now, and i'm amazed how stable kde-svn is. and it's nice to see all these changes

[mario]

The problem is the inconsistent layout of different branches and trunk on svn. Take a look at websvn.kde.org to see if you can figure out a consistent way to switch branches.

so , is there any way we could use a svn branch ebuild ?!? and maybe combine branch with trunk ?? that would rock !

[Debentoo_Gao]

3

getting this to work takes time, many re-tries and patience

try again; try to go to the place it went wrong and do it by hand (all info is in the error: go to the /usr/portage/etc/trunk folder and type "svn --non-inblablabla" and see what happens. fix it, and try again

You shouldn't need to do that. Externals are disabled after at least a portion of the folder is created, so only 2 passes should suffice. If they don't, let me know, as there must be a bug in the code. I think the best solution would be to import keys, since the ebuilds are not supposed to be interactive to ask you to confirm certificates. I will look into key importation from the eclass.

sorry 4 my poor english understanding. could u tell me the way 2 go on my emerge ?

Thanks, this morning I emerge it again,it works .so cool,mario

[mario]

Hello,

Is anybody here reading the Commit Digest? I wondered if I could ask you to create a list of changed packages when the digest comes out, if you read it. I would then bump all revisions and that would end up available to anyone to rsync. I am thinking of a way to automate that, but it won't happen very soon, so maybe the "once a week revision by looking at Commit Digest" will do fine for now.

Also, if anyone is following security announcement, we could do the same for those. I could even give you access to the repository so that you bump them (there's a utility called ebump, but simple copy/paste will also do).

Thanks,
Mario

[superstoned]

Hello,

Is anybody here reading the Commit Digest?

of course

I wondered if I could ask you to create a list of changed packages when the digest comes out, if you read it. I would then bump all revisions and that would end up available to anyone to rsync. I am thinking of a way to automate that, but it won't happen very soon, so maybe the "once a week revision by looking at Commit Digest" will do fine for now.

Also, if anyone is following security announcement, we could do the same for those. I could even give you access to the repository so that you bump them (there's a utility called ebump, but simple copy/paste will also do).

Thanks,
Mario

i THINK i could figure out how to do it... let me think about it (have to work today, it's 5:38 in the morning, damn, not used to that - i usally get up at 9 )

[Debentoo_Gao]

I got this error just now

Code: Select all

Making all in kicker
make[2]: Entering directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker'
Making all in taskbar
make[3]: Entering directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker/taskbar'
/usr/kde/devel/bin/kconfig_compiler ./taskbar.kcfg ./taskbarsettings.kcfgc; ret=$?; \
if test "$ret" != 0; then rm -f taskbarsettings.h ; exit $ret ;  fi
make[3]: *** No rule to make target `../libkicker/kickerSettings.h', needed by `libtaskbar_la.all_cpp.cpp'.  Stop.
make[3]: Leaving directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker/taskbar'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase/kicker'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kcontrol-7/work/KDE/kdebase'
make: *** [all] Error 2

!!! ERROR: kde-base/kcontrol-7 failed.
!!! Function kde-meta_src_compile, Line 491, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.

[Bonkie]

I got this error just now

See this

the thing is that kcontrol/kicker needs ../kicker/libkicker compiled first to generate kickerSettings.h

Fixed, gensync to update

He's not kidding, it fixed the error here