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

Goto page Previous  1, 2, 3 ... 13, 14, 15 ... 38, 39, 40  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
neuron
Advocate
Advocate


Joined: 28 May 2002
Posts: 2371

PostPosted: Tue Jan 27, 2009 3:12 pm    Post subject: Reply with quote

a lot of hash'es failing for me, but that includes when downloading from the other mirrors. Guessing the hash'es in the tree arnt correct to the newly released files, just something to be aware of.
Back to top
View user's profile Send private message
titoucha
Advocate
Advocate


Joined: 21 Jul 2005
Posts: 2374
Location: Genève

PostPosted: Tue Jan 27, 2009 3:21 pm    Post subject: Reply with quote

neuron wrote:
GENTOO_MIRRORS="http://geezer.mine.nu/kde/" emerge -Duf @kde-4.2 should speed things up a bit.


thanks a lot...
_________________
Assurez-vous que le titre de votre message soit conforme aux conventions de ce forum (paragraphe 3/3 : Comment poster sur le forum ??)
Back to top
View user's profile Send private message
neuron
Advocate
Advocate


Joined: 28 May 2002
Posts: 2371

PostPosted: Tue Jan 27, 2009 3:28 pm    Post subject: Reply with quote

a note about that mirror, if you find a hash that doesn't match that of kde.org let me know please, it's a bit hard to test atm myself :)
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6948
Location: Austria

PostPosted: Tue Jan 27, 2009 3:42 pm    Post subject: Reply with quote

kdebase-runtime-4.2.0.tar.bz2 fails here.
_________________
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
neuron
Advocate
Advocate


Joined: 28 May 2002
Posts: 2371

PostPosted: Tue Jan 27, 2009 3:43 pm    Post subject: Reply with quote

genstorm wrote:
kdebase-runtime-4.2.0.tar.bz2 fails here.


Yeah but that's a bad checksum in the tree I believe, along with a few other packages that arnt matching. I did redownload that on geezer from one of the kde mirrors, but it's still a different checksum than what portage expects.
Back to top
View user's profile Send private message
albright
Advocate
Advocate


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

PostPosted: Tue Jan 27, 2009 3:45 pm    Post subject: Reply with quote

me too. I spoke too soon above ... not useful
at the moment I'm afraid. Fast though :)
_________________
.... 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
spongo
n00b
n00b


Joined: 27 Jan 2009
Posts: 4

PostPosted: Tue Jan 27, 2009 8:26 pm    Post subject: Reply with quote

Manifests for at least kdelibs and runtime were wrong. I checked with md5s from http://kde.org/info/4.2.0.php and deleted the Manifests for an install without problems.

Thanks! ebuilds worked great in the last months even beta, greatest desktop I ever had!

Now I had problems with the last glitch in usability...the cashew. iHateTheCashew is broken. Had to do:

Code:
--- CMakeLists.txt~     2009-01-27 20:19:37.000000000 +0100
+++ CMakeLists.txt      2009-01-27 20:23:43.000000000 +0100
@@ -4,17 +4,17 @@
 include (KDE4Defaults)
 include(MacroOptionalAddSubdirectory)

-find_package(Plasma REQUIRED)
+#find_package(Plasma REQUIRED)

 add_definitions (${QT_DEFINITIONS} ${KDE4_DEFINITIONS})
 include_directories (${CMAKE_SOURCE_DIR} ${CMAKE_BINARY_DIR} ${KDE4_INCLUDES})

-include_directories(${CMAKE_CURRENT_SOURCE_DIR} ${PLASMA_INCLUDE_DIR})
+include_directories(${CMAKE_CURRENT_SOURCE_DIR})

 set(ihatethecashew_SRCS ihtc.cpp)

 kde4_add_plugin(plasma_applet_ihatethecashew ${ihatethecashew_SRCS})
-target_link_libraries(plasma_applet_ihatethecashew ${KDE4_KDEUI_LIBS} ${PLASMA_LIBS} )
+target_link_libraries(plasma_applet_ihatethecashew ${KDE4_KDEUI_LIBS} ${KDE4_PLASMA_LIBS} )

 install(TARGETS plasma_applet_ihatethecashew DESTINATION ${PLUGIN_INSTALL_DIR})
 install(FILES plasma-applet-ihatethecashew.desktop DESTINATION ${SERVICES_INSTALL_DIR})


> files/iHateTheCashew-0.1-libplasmanowincluded.patch

Code:
--- iHateTheCashew-0.1.ebuild~  2009-01-27 21:10:37.000000000 +0100                               
+++ iHateTheCashew-0.1.ebuild   2009-01-27 20:54:46.000000000 +0100                               
@@ -16,6 +16,12 @@                                                                               
 IUSE=""                                                                                         
                                                                                                 
 DEPEND="!kde-misc/plasmoids                                                                     
-               kde-base/libplasma"                                                               
+       kde-base/kdelibs"                                                                         

 S="${WORKDIR}/${PN}"
+
+src_unpack() {
+       unpack ${A}
+       cd "${S}"
+       epatch "${FILESDIR}"/${P}-libplasmanowincluded.patch
+}


to the ebuild
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6948
Location: Austria

PostPosted: Tue Jan 27, 2009 8:27 pm    Post subject: Reply with quote

Ebuilds are now in portage anyway and the manifests there seem to work. ;)
_________________
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
devsk
Advocate
Advocate


Joined: 24 Oct 2003
Posts: 2864
Location: Bay Area, CA

PostPosted: Tue Jan 27, 2009 8:42 pm    Post subject: Reply with quote

Does anybody know what exactly has changed since RC1? I don't really want to compile it again if its just about tagging RC1 to release.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6948
Location: Austria

PostPosted: Tue Jan 27, 2009 9:49 pm    Post subject: Reply with quote

I can't find a changelog from 4.1.96...


libkpgp-4.2.0 from portage fails because of a missing patch source!
Code:
 * Messages for package kde-base/libkpgp-4.2.0:

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 *                                                         
 *   /usr/portage/kde-base/libkpgp/files/libkpgp-4.1.72-fix.patch
 *   ( libkpgp-4.1.72-fix.patch )

For now you can acquire it from here.

EDIT: Also, kmail-4.2.0 fails because of missing patch:
Code:
 * Messages for package kde-base/kmail-4.2.0:

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 *
 *   /usr/portage/kde-base/kmail/files/kmail-4.1.72-fix.patch
 *   ( kmail-4.1.72-fix.patch )

_________________
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
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 821
Location: Alaska

PostPosted: Wed Jan 28, 2009 1:57 am    Post subject: Reply with quote

pardon me for the idiot question but I'm in a download loop for kdebase-runtime since the checksum is incorrect. How do you delete these or otherwise fix it for kde-testing overlay?
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6948
Location: Austria

PostPosted: Wed Jan 28, 2009 2:07 am    Post subject: Reply with quote

FEATURES="assume-digests" should do the trick. But I'd use the portage ebuilds in the first place.
_________________
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
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 821
Location: Alaska

PostPosted: Wed Jan 28, 2009 2:29 am    Post subject: Reply with quote

so kill the current emerge and place FEATURES="assume-digests" in make.conf I'll assume, or do a:
"FEATURES="assume-digests" emerge --resume"

How do you use the portage ebuilds if you have the overlay going? I suppose you have to remove the overlay and make sure 4.2 is unmasked (which it is already to get the overlay emerge going on 4.2). Would the portage ebuilds require starting over on downloading and installing the packages already downloaded/installed? (Only 3 installed but I think all downloaded).

thanks for info! /jd
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 821
Location: Alaska

PostPosted: Wed Jan 28, 2009 3:44 am    Post subject: Reply with quote

well I can't get FEATURES="assume-digests" to work. Keeps downloading and failing on checksum. Guess I'll try removing the overlay.
Back to top
View user's profile Send private message
Dont Panic
Guru
Guru


Joined: 20 Jun 2007
Posts: 322
Location: SouthEast U.S.A.

PostPosted: Wed Jan 28, 2009 4:36 am    Post subject: Reply with quote

If I were smart, I just wait for them to re-do the Manifest files.

But I'm stubborn, and I've been editing the Manifest files in the overlay, deleting the kdebase-runtime-4.2.0.tar.bz2 entry, and re-manifesting the package in the overlay (with the correct kdebase-runtime-4.2.0.tar.bz2 in my distfiles dir).

As somebody mentioned in an earlier post, you can check the md5sum of the kdebase-runtime-4.2.0.tar.bz2 file in your distfiles dir against KDE's value to make sure you have the correct download.
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 821
Location: Alaska

PostPosted: Wed Jan 28, 2009 7:26 am    Post subject: Reply with quote

ok, maybe I'll be patient. Thanks for the reply!

I don't know how to edit manifest files - although I've just located the /usr/local/portage/layman/kde-testing/kde-base/kdebase-data/Manifest file. I see the runtime hash in there. So you delete that. Then to re-manifest the file you just run ebuild kdebase-data-4.2.0.ebuild digest on the layman/kde-testing ebuild. That wants to download the runtime file to the distfiles directory - but you have already downloaded the correct one from somewhere. I think I'm getting it.

cheers, JD

[edit] OK - I'm set - got that one figured out - thanks!
Back to top
View user's profile Send private message
Boccaccio
Apprentice
Apprentice


Joined: 19 Jul 2005
Posts: 276

PostPosted: Wed Jan 28, 2009 10:00 am    Post subject: Reply with quote

I started emerging KDE-4.2. However, since I have both kde-testing and the portage tree, I get the overlay version installed. Is there a simple way to tell portage to emerge the portage version?
Back to top
View user's profile Send private message
neuron
Advocate
Advocate


Joined: 28 May 2002
Posts: 2371

PostPosted: Wed Jan 28, 2009 10:22 am    Post subject: Reply with quote

Boccaccio wrote:
I started emerging KDE-4.2. However, since I have both kde-testing and the portage tree, I get the overlay version installed. Is there a simple way to tell portage to emerge the portage version?


Grabbing the set and doing emerge @kde-4.2 might be a decent way of getting some of the packages reinstalled.
Back to top
View user's profile Send private message
Benni123
Tux's lil' helper
Tux's lil' helper


Joined: 13 Mar 2005
Posts: 110

PostPosted: Wed Jan 28, 2009 10:31 am    Post subject: Reply with quote

a strange error is, that the kile and k3b live ebuilds seem not to work anymore. I tried to download the source manually. But svn reports:


svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/office/kile
svn: No such revision 917648


I do not know, what I should do. What has happened here?....


Last edited by Benni123 on Wed Jan 28, 2009 10:44 am; edited 1 time in total
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


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

PostPosted: Wed Jan 28, 2009 10:43 am    Post subject: Reply with quote

genstorm,
I found that other kmail patch here http://gentoo-overlays.zugaina.org/kde-crazy/portage/kde-base/kmail/files/kmail-4.1.72-fix.patch
Worked fine. Now compiling all the packages for kmail-4.2.0. :D I just created a "files" directory in the ebuild directory and put the patches in there.
On the kmail patch I got this, which was a copy/paste error, so I just added a space by placing the cursor at the end of the last line in the file, and pressed enter.
Code:
!!! Digest verification failed:
!!! /usr/portage/kde-base/kmail/files/kmail-4.1.72-fix.patch
!!! Reason: Filesize does not match recorded size
!!! Got: 302
!!! Expected: 303

_________________
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.1.12-gentoo USE=experimental
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6948
Location: Austria

PostPosted: Wed Jan 28, 2009 11:33 am    Post subject: Reply with quote

wrc1944 wrote:
genstorm,
I found that other kmail patch here http://gentoo-overlays.zugaina.org/kde-crazy/portage/kde-base/kmail/files/kmail-4.1.72-fix.patch[/code]

Of course you could have also searched for it on the overlay page I posted above. ;)
_________________
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
d-fens
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jan 2004
Posts: 92

PostPosted: Wed Jan 28, 2009 1:36 pm    Post subject: Reply with quote

Boccaccio wrote:
I started emerging KDE-4.2. However, since I have both kde-testing and the portage tree, I get the overlay version installed. Is there a simple way to tell portage to emerge the portage version?


same question here, i have 9999 from testing but want 4.2 from portage. howto do this?
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6948
Location: Austria

PostPosted: Wed Jan 28, 2009 1:54 pm    Post subject: Reply with quote

Good question actually. Not a solution, but a quick hack that should work: Comment the source statement in your make.conf out for the time emerging kde-4.2.0.
_________________
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
Boccaccio
Apprentice
Apprentice


Joined: 19 Jul 2005
Posts: 276

PostPosted: Wed Jan 28, 2009 3:46 pm    Post subject: Reply with quote

Otherwise, one could wait, until 4.2.0 gets removed from the overlay, which usually is done quite soon after the movement to the tree.
Back to top
View user's profile Send private message
Krog
Guru
Guru


Joined: 26 Jun 2007
Posts: 330
Location: Roma, Italy

PostPosted: Wed Jan 28, 2009 4:45 pm    Post subject: Reply with quote

in my /usr/portage/profiles/package.mask every >= -4.1.96 is masked
so i have to unmask manually? and which 4.2.0 is "better", portage or overlay?
I still want to use weekly snapshots of the overlay...
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 ... 13, 14, 15 ... 38, 39, 40  Next
Page 14 of 40

 
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