http://blog.gmane.org/gmane.comp.kde.releases hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.kde.releases/5671 <pre>Hi, I've just learnt that nepomuk-core needs an unreleased Soprano, so until Sebastian does a new release you'll have to use the git version of soprano. Sorry for just learning this. Albert </pre> Albert Astals Cid 2012-05-26T14:57:46 http://comments.gmane.org/gmane.comp.kde.releases/5667 <pre>When compiling nepomuk-core beta1 in a totally clean environment it'll complain that you need kde-workspace. You can ignore that warning without any negative outcome. This will be fixed for Beta2. Albert </pre> Albert Astals Cid 2012-05-26T14:34:20 http://comments.gmane.org/gmane.comp.kde.releases/5664 <pre>Hello Packagers! We seem to have 2 minute problems - * Nepomuk-core and kde-runtime both install libnepomukcommon.so * You can ignore the kde-runtime version * Nepomuk-core and kdelibs both install rcgen * You can ignore the nepomuk-core one Sorry about all the trouble. I've fixed them in the git repositories and the beta2 release will contain these fixes. Thanks </pre> Vishesh Handa 2012-05-25T18:17:08 http://comments.gmane.org/gmane.comp.kde.releases/5660 <pre>The packages should be in their usual location in a few seconds (or so Ben told me :D) I'm attaching the sha1sum of the packages and the branches, hashes/revisions of the packages. The kdelibs one is manually forged to include changes in * kdelibs/CMakeLists.txt ---&gt; KDE_VERSION_RELEASE and KDE_VERSION_STRING * kdelibs/kdecore/sycoca/ksycoca.cpp --&gt; ksycoca version number * kdelibs/README --&gt; This is version... since it's taken from KDE/4.8 branch - nepomuk-core is a new dependency of kde-runtime (is partly split of it and partly includes nepomuk libs v2) - ksecrets is gone - pairs is a new edu game - kde-base-artwork has its own tarball - kdemultimedia is now also split in * audiocd-kio * dragon * ffmpegthumbs * juk * kmix * kscd * libkcddb * libkcompactdisc * mplayerthumbs * strigi-multimedia I have not tried the packages are buildable so testing more than welcome :-) The l10n packages are being generated (hope to get them up tomorrow, not sure which</pre> Albert Astals Cid 2012-05-24T22:54:09 http://comments.gmane.org/gmane.comp.kde.releases/5652 <pre>Unless someone disagrees i'll give kde-base-artwork it's own tarball, since well, it's a toplevel module. Cheers, Albert </pre> Albert Astals Cid 2012-05-23T16:59:58 http://comments.gmane.org/gmane.comp.kde.releases/5650 <pre>Hi all, I noticed something while we were on the topic of tagging the beta tomorrow that I wanted to bring up, which is a concern with tarball generation. Specifically, the various parallizeable tarball generators (pixz, pbzip2) seem to generate extraneous data. tar is smart enough to ignore this extra data, but this can affect decompressing our tarballs in a pipeline (i.e. xz --decompress kdelibs-4.foo.tar.xz | tar xf -), as tar closing its STDIN causes xz to write its excess data to a broken pipe. This probably doesn't annoy a ton of different people (except for the obvious problem with source-based distros like Gentoo, e.g. https://bugs.gentoo.org/show_bug.cgi?id=410861) but if the speedup is not very substantial it would be better to use xz or bzip2 to avoid the problem entirely. (This is done by adjusting the value of "compressors" in the pack release script in case you're wondering). It might be possible to still get some concurrency benefit by batching up modules to "pack" and then ru</pre> Michael Pyne 2012-05-23T03:48:25 http://comments.gmane.org/gmane.comp.kde.releases/5645 <pre>Hi Vishes, how's the nepomuk situation for 4.9 Beta 1 tagging that is happening tomorrow? Should I package nepomuk-core? Albert </pre> Albert Astals Cid 2012-05-22T23:07:21 http://comments.gmane.org/gmane.comp.kde.releases/5644 <pre>I understand we do *not* want KSecrets in 4.9 releases, right? Albert </pre> Albert Astals Cid 2012-05-22T23:04:31 http://comments.gmane.org/gmane.comp.kde.releases/5637 <pre>Soooo, now that I've bitten the bait and decided to package 4.9 beta 1 myself I have a question :D kdelibs is special since we don't have a master branch to package, i need to package from the 4.8 branch, that's fine *but* the issue is that i have to increase the version number and thus I can't tag 4.8.80 since I can't commit the version number increase to 4.8 branch. Ben suggests we create the 4.9 branch already. That'd go along with Martin's suggestion to create the 4.9 branch too. Any comments? Albert </pre> Albert Astals Cid 2012-05-22T21:36:54 http://comments.gmane.org/gmane.comp.kde.releases/5612 <pre>Howdy, kdewebdev has had zero love and attention for a long time now. I don't think it was ever ported to KDE4/Qt4. kdetoys is really small and hardly warrants its own module. How about no longer releasing these as part of KDE SC? </pre> Allen Winter 2012-05-18T20:06:19 http://comments.gmane.org/gmane.comp.kde.releases/5609 <pre>Supposed to happen next thursday. Do we have any plan? Albert </pre> Albert Astals Cid 2012-05-17T22:35:18 http://comments.gmane.org/gmane.comp.kde.releases/5595 <pre>Hi, I notice that the (old) v4.6.1 tag is missing in the konsole repository[1]. After comparing with the contents within kdebase-4.6.1.tar.bz2[2], I think the matching commit within konsole repository is 249dc86a1b6239bb4509d13157bfd9ebe5847fc2[3]. Could someone please check, create and push that missing tag? Regards Jekeyll [1] https://projects.kde.org/projects/kde/kde-baseapps/konsole/repository [2] ftp://ftp.kde.org/pub/kde/Attic/4.6.1/src/kdebase-4.6.1.tar.bz2 [3] https://projects.kde.org/projects/kde/kde-baseapps/konsole/repository/show?rev=249dc86a1b6239bb4509d13157bfd9ebe5847fc2 </pre> Jekyll Wu 2012-05-08T16:08:25 http://comments.gmane.org/gmane.comp.kde.releases/5573 <pre>Hi, As I was late with providing the tarballs, let's delay release until Thursday to have more time for testing and preparation. Also my internet connection does not allow openvpn ATM. ;-( Cya, Dirk</pre> Dirk Müller 2012-05-01T06:20:58 http://comments.gmane.org/gmane.comp.kde.releases/5569 <pre> Hi, I just finished uploading the first part of KDE 4.8.3 tarballs. Known issues: - the re-assembled kdemultimedia tarball does not compile - kde-l10n is still generating. I'm on a business trip tomorrow so I'll only have internet access in the evening. I'll try to upload the rest and the fixes asap. Any help with kdemultimedia is appreciated. the script is in kde- common/release/setup-kdemultimedia.sh TIA, Dirk </pre> Dirk Mueller 2012-04-29T21:15:18 http://comments.gmane.org/gmane.comp.kde.releases/5567 <pre>Hi, I apologize, I did not start tagging on Thursday like planned, due to various urgent work and private matters. I currently have only limited internet access. I'll be able to finish the tarballs on Monday. Sorry, Dirk</pre> Dirk Müller 2012-04-28T20:28:24 http://comments.gmane.org/gmane.comp.kde.releases/5566 <pre>Howdy, I started jotting down some thoughts about a brand new KDE SC Release Process at http://techbase.kde.org/User:Winterz. For your convenience, a copy of that wiki page is enclosed below. Let's discuss what I wrote there. After we reach some agreement, I will replace the current http://techbase.kde.org/Projects/Release_Team/Release_Process Note that we are talking about general ideas and workflow now. Please no CDash vs. Jenkins arguments, for example. However, if you have interest in helping out in specific areas it would be great to know about that. Those who do the work will eventually make the final decisions on things. = start wiki = KDE SC Release Packaging Thoughts 1. the Continuous Integration (CI) System - all the KDE SC modules are built continuously - no packaging unless all modules build ok (even better would be to force all make tests too) - the packaging tools run on the CI system generating "test" tarballs. - the "test" tarballs could be downloaded from the CI system - 2</pre> Allen Winter 2012-04-27T22:18:06 http://comments.gmane.org/gmane.comp.kde.releases/5565 <pre>Dirk, can you please push the tags for the 4.8.2 release? Cheers, Albert </pre> Albert Astals Cid 2012-04-25T18:22:12 http://comments.gmane.org/gmane.comp.kde.releases/5563 <pre> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/6936/ ----------------------------------------------------------- Review request for Release Team. Description ------- This extends the changelog XML to contain "review" in bugfix entries and co. XSL is adjusted to generate links to the review requests. Diffs ----- trunk/www/sites/www/announcements/changelogs/changelog.dtd 1287767 trunk/www/sites/www/announcements/changelogs/changelog.xsl 1287767 Diff: http://svn.reviewboard.kde.org/r/6936/diff/ Testing ------- example changelog: &lt;product name="kwin"&gt; &lt;bugfix rev="05e1ee03e8b2dcd8e7a7563ca36f4fc01299e570" class="normal" review="12345 123456"&gt;Ensure that KConfig update script does not overwrite custom settings.&lt;/bugfix&gt; &lt;bugfix rev="095c602617949afc55e34d0634f8de8357ca28eb" class="normal" bugno="80897" review="45678"&gt;Lower windows does not change focus for Focus (Strict</pre> Martin Gräßlin 2012-04-19T08:54:05 http://comments.gmane.org/gmane.comp.kde.releases/5556 <pre> Me and Sho would like to see kde-packager opened up. As a list it is little known which leads to duplication or lack of use, some KDE projects use their own list and some don't announce releases at all. kde-packager is secret because of security pre-announces but it seems better to move these to an existing list, http://oss-security.openwall.org/wiki/mailing-lists/distros all distros should be subscribed to this and the KDE guy and security guy in a distro need to coordinate for security issues anyway so that's no change. The other secret part of kde-packager is SC pre-announces but those go to the public release-team list anyway. Jonathan </pre> Jonathan Riddell 2012-04-11T10:32:20 http://comments.gmane.org/gmane.comp.kde.releases/5552 <pre>There are some data at the end of kdelibs' tar (and maybe in others as well). Not sure what kind of data are, but they seem to me like garbage. For example this fails due to SIGPIPE error (basically tar closes the pipe too "early"; probably there are some data/garbage besides tar's data): xz -dc kdelibs-4.8.2.tar.xz | tar xf - --no-same-owner Have a nice day!! :-) </pre> Aleksandar Petrinic 2012-04-06T11:47:22 http://comments.gmane.org/gmane.comp.kde.releases/5548 <pre>Hi all, after the last release I decided to never want to manually create the changelog ever again. All the information required to generate the changelog /should/ be in our bugtracker, so why do we create the changelog manually? Today I scratched my own itch and I present the changelog generator: http://quickgit.kde.org/index.php?p=scratch%2Fgraesslin%2Fchangelog- generator.git&amp;a=summary All that is needed to get proper changelogs is everybody including BUG: 12345 FIXED-IN: 4.8.3 in their commits. Now I have no idea how well our developers tend to use this when committing, but personally I would go so far that we should not have any commits to the stable branch which have not a referenced bug report. If there is interest in it I am willing to extend the tool so that we can use it to generate the complete changelog for all of KDE in one go so that we never again have to manually edit XML files and never again have to write "that these changelogs are incomplete" :-) Cheers Martin Gräßlin ----</pre> Martin Gräßlin 2012-04-06T17:27:01 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.kde.releases