Re: releaseme new requirement: non-conflicting files on case-insensitive FS/OS
On Monday, 20 November 2017 16:50:58 CET Harald Sitter wrote: > Guten Abend Everyone! > > To aid with use of our tarballs on Windows and case-insensitive file > systems, releaseme now makes sure [1] that the tarballs it generates > are safe to use in such contexts. Thanks for helping out on that front! Regards, Kevin > As this is a major problem for pretty much every source tarball as it > prevents people from doing Windows builds and/or unpack on exfat/fat32 > this is considered a fatal flaw in the tarball. To that end if you use > releaseme you may want to run tarme now so your next release doesn't > get held up by case-insensitive file conflicts. > > If you have any questions please do ask. > > [1] > https://phabricator.kde.org/R572:0936ab0e02551fe6d3e8ad07b97cd7d7d3d26838 > > HS -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: Dropping the svn kio from kdesdk-kioslaves
On Friday, 16 December 2016 06:31:46 CET Christian Ehrlicher wrote: > Am 15.12.2016 um 23:12 schrieb Kevin Funk: > > On Thursday, 15 December 2016 22:14:38 CET Albert Astals Cid wrote: > >> Why? > >> > >> * It doesn't compile with newer libsvn > >> * It's kdelibs4-based > > > > Heya, > > > > I know a few people that use kdesvn, how's the relation to that? > > > > I saw that Christian (CC'ed) put quite some effort in porting kdesvn over > > to a KF5-based kdelibs4support-free code base. If I understand correctly > > kdesvn.git even contains a copy of the KIO SVN implementation (c.f. > > kdesvn.git:src/ kiosvn)? > > > > Please elaborate :) > > You're correct - kdesvn contains a kioslave for svn and I ported it to > KF5 (just released kdesvn 2.0.0 some days ago). I don't know if > kdesdk-kioslaves has more functionality but from my point of view it can > be dropped. If the SVN kioslave is standalone, wouldn't it make more sense to actually keep it in a separate repository/package? So users who just want the Dolphin integration can just use that? Wouldn't it make more sense to move your kioslave implementation into kdesdk- kioslaves, replacing the older copy? I'm not sure whether Albert just wants to kill the repository or he's just phasing old unmaintained software. In case of the latter, updating the copy with the better maintained version probably makes more sense. Cheers, Kevin > Cheers, > Christian -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: Dropping the svn kio from kdesdk-kioslaves
On Thursday, 15 December 2016 22:14:38 CET Albert Astals Cid wrote: > Why? > * It doesn't compile with newer libsvn > * It's kdelibs4-based Heya, I know a few people that use kdesvn, how's the relation to that? I saw that Christian (CC'ed) put quite some effort in porting kdesvn over to a KF5-based kdelibs4support-free code base. If I understand correctly kdesvn.git even contains a copy of the KIO SVN implementation (c.f. kdesvn.git:src/ kiosvn)? Please elaborate :) PS: /me never uses SVN directly usually. Cheers, Kevin > Any disagreement on dropping it? > > Cheers, > Albert -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: kconfig_compiler (Re: KDE Frameworks 5.29.0)
On Saturday, 10 December 2016 17:17:10 CET Nicolás Alvarez wrote: > > El 10 dic 2016, a las 17:10, David Faure <fa...@kde.org> escribió: > >> On samedi 10 décembre 2016 19:49:07 CET Martin Graesslin wrote: > >> So from my point of view breaking the incorrect behavior could be > >> acceptable here. > > > > Yes, but after the next kdevplatform release, then, to avoid breaking > > compilation of released code. > > > > Is the kdevplatform bugfix getting into the final 16.12 release? > > If I read > > https://community.kde.org/Schedules/Applications/16.12_Release_Schedule > > correctly, there's still time to sneak it in if needed, before Dec 15. > > KDevPlatform and KDevelop are extragear ;) > > The fix is already in the 5.0 branch, I guess we could release a v5.0.4 soon > if needed. +1 We could do this in 1-2 weeks (would fit our schedule). I don't think we want to rush and release v5.0.4 right now though. That would be an almost identical release to v5.0.3. Cheers, Kevin -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: KDE Frameworks 5.29.0
On Wednesday, 7 December 2016 20:10:40 CET Albert Astals Cid wrote: > El dimecres, 7 de desembre de 2016, a les 10:08:18 CET, David Faure va > > escriure: > > On lundi 5 décembre 2016 18:40:46 CET Martin Gräßlin wrote: > > > Am 2016-12-05 09:20, schrieb David Faure: > > > > On dimanche 4 décembre 2016 23:42:44 CET šumski wrote: > > > >> On nedjelja, 4. prosinca 2016. 00:37:52 CET David Faure wrote: > > > >> > Dear packagers, > > > >> > > > > >> > KDE Frameworks 5.29.0 has been uploaded to the usual place. > > > >> > > > > >> > New framework: prison > > > >> > > > > >> > Public release next Saturday. > > > >> > > > > >> > Thanks for the packaging work! > > > >> > > > >> kconfig (r129382) breaks compilation of kdevplatform: > > > >> http://paste.opensuse.org/82016854 > > > > > > > > Indeed (but it's not the change from RR 129382, it's commit cd4e650 > > > > from > > > > https://phabricator.kde.org/D3386 > > > > > > > > Seems to come from Inherits=BaseClass while BaseClass doesn't use > > > > arg="true". > > > > > > > > Here's a testcase for the kconfig unittests. Martin, can you take a > > > > look? > > > > > > The earliest I can have a look is probably on Friday, I'm sorry. > > > > > > My suggestion is to revert my two commits and I'll redo for next > > > frameworks. > > > > OK, done. New git tag and tarball: > > > > kconfig v5.29.0-rc2 > > 47f7e954a58ba5538d055e2f75e483cade48ee8a > > d6c12e0908de1b91529de15e75a52c9974685c91b423d5b5abeb06f261d0fa47 > > sources/kconfig-5.29.0.tar.xz > > Acoording to kfunk the thing that broke kdevplatform wasn't really kconfigs > fault but a side effect of kdevplatform code not being very good. Heya, the patch restoring the kdevplatform build with KF5 5.29: https://cgit.kde.org/kdevplatform.git/commit/? id=e84645d1694bdad7f179cd41babce723fe07aa63 The code in kdevplatform is a bit special, it's probably the only place in whole KDE which broke due to the recent changes in kconfig. I don't see an easy migration path, even if you introduce said change in a later kconfig release. I don't mind if you leave kconfig as-is. But that's probably something for dfaure to decide. Cheers, Kevin > I haven't read any of the diffs so i can't comment if this should be > reverted or not, but just bringing in some of the IRC context i read. > > Cheers, > Albert -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
Re: Dropping kdelibs4-based applications in KDE Applications 17.12
On Thursday, 17 November 2016 00:51:50 CET Sven Brauch wrote: > On 11/11/16 16:45, Dominik Haumann wrote: > > What do you think about having a Randa meeting (or similar) with focus > > on finishing ports to KF5? Would that make sense? > > +1 actually. There are a few applications on that list which would, in > my eyes, be a real loss if they were not maintained any more; I'm > especially looking at kcachegrind (I know of no comparable tool and it's > really good), maybe kopete. kmag is nice too on occasion but I don't > know if it will die with wayland anyways. +1 on kcachegrind, that would be a real loss. Actually there's an actively maintained frameworks branch, maybe we just need to poke Josef? ;) @Josef: Is the frameworks branch stable? If yes, let's release! > I'd be in for a sprint (or a few days of a sprint) to port those. Consider me in as well. Cheers, Kevin > Greetings, > Sven -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
