Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
On Saturday 21 May 2011, Dirk Mueller wrote: Please report any important packaging issues or must-fix bugs to the release- t...@kde.org mailinglist. I found several myself already: 9b0d645e5276f2a1ca49f12fbfd6cac1 kdelibs-4.6.80.tar.bz2 f41ed3db5ed14087bb1a746967b33248 kdelibs-experimental-4.6.80.tar.bz2 Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
On Saturday 21 May 2011, Dirk Mueller wrote: I found several myself already: And as I found out, kdelibs now depends on kdelibs-experimental, so I had to remove the splitting for now: 890d551e6332baea19b9bcb0655fce0c kdelibs-4.6.80.tar.bz2 Thanks, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
[4.7 Beta1 blocker] KIO Broken.
Hi, According to http://bugs.kde.org/273783 KIO is broken. Although this could be introduced after Dirks tag, but that would mean someone broke the tag freeze. Can someone confirm and find a solution ASAP? Best, Tom -- Tom Albers KDE Sysadmin ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 21 May 2011, Dirk Mueller wrote: On Saturday 21 May 2011, Dirk Mueller wrote: I found several myself already: And as I found out, kdelibs now depends on kdelibs-experimental, so I had to remove the splitting for now: 890d551e6332baea19b9bcb0655fce0c kdelibs-4.6.80.tar.bz2 Thanks, Dirk Oh boy. The turn of events with KDE 4.7.x is most unfortunate. I noticed an explosion of source tarballs. Dirk, are instructions available on how to re-assemble sources back to the original set? Or else, are instructions available on how to compile the bigger all-comprising packages where the separated applications and libraries are included again, like was the case all the time up to 4.7? It would be nice if there would at least be scripts available for distro packagers that allow to checkout bundled source tarballs from the repository. In the presence of such scripts, I would be able to generate old-style source tarballs and make them available for other packagers, if the KDE release team decided against making those available on the ftp site. Why am I proposing this? I am afraid that for Slackware, the bloat in KDE packages is not acceptible from a maintenance point of view. I do not speak _for_ Patrick Volkerding, but I spoke _with_ him, and since I also do a lot of the work with regard to researching and packaging KDE for Slackware, I have to say this on the matter: If there are no ways around this, then we are seriously considering the removal of KDE from the Slackware distribution and turning support over to willing third parties. This will go the way of GNOME which was abandoned by Slackware for the same reasons - we refuse to participate in a maintenance hell. Cheers (but not really), Eric - -- Eric Hameleers al...@slackware.com Jabber: al...@jabber.xs4all.nl -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iEYEARECAAYFAk3X92EACgkQXlaqr6dcvaDoyQCgpdZ+6W2wIfbL/wRAOwkYhgtm FrAAn2VKLO1H9FUWMY1hq3k98ZrTlKAj =ZBu3 -END PGP SIGNATURE- ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [4.7 Beta1 blocker] KIO Broken.
On Saturday 21 May 2011, Tom Albers wrote: According to http://bugs.kde.org/273783 KIO is broken. Although this could be introduced after Dirks tag, but that would mean someone broke the tag freeze. Can someone confirm and find a solution ASAP? Hi Tom, Thank you for letting me know. I've included the revert in the respinned tarball now: b998dea244b310759712241b319aa000 kdelibs-4.6.80.tar.bz2 Greetings, Dirk ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
On Saturday 21 May 2011, Eric Hameleers wrote: The turn of events with KDE 4.7.x is most unfortunate. I noticed an explosion of source tarballs. Yes, I started to resemble the git layout in the tarballs, given that I had a pain in the ass of work to do with reverting the git splitting for the 4.6 branch releases. I'll attach them for reference, but those scripts are ugly. I'm not aware of a better solution though, unless we use git submodules or maintain those scripts in the SVN. Dirk, are instructions available on how to re-assemble sources back to the original set? Or else, are instructions available on how to compile the bigger all-comprising packages where the separated applications and libraries are included again, like was the case all the time up to 4.7? I don't have those available at the moment. I used scripts to reassemble them to original tarballs, but I haven't properly pushed this into KDE git back yet. Can I get the opinion of the other distro packagers as well please? Personally I was much more happy with the previous module-based layout, though I can cope reasonable with the current situation as well. Any other opinon? Eric, thanks for sharing your thoughts. I hope we can find a solution that suits your needs as well. If all else fails, I'm willing to give maintaining those reassembling-scripts a try, but it is an extra effort, given that the tarballs are much different from how developers build it, so regressions in the build system are likely. Greetings, Dirk setup-kdeedu.sh Description: application/shellscript setup-kdegraphics.sh Description: application/shellscript ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
The turn of events with KDE 4.7.x is most unfortunate. I noticed an explosion of source tarballs. I strongly disagree. Splitting KDE SC up more is a step in the right direction as it allows for easier control about what to install. I am afraid that for Slackware, the bloat in KDE packages is not acceptible from a maintenance point of view. Again, I disagree. Yes, it's a bit more work but it reduces the bloat for users in the end. Most people don't need everything KDE SC has to offer and, thus, it's well worth some effort. If there are no ways around this, then we are seriously considering the removal of KDE from the Slackware distribution and turning support over to willing third parties. This will go the way of GNOME which was abandoned by Slackware for the same reasons - we refuse to participate in a maintenance hell. I suppose you've gotten rid of X.org, too? :-) Best regards, Wulf signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
Dirk Mueller muel...@kde.org writes: Can I get the opinion of the other distro packagers as well please? Personally I was much more happy with the previous module-based layout, though I can cope reasonable with the current situation as well. Any other opinon? On the FreeBSD side, we will just have to spend some time adjusting our ports, as we will probably create a separate port for each application that has been split. Other than, we're fine with either layout. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: KDE 4.7 Beta1 (4.6.80) tarballs uploaded (try#1)
Hello, On sekmadienis 22 Gegužė 2011 00:29:10 Wulf C. Krueger wrote: The turn of events with KDE 4.7.x is most unfortunate. I noticed an explosion of source tarballs. I strongly disagree. Splitting KDE SC up more is a step in the right direction as it allows for easier control about what to install. Since unrelated or slightly related applications are no longer bundled in the same source package, each package is faster to build and links fewer system components together. In the end, users can freely choose what to install and maintainers what and how to package. I am afraid that for Slackware, the bloat in KDE packages is not acceptible from a maintenance point of view. Again, I disagree. Yes, it's a bit more work but it reduces the bloat for users in the end. Most people don't need everything KDE SC has to offer and, thus, it's well worth some effort. The split does not bloat KDE SC since it has been bloated for a long time already. On the contrary, the split allows to ignore applications which are not that important for the distro (but used to be shipped in the bundle next to important applications). Also more people can work in parallel and responsibilities can be split according to the maintainer/user interest in the applications themselves. Therefore I also welcome the split very much and please continue the work in this direction. -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
