kdebluetooth-1.0-0.41.beta8.fc9.src.rpm Failed To Build From Source against the rawhide tree. See http://fedoraproject.org/wiki/FTBFS for more information.
Created attachment 307979 [details] root.log.bz2 root.log for i386
Created attachment 307980 [details] build.log.bz2 build.log for i386
Created attachment 307981 [details] root.log.bz2 root.log for x86_64
Created attachment 307982 [details] build.log.bz2 build.log for x86_64
I might be missing something - but I don't see any errors. (Though, kdebluetooth won't be supported in F10 - being KDE3 only and having a dead upstream - I've yet to get it to work reliably under F9...) Can you post the actual build log? (Both build and root logs look clean [unless I missed something]) - Gilboa
ERROR: Bad build req: No Package Found for kdepim3-devel. Exiting. rpm -qp --provides kdepim-devel-* kdepim4-devel = 4.0.80-2.fc10 kdepim-devel = 6:4.0.80-2.fc10
Guessed as much. As kde3 support libraries are to be removed from F10, kdebluetooth should be removed too... Any idea which procedure I should follow to get kdebluetooth removed for rawhide? - Gilboa
http://fedoraproject.org/wiki/PackageMaintainers/RetiredPackages http://fedoraproject.org/wiki/PackageMaintainers/PackageEndOfLife
Gilboa, don't do that just yet :) http://sourceforge.net/project/shownotes.php?release_id=610960 Let me know if you need help with this, I think I can find some time next week to take a look if needed.
Was about the post the same. kdebletooth4 was officially released yesterday. [1]. I'll do some testing before packaging it for F9 and devel. (kdebluetooth3/F9 is completely broken... :( ) - Gilboa [1] http://bluetooth.kmobiletools.org/
This package has Failed to Build From Source for many months. Per http://fedoraproject.org/wiki/FTBFS, this package is now proposed for removal from the distribution. Please address this FTBFS bug immediately, or this package will be removed from the distribution within the next few weeks. Thank you for your continued contributions to Fedora, and your commitment to ensuring Fedora packages remain buildable from source code.
kdebluetooth4 0.2 was released a couple of days ago. Gilboa, would you like me to have a look at packaging it?
Thanks for the head's up. kdebluetooth web site only has 0.1 (which was pretty broken). Never the less, if you have free time, feel free to package it. Thanks for the offer. :) (If you can't I'll free up some time and do it ASAP. [I promised myself to do it last week... but :(]) One problem - though. (That I couldn't really solve). kdebluetooth 3.5.x was 0.9.beta.something. kdelbuetooth 4 is 0.2.x. And kdebluetooth4 must obsolete kdebluetooth - or we'll face an EVR problem. We'll need to create a new kdebluetooth4 branch in the CVS. (Unless you I missed something) - Gilboa
http://scop.fedorapeople.org/packages/kdebluetooth4.spec This one builds and kinda sorta works. The only useful thing I managed to in a 2 minute test do was to send a file to my mobile phone, and after that kbluetooth4 crashed. I have no BT input devices handy so I could not test that stuff. I don't see any problem with obsoleting the old version and just getting a new CVS dir structure and a devel branch for kdebluetooth4 when we think this is ready for general consumption.
(CCing Rex who has worked on the old kdebluetooth too.) Testing and comments very much welcome about the new kdebluetooth4 package (comment 14).
I just fixed the current kde3-based build in rawhide. When/if you use kdebluetooth4, I'd recommend simply sticking with Name: kdebluetooth and use Epoch: 1 to handle the upgrade for you. Imo, if you're gonna pull the trigger here, do it soon, before the beta.
Re: Epoch and using Obsoletes for previous/stray subpkgs, of course, like -libs
I assume that by default (read: in-case Epoc was not defined) Epoc is auto-defined as 0? Ville - if you don't mind I'll upload a fixed version within the next hour or so. (I rather revert to the old bin/libs/devel structure to reduce the multilib problems) - Gilboa
Please ignore the previous comment. Seem to had a broken combo kdebluetooth3/4 installation. (that created the so files.) http://gilboadavara.thecodergeek.com/kdebluetooth.spec Ville/Rex, Seems OK to you? - Gilboa "late to the party, as usual..." Davara
Fine with me, but a couple of remarks: Please make the Obsoletes versioned, ie. Obsoletes: %{name}-libs < 1:0.2 Obsoletes: %{name}-devel < 1:0.2 The old %description may no longer be accurate (esp. the first sentence), that's why I switched it to the short description they have for kdebluetooth4 on the project website.
Ville, Thanks - my mistake, I should have kept the Obsoletes versions. Fixed. http://gilboadavara.thecodergeek.com/kdebluetooth.spec As for the description - from [1]: "The KDE Bluetooth Framework is a set of tools built on top of Linux' Bluetooth stack BlueZ. Our goal is to provide easy access to the most common Bluetooth profiles and to make data exchange with Bluetooth enabled phones and PDAs as straightforward as possible." While kdebluetooth4 is not as extensive as its KDE 3.5 counter-part, AFAIK, the project goals have more-or-less remained the same. Anyway, if it looks OK to you, I'll commit to the cvs and issue and rawhide build. Unless I hear anything, I'll wait a week and commit it to F9-updates as well. - Gilboa [1] http://bluetooth.kmobiletools.org/
Sure, go ahead. But as I mentioned, the first sentence of the old description might no longer be accurate - kdebluetooth4 is not currently directly built on top of BlueZ, it uses something else (Solid?) from KDE 4. But I don't really care that much, you make the call with the description.
OK. 0.2 pushed. Ville/Rex: Thanks for the help. - Gilboa