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

Goto page Previous  1, 2, 3, 4 ... 19, 20, 21  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Tue Oct 19, 2010 12:09 pm    Post subject: Reply with quote

Since QT-4.7 some websites are b0rked with KHTML (konqueror 4.5.2 as well as akregator 4.4.6 are affected), e.g. http://www.pro-linux.de/

rekonq/webkit render it just fine. Anyone else seen this?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Wed Oct 27, 2010 5:22 am    Post subject: Reply with quote

Not much posting on this and the qting-edge threads, so I thought I'd chime in with what I'm doing on my kde/qt live ~amd64 box.

I went to qt-4.7.9999 with -stable-branch (which is qt-4.7.1), as on my first run after updating the qting-edge overlay I noticed this:
Code:
 !!! WARNING !!!
 * Qt-4.7 stable branch is outdated. If you are
 * seeking for bleeding edge code your are kindly advised
 * to disable 'stable-branch' use flag and rebuild all the Qt modules

Using this little nifty command:
Code:
equery list qt-* | grep 9999 | xargs -n1 -i echo ={} | xargs emerge -vp1

After putting -stable-branch USE flag on all my qt packages in /etc/portage/package.use, I emerged all 14 of my qt 9999 packages with no issues. :D

Then I went on to kde-live, with my usual pruned down kde packages command:
Code:
emerge -pv1 @kdedeps-live @kdelibs-live @kdebase-live @kdeartwork-live @kdeadmin-live kde-base/gwenview ark kdf okular ksystemlog konq-plugins rekonq marble dragonplayer k3b kwebkitpart knetworkmanager --keep-going

Only had these 3 fail:
Code:
 The following 3 packages have failed to build or install:
    *  (dev-libs/shared-desktop-ontologies-9999::kde, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/dev-libs:shared-desktop-ontologies-9999:20101027-003726.log'
 *  (sys-auth/polkit-qt-9999::kde, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/sys-auth:polkit-qt-9999:20101027-003820.log'
 *  (sys-auth/polkit-kde-9999::kde, ebuild scheduled for merge), Log file:
 *   '/var/log/portage/sys-auth:polkit-kde-9999:20101027-020252.log'

and marble
Code:
 Scanning dependencies of target python_module_PyKDE4_marble
[ 99%] [ 99%] [ 99%] Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart1.o
Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart0.o
Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart2.o
In file included from /usr/include/python2.6/Python.h:8:0,
                 from /usr/include/python2.6/sip.h:32,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart1.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/python2.6/Python.h:8:0,
                 from /usr/include/python2.6/sip.h:32,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart0.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/python2.6/Python.h:8:0,
                 from /usr/include/python2.6/sip.h:32,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart2.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewportParams_focusPointIsCenter(PyObject*, PyObject*)':
sipmarblepart1.cpp:3269:30: error: 'class Marble::ViewportParams' has no member named 'focusPointIsCenter'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_RenderPluginInterface_pluginInstance(PyObject*, PyObject*)':
sipmarblepart2.cpp:2171:30: error: 'class Marble::RenderPluginInterface' has no member named 'pluginInstance'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_needsUpdate(PyObject*, PyObject*)':
sipmarblepart2.cpp:14310:30: error: 'class Marble::MarbleWidget' has no member named 'needsUpdate'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_setNeedsUpdate(PyObject*, PyObject*)':
sipmarblepart2.cpp:14335:21: error: 'class Marble::MarbleWidget' has no member named 'setNeedsUpdate'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_northPoleY(PyObject*, PyObject*)':
sipmarblepart2.cpp:14363:30: error: 'class Marble::MarbleWidget' has no member named 'northPoleY'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_setProxy(PyObject*, PyObject*)':
sipmarblepart2.cpp:15301:21: error: 'class Marble::MarbleWidget' has no member named 'setProxy'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_proxyHost(PyObject*, PyObject*)':
sipmarblepart2.cpp:15332:42: error: 'class Marble::MarbleWidget' has no member named 'proxyHost'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_proxyPort(PyObject*, PyObject*)':
sipmarblepart2.cpp:15359:30: error: 'class Marble::MarbleWidget' has no member named 'proxyPort'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_user(PyObject*, PyObject*)':
sipmarblepart2.cpp:15386:42: error: 'class Marble::MarbleWidget' has no member named 'user'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_password(PyObject*, PyObject*)':
sipmarblepart2.cpp:15413:42: error: 'class Marble::MarbleWidget' has no member named 'password'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_changeCurrentPosition(PyObject*, PyObject*)':
sipmarblepart2.cpp:16914:21: error: 'class Marble::MarbleWidget' has no member named 'changeCurrentPosition'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_updateGps(PyObject*, PyObject*)':
sipmarblepart2.cpp:16968:21: error: 'class Marble::MarbleWidget' has no member named 'updateGps'
make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart1.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart2.o] Error 1
make[1]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/all] Error 2
make: *** [all] Error 2
emake failed
 * ERROR: kde-base/marble-9999 failed:
 *   Make failed!
 *
 * Call stack:
 *     ebuild.sh, line   56:  Called src_compile
 *   environment, line 6493:  Called kde4-meta_src_compile
 *   environment, line 3876:  Called kde4-base_src_compile
 *   environment, line 3523:  Called cmake-utils_src_compile
 *   environment, line 1726:  Called _execute_optionaly 'src_compile'
 *   environment, line  728:  Called enable_cmake-utils_src_compile
 *   environment, line 2095:  Called cmake-utils_src_make
 *   environment, line 1745:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!"; 


I emerged gpsd, but still got the same error, so I figure it must be something sip/python bindings eclass related?
Anyone know how to work around this marble problem? I already had polkit-qt-9999 installed- just today it fails. Need to try again and look at the output.

OK- emerge polkit-qt says:
Code:
-- Could NOT find Policykit  (missing:  _POLICYKIT_LIBRARY _POLICYKIT_GRANT_LIBRARY _POLICYKIT_DBUS_LIBRARY _POLICYKIT_INCLUDE_DIR)
-- PolicyKit was not found on your system. Skipping compilation of polkit-qt

Guess I'll emerge policykit, but IIRC I had to remove that package some time ago due to some conflict or deprecation problem? :roll:

OK- installed policykit, but now polkit-qt bails out at the last moment with this:
Code:
 [100%] Built target polkit-qt-gui
Install the project...
-- Install configuration: "Gentoo"
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/libpolkit-qt-core.so.0.9.5
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/libpolkit-qt-core.so.0
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/libpolkit-qt-core.so
-- Removed runtime path from "/var/tmp/portage/sys-auth/polkit-qt-9999/image//usr/lib64/libpolkit-qt-core.so.0.9.5"
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/libpolkit-qt-gui.so.0.9.5
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/libpolkit-qt-gui.so.0
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/libpolkit-qt-gui.so
-- Removed runtime path from "/var/tmp/portage/sys-auth/polkit-qt-9999/image//usr/lib64/libpolkit-qt-gui.so.0.9.5"
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/action.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/auth.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/context.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/actionbutton.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/actionbuttons.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/export.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/polkitqtversion.h
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/Action
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/Auth
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/Context
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/ActionButton
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/include/PolicyKit/polkit-qt/ActionButtons
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/pkgconfig/polkit-qt.pc
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/pkgconfig/polkit-qt-core.pc
-- Installing: /var/tmp/portage/sys-auth/polkit-qt-9999/image/usr/lib64/pkgconfig/polkit-qt-gui.pc
!!! dodoc: README.porting does not exist
dodoc failed
 * ERROR: sys-auth/polkit-qt-9999 failed:
 *   dodoc failed 
Call stack:
 *     ebuild.sh, line   56:  Called src_install
 *   environment, line 3250:  Called cmake-utils_src_install
 *   environment, line  812:  Called _execute_optionaly 'src_install'
 *   environment, line  279:  Called enable_cmake-utils_src_install
 *   environment, line 1233:  Called base_src_install
 *   environment, line  488:  Called base_src_install_docs
 *   environment, line  499:  Called die
 * The specific snippet of code:
 *               dodoc "${x}" || die "dodoc failed";
 *
 * If you need support, post the output of 'emerge --info =sys-auth/polkit-qt-9999',
 * the complete build log and the output of 'emerge -pqv =sys-auth/polkit-qt-9999'.
 * This ebuild used the following eclasses from overlays:
 *   /var/lib/layman/kde/eclass/git.eclass
 * This ebuild is from an overlay named 'kde': '/var/lib/layman/kde/'
 * The complete build log is located at '/var/log/portage/sys-auth:polkit-qt-9999:20101027-141153.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-auth/polkit-qt-9999/temp/environment'.
 * S: '/var/tmp/portage/sys-auth/polkit-qt-9999/work/polkit-qt-9999'
 * QA Notice: file does not exist:
 

Any idea of what to do here? I've looked at the /var/tmp/portage/sys-auth/polkit-qt temp and work files, and the cmake lists in the polkit-qt source files to see if I can stop dodoc wanting README.porting from being in the mix, but have failed so far. Could this be addressed in the ebuild? The latest portage and ovelay polkit-qt ebuilds are similar, but not exactly the same.

Even more confusing, the /usr/portage/distfiles/svn-src/polkit-qt/polkit-qt-1/README.porting file DOES exist. :roll: Maybe copy it to another location?

UPDATE: OK- rebooted into kde-live (now at Version 4.5.73 (4.6 >= 20101019), using qt-4.7.9999 (4.7.1). The above described problems don't seem to be causing any trouble so far. No time to use kde right now, but looks good.
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
cruzki123
Apprentice
Apprentice


Joined: 16 May 2008
Posts: 233

PostPosted: Thu Oct 28, 2010 9:27 pm    Post subject: Reply with quote

Any one knows if devs are working on bringing koffice beta to the overlay?

I'm trying with the live build without look for several month :(
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Thu Oct 28, 2010 9:36 pm    Post subject: Reply with quote

What's wrong with koffice-2.2.2 in portage?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
cruzki123
Apprentice
Apprentice


Joined: 16 May 2008
Posts: 233

PostPosted: Fri Oct 29, 2010 7:09 am    Post subject: Reply with quote

genstorm wrote:
What's wrong with koffice-2.2.2 in portage?


I only want to TRY the new one. I think this was clear. In the end, this is a thread about testing new releases of kde SC, isn't it?
Back to top
View user's profile Send private message
xibo
Apprentice
Apprentice


Joined: 21 Aug 2007
Posts: 152
Location: moving between kubuntu and ubuntu kde edition

PostPosted: Fri Oct 29, 2010 6:48 pm    Post subject: Reply with quote

cruzki123 wrote:
genstorm wrote:
What's wrong with koffice-2.2.2 in portage?


I only want to TRY the new one. I think this was clear. In the end, this is a thread about testing new releases of kde SC, isn't it?


Well, then why bother to wait for releases? Especially ones that are officially not stable... There's a svn head version of koffice in this set.
_________________
pjp wrote:
shickapooka800 wrote:
there are plenty of ubuntards in coffee shops around the globe these days.
Yes, but they're only smart enough to recognize they want to be popular, yet too stupid to recognize that it isn't a Mac.
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Fri Oct 29, 2010 8:38 pm    Post subject: Reply with quote

cruzki123 wrote:
I only want to TRY the new one. I think this was clear. In the end, this is a thread about testing new releases of kde SC, isn't it?

Sorry, I didn't realize there already was a new 2.3 beta. ;)

Anyway, as long as koffice 2.3 has beta status, I wouldn't bother with ebuilds. Especially when it has a track record of breaking stuff, files moving from one package to another, leading to upgrade blocks from one beta to another (and even with RCs). So... better use live ebuilds for now until there's actually an RC around and watch out for user ebuilds on bugs.gentoo.org then.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
cruzki123
Apprentice
Apprentice


Joined: 16 May 2008
Posts: 233

PostPosted: Sat Oct 30, 2010 10:36 am    Post subject: Reply with quote

genstorm wrote:
cruzki123 wrote:
I only want to TRY the new one. I think this was clear. In the end, this is a thread about testing new releases of kde SC, isn't it?

Sorry, I didn't realize there already was a new 2.3 beta. ;)

Anyway, as long as koffice 2.3 has beta status, I wouldn't bother with ebuilds. Especially when it has a track record of breaking stuff, files moving from one package to another, leading to upgrade blocks from one beta to another (and even with RCs). So... better use live ebuilds for now until there's actually an RC around and watch out for user ebuilds on bugs.gentoo.org then.


I already know that, but as I said before I can't use the live ebuild for a unknow reason. It's halt in the same point (see my previuos post about that) complaining about a missing file. I had been having this issue for 2 month (so I can't compile any version of the 2.3 series). This is why I ask for a beta ebuild (I yes, I have looked to ebuilds in bug tracker too).

Thanks for the response ;)
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Sat Oct 30, 2010 10:44 am    Post subject: Reply with quote

hm, how is polkit-qt related to koffice? There is no dependency.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
cruzki123
Apprentice
Apprentice


Joined: 16 May 2008
Posts: 233

PostPosted: Sun Oct 31, 2010 11:45 am    Post subject: Reply with quote

genstorm wrote:
hm, how is polkit-qt related to koffice? There is no dependency.


O.o when I say something about polkit? When I said "previos" I'm talking about my previous post (I think it was at the begining of this page, but I'm not sure) Anyway, the error I am talking on koffice-libs is:

Code:

[ 78%] Building CXX object filters/kspread/excel/import/CMakeFiles/excelimporttodoc.dir/excelimporttodoc_automoc.o
[ 78%] Building CXX object filters/kspread/excel/import/CMakeFiles/excelimporttodoc.dir/ExcelImport.o
[ 78%] Building CXX object filters/kspread/excel/import/CMakeFiles/excelimport.dir/excelimport_automoc.o
In file included from /home/portage/portage/app-office/koffice-libs-9999/work/koffice-libs-9999/filters/kspread/excel/import/../sidewinder/swinder.h:25:0,
                 from /home/portage/portage/app-office/koffice-libs-9999/work/koffice-libs-9999/filters/kspread/excel/import/ExcelImport.cpp:78:
/home/portage/portage/app-office/koffice-libs-9999/work/koffice-libs-9999/filters/kspread/excel/import/../sidewinder/cell.h:30:36: error fatal: generated/simpleParser.h: Do no exist file or directory


I have look to the other ebuild and I think they have a patch related to this but it did not apply to de svn sources.
Back to top
View user's profile Send private message
benneque
Tux's lil' helper
Tux's lil' helper


Joined: 01 Dec 2007
Posts: 134

PostPosted: Mon Nov 01, 2010 8:18 pm    Post subject: Reply with quote

(when) will there be ebuilds for kde-4.5.74 etc. ? ( ftp://ftp.kde.org/pub/kde/unstable/4.5.74/src/ )
Back to top
View user's profile Send private message
Shining Arcanine
Veteran
Veteran


Joined: 24 Sep 2009
Posts: 1110

PostPosted: Thu Nov 04, 2010 12:08 pm    Post subject: Reply with quote

KDE 4.5.3 ebuilds went into portage yesterday. My desktop upgraded without an issue. My laptop is still compiling.
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Sat Nov 06, 2010 3:53 pm    Post subject: Reply with quote

Tried to update my kde-live today, and kdelibs-9999 fails with a patch problem. Saw this similar thing on bugzilla, but said it was fixed. It must be back. :roll:
Code:

* Using existing repository copy at revision 1193588.
 *    working copy: /usr/portage/distfiles/svn-src/kdelibs/kdelibs

>>> Source unpacked in /var/tmp/portage/kde-base/kdelibs-9999/work
>>> Preparing source in /var/tmp/portage/kde-base/kdelibs-9999/work/kdelibs-9999 ...
 * Applying 01_gentoo_set_xdg_menu_prefix.patch ...                                                     [ ok ]
 * Applying 02_gentoo_append_xdg_config_dirs.patch ...                                                  [ ok ]
 * Applying kdelibs-4.5.73-module-suffix.patch ...                                                      [ ok ]
 * Applying kdelibs-4.4.66-macos-unbundle.patch ...                                                     [ ok ]
 * Applying kdelibs-4.3.3-klauncher_kioslave.patch ...                                                  [ ok ]
 * Applying kdelibs-4.3.3-klauncher_mac.patch ...

 * Failed Patch: kdelibs-4.3.3-klauncher_mac.patch !
 *  ( /var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/kde-base/kdelibs-9999/temp/kdelibs-4.3.3-klauncher_mac.patch.out

 * ERROR: kde-base/kdelibs-9999 failed:
 *   Failed Patch: kdelibs-4.3.3-klauncher_mac.patch!
 *
 * Call stack:
 *     ebuild.sh, line   56:  Called src_prepare
 *   environment, line 4167:  Called kde4-base_src_prepare
 *   environment, line 3238:  Called base_src_prepare
 *   environment, line 1050:  Called epatch '/var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch'
 *   environment, line 2274:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 *
 * If you need support, post the output of 'emerge --info =kde-base/kdelibs-9999',
 * the complete build log and the output of 'emerge -pqv =kde-base/kdelibs-9999'.
 * This ebuild used the following eclasses from overlays:
 *   /var/lib/layman/kde/eclass/kde4-base.eclass
 *   /var/lib/layman/kde/eclass/kde4-functions.eclass
 * This ebuild is from an overlay named 'kde': '/var/lib/layman/kde/'
 * The complete build log is located at '/var/log/portage/kde-base:kdelibs-9999:20101106-135620.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/kdelibs-9999/temp/environment'.
 * S: '/var/tmp/portage/kde-base/kdelibs-9999/work/kdelibs-9999'

>>> Failed to emerge kde-base/kdelibs-9999, Log file:

>>>  '/var/log/portage/kde-base:kdelibs-9999:20101106-135620.log'


AND:
* Messages for package kde-base/kdelibs-9999:

 * Package:    kde-base/kdelibs-9999
 * Repository: kde
 * Maintainer: kde@gentoo.org
 * USE:  3dnow acl alsa amd64 bzip2 elibc_glibc handbook kernel_linux mmx nls opengl semantic-desktop sse sse2 ssl udev userland_GNU
 * Fetching disabled since 1 hours has not passed since last update.
 * Using existing repository copy at revision 1193588.
 *    working copy: /usr/portage/distfiles/svn-src/kdelibs/kdelibs
 * Applying 01_gentoo_set_xdg_menu_prefix.patch ...
 * Applying 02_gentoo_append_xdg_config_dirs.patch ...
 * Applying kdelibs-4.5.73-module-suffix.patch ...
 * Applying kdelibs-4.4.66-macos-unbundle.patch ...
 * Applying kdelibs-4.3.3-klauncher_kioslave.patch ...
 * Applying kdelibs-4.3.3-klauncher_mac.patch ...
 * Failed Patch: kdelibs-4.3.3-klauncher_mac.patch !
 *  ( /var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/kde-base/kdelibs-9999/temp/kdelibs-4.3.3-klauncher_mac.patch.out
 * ERROR: kde-base/kdelibs-9999 failed:
 *   Failed Patch: kdelibs-4.3.3-klauncher_mac.patch!

So, here it is- anyone run into this, and know what to do? I resynced layman -s kde, and pulled new svn-src files just to be sure (hadn't done so in a while). The bug referenced is over a year old https://bugs.kde.org/show_bug.cgi?id=209903 and seems to refer to a qt problem. Do I need to update qting-edge and recompile all my qt packages, or is that the wrong track. The "can't find file to patch at input line 10" and "Perhaps you used the wrong -p or --strip option?' would seem more likely. The patch is not missing in the kdelibs overlay ebuild directory- I checked and it is there.

Also, I'm not understanding why kdelibs-4.3.3 is even involved here- this is kde-live (kde-4.6 trunk)?
Code:
 ***** kdelibs-4.3.3-klauncher_mac.patch *****

=============================================

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch'

=============================================
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Please refer to
|  https://bugs.kde.org/show_bug.cgi?id=209903
|
|  http://www.davidfaure.fr/2009/klauncher_mac.diff
|
|Index: klauncher.cpp
|===================================================================
|--- kdelibs-4.3.3/kinit/klauncher.cpp   (revision 1034932)
|+++ kdelibs-4.3.3/kinit/klauncher.cpp   (working copy)
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=============================================

PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch'

=============================================
patching file kinit/klauncher.cpp
Hunk #1 succeeded at 1151 (offset 7 lines).
Hunk #2 FAILED at 1160.
1 out of 2 hunks FAILED -- saving rejects to file kinit/klauncher.cpp.rej
=============================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch'

=============================================
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Please refer to
|  https://bugs.kde.org/show_bug.cgi?id=209903
|
|  http://www.davidfaure.fr/2009/klauncher_mac.diff
|
|Index: klauncher.cpp
|===================================================================
|--- kdelibs-4.3.3/kinit/klauncher.cpp   (revision 1034932)
|+++ kdelibs-4.3.3/kinit/klauncher.cpp   (working copy)
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=============================================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch'

=============================================
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Please refer to
|  https://bugs.kde.org/show_bug.cgi?id=209903
|
|  http://www.davidfaure.fr/2009/klauncher_mac.diff
|
|Index: klauncher.cpp
|===================================================================
|--- kdelibs-4.3.3/kinit/klauncher.cpp   (revision 1034932)
|+++ kdelibs-4.3.3/kinit/klauncher.cpp   (working copy)
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
=============================================

PATCH COMMAND:  patch -p4 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/kde/kde-base/kdelibs/files/kdelibs-4.3.3-klauncher_mac.patch'

=============================================
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Please refer to
|  https://bugs.kde.org/show_bug.cgi?id=209903
|
|  http://www.davidfaure.fr/2009/klauncher_mac.diff
|
|Index: klauncher.cpp
|===================================================================
|--- kdelibs-4.3.3/kinit/klauncher.cpp   (revision 1034932)
|+++ kdelibs-4.3.3/kinit/klauncher.cpp   (working copy)
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored

_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
Shining Arcanine
Veteran
Veteran


Joined: 24 Sep 2009
Posts: 1110

PostPosted: Sun Nov 07, 2010 2:48 am    Post subject: Reply with quote

Qt 4.7.0 ebuilds just became available in the portage testing tree today. I had a pesky memory leak issue that caused compositing to fail, but that seems to have been fixed with the Qt updates.
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Sun Nov 07, 2010 12:13 pm    Post subject: Reply with quote

Does then mean we should go with portage Qt-4.7.0 for portage kde (4.5.3) as well as our overlay kde-live, and do complete kde rebuilds?

I'm currently using Qt 4.7.9999 on my kde-live installation, as it helped solve some previous problems, but my kdelibs klauncher_mac.patch failure mentioned above is still not resolved. I've resynced several times- no fix yet. I'd hate to go back to 4.7.0, and find I again have the other problems, but in general I really don't like running QT 9999 versions with kde-live.

Guess I should try editing the overlay ebuild and comment out that patch. From what I've read online, it seems to be for dealing with Mac OS systems, which I don't really need. Is this correct, and isn't anyone else running into this kdelibs-live patch issue?
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Sun Nov 07, 2010 12:32 pm    Post subject: Reply with quote

Shining Arcanine wrote:
Qt 4.7.0 ebuilds just became available in the portage testing tree today. I had a pesky memory leak issue that caused compositing to fail, but that seems to have been fixed with the Qt updates.

qt-4.7.0 ebuilds are inside portage since Sept. 21st, hardmasked still.

@wrc1944: You don't need to go with it for 4.5.3, also qt-4.6.x still is the best choice if you also plan to compile openoffice with +kde. I'm using 4.7.0 and having GUI display issues in OO, besides no errors. What issues were you facing?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Sun Nov 07, 2010 1:38 pm    Post subject: Reply with quote

@genstorm,
Sorry- should have mentioned I was referring to my ~amd64 kde-live Gentoo partition regarding qt-4.7.0. I unmasked it as soon as it was in portage, and then tried rebuilding kde-live, but ran into a few compiling issues. After going to qting-edge/qt-4.7.9999 as mentioned on the kde-testing thread that resolved those problems (can't recall exactly what they were at the moment). Don't plan on compiling OO.

Anyway, currently on my ~x86 partition and I'm about halfway through an @world upgrade, including the qt-4.7.0 (from 4.6.3) and xfce4 updates (18 of 42, presently at qt-gui). Hope I don't have to rebuild all of kde-4.5.3, but expect I will.
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Sun Nov 07, 2010 1:58 pm    Post subject: Reply with quote

Then you should stay with qt-4.7.9999 as it is in no way related to your failing patch. Simply remove it from the ebuild. Patches don't get renamed as long as there's no need to adapt to newer sources.

PS: I like to combine major Qt updates with upcoming KDE upgrades.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Sun Nov 07, 2010 3:02 pm    Post subject: Reply with quote

Thanks genstorm, good advice. I'll try removing the patch from the ebuild. Any ideas as to why this would be happening on my kde-live system, and apparently nobody else is also reporting it?

Just finished the qt-4.7.0 and xfce4 updates- only xfwm4-4.7.1 failed. All my qt updates went fine. Hope kde still works after reboot. Revdep-rebuild turns up nothing.
Running emerge @preserved-rebuild (xfwm is No. 5 of 6). OK- xfwm-4.7.1 went OK. :)
_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
Shining Arcanine
Veteran
Veteran


Joined: 24 Sep 2009
Posts: 1110

PostPosted: Sun Nov 07, 2010 3:30 pm    Post subject: Reply with quote

wrc1944 wrote:
Does then mean we should go with portage Qt-4.7.0 for portage kde (4.5.3) as well as our overlay kde-live, and do complete kde rebuilds?

I'm currently using Qt 4.7.9999 on my kde-live installation, as it helped solve some previous problems, but my kdelibs klauncher_mac.patch failure mentioned above is still not resolved. I've resynced several times- no fix yet. I'd hate to go back to 4.7.0, and find I again have the other problems, but in general I really don't like running QT 9999 versions with kde-live.

Guess I should try editing the overlay ebuild and comment out that patch. From what I've read online, it seems to be for dealing with Mac OS systems, which I don't really need. Is this correct, and isn't anyone else running into this kdelibs-live patch issue?


My upgrade experience was that Qt 4.7 is binary compatible with Qt 4.6.

genstorm wrote:
Shining Arcanine wrote:
Qt 4.7.0 ebuilds just became available in the portage testing tree today. I had a pesky memory leak issue that caused compositing to fail, but that seems to have been fixed with the Qt updates.

qt-4.7.0 ebuilds are inside portage since Sept. 21st, hardmasked still.

@wrc1944: You don't need to go with it for 4.5.3, also qt-4.6.x still is the best choice if you also plan to compile openoffice with +kde. I'm using 4.7.0 and having GUI display issues in OO, besides no errors. What issues were you facing?


It is no longer hardmasked.
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Sun Nov 07, 2010 3:52 pm    Post subject: Reply with quote

Yep, same here! Rebooted to kde-4.5.3 with no issues. Very nice! :D All xfce4 updates went fine too, but haven't booted to xfce4 yet.
Code:
 gentoo wrc # emerge -pv1 $(qlist -IC qt-*)

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

Calculating dependencies... done!
[ebuild   R   ] x11-libs/qt-core-4.7.0  USE="exceptions glib iconv qt3support ssl (-aqua) -debug -optimized-qmake -pch -private-headers" 0 kB                                                                                                   
[ebuild   R   ] x11-libs/qt-sql-4.7.0  USE="exceptions iconv mysql qt3support sqlite (-aqua) -debug -firebird -freetds -odbc -pch -postgres" 0 kB                                                                                               
[ebuild   R   ] x11-libs/qt-dbus-4.7.0  USE="exceptions (-aqua) -debug -pch" 0 kB
[ebuild   R   ] x11-libs/qt-script-4.7.0  USE="exceptions iconv (-aqua) -debug -pch -private-headers" 0 kB
[ebuild   R   ] x11-libs/qt-xmlpatterns-4.7.0  USE="(-aqua) -debug -pch" 0 kB
[ebuild   R   ] x11-libs/qt-test-4.7.0  USE="exceptions iconv (-aqua) -debug -pch" 0 kB
[ebuild   R   ] x11-libs/qt-gui-4.7.0-r1  USE="accessibility cups dbus exceptions glib gtk mng qt3support raster tiff (-aqua) -debug -egl -nas -nis -pch -private-headers -trace -xinerama" 0 kB                                               
[ebuild   R   ] x11-libs/qt-qt3support-4.7.0  USE="accessibility exceptions kde (-aqua) -debug -pch -phonon" 0 kB
[ebuild   R   ] x11-libs/qt-webkit-4.7.0  USE="dbus exceptions kde (-aqua) -debug -pch" 0 kB
[ebuild   R   ] x11-libs/qt-multimedia-4.7.0  USEVery Happy="exceptions iconv (-aqua) -debug -pch" 0 kB
[ebuild   R   ] x11-libs/qt-opengl-4.7.0-r1  USE="exceptions qt3support (-aqua) -debug -egl -pch" 0 kB
[ebuild   R   ] x11-libs/qt-svg-4.7.0  USE="exceptions iconv (-aqua) -debug -pch" 0 kB
[ebuild   R   ] dev-libs/libdbusmenu-qt-0.6.2  USE="-debug -test" 0 kB
[ebuild   R   ] x11-libs/qt-declarative-4.7.0  USE="exceptions qt3support (-aqua) -debug -pch -private-headers" 0 kB
[ebuild   R   ] x11-libs/qt-assistant-4.7.0  USE="exceptions glib (-aqua) -compat -debug -doc -pch -trace" 0 kB

Total: 15 packages (15 reinstalls), Size of downloads: 0 kB
gentoo wrc #

_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
genstorm
Advocate
Advocate


Joined: 05 Apr 2007
Posts: 2470
Location: Austria

PostPosted: Sun Nov 07, 2010 4:01 pm    Post subject: Reply with quote

Shining Arcanine wrote:
It is no longer hardmasked.

Well then packages.gentoo.org is lagging behind. Indeed, when I removed my package.unmask file for qt it is still listed unmasked.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Shining Arcanine
Veteran
Veteran


Joined: 24 Sep 2009
Posts: 1110

PostPosted: Sun Nov 07, 2010 4:05 pm    Post subject: Reply with quote

genstorm wrote:
Shining Arcanine wrote:
It is no longer hardmasked.

Well then packages.gentoo.org is lagging behind. Indeed, when I removed my package.unmask file for qt it is still listed unmasked.


It tends to lag behind. I learned that the hard way.
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Sun Nov 07, 2010 6:01 pm    Post subject: Reply with quote

Looks like my kdelibs klauncher_mac.patch problem might be fixed with a new kdelibs-4.5.74-klauncher_mac.patch commit! :D I'll give it a try.
Code:
amd64 wrc # layman -s kde
* Running... # ( cd /var/lib/layman/kde  && /usr/bin/git pull )
remote: Counting objects: 67, done.
remote: Compressing objects: 100% (40/40), done.
remote: Total 40 (delta 28), reused 0 (delta 0)
Unpacking objects: 100% (40/40), done.
From git://git.overlays.gentoo.org/proj/kde
   2d31409..c397ce1  master     -> origin/master
Updating 2d31409..c397ce1
Fast-forward
 .../package.keywords/.kde-live/kdesdk-live         |    1 -
 Documentation/package.keywords/kde-live.keywords   |    1 -
 Documentation/package.unmask/kde-live              |    1 -
 kde-base/kbugbuster/Manifest                       |    1 -
 kde-base/kbugbuster/kbugbuster-9999.ebuild         |   17 -----------
 kde-base/kdelibs/Manifest                          |   23 +++++++++++++++-
 .../files/kdelibs-4.5.74-klauncher_mac.patch       |   26 +++++++++++++++++
 kde-base/kdelibs/kdelibs-9999.ebuild               |    2 +-
 kde-base/kdesdk-meta/Manifest                      |    2 +-
 kde-base/kdesdk-meta/kdesdk-meta-9999.ebuild       |    1 -
 kde-misc/smooth-tasks/Manifest                     |    4 ---
 kde-misc/smooth-tasks/metadata.xml                 |    6 ----
 kde-misc/smooth-tasks/smooth-tasks-20100227.ebuild |   29 --------------------
 kde-misc/smooth-tasks/smooth-tasks-9999.ebuild     |   27 ------------------
 sets/kdesdk-live                                   |    1 -
 sys-auth/polkit-kde-agent/Manifest                 |    2 +-
 .../polkit-kde-agent/polkit-kde-agent-9999.ebuild  |    4 ++-
 17 files changed, 54 insertions(+), 94 deletions(-)
 delete mode 100644 kde-base/kbugbuster/kbugbuster-9999.ebuild
 create mode 100644 kde-base/kdelibs/files/kdelibs-4.5.74-klauncher_mac.patch
 delete mode 100644 kde-misc/smooth-tasks/Manifest
 delete mode 100644 kde-misc/smooth-tasks/metadata.xml
 delete mode 100644 kde-misc/smooth-tasks/smooth-tasks-20100227.ebuild
 delete mode 100644 kde-misc/smooth-tasks/smooth-tasks-9999.ebuild
*
* Success:
* ------
*
* Successfully synchronized overlay "kde".

_________________
Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.19-r1, gcc-4.9.1 kernel 3.17.1-gentoo-r1 (USE=experimental "native")
Back to top
View user's profile Send private message
albright
Advocate
Advocate


Joined: 16 Nov 2003
Posts: 2109
Location: Near Toronto

PostPosted: Sun Nov 07, 2010 6:45 pm    Post subject: Reply with quote

today after updating to qt 4.7.0 on amd64, kmail would no longer
receive or send mail (just gave an "unable to connect / protocol
unexpectedly died" error).

Something wrong with openssl and kmail (I have both
openssl-0.1X and openssl-0.0.9x installed)

found on the web the idea of:

Code:
ln -s libcrypto.so.1.0.0 libcrypto.so.0.9.8


Now kmail works again.

So in case anyone bumps into this ...

Strangely, this problem did not occur on my x86 notebook
_________________
.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4 ... 19, 20, 21  Next
Page 3 of 21

 
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