From pierre at archlinux.de Mon Feb 1 03:46:44 2010 From: pierre at archlinux.de (Pierre Schmitz) Date: Mon, 1 Feb 2010 03:46:44 +0100 Subject: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201001312236.37813.mueller@kde.org> References: <201001312236.37813.mueller@kde.org> Message-ID: <201002010346.45721.pierre@archlinux.de> Am Sonntag, 31. Januar 2010 22:36:37 schrieb Dirk Mueller: > when > somebody confirms that it all compiles It seems to compile fine (including the csharp bindings that were broken in RC2). -- Pierre Schmitz, https://users.archlinux.de/~pierre From sebas at kde.org Mon Feb 1 15:25:58 2010 From: sebas at kde.org (=?utf-8?q?Sebastian=20K=C3=BCgler?=) Date: Mon, 01 Feb 2010 14:25:58 +0000 Subject: www/sites/www Message-ID: <1265034358.797002.6989.nullmailer@svn.kde.org> SVN commit 1083582 by sebas: Release 4.4.RC3 CCMAIL:release-team at kde.org A announcements/announce-4.4-rc3.php announcements/announce-4.4-rc2.php#1083564 M +6 -0 announcements/index.php M +5 -3 index.php M +1 -1 info/releases.php M +2 -0 whatiskde/project.php --- trunk/www/sites/www/announcements/index.php #1083581:1083582 @@ -9,6 +9,12 @@ KDE Announcements mailinglist !

+ +1st February 2010 - KDE SC 4.4 RC3 Released +
+"KDE Community Ships Third Release Candidate for KDE SC 4.4.0." +

+ 26th January 2010 - KDE SC 4.3.5 Released
--- trunk/www/sites/www/index.php #1083581:1083582 @@ -63,12 +63,14 @@

+ +KDE Software Compilation 4.4 Release Candidate 3 released
+On 1st February 2010, KDE Software Compilation 4.4 RC3 was released. KDE SC 4.4 RC3 is the third release candidate of a new major release in the KDE 4 series, aimed at testers to identify show-stopper bugs.

+ +

KDE Software Compilation 4.3.5 released
On 26th January 2010, KDE SC 4.3.5 was released. 4.3.5 provides bugfix and translation updates and is a recommended update for everybody running 4.3.4 or earlier versions.

-KDE Software Compilation 4.4 Release Candidate 2 released
-On 25th January 2010, KDE Software Compilation 4.4 RC2 was released. KDE SC 4.4 RC2 is the second release candidate of a new major release in the KDE 4 series, aimed at testers to identify show-stopper bugs.

-

KDE 4.3.0 released
On 4th August 2009, KDE 4.3.0 was released by the KDE community. KDE 4.3 is the latest major release --- trunk/www/sites/www/info/releases.php #1083581:1083582 @@ -17,7 +17,7 @@

-KDE 4.4 RC2 (unstable version, only for testing) +KDE 4.4 RC3 (unstable version, only for testing)

Previous KDE Releases

--- trunk/www/sites/www/whatiskde/project.php #1083581:1083582 @@ -410,6 +410,8 @@ was released on January 25th, 2010
  • 4.3.5 was released on January 26th, 2010
  • +
  • 4.4 RC 3 +was released on February 1st, 2010
  • From rdieter at math.unl.edu Mon Feb 1 21:27:18 2010 From: rdieter at math.unl.edu (Rex Dieter) Date: Mon, 01 Feb 2010 14:27:18 -0600 Subject: Kopete-jabber is not working anymore In-Reply-To: <201001282251.07980.detlev.casanova@gmail.com> References: <201001282251.07980.detlev.casanova@gmail.com> Message-ID: <4B673926.2040400@math.unl.edu> On 01/28/2010 03:51 PM, Detlev Casanova wrote: > Hi, > jabber.org has recently changed it's server configuration. > Now, Kopete is not connecting to any jabber.org account. > > How can I tell the release team that this is blocking for KDE 4.4 before we > have worked the problem out ? You can propose it as you just did... However, I don't consider what jabber.org does raises to the level of blocking a kde release. It's a bug like any other, and it'll get fixed when it gets fixed, hopefully sooner rather than later. any bug(s) filed (for tracking purposes)? -- Rex From rdieter at math.unl.edu Tue Feb 2 20:41:43 2010 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 02 Feb 2010 13:41:43 -0600 Subject: getting rid of kde-l10n Message-ID: <4B687FF7.80601@math.unl.edu> Hear me out. :) I'm not proposing anything yet, but would like to hear about the pros/cons of 1. status quo: shipping translations separately to software 2. shipping translations alonside (ie, in the same release tarballs) the software. How hard would it be to work toward something closer to 2 for KDE SC? -- Rex From neundorf at kde.org Tue Feb 2 21:27:41 2010 From: neundorf at kde.org (Alexander Neundorf) Date: Tue, 2 Feb 2010 21:27:41 +0100 Subject: polkit-1 in 4.4 branch In-Reply-To: <201002011123.14862.urkud@ya.ru> References: <201002011123.14862.urkud@ya.ru> Message-ID: <201002022127.41587.neundorf@kde.org> On Monday 01 February 2010, Yury G. Kudryashov wrote: > Hi! > > I've compiled 4.3.95 with polkit-1 kauth backend but > KDE4_INSTALL_AUTH_ACTION installs action files into policykit-0 actions dir > (see below). The problems seems to be fixed in trunk but there are many > changes in kauth-related cmake code. Is it possible to backport these > changes, or this is too large change for RC3? Dario is taking care of it. It should be working then. This will then still go into 4.4.0 ? Alex From rdieter at math.unl.edu Tue Feb 2 21:32:58 2010 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 02 Feb 2010 14:32:58 -0600 Subject: polkit-1 in 4.4 branch In-Reply-To: <201002022127.41587.neundorf@kde.org> References: <201002011123.14862.urkud@ya.ru> <201002022127.41587.neundorf@kde.org> Message-ID: <4B688BFA.50300@math.unl.edu> On 02/02/2010 02:27 PM, Alexander Neundorf wrote: > On Monday 01 February 2010, Yury G. Kudryashov wrote: >> Hi! >> >> I've compiled 4.3.95 with polkit-1 kauth backend but >> KDE4_INSTALL_AUTH_ACTION installs action files into policykit-0 actions dir >> (see below). The problems seems to be fixed in trunk but there are many >> changes in kauth-related cmake code. Is it possible to backport these >> changes, or this is too large change for RC3? > > Dario is taking care of it. It should be working then. > This will then still go into 4.4.0 ? Looks fixed/ok in 4.3.98 to me. -- Rex From aacid at kde.org Tue Feb 2 22:45:02 2010 From: aacid at kde.org (Albert Astals Cid) Date: Tue, 2 Feb 2010 21:45:02 +0000 Subject: getting rid of kde-l10n In-Reply-To: <4B687FF7.80601@math.unl.edu> References: <4B687FF7.80601@math.unl.edu> Message-ID: <201002022145.02659.aacid@kde.org> A Dimarts, 2 de febrer de 2010, Rex Dieter va escriure: > Hear me out. :) > > I'm not proposing anything yet, but would like to hear about the > pros/cons of > 1. status quo: shipping translations separately to software > > 2. shipping translations alonside (ie, in the same release tarballs) > the software. > > How hard would it be to work toward something closer to 2 for KDE SC? What would be the benefit? Albert > > -- Rex > _______________________________________________ > release-team mailing list > release-team at kde.org > https://mail.kde.org/mailman/listinfo/release-team > From rdieter at math.unl.edu Tue Feb 2 23:00:57 2010 From: rdieter at math.unl.edu (Rex Dieter) Date: Tue, 02 Feb 2010 16:00:57 -0600 Subject: getting rid of kde-l10n In-Reply-To: <201002022145.02659.aacid@kde.org> References: <4B687FF7.80601@math.unl.edu> <201002022145.02659.aacid@kde.org> Message-ID: <4B68A099.8060200@math.unl.edu> On 02/02/2010 03:45 PM, Albert Astals Cid wrote: > A Dimarts, 2 de febrer de 2010, Rex Dieter va escriure: >> Hear me out. :) >> >> I'm not proposing anything yet, but would like to hear about the >> pros/cons of >> 1. status quo: shipping translations separately to software >> >> 2. shipping translations alonside (ie, in the same release tarballs) >> the software. >> >> How hard would it be to work toward something closer to 2 for KDE SC? > > What would be the benefit? I know it's been this way for like forever. Just wondering what kinds of attachments there are, and pros/cons of each approach. Honestly, part of this comes from my being a distro packager, but keeping these separate is ... a bit painful(1). Also, fedora's release team keeps asking my why kde keeps translations separate, and I honestly don't have a good answer for them. Seems only the SC portions keep things separate, I mean extragear releases bundle software/translations together, so it's not like it's something new or different. -- Rex (1) releases that kept software/translations bundled together makes their packaging simpler, imo. From l.lunak at suse.cz Tue Feb 2 23:10:53 2010 From: l.lunak at suse.cz (Lubos Lunak) Date: Tue, 2 Feb 2010 23:10:53 +0100 Subject: getting rid of kde-l10n In-Reply-To: <4B68A099.8060200@math.unl.edu> References: <4B687FF7.80601@math.unl.edu> <201002022145.02659.aacid@kde.org> <4B68A099.8060200@math.unl.edu> Message-ID: <201002022310.53497.l.lunak@suse.cz> On Tuesday 02 of February 2010, Rex Dieter wrote: > On 02/02/2010 03:45 PM, Albert Astals Cid wrote: > > A Dimarts, 2 de febrer de 2010, Rex Dieter va escriure: > >> 2. shipping translations alonside (ie, in the same release tarballs) > >> the software. > >> > >> How hard would it be to work toward something closer to 2 for KDE SC? > > > > What would be the benefit? > > I know it's been this way for like forever. Just wondering what kinds > of attachments there are, and pros/cons of each approach. > > Honestly, part of this comes from my being a distro packager, but > keeping these separate is ... a bit painful(1). Also, fedora's release > team keeps asking my why kde keeps translations separate, and I honestly > don't have a good answer for them. Why don't you ask them why it should be changed, and just stop there if they don't have a good answer? Why fix something that is not broken. > Seems only the SC portions keep things separate, I mean extragear > releases bundle software/translations together, so it's not like it's > something new or different. openSUSE actually bundles together even translations for some extragear stuff. And, as a user, I'll much rather install czech translations for few apps I perhaps don't use rather than translations for all the languages in the world I definitely do not use. > (1) releases that kept software/translations bundled together makes > their packaging simpler, imo. Why? You just package a tarball and that's it. What is there so complicated about that? -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak at suse.cz , l.lunak at kde.org From mueller at kde.org Tue Feb 2 23:33:05 2010 From: mueller at kde.org (Dirk Mueller) Date: Tue, 2 Feb 2010 23:33:05 +0100 Subject: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002021704.43443.than@redhat.com> References: <201001312236.37813.mueller@kde.org> <201002021704.43443.than@redhat.com> Message-ID: <201002022333.05902.mueller@kde.org> On Tuesday 02 February 2010, Than Ngo wrote: > The kde-l10n packages are still missing. Dirk, do you know when the > kde-l10n will be available on ktown? ouch.. uploaded, thanks! Greetings, Dirk From ana at debian.org Wed Feb 3 00:52:46 2010 From: ana at debian.org (Ana Guerrero) Date: Wed, 3 Feb 2010 00:52:46 +0100 Subject: getting rid of kde-l10n In-Reply-To: <4B68A099.8060200@math.unl.edu> References: <4B687FF7.80601@math.unl.edu> <201002022145.02659.aacid@kde.org> <4B68A099.8060200@math.unl.edu> Message-ID: <20100202235246.GA4612@ana.debian.net> On Tue, Feb 02, 2010 at 04:00:57PM -0600, Rex Dieter wrote: > On 02/02/2010 03:45 PM, Albert Astals Cid wrote: > > A Dimarts, 2 de febrer de 2010, Rex Dieter va escriure: > >> Hear me out. :) > >> > >> I'm not proposing anything yet, but would like to hear about the > >> pros/cons of > >> 1. status quo: shipping translations separately to software > >> > >> 2. shipping translations alonside (ie, in the same release tarballs) > >> the software. > >> > >> How hard would it be to work toward something closer to 2 for KDE SC? > > > > What would be the benefit? > > I know it's been this way for like forever. Just wondering what kinds > of attachments there are, and pros/cons of each approach. > > Honestly, part of this comes from my being a distro packager, but > keeping these separate is ... a bit painful(1). Also, fedora's release > team keeps asking my why kde keeps translations separate, and I honestly > don't have a good answer for them. > > Seems only the SC portions keep things separate, I mean extragear > releases bundle software/translations together, so it's not like it's > something new or different. > With my packager hat on, I only see benefits, and not only because you can provide translations updates without having to update anything else. This is useful specially when you distro is close to release and frozen. First, most of the users are only interested in translations of their own language(s) and the easiest is just install the package kde-l10-XX from their distro and get done with it. If you ship e.g. the kdeedu tarball with the translations, you have several options: - ship every app with their translations. This is not a big pain for packagers but it will make users have a lot of translations installed they are not interested in. - ship the translations in another package, per application (kdeedu-l10n) or per module (marble-l10n). Again you make users install translations they are not interested in and also have them installing several translation packages. Packages have here aditional work having to care for way more translations packages than before. - ship the translations in another package for every language: kdeedu-l10n-es, kdeedu-l10n-fr, etc. Again, more work for packagers and for users. - I will omit the possibility of translation package for application and language (marble-l10n-fr), because I think it is plain crazy. You could say that with the current approach, you have translations installed that you do not need if you use only a couple of KDE apps, but it seems a better approach installing 30 MB of translations for a couple of KDE apps that make KDE users install 600 MB of translations. The handling of extragears translation is not exaclty the way to follow here. In every release packager have to update the languages, and users in some cases do not know they have to install a translation for this package manually. For them, it is just another kde app... Said all this, could you tell me the benefits of shipping translations alonside? I just do not see any. Ana From helio at kde.org Wed Feb 3 00:21:24 2010 From: helio at kde.org (Helio Chissini de Castro) Date: Tue, 2 Feb 2010 21:21:24 -0200 Subject: getting rid of kde-l10n In-Reply-To: <4B687FF7.80601@math.unl.edu> References: <4B687FF7.80601@math.unl.edu> Message-ID: <201002022121.25492.helio@kde.org> On Tuesday 02 February 2010 17:41:43 Rex Dieter wrote: > Hear me out. :) > > I'm not proposing anything yet, but would like to hear about the > pros/cons of > 1. status quo: shipping translations separately to software > > 2. shipping translations alonside (ie, in the same release tarballs) > the software. > > How hard would it be to work toward something closer to 2 for KDE SC? > > -- Rex For me i see only one clear reason where this situation can provide some benefits, if we go to git path to have per app repository. Otherwise, change current structure is bad bad idea, nothing matter pros/cons, is just change a secular ( yes, comes from last one :-) process. So i would advise to raise this question for l10n team and scm discussion. []'s -- Helio Chissini de Castro South America and Brazil Primary Contact KDE Developer since 2002 From aacid at kde.org Wed Feb 3 00:25:29 2010 From: aacid at kde.org (Albert Astals Cid) Date: Tue, 2 Feb 2010 23:25:29 +0000 Subject: getting rid of kde-l10n In-Reply-To: <201002022121.25492.helio@kde.org> References: <4B687FF7.80601@math.unl.edu> <201002022121.25492.helio@kde.org> Message-ID: <201002022325.29634.aacid@kde.org> A Dimarts, 2 de febrer de 2010, Helio Chissini de Castro va escriure: > On Tuesday 02 February 2010 17:41:43 Rex Dieter wrote: > > Hear me out. :) > > > > I'm not proposing anything yet, but would like to hear about the > > pros/cons of > > 1. status quo: shipping translations separately to software > > > > 2. shipping translations alonside (ie, in the same release tarballs) > > the software. > > > > How hard would it be to work toward something closer to 2 for KDE SC? > > > > -- Rex > > For me i see only one clear reason where this situation can provide some > benefits, if we go to git path to have per app repository. > Otherwise, change current structure is bad bad idea, nothing matter > pros/cons, is just change a secular ( yes, comes from last one :-) > process. > So i would advise to raise this question for l10n team and scm discussion. Moving the po files to the repository of each of the apps is the worst mistake you could make. Gnome had to write a whole web app just to overcome this problem in their repo. Albert > > []'s > From coolo at suse.de Wed Feb 3 13:45:22 2010 From: coolo at suse.de (Stephan Kulow) Date: Wed, 3 Feb 2010 13:45:22 +0100 Subject: getting rid of kde-l10n In-Reply-To: <4B68A099.8060200@math.unl.edu> References: <4B687FF7.80601@math.unl.edu> <201002022145.02659.aacid@kde.org> <4B68A099.8060200@math.unl.edu> Message-ID: <201002031345.22398.coolo@suse.de> Am Dienstag 02 Februar 2010 schrieb Rex Dieter: > (1) releases that kept software/translations bundled together makes > their packaging simpler, imo. And it makes translation much harder and it makes adding new languages much harder. And it wastes quite some download time for users - that usually only speak a small portion of the languages we offer. Greetings, Stephan From sebas at kde.org Wed Feb 3 13:59:56 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Wed, 3 Feb 2010 13:59:56 +0100 Subject: getting rid of kde-l10n In-Reply-To: <201002031345.22398.coolo@suse.de> References: <4B687FF7.80601@math.unl.edu> <4B68A099.8060200@math.unl.edu> <201002031345.22398.coolo@suse.de> Message-ID: <201002031359.56581.sebas@kde.org> On Wednesday 03 February 2010 13:45:22 Stephan Kulow wrote: > Am Dienstag 02 Februar 2010 schrieb Rex Dieter: > > (1) releases that kept software/translations bundled together makes > > their packaging simpler, imo. > > And it makes translation much harder and it makes adding new languages > much harder. And it wastes quite some download time for users - that > usually only speak a small portion of the languages we offer. And I think it makes splitting out the translations necessary for LiveCDs with constrained space. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From mueller at kde.org Thu Feb 4 11:34:54 2010 From: mueller at kde.org (Dirk Mueller) Date: Thu, 4 Feb 2010 11:34:54 +0100 Subject: KDE 4.4.0 tagged Message-ID: <201002041134.54430.mueller@kde.org> Hi, I've created an initial KDE 4.4.0 tag from branches/KDE/4.4 and will start to sort out the l10n-kde4 stuff now. Meanwhile there are tagged KDE 4.4.0 blockers: https://bugs.kde.org/buglist.cgi?keywords=kde-4.4.0-blocker It looks like bug 191589 is something that we should get fixed for KDE 4.4.0, any opinion about the others? Thanks, Dirk From rdieter at math.unl.edu Thu Feb 4 14:15:05 2010 From: rdieter at math.unl.edu (Rex Dieter) Date: Thu, 04 Feb 2010 07:15:05 -0600 Subject: kde-4.4, virtuoso-6.1.0, and virtuosoconverter Message-ID: <4B6AC859.4040300@math.unl.edu> FYI, http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter 1. The requirements for kde-4.4/nepomuk have changed pretty late in the game (after all 4.4rc's). 2. I personally have had trouble downloading 6.1.0 for the past 24hrs from sourceforge, if this is a continuing problem for others, perhaps we could put it on kde mirrors somewhere? 3. the aforementioned data conversion tool (from 5.0.x) as-is seems... less than optimal. Comments? -- Rex From pierre at archlinux.de Thu Feb 4 14:41:47 2010 From: pierre at archlinux.de (Pierre Schmitz) Date: Thu, 04 Feb 2010 14:41:47 +0100 Subject: KDE 4.4.0 tagged Message-ID: On Thu, 4 Feb 2010 11:34:54 +0100, Dirk Mueller wrote: > Hi, > > I've created an initial KDE 4.4.0 tag from branches/KDE/4.4 kdebindings fails to compile. I have not much time right now, so I'll just attach the buildlog for now. Pierre PS: Sorry attachment was too big fpr this list. So I'll resend this. -- Pierre Schmitz, https://users.archlinux.de/~pierre -------------- next part -------------- A non-text attachment was scrubbed... Name: kdebindings-4.4.0-1-x86_64-build.log.gz Type: application/x-gzip Size: 17313 bytes Desc: not available Url : http://mail.kde.org/pipermail/release-team/attachments/20100204/d8a71ed4/attachment.gz From toma at kde.org Thu Feb 4 15:21:53 2010 From: toma at kde.org (Tom Albers) Date: Thu, 04 Feb 2010 15:21:53 +0100 Subject: kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6AC859.4040300@math.unl.edu> Message-ID: <2395293.dfDzQ7E0tU@kde.org> Op Thursday 4 February 2010 14:15 schreef u: > FYI, > http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter > > 1. The requirements for kde-4.4/nepomuk have changed pretty late in the > game (after all 4.4rc's). That is not allowed. Please revert the offending commit. Best, Toma From rdieter at math.unl.edu Thu Feb 4 16:02:24 2010 From: rdieter at math.unl.edu (Rex Dieter) Date: Thu, 04 Feb 2010 09:02:24 -0600 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6ACEEE.5070303@kde.org> References: <4B6AC859.4040300@math.unl.edu> <4B6ACEEE.5070303@kde.org> Message-ID: <4B6AE180.8070805@math.unl.edu> On 02/04/2010 07:43 AM, Sebastian Trueg wrote: > Rex Dieter wrote: >> FYI, >> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter >> >> 1. The requirements for kde-4.4/nepomuk have changed pretty late in the >> game (after all 4.4rc's). > > No, they did not. I always said that Virtuoso 6 would be the dependency > for KDE 4.4. That's all well and good. I had held off trying to use 6.0 myself, based on comments from you that it was buggy and didn't work, ie, waiting for 6.0.1 or 6.1, which has now landed. Fact is that we're in a bad situation of now requiring something that's been untested and it's data is incompatible with what was tested. >> 3. the aforementioned data conversion tool (from 5.0.x) as-is seems... >> less than optimal. > > "less than optimal" is way too detailed for me to give any feedback on. ;) > > Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 > who already tries Nepomuk with Virtuoso 5 (and thus, compile > themselves!) to easily convert their data. I get that. I was hoping we could do better. This is just a consequence of (1), and not having ample time to adapt to the new stuff. -- Rex From toma at kde.org Thu Feb 4 16:16:34 2010 From: toma at kde.org (Tom Albers) Date: Thu, 04 Feb 2010 16:16:34 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6AE180.8070805@math.unl.edu> Message-ID: <4235196.m1ciYH076x@kde.org> Op Thursday 4 February 2010 16:02 schreef u: > On 02/04/2010 07:43 AM, Sebastian Trueg wrote: > > Rex Dieter wrote: > >> FYI, > >> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter > >> > >> 1. The requirements for kde-4.4/nepomuk have changed pretty late in the > >> game (after all 4.4rc's). > > > > No, they did not. I always said that Virtuoso 6 would be the dependency > > for KDE 4.4. You can not add a new dependency for KDE 4.4 the day before the release without testing. I consider it a new feature which is not allowed since ages. for KDE 4.5 I've planned to add it to the release schedule explicitly to make it even more clear. It is too late in the cycle for 4.4 to change this dependency. Really. Some packagers can not add a new dependency to their repository in one day and have prepared the KDE 4.4 packaging based on the 4.4 release candidates we have given them. Please don't do this. > Fact is that we're in a bad situation of now requiring something that's > been untested and it's data is incompatible with what was tested. +1 Unacceptable imho. > > Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 > > who already tries Nepomuk with Virtuoso 5 (and thus, compile > > themselves!) to easily convert their data. Distro's who have provided RC's to their users are now more or less obliged to run that script. Virtuoso was made a hard dependency (at least for anyone compiling kdepim) so all svn users also need to update. Best, Toma From sebas at kde.org Thu Feb 4 17:42:32 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Thu, 4 Feb 2010 17:42:32 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4235196.m1ciYH076x@kde.org> References: <4235196.m1ciYH076x@kde.org> Message-ID: <201002041742.33583.sebas@kde.org> On Thursday 04 February 2010 16:16:34 Tom Albers wrote: > Op Thursday 4 February 2010 16:02 schreef u: > > On 02/04/2010 07:43 AM, Sebastian Trueg wrote: > > > Rex Dieter wrote: > > >> FYI, > > >> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter > > >> > > >> 1. The requirements for kde-4.4/nepomuk have changed pretty late in > > >> the game (after all 4.4rc's). > > > > > > No, they did not. I always said that Virtuoso 6 would be the dependency > > > for KDE 4.4. > > You can not add a new dependency for KDE 4.4 the day before the release > without testing. I consider it a new feature which is not allowed since > ages. for KDE 4.5 I've planned to add it to the release schedule > explicitly to make it even more clear. It is too late in the cycle for 4.4 > to change this dependency. Really. Some packagers can not add a new > dependency to their repository in one day and have prepared the KDE 4.4 > packaging based on the 4.4 release candidates we have given them. Please > don't do this. > > > Fact is that we're in a bad situation of now requiring something that's > > been untested and it's data is incompatible with what was tested. > > +1 > Unacceptable imho. What will happen is that distros will ship Virtuoso 6 anyway, because they don't want to introduce V5, and then have to convert users' data again (first time from the sesame2) backend. I don't know in how far V6 is different from V5, other than the dataformat, but we might consider recommending V6 anyway, because it has a clearer road forward. It's a bit unfortunate that there was a bug in V6.0 that prevented us from testing with it, that seems fixed in 6.1? I'd also be interested in more (dis)advantages of V6 over V5, and how different V5 and 6 actually are from a "what can break KDE?"-point of view. Sebastian, can you give more details? > > > Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 > > > who already tries Nepomuk with Virtuoso 5 (and thus, compile > > > themselves!) to easily convert their data. > > Distro's who have provided RC's to their users are now more or less obliged > to run that script. Virtuoso was made a hard dependency (at least for > anyone compiling kdepim) so all svn users also need to update. Bottom line is that distros will probably shop Virtuoso 6 to their end-users anyway, so we need to make sure it works well with it. I don't think it's as easy as saying "it's too late to require V6", because it's not. Note that I don't like the situation, but to me it's more complex ... There's also the question what we require. As far as I know, KDE 4.4.0 works with virtuoso 5 and 6, so what would be natural is requiring at least V5, recommending V6 (for the upgrade path, BUT we haven't tested it yet). -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From mueller at kde.org Thu Feb 4 19:31:23 2010 From: mueller at kde.org (Dirk Mueller) Date: Thu, 4 Feb 2010 19:31:23 +0100 Subject: KDE 4.4.0 tarballs uploaded (try #1..) Message-ID: <201002041931.23553.mueller@kde.org> Hi, I've just finished uploading the first set of 4.4.0 tarballs. Please use the kde-4.4.0-blocker keyword in bugzilla and cc me on commits that should end up in 4.4.0. Planned release is Tuesday next week. Greetings, Dirk From mueller at kde.org Thu Feb 4 19:33:25 2010 From: mueller at kde.org (Dirk Mueller) Date: Thu, 4 Feb 2010 19:33:25 +0100 Subject: Fwd: Re: KDE 4.4.98 (4.4 RC3) Message-ID: <201002041933.25882.mueller@kde.org> Hi, both seem to be present in 4.4.0 as well. does anyone know which commits introduced those bugs? Thanks, Dirk -------------- next part -------------- An embedded message was scrubbed... From: Arkadiusz Miskiewicz Subject: Re: KDE 4.4.98 (4.4 RC3) Date: Mon, 1 Feb 2010 14:29:52 +0100 Size: 3976 Url: http://mail.kde.org/pipermail/release-team/attachments/20100204/26bd4740/attachment.eml From mueller at kde.org Thu Feb 4 19:34:11 2010 From: mueller at kde.org (Dirk Mueller) Date: Thu, 4 Feb 2010 19:34:11 +0100 Subject: offline until sunday Message-ID: <201002041934.11124.mueller@kde.org> Hi, I'll be completely offline friday/saturday, back on sunday afternoon. Greetings, Dirk From aseigo at kde.org Thu Feb 4 19:55:37 2010 From: aseigo at kde.org (Aaron J. Seigo) Date: Thu, 4 Feb 2010 10:55:37 -0800 Subject: Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002041933.25882.mueller@kde.org> References: <201002041933.25882.mueller@kde.org> Message-ID: <201002041055.38209.aseigo@kde.org> On February 4, 2010, Dirk Mueller wrote: > Hi, > > both seem to be present in 4.4.0 as well. does anyone know which commits > introduced those bugs? if nobody answers here, this should go to kdepim-devel@ -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From aseigo at kde.org Thu Feb 4 19:57:34 2010 From: aseigo at kde.org (Aaron J. Seigo) Date: Thu, 4 Feb 2010 10:57:34 -0800 Subject: KDE 4.4.0 tarballs uploaded (try #1..) In-Reply-To: <201002041931.23553.mueller@kde.org> References: <201002041931.23553.mueller@kde.org> Message-ID: <201002041057.34758.aseigo@kde.org> On February 4, 2010, Dirk Mueller wrote: > I've just finished uploading the first set of 4.4.0 tarballs. Please use > the kde-4.4.0-blocker keyword in bugzilla and cc me on commits that should > end up in 4.4.0. r1085260 (to kdebase/apps/plasma/applets/folderview/folderview.cpp) and r1085255 (to kdebase/workspace/plasma/desktop/shells/desktopview.[h|cpp]) should be in 4.4.0; they fix a bug with folderview-as-desktop-activity on multiscreen systems. sorry i didn't get these in sooner... this looks like the last of the serious issues for 4.4.0 in any case. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From than at redhat.com Tue Feb 2 17:04:43 2010 From: than at redhat.com (Than Ngo) Date: Tue, 2 Feb 2010 17:04:43 +0100 Subject: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201001312236.37813.mueller@kde.org> References: <201001312236.37813.mueller@kde.org> Message-ID: <201002021704.43443.than@redhat.com> The kde-l10n packages are still missing. Dirk, do you know when the kde-l10n will be available on ktown? thanks, Than > Hi, > > I just finished uploading RC3 to unstable/4.4.98. Release is hopefully, > when somebody confirms that it all compiles, tomorrow. > > > Greetings, > Dirk > _______________________________________________ From shadzik at pld-linux.org Wed Feb 3 00:53:35 2010 From: shadzik at pld-linux.org (=?UTF-8?B?QmFydG9zeiDFmndpxIV0ZWs=?=) Date: Wed, 3 Feb 2010 00:53:35 +0100 Subject: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002022333.05902.mueller@kde.org> References: <201001312236.37813.mueller@kde.org> <201002021704.43443.than@redhat.com> <201002022333.05902.mueller@kde.org> Message-ID: 2010/2/2 Dirk Mueller : > On Tuesday 02 February 2010, Than Ngo wrote: >> The kde-l10n packages are still missing. Dirk, do you know when the >> ?kde-l10n will be available on ktown? > > ouch.. uploaded, thanks! Those problems Arkadiusz mentioned seem really annoying... Dirk I know you're not the one to fix them, but maybe you could ask the kdepim developers to fix these issues before 4.4 launches? Would be great. Greets, -- "I'm living proof if you do one thing right in your career, you can coast for a long time. A LOOOOONG time." -Guy Kawasaki From drf54321 at gmail.com Wed Feb 3 10:00:43 2010 From: drf54321 at gmail.com (Dario Freddi) Date: Wed, 3 Feb 2010 10:00:43 +0100 Subject: polkit-1 in 4.4 branch In-Reply-To: <201002022127.41587.neundorf@kde.org> References: <201002011123.14862.urkud@ya.ru> <201002022127.41587.neundorf@kde.org> Message-ID: <201002031000.48862.drf54321@gmail.com> On Tuesday 02 February 2010 21:27:41 Alexander Neundorf wrote: > On Monday 01 February 2010, Yury G. Kudryashov wrote: > > Hi! > > > > I've compiled 4.3.95 with polkit-1 kauth backend but > > KDE4_INSTALL_AUTH_ACTION installs action files into policykit-0 actions > > dir (see below). The problems seems to be fixed in trunk but there are > > many changes in kauth-related cmake code. Is it possible to backport > > these changes, or this is too large change for RC3? > > Dario is taking care of it. > It should be working then. > This will then still go into 4.4.0 ? I actually had backported this on the 24th January: http://websvn.kde.org/?view=revision&revision=1079649 , so I'm still not crazy and it should already be in since a while :) > > Alex > -- ------------------- Dario Freddi KDE Developer GPG Key Signature: 511A9A3B -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100203/b8ce947b/attachment-0001.sig From arekm at maven.pl Thu Feb 4 12:16:34 2010 From: arekm at maven.pl (Arkadiusz Miskiewicz) Date: Thu, 4 Feb 2010 12:16:34 +0100 Subject: KDE 4.4.0 tagged In-Reply-To: <201002041134.54430.mueller@kde.org> References: <201002041134.54430.mueller@kde.org> Message-ID: <201002041216.35840.arekm@maven.pl> On Thursday 04 of February 2010, Dirk Mueller wrote: > Hi, > > I've created an initial KDE 4.4.0 tag from branches/KDE/4.4 and will start > to sort out the l10n-kde4 stuff now. Nothing critical but another nasty regression for me. https://bugs.kde.org/show_bug.cgi?id=225318 -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ From pierre at archlinux.de Thu Feb 4 14:36:18 2010 From: pierre at archlinux.de (Pierre Schmitz) Date: Thu, 04 Feb 2010 14:36:18 +0100 Subject: KDE 4.4.0 tagged In-Reply-To: <201002041134.54430.mueller@kde.org> References: <201002041134.54430.mueller@kde.org> Message-ID: On Thu, 4 Feb 2010 11:34:54 +0100, Dirk Mueller wrote: > Hi, > > I've created an initial KDE 4.4.0 tag from branches/KDE/4.4 kdebindings fails to compile. I have not much time right now, so I'll just attach the buildlog for now. Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre -------------- next part -------------- -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found. -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found. -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found. -- Found Qt-Version 4.6.1 (using /usr/bin/qmake) -- Found OpenSSL: /usr/lib/libssl.so;/usr/lib/libcrypto.so -- Looking for _POSIX_TIMERS -- Looking for _POSIX_TIMERS - found -- Found Qt-Version 4.6.1 (using /usr/bin/qmake) -- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so -- Looking for XOpenDisplay in /usr/lib/libX11.so;/usr/lib/libXext.so;/usr/lib/libXft.so;/usr/lib/libXau.so;/usr/lib/libXdmcp.so - found -- Looking for gethostbyname -- Looking for gethostbyname - found -- Looking for connect -- Looking for connect - found -- Looking for remove -- Looking for remove - found -- Looking for shmat -- Looking for shmat - found -- Looking for IceConnectionNumber in ICE -- Looking for IceConnectionNumber in ICE - found -- Found X11: /usr/lib/libX11.so -- Looking for include files CMAKE_HAVE_PTHREAD_H -- Looking for include files CMAKE_HAVE_PTHREAD_H - found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE -- Found OpenSSL: /usr/lib/libssl.so -- Found Automoc4: /usr/bin/automoc4 -- Found Perl: /usr/bin/perl -- Phonon Version: 4.3.80 -- Found Phonon: /usr/lib/libphonon.so -- Found Phonon Includes: /usr/include/KDE;/usr/include -- Performing Test _OFFT_IS_64BIT -- Performing Test _OFFT_IS_64BIT - Success -- Performing Test HAVE_FPIE_SUPPORT -- Performing Test HAVE_FPIE_SUPPORT - Success -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL -- Performing Test __KDE_HAVE_W_OVERLOADED_VIRTUAL - Success -- Performing Test __KDE_HAVE_GCC_VISIBILITY -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success -- Found KDE 4.4 include dir: /usr/include -- Found KDE 4.4 library dir: /usr/lib -- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler -- Found automoc4: /usr/bin/automoc4 -- Found Soprano: /usr/include -- Found SharedDesktopOntologies: /usr/share/ontology -- Found Nepomuk: /usr/lib/libnepomuk.so -- Found KdepimLibs: /usr/lib/cmake/KdepimLibs/KdepimLibsConfig.cmake -- Phonon Version: 4.3.80 -- Found QScintilla2: /usr/lib/libqscintilla2.so -- Found Okular: /usr/lib/libokularcore.so -- Found Akonadi: /usr/lib/cmake/Akonadi/AkonadiConfig.cmake -- Checking how Qt was built... -- Threshold is set to 10 -- QT_NO_DEBUG *Undefined* -- QT_NO_BUTTONGROUP *Undefined* -- QT_NO_COLORDIALOG *Undefined* -- QT_NO_DATETIMEEDIT *Undefined* -- QT_NO_DIALOG *Undefined* -- QT_NO_ERRORMESSAGE *Undefined* -- QT_NO_FILEDIALOG *Undefined* -- QT_NO_FONTDIALOG *Undefined* -- QT_NO_GROUPBOX *Undefined* -- QT_NO_LCDNUMBER *Undefined* -- QT_NO_LINEEDIT *Undefined* -- QT_NO_LISTVIEW *Undefined* -- QT_NO_MAINWINDOW *Undefined* -- QT_NO_MENUBAR *Undefined* -- QT_NO_MESSAGEBOX *Undefined* -- QT_NO_PRINTDIALOG *Undefined* -- QT_NO_PROGRESSBAR *Undefined* -- QT_NO_PROGRESSDIALOG *Undefined* -- QT_NO_PUSHBUTTON *Undefined* -- QT_NO_RADIOBUTTON *Undefined* -- QT_NO_SCROLLBAR *Undefined* -- QT_NO_SLIDER *Undefined* -- QT_NO_STYLE_PLASTIQUE *Undefined* -- QT_NO_STYLE_WINDOWSXP [Defined] -- QT_NO_STYLE_WINDOWS *Undefined* -- QT_NO_STYLE_MAC [Defined] -- QT_NO_STYLE_CLEANLOOKS *Undefined* -- QT_NO_TABLEVIEW *Undefined* -- QT_NO_TEXTBROWSER *Undefined* -- QT_NO_TEXTEDIT *Undefined* -- QT_NO_TOOLBUTTON *Undefined* -- Found Qt-Version 4.6.1 (using /usr/bin/qmake) -- Found X11: /usr/lib/libX11.so -- Phonon Version: 4.3.80 /usr/include -- Found QScintilla2: /usr/lib/libqscintilla2.so -- found qimageblitz, version 4.0.0 -- Found QImageBlitz: /usr/include/qimageblitz -- Found libattica: /usr/lib/libattica.so -- Build Smoke... yes - Qt, QtCore, QtNetwork, QtDBus, QtGui, QtSvg, QtSql, QtXml, QtXmlPatterns, QtOpenGL, QtWebKit, QtScript, QtUiTools, QtTest, QtMultimedia, Phonon, QScintilla2, QImageBlitz, Solid, Soprano, Plasma, KDECore, KDEUi, KIO, KParts, KFile, KNewStuff2, KNewStuff3, KUtils, Akonadi, KHTML, KTextEditor, Attica, Nepomuk, Okular -- Ruby found: /usr/lib/libruby.so -- Ruby found: /usr/lib/libruby.so -- Ruby found: /usr/lib/libruby.so -- rbuic4 not found, ruby-clock will not created -- Ruby found: /usr/lib/libruby.so -- rbuic4 not found, ruby-digital-clock will not created -- Build QtRuby... yes -- Build QtWebKit Ruby... yes -- Build QtUiTools Ruby... yes -- Build QtScript... yes -- Build QtTest... yes -- Build Soprano Ruby... yes -- Build QScintilla Ruby... no -- Build Qwt Ruby... no -- Build Phonon Ruby... no -- Build Akonadi Ruby... yes -- Build KHTML Ruby... yes -- Build Korundum... yes -- Build KDevPlatform Ruby... no -- Build KTextEditor Ruby... yes -- Build Nepomuk Ruby... yes -- Build Okular Ruby... yes -- Build Plasma Ruby... yes -- Build Solid Ruby... yes -- Build Kross Ruby... no -- Found PythonInterp: /usr/bin/python2.6 -- Found Python executable: /usr/bin/python2.6 -- Found Python version: 2.6.4 -- Found Python library: /usr/lib/libpython2.6.so -- Found Python executable: /usr/bin/python2.6 -- Found Python version: 2.6.4 -- Found Python library: /usr/lib/libpython2.6.so -- Python Libraries: /usr/lib/libpython2.6.so -- Python Include Path: /usr/include/python2.6 -- Build Kross Python... yes -- Found SIP version: 4.10 -- Found PyQt4 version: 4.7 -- Found Python executable: /usr/bin/python2.6 -- Found Python version: 2.6.4 -- Found Python library: /usr/lib/libpython2.6.so -- Found PyQt4 version: 4.7 -- KDE_VERSION: 4.4.00 -- KDE4_INCLUDE_DIR: /usr/include -- KDE4_LIB_DIR: /usr/lib -- PYTHON_SITE_PACKAGES_DIR: /usr/lib/python2.6/site-packages -- Build PyKDE4... yes -- Path of mono: /usr/bin/mono -- Path of gmcs: /usr/bin/gmcs -- Path of gacutil: /usr/bin/gacutil -- checking for one of the modules 'mono-cecil' -- checking for one of the modules 'cecil' -- found cecil, version 2.6.1 -- Using GAC dir: /usr/lib/mono -- checking for one of the modules 'mono' -- found mono, version 2.6.1 -- checking for one of the modules 'glib-2.0' -- found glib-2.0, version 2.22.4 -- checking for module 'monodoc' -- found monodoc, version 2.6.1 -- Build Qyoto... yes -- Build PhononSharp... no -- Build QScintillaSharp... no -- Build SopranoSharp... yes -- Build NepomukSharp... yes -- Build PlasmaSharp... yes -- Build Kimono... yes -- Build KHTMLSharp... yes -- Build KTextEditorSharp... yes ----------------------------------------------------------------------------- -- The following external packages were located on your system. -- This installation will have the extra features provided by these packages. ----------------------------------------------------------------------------- * Shared desktop ontologies - Desktop ontologies * Soprano - Soprano Libraries * Soprano - Soprano Libraries * Soprano - Soprano Libraries * Soprano - Soprano Libraries * Nepomuk - Nepomuk Libraries * Kdepimlibs - KDE pim Libraries ----------------------------------------------------------------------------- -- The following OPTIONAL packages could NOT be located on your system. -- Consider installing them to enable more features from this software. ----------------------------------------------------------------------------- * Polkit-Qt Qt Wrapper around PolicyKit Required to build PolicyKit-Qt support ----------------------------------------------------------------------------- -- Configuring done -- Generating done -- Build files have been written to: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build Scanning dependencies of target rbuic4_bin Scanning dependencies of target cppparser [ 1%] [ 1%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/customwidgetsinfo.o Building CXX object generator/parser/CMakeFiles/cppparser.dir/ast.o [ 1%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/default_visitor.o [ 1%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/databaseinfo.o [ 1%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/memorypool.o [ 1%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/visitor.o [ 1%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/control.o [ 1%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/driver.o [ 1%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/lexer.o /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/ruby/qtruby/tools/rbuic/driver.cpp: In function ?bool isAnsiCCharacter(const QChar&)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/ruby/qtruby/tools/rbuic/driver.cpp:215: Warnung: suggest parentheses around ?&&? within ?||? [ 1%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/treewalker.o [ 1%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ui4.o [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/parser.o In Datei, eingef?gt von /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.3/../../../../include/c++/4.4.3/ext/hash_map:59, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parser.h:36, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parser.cpp:23: /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.3/../../../../include/c++/4.4.3/backward/backward_warning.h:28:2: Warnung: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file backward_warning.h. To disable this warning use -Wno-deprecated. /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parser.cpp:1034:2: Warnung: #warning "implement me" /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parser.cpp:2601:2: Warnung: #warning "implemente me (AST)" /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parser.cpp:3487:2: Warnung: #warning "mark the ast as constant" [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/listnode.o [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/tokens.o [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/dumptree.o [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/parsesession.o /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parsesession.cpp: In destructor ?ParseSession::~ParseSession()?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parsesession.cpp:42: Warnung: m?gliches Problem bei Aufruf des ?delete?-Operators erkannt /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parsesession.cpp:42: Warnung: invalid use of incomplete type ?struct rpp::MacroBlock? /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parsesession.h:43: Warnung: forward declaration of ?struct rpp::MacroBlock? /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/generator/parser/parsesession.cpp:42: Anmerkung: weder der Destruktor noch der klassenspezifische Operator ?delete? wird aufgerufen, auch wenn sie bei der Klassendefinition deklariert werden [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/commentparser.o [ 2%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/commentformatter.o [ 2%] [ 3%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/uic.o Building CXX object generator/parser/CMakeFiles/cppparser.dir/codegenerator.o [ 3%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/validator.o [ 3%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/indexedstring.o [ 4%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ruby/rbextractimages.o [ 4%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/stringhelpers.o [ 4%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ruby/rbwritedeclaration.o [ 4%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ruby/rbwriteicondata.o [ 4%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-stream.o [ 4%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ruby/rbwriteicondeclaration.o [ 4%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-macro-expander.o [ 4%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ruby/rbwriteiconinitialization.o [ 4%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/ruby/rbwriteinitialization.o [ 4%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-scanner.o [ 4%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-macro.o [ 5%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-engine.o [ 5%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-internal.o [ 5%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-environment.o [ 5%] Building CXX object ruby/qtruby/tools/rbuic/CMakeFiles/rbuic4_bin.dir/main.o [ 5%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/pp-location.o Linking CXX executable rbuic4 [ 5%] Built target rbuic4_bin [ 5%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/preprocessor.o Scanning dependencies of target rbrcc [ 5%] Building CXX object ruby/qtruby/tools/rbrcc/CMakeFiles/rbrcc.dir/rcc.o [ 5%] Building CXX object generator/parser/CMakeFiles/cppparser.dir/rpp/chartools.o Linking CXX shared library ../bin/libcppparser.so [ 5%] Built target cppparser [ 5%] Building CXX object ruby/qtruby/tools/rbrcc/CMakeFiles/rbrcc.dir/main.o Scanning dependencies of target korundum4_automoc [ 5%] Built target korundum4_automoc Scanning dependencies of target krubyapplication_automoc [ 5%] Built target krubyapplication_automoc Scanning dependencies of target krubypluginfactory_automoc [ 5%] Built target krubypluginfactory_automoc Scanning dependencies of target rbkconfig_compiler4_automoc [ 5%] Built target rbkconfig_compiler4_automoc Scanning dependencies of target plasma_applet_automoc [ 5%] Built target plasma_applet_automoc Scanning dependencies of target krosspython_automoc [ 5%] Built target krosspython_automoc Scanning dependencies of target compile_python_files [ 5%] Built target compile_python_files [ 5%] Generating sip/akonadi/sipakonadipart0.cpp, sip/akonadi/sipakonadipart1.cpp, sip/akonadi/sipakonadipart2.cpp, sip/akonadi/sipakonadipart3.cpp, sip/akonadi/sipakonadipart4.cpp, sip/akonadi/sipakonadipart5.cpp, sip/akonadi/sipakonadipart6.cpp, sip/akonadi/sipakonadipart7.cpp Linking CXX executable rbrcc [ 5%] Built target rbrcc [ 5%] Generating sip/dnssd/sipdnssdpart0.cpp, sip/dnssd/sipdnssdpart1.cpp, sip/dnssd/sipdnssdpart2.cpp, sip/dnssd/sipdnssdpart3.cpp, sip/dnssd/sipdnssdpart4.cpp, sip/dnssd/sipdnssdpart5.cpp, sip/dnssd/sipdnssdpart6.cpp, sip/dnssd/sipdnssdpart7.cpp Scanning dependencies of target python_module_PyKDE4_dnssd [ 5%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipAPIdnssd.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipdnssdpart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 5%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipAPIdnssd.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipdnssdpart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipdnssdpart1.cpp: In function ?PyObject* meth_DNSSD_ServiceTypeBrowser_isRunning(PyObject*, PyObject*)?: sipdnssdpart1.cpp:530: Warnung: ?bool DNSSD::ServiceTypeBrowser::isRunning() const? ist veraltet (deklariert bei /usr/include/dnssd/servicetypebrowser.h:97) [ 5%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipAPIdnssd.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipdnssdpart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 5%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipAPIdnssd.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipdnssdpart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipAPIdnssd.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipdnssdpart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipAPIdnssd.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/dnssd/sipdnssdpart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart6.o [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_dnssd.dir/sip/dnssd/sipdnssdpart7.o Linking CXX shared library ../../lib/pykde/dnssd.so [ 6%] Built target python_module_PyKDE4_dnssd [ 6%] Generating sip/kdecore/sipkdecorepart0.cpp, sip/kdecore/sipkdecorepart1.cpp, sip/kdecore/sipkdecorepart2.cpp, sip/kdecore/sipkdecorepart3.cpp, sip/kdecore/sipkdecorepart4.cpp, sip/kdecore/sipkdecorepart5.cpp, sip/kdecore/sipkdecorepart6.cpp, sip/kdecore/sipkdecorepart7.cpp Scanning dependencies of target python_module_PyKDE4_akonadi [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip: In function ?PyObject* convertFrom_QSet_0100QByteArray(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip:609: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden Scanning dependencies of target python_module_PyKDE4_kdecore [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 6%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdecorepart1.cpp: In function ?PyObject* meth_KUser_fullName(PyObject*, PyObject*)?: sipkdecorepart1.cpp:4557: Warnung: ?QString KUser::fullName() const? ist veraltet (deklariert bei /usr/include/kuser.h:179) sipkdecorepart1.cpp: In function ?PyObject* meth_KUrl_cmp(PyObject*, PyObject*)?: sipkdecorepart1.cpp:9947: Warnung: ?bool KUrl::cmp(const KUrl&, bool) const? ist veraltet (deklariert bei /usr/include/kurl.h:869) sipkdecorepart1.cpp: In function ?PyObject* meth_KUrl_fromPathOrUrl(PyObject*, PyObject*)?: sipkdecorepart1.cpp:10135: Warnung: ?static KUrl KUrl::fromPathOrUrl(const QString&)? ist veraltet (deklariert bei /usr/include/kurl.h:967) sipkdecorepart1.cpp: In function ?PyObject* meth_KUrl_encode_string(PyObject*, PyObject*)?: sipkdecorepart1.cpp:10225: Warnung: ?static QString KUrl::encode_string(const QString&)? ist veraltet (deklariert bei /usr/include/kurl.h:1006) sipkdecorepart1.cpp: In function ?PyObject* meth_KUrl_encode_string_no_slash(PyObject*, PyObject*)?: sipkdecorepart1.cpp:10254: Warnung: ?static QString KUrl::encode_string_no_slash(const QString&)? ist veraltet (deklariert bei /usr/include/kurl.h:1021) sipkdecorepart1.cpp: In function ?PyObject* meth_KUrl_decode_string(PyObject*, PyObject*)?: sipkdecorepart1.cpp:10283: Warnung: ?static QString KUrl::decode_string(const QString&)? ist veraltet (deklariert bei /usr/include/kurl.h:1035) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipakonadipart2.cpp: In constructor ?sipAkonadi_ItemView::sipAkonadi_ItemView(KXmlGuiWindow*, QWidget*)?: sipakonadipart2.cpp:7434: Warnung: ?Akonadi::ItemView::ItemView(KXmlGuiWindow*, QWidget*)? ist veraltet (deklariert bei /usr/include/akonadi/itemview.h:80) sipakonadipart2.cpp: In function ?PyObject* meth_Akonadi_ItemView_setXmlGuiWindow(PyObject*, PyObject*)?: sipakonadipart2.cpp:12275: Warnung: ?void Akonadi::ItemView::setXmlGuiWindow(KXmlGuiWindow*)? ist veraltet (deklariert bei /usr/include/akonadi/itemview.h:104) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdecorepart3.cpp: In function ?PyObject* meth_KSycoca_isChanged(PyObject*, PyObject*)?: sipkdecorepart3.cpp:850: Warnung: ?static bool KSycoca::isChanged(const char*)? ist veraltet (deklariert bei /usr/include/ksycoca.h:164) sipkdecorepart3.cpp: In function ?PyObject* meth_KSycoca_readError(PyObject*, PyObject*)?: sipkdecorepart3.cpp:900: Warnung: ?static bool KSycoca::readError()? ist veraltet (deklariert bei /usr/include/ksycoca.h:173) sipkdecorepart3.cpp: In function ?PyObject* meth_KStandardDirs_addResourceType(PyObject*, PyObject*)?: sipkdecorepart3.cpp:2189: Warnung: ?bool KStandardDirs::addResourceType(const char*, const QString&, bool)? ist veraltet (deklariert bei /usr/include/kstandarddirs.h:257) sipkdecorepart3.cpp: In function ?PyObject* meth_KStandardDirs_kde_default(PyObject*, PyObject*)?: sipkdecorepart3.cpp:2828: Warnung: ?static QString KStandardDirs::kde_default(const char*)? ist veraltet (deklariert bei /usr/include/kstandarddirs.h:654) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/kservicetype.sip: In function ?PyObject* convertFrom_QMap_0100QString_0100QVariant_Type(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/kservicetype.sip:178: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden sipkdecorepart3.cpp: In function ?PyObject* meth_KServiceGroup_baseGroup(PyObject*, PyObject*)?: sipkdecorepart3.cpp:6962: Warnung: ?static KSharedPtr KServiceGroup::baseGroup(const QString&)? ist veraltet (deklariert bei /usr/include/kservicegroup.h:252) sipkdecorepart3.cpp: In function ?PyObject* meth_KService_type(PyObject*, PyObject*)?: sipkdecorepart3.cpp:7924: Warnung: ?QString KService::type() const? ist veraltet (deklariert bei /usr/include/kservice.h:104) sipkdecorepart3.cpp: In function ?PyObject* meth_KService_desktopEntryPath(PyObject*, PyObject*)?: sipkdecorepart3.cpp:8140: Warnung: ?QString KService::desktopEntryPath() const? ist veraltet (deklariert bei /usr/include/kservice.h:169) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdecorepart4.cpp: In constructor ?sipKPluginFactory::sipKPluginFactory(const KAboutData*, QObject*)?: sipkdecorepart4.cpp:5592: Warnung: ?KPluginFactory::KPluginFactory(const KAboutData*, QObject*)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:262) sipkdecorepart4.cpp: In constructor ?sipKPluginFactory::sipKPluginFactory(QObject*)?: sipkdecorepart4.cpp:5597: Warnung: ?KPluginFactory::KPluginFactory(QObject*)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:267) sipkdecorepart4.cpp: In member function ?virtual QObject* sipKPluginFactory::createObject(QObject*, const char*, const QStringList&)?: sipkdecorepart4.cpp:5653: Warnung: ?virtual QObject* KPluginFactory::createObject(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:415) sipkdecorepart4.cpp: In member function ?QObject* sipKPluginFactory::sipProtectVirt_createObject(bool, QObject*, const char*, const QStringList&)?: sipkdecorepart4.cpp:5847: Warnung: ?virtual QObject* KPluginFactory::createObject(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:415) sipkdecorepart4.cpp: In function ?PyObject* meth_KPluginFactory_create(PyObject*, PyObject*)?: sipkdecorepart4.cpp:6085: Warnung: ?QObject* KPluginFactory::create(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:342) sipkdecorepart4.cpp: In function ?PyObject* meth_KMimeType_parentMimeType(PyObject*, PyObject*)?: sipkdecorepart4.cpp:7451: Warnung: ?QString KMimeType::parentMimeType() const? ist veraltet (deklariert bei /usr/include/kmimetype.h:331) sipkdecorepart4.cpp: In function ?PyObject* meth_KServiceType_desktopEntryPath(PyObject*, PyObject*)?: sipkdecorepart4.cpp:7910: Warnung: ?QString KServiceType::desktopEntryPath() const? ist veraltet (deklariert bei /usr/include/kservicetype.h:75) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdecorepart5.cpp: In function ?PyObject* meth_KLibrary_factory(PyObject*, PyObject*)?: sipkdecorepart5.cpp:4305: Warnung: ?KPluginFactory* KLibrary::factory(const char*)? ist veraltet (deklariert bei /usr/include/klibrary.h:59) sipkdecorepart5.cpp: In function ?PyObject* meth_KLibLoader_self(PyObject*, PyObject*)?: sipkdecorepart5.cpp:4746: Warnung: ?static KLibLoader* KLibLoader::self()? ist veraltet (deklariert bei /usr/include/klibloader.h:142) sipkdecorepart5.cpp: In function ?PyObject* meth_KEncodingProber_encodingName(PyObject*, PyObject*)?: sipkdecorepart5.cpp:9359: Warnung: ?const char* KEncodingProber::encodingName() const? ist veraltet (deklariert bei /usr/include/kencodingprober.h:132) /usr/include/kconfig.h: At global scope: /usr/include/kconfig.h:375: Warnung: ?virtual const KConfigGroup KConfig::groupImpl(const QByteArray&) const? war versteckt sipkdecorepart5.cpp:10533: Warnung: von ?virtual KConfigGroup sipKDesktopFile::groupImpl(const QByteArray&)? [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipakonadipart4.cpp: In constructor ?sipAkonadi_CollectionView::sipAkonadi_CollectionView(KXmlGuiWindow*, QWidget*)?: sipakonadipart4.cpp:10101: Warnung: ?Akonadi::CollectionView::CollectionView(KXmlGuiWindow*, QWidget*)? ist veraltet (deklariert bei /usr/include/akonadi/collectionview.h:83) sipakonadipart4.cpp: In function ?PyObject* meth_Akonadi_CollectionView_setXmlGuiWindow(PyObject*, PyObject*)?: sipakonadipart4.cpp:14858: Warnung: ?void Akonadi::CollectionView::setXmlGuiWindow(KXmlGuiWindow*)? ist veraltet (deklariert bei /usr/include/akonadi/collectionview.h:106) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /usr/include/kconfiggroup.h:623: Warnung: ?virtual const KConfigGroup KConfigGroup::groupImpl(const QByteArray&) const? war versteckt sipkdecorepart6.cpp:12977: Warnung: von ?virtual KConfigGroup sipKConfigGroup::groupImpl(const QByteArray&)? sipkdecorepart6.cpp: In function ?PyObject* meth_KConfigGroup_changeGroup(PyObject*, PyObject*)?: sipkdecorepart6.cpp:13394: Warnung: ?void KConfigGroup::changeGroup(const QString&)? ist veraltet (deklariert bei /usr/include/kconfiggroup.h:152) sipkdecorepart6.cpp:13411: Warnung: ?void KConfigGroup::changeGroup(const char*)? ist veraltet (deklariert bei /usr/include/kconfiggroup.h:159) /usr/include/kconfig.h: At global scope: /usr/include/kconfig.h:375: Warnung: ?virtual const KConfigGroup KConfig::groupImpl(const QByteArray&) const? war versteckt sipkdecorepart6.cpp:16321: Warnung: von ?virtual KConfigGroup sipKConfig::groupImpl(const QByteArray&)? sipkdecorepart6.cpp: In function ?PyObject* meth_KConfig_setForceGlobal(PyObject*, PyObject*)?: sipkdecorepart6.cpp:16958: Warnung: ?void KConfig::setForceGlobal(bool)? ist veraltet (deklariert bei /usr/include/kconfig.h:343) sipkdecorepart6.cpp: In function ?PyObject* meth_KConfig_forceGlobal(PyObject*, PyObject*)?: sipkdecorepart6.cpp:16986: Warnung: ?bool KConfig::forceGlobal() const? ist veraltet (deklariert bei /usr/include/kconfig.h:353) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipakonadipart5.cpp: In function ?PyObject* meth_Akonadi_CollectionFetchJob_setResource(PyObject*, PyObject*)?: sipakonadipart5.cpp:16046: Warnung: ?void Akonadi::CollectionFetchJob::setResource(const QString&)? ist veraltet (deklariert bei /usr/include/akonadi/collectionfetchjob.h:106) sipakonadipart5.cpp: In function ?PyObject* meth_Akonadi_CollectionFetchJob_includeUnsubscribed(PyObject*, PyObject*)?: sipakonadipart5.cpp:16074: Warnung: ?void Akonadi::CollectionFetchJob::includeUnsubscribed(bool)? ist veraltet (deklariert bei /usr/include/akonadi/collectionfetchjob.h:112) sipakonadipart5.cpp: In function ?PyObject* meth_Akonadi_CollectionFetchJob_includeStatistics(PyObject*, PyObject*)?: sipakonadipart5.cpp:16101: Warnung: ?void Akonadi::CollectionFetchJob::includeStatistics(bool)? ist veraltet (deklariert bei /usr/include/akonadi/collectionfetchjob.h:120) sipakonadipart5.cpp: In member function ?virtual void sipAkonadi_CollectionComboBox::setContextMenuEnabled(bool)?: sipakonadipart5.cpp:26771: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) [ 7%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdecore.dir/sip/kdecore/sipkdecorepart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipAPIkdecore.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdecore/sipkdecorepart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdecorepart7.cpp: In function ?PyObject* meth_KCharsets_languageForEncoding(PyObject*, PyObject*)?: sipkdecorepart7.cpp:1496: Warnung: ?QString KCharsets::languageForEncoding(const QString&) const? ist veraltet (deklariert bei /usr/include/kcharsets.h:147) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip: In function ?int convertTo_QHash_1800_1800(PyObject*, void**, int*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip:950: Warnung: Variable ?state2? wird nicht verwendet /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip: In function ?PyObject* convertFrom_QHash_1800_1800(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip:898: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip:901: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden [ 8%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipakonadipart6.cpp: In function ?PyObject* meth_Akonadi_Collection_parent(PyObject*, PyObject*)?: sipakonadipart6.cpp:822: Warnung: ?qint64 Akonadi::Collection::parent() const? ist veraltet (deklariert bei /usr/include/akonadi/collection.h:166) sipakonadipart6.cpp: In function ?PyObject* meth_Akonadi_Collection_setParent(PyObject*, PyObject*)?: sipakonadipart6.cpp:848: Warnung: ?void Akonadi::Collection::setParent(const Akonadi::Collection&)? ist veraltet (deklariert bei /usr/include/akonadi/collection.h:178) sipakonadipart6.cpp:863: Warnung: ?void Akonadi::Collection::setParent(qint64)? ist veraltet (deklariert bei /usr/include/akonadi/collection.h:172) sipakonadipart6.cpp: In function ?PyObject* meth_Akonadi_Collection_parentRemoteId(PyObject*, PyObject*)?: sipakonadipart6.cpp:891: Warnung: ?QString Akonadi::Collection::parentRemoteId() const? ist veraltet (deklariert bei /usr/include/akonadi/collection.h:185) sipakonadipart6.cpp: In function ?PyObject* meth_Akonadi_Collection_setParentRemoteId(PyObject*, PyObject*)?: sipakonadipart6.cpp:918: Warnung: ?void Akonadi::Collection::setParentRemoteId(const QString&)? ist veraltet (deklariert bei /usr/include/akonadi/collection.h:191) Linking CXX shared library ../../lib/pykde/kdecore.so [ 8%] Built target python_module_PyKDE4_kdecore [ 8%] Generating sip/kdeui/sipkdeuipart0.cpp, sip/kdeui/sipkdeuipart1.cpp, sip/kdeui/sipkdeuipart2.cpp, sip/kdeui/sipkdeuipart3.cpp, sip/kdeui/sipkdeuipart4.cpp, sip/kdeui/sipkdeuipart5.cpp, sip/kdeui/sipkdeuipart6.cpp, sip/kdeui/sipkdeuipart7.cpp [ 8%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipAPIakonadi.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/akonadi/sipakonadipart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Linking CXX shared library ../../lib/pykde/akonadi.so [ 8%] Built target python_module_PyKDE4_akonadi [ 8%] Generating sip/khtml/sipkhtmlpart0.cpp, sip/khtml/sipkhtmlpart1.cpp, sip/khtml/sipkhtmlpart2.cpp, sip/khtml/sipkhtmlpart3.cpp, sip/khtml/sipkhtmlpart4.cpp, sip/khtml/sipkhtmlpart5.cpp, sip/khtml/sipkhtmlpart6.cpp, sip/khtml/sipkhtmlpart7.cpp Scanning dependencies of target python_module_PyKDE4_kdeui [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdeuipart0.cpp:3953: Warnung: unbenutzter Parameter ?a3? sipkdeuipart0.cpp: In function ?PyObject* func_UserIconSet(PyObject*, PyObject*)?: sipkdeuipart0.cpp:4947: Warnung: ?QIcon UserIconSet(const QString&)? ist veraltet (deklariert bei /usr/include/kiconloader.h:520) sipkdeuipart0.cpp:4947: Warnung: ?QIcon UserIconSet(const QString&)? ist veraltet (deklariert bei /usr/include/kiconloader.h:520) sipkdeuipart0.cpp: In function ?PyObject* func_MainBarIconSet(PyObject*, PyObject*)?: sipkdeuipart0.cpp:5011: Warnung: ?QIcon MainBarIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:507) sipkdeuipart0.cpp:5011: Warnung: ?QIcon MainBarIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:507) sipkdeuipart0.cpp: In function ?PyObject* func_SmallIconSet(PyObject*, PyObject*)?: sipkdeuipart0.cpp:5076: Warnung: ?QIcon SmallIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:493) sipkdeuipart0.cpp:5076: Warnung: ?QIcon SmallIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:493) sipkdeuipart0.cpp: In function ?PyObject* func_BarIconSet(PyObject*, PyObject*)?: sipkdeuipart0.cpp:5141: Warnung: ?QIcon BarIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:479) sipkdeuipart0.cpp:5141: Warnung: ?QIcon BarIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:479) sipkdeuipart0.cpp: In function ?PyObject* func_DesktopIconSet(PyObject*, PyObject*)?: sipkdeuipart0.cpp:5206: Warnung: ?QIcon DesktopIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:465) sipkdeuipart0.cpp:5206: Warnung: ?QIcon DesktopIconSet(const QString&, int)? ist veraltet (deklariert bei /usr/include/kiconloader.h:465) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdeui/kabstractwidgetjobtracker.sip: In function ?const sipTypeDef* sipSubClass_KAbstractWidgetJobTracker(void**)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdeui/kabstractwidgetjobtracker.sip:420: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip: In function ?PyObject* convertFrom_QSet_0100QString(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdecore/typedefs.sip:609: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden sipkdeuipart0.cpp: In member function ?virtual void sipSonnet_DictionaryComboBox::setContextMenuEnabled(bool)?: sipkdeuipart0.cpp:11918: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdeuipart1.cpp:16692: Warnung: ?berlauf in impliziter Konstantenkonvertierung sipkdeuipart1.cpp: In member function ?void sipKWidgetItemDelegate::sipProtect_paintWidgets(QPainter*, const QStyleOptionViewItem&, const QPersistentModelIndex&) const?: sipkdeuipart1.cpp:19838: Warnung: ?void KWidgetItemDelegate::paintWidgets(QPainter*, const QStyleOptionViewItem&, const QPersistentModelIndex&) const? ist veraltet (deklariert bei /usr/include/kwidgetitemdelegate.h:125) sipkdeuipart1.cpp: In member function ?virtual void sipKTreeWidgetSearchLine::setContextMenuEnabled(bool)?: sipkdeuipart1.cpp:36120: Warnung: ?virtual void KLineEdit::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/klineedit.h:224) sipkdeuipart1.cpp: In function ?PyObject* meth_KToolBarPopupAction_popupMenu(PyObject*, PyObject*)?: sipkdeuipart1.cpp:41400: Warnung: ?KMenu* KToolBarPopupAction::popupMenu() const? ist veraltet (deklariert bei /usr/include/ktoolbarpopupaction.h:79) sipkdeuipart1.cpp: In function ?PyObject* meth_KToolBar_setContextMenuEnabled(PyObject*, PyObject*)?: sipkdeuipart1.cpp:45264: Warnung: ?void KToolBar::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/ktoolbar.h:136) sipkdeuipart1.cpp: In function ?PyObject* meth_KToolBar_contextMenuEnabled(PyObject*, PyObject*)?: sipkdeuipart1.cpp:45292: Warnung: ?bool KToolBar::contextMenuEnabled() const? ist veraltet (deklariert bei /usr/include/ktoolbar.h:143) Scanning dependencies of target python_module_PyKDE4_khtml [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkhtmlpart0.cpp: In member function ?bool sipKHTMLPart::sipProtect_isLocalFileTemporary() const?: sipkhtmlpart0.cpp:9922: Warnung: ?bool KParts::ReadOnlyPart::isLocalFileTemporary() const? ist veraltet (deklariert bei /usr/include/kparts/part.h:686) sipkhtmlpart0.cpp: In member function ?void sipKHTMLPart::sipProtect_setLocalFileTemporary(bool)?: sipkhtmlpart0.cpp:9927: Warnung: ?void KParts::ReadOnlyPart::setLocalFileTemporary(bool)? ist veraltet (deklariert bei /usr/include/kparts/part.h:691) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLObjectElement_setHspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:20491: Warnung: ?void DOM::HTMLObjectElement::setHspace(const DOM::DOMString&)? ist veraltet (deklariert bei /usr/include/dom/html_object.h:427) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLObjectElement_hspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:20519: Warnung: ?DOM::DOMString DOM::HTMLObjectElement::hspace() const? ist veraltet (deklariert bei /usr/include/dom/html_object.h:422) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLObjectElement_setVspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:20857: Warnung: ?void DOM::HTMLObjectElement::setVspace(const DOM::DOMString&)? ist veraltet (deklariert bei /usr/include/dom/html_object.h:520) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLObjectElement_vspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:20885: Warnung: ?DOM::DOMString DOM::HTMLObjectElement::vspace() const? ist veraltet (deklariert bei /usr/include/dom/html_object.h:515) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLAppletElement_setHspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:21690: Warnung: ?void DOM::HTMLAppletElement::setHspace(const DOM::DOMString&)? ist veraltet (deklariert bei /usr/include/dom/html_object.h:175) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLAppletElement_hspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:21718: Warnung: ?DOM::DOMString DOM::HTMLAppletElement::hspace() const? ist veraltet (deklariert bei /usr/include/dom/html_object.h:170) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLAppletElement_setVspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:21894: Warnung: ?void DOM::HTMLAppletElement::setVspace(const DOM::DOMString&)? ist veraltet (deklariert bei /usr/include/dom/html_object.h:228) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLAppletElement_vspace(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:21922: Warnung: ?DOM::DOMString DOM::HTMLAppletElement::vspace() const? ist veraltet (deklariert bei /usr/include/dom/html_object.h:223) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLBaseFontElement_setSize(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:22850: Warnung: ?void DOM::HTMLBaseFontElement::setSize(const DOM::DOMString&)? ist veraltet (deklariert bei /usr/include/dom/html_misc.h:113) sipkhtmlpart0.cpp: In function ?PyObject* meth_DOM_HTMLBaseFontElement_size(PyObject*, PyObject*)?: sipkhtmlpart0.cpp:22878: Warnung: ?DOM::DOMString DOM::HTMLBaseFontElement::size() const? ist veraltet (deklariert bei /usr/include/dom/html_misc.h:108) [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkhtmlpart1.cpp: In function ?PyObject* meth_DOM_HTMLImageElement_setBorder(PyObject*, PyObject*)?: sipkhtmlpart1.cpp:5633: Warnung: ?void DOM::HTMLImageElement::setBorder(long int)? ist veraltet (deklariert bei /usr/include/dom/html_image.h:264) sipkhtmlpart1.cpp: In function ?PyObject* meth_DOM_HTMLImageElement_border(PyObject*, PyObject*)?: sipkhtmlpart1.cpp:5661: Warnung: ?long int DOM::HTMLImageElement::border() const? ist veraltet (deklariert bei /usr/include/dom/html_image.h:259) [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkhtmlpart2.cpp: In function ?PyObject* meth_DOM_HTMLInputElement_size(PyObject*, PyObject*)?: sipkhtmlpart2.cpp:7598: Warnung: ?DOM::DOMString DOM::HTMLInputElement::size() const? ist veraltet (deklariert bei /usr/include/dom/html_form.h:537) sipkhtmlpart2.cpp: In function ?PyObject* meth_DOM_HTMLInputElement_setSize(PyObject*, PyObject*)?: sipkhtmlpart2.cpp:7624: Warnung: ?void DOM::HTMLInputElement::setSize(const DOM::DOMString&)? ist veraltet (deklariert bei /usr/include/dom/html_form.h:542) sipkdeuipart2.cpp: In member function ?void sipKTabWidget::sipProtect_currentChanged(int)?: sipkdeuipart2.cpp:15103: Warnung: ?void KTabWidget::currentChanged(int)? ist veraltet (deklariert bei /usr/include/ktabwidget.h:351) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabWidget_hoverCloseButton(PyObject*, PyObject*)?: sipkdeuipart2.cpp:16371: Warnung: ?bool KTabWidget::hoverCloseButton() const? ist veraltet (deklariert bei /usr/include/ktabwidget.h:95) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabWidget_hoverCloseButtonDelayed(PyObject*, PyObject*)?: sipkdeuipart2.cpp:16398: Warnung: ?bool KTabWidget::hoverCloseButtonDelayed() const? ist veraltet (deklariert bei /usr/include/ktabwidget.h:103) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabWidget_isCloseButtonEnabled(PyObject*, PyObject*)?: sipkdeuipart2.cpp:16425: Warnung: ?bool KTabWidget::isCloseButtonEnabled() const? ist veraltet (deklariert bei /usr/include/ktabwidget.h:112) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabWidget_tabCloseActivatePrevious(PyObject*, PyObject*)?: sipkdeuipart2.cpp:16452: Warnung: ?bool KTabWidget::tabCloseActivatePrevious() const? ist veraltet (deklariert bei /usr/include/ktabwidget.h:120) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_setTabReorderingEnabled(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20098: Warnung: ?void KTabBar::setTabReorderingEnabled(bool)? ist veraltet (deklariert bei /usr/include/ktabbar.h:62) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_isTabReorderingEnabled(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20126: Warnung: ?bool KTabBar::isTabReorderingEnabled() const? ist veraltet (deklariert bei /usr/include/ktabbar.h:69) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_setHoverCloseButton(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20152: Warnung: ?void KTabBar::setHoverCloseButton(bool)? ist veraltet (deklariert bei /usr/include/ktabbar.h:79) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_hoverCloseButton(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20180: Warnung: ?bool KTabBar::hoverCloseButton() const? ist veraltet (deklariert bei /usr/include/ktabbar.h:82) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_setHoverCloseButtonDelayed(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20206: Warnung: ?void KTabBar::setHoverCloseButtonDelayed(bool)? ist veraltet (deklariert bei /usr/include/ktabbar.h:91) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_hoverCloseButtonDelayed(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20234: Warnung: ?bool KTabBar::hoverCloseButtonDelayed() const? ist veraltet (deklariert bei /usr/include/ktabbar.h:94) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_setCloseButtonEnabled(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20260: Warnung: ?void KTabBar::setCloseButtonEnabled(bool)? ist veraltet (deklariert bei /usr/include/ktabbar.h:105) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_isCloseButtonEnabled(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20288: Warnung: ?bool KTabBar::isCloseButtonEnabled() const? ist veraltet (deklariert bei /usr/include/ktabbar.h:114) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_setTabCloseActivatePrevious(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20314: Warnung: ?void KTabBar::setTabCloseActivatePrevious(bool)? ist veraltet (deklariert bei /usr/include/ktabbar.h:123) sipkdeuipart2.cpp: In function ?PyObject* meth_KTabBar_tabCloseActivatePrevious(PyObject*, PyObject*)?: sipkdeuipart2.cpp:20342: Warnung: ?bool KTabBar::tabCloseActivatePrevious() const? ist veraltet (deklariert bei /usr/include/ktabbar.h:131) sipkdeuipart2.cpp: In function ?PyObject* meth_KStandardAction_stdName(PyObject*, PyObject*)?: sipkdeuipart2.cpp:42111: Warnung: ?const char* KStandardAction::stdName(KStandardAction::StandardAction)? ist veraltet (deklariert bei /usr/include/kstandardaction.h:179) sipkdeuipart2.cpp:42111: Warnung: ?const char* KStandardAction::stdName(KStandardAction::StandardAction)? ist veraltet (deklariert bei /usr/include/kstandardaction.h:179) sipkdeuipart2.cpp: In function ?PyObject* meth_KShortcutWidget_setCheckActionList(PyObject*, PyObject*)?: sipkdeuipart2.cpp:51393: Warnung: ?void KShortcutWidget::setCheckActionList(const QList&)? ist veraltet (deklariert bei /usr/include/kshortcutwidget.h:66) sipkdeuipart2.cpp: In function ?PyObject* meth_KShortcutsEditor_exportConfiguration(PyObject*, PyObject*)?: sipkdeuipart2.cpp:55155: Warnung: ?void KShortcutsEditor::exportConfiguration(KConfig*) const? ist veraltet (deklariert bei /usr/include/kshortcutseditor.h:187) sipkdeuipart2.cpp: In function ?PyObject* meth_KShortcutsEditor_importConfiguration(PyObject*, PyObject*)?: sipkdeuipart2.cpp:55197: Warnung: ?void KShortcutsEditor::importConfiguration(KConfig*)? ist veraltet (deklariert bei /usr/include/kshortcutseditor.h:198) sipkdeuipart2.cpp: In function ?PyObject* meth_KRuler_setMinValue(PyObject*, PyObject*)?: sipkdeuipart2.cpp:71592: Warnung: ?void KRuler::setMinValue(int)? ist veraltet (deklariert bei /usr/include/kruler.h:162) sipkdeuipart2.cpp: In function ?PyObject* meth_KRuler_minValue(PyObject*, PyObject*)?: sipkdeuipart2.cpp:71620: Warnung: ?int KRuler::minValue() const? ist veraltet (deklariert bei /usr/include/kruler.h:167) sipkdeuipart2.cpp: In function ?PyObject* meth_KRuler_setMaxValue(PyObject*, PyObject*)?: sipkdeuipart2.cpp:71646: Warnung: ?void KRuler::setMaxValue(int)? ist veraltet (deklariert bei /usr/include/kruler.h:175) sipkdeuipart2.cpp: In function ?PyObject* meth_KRuler_maxValue(PyObject*, PyObject*)?: sipkdeuipart2.cpp:71674: Warnung: ?int KRuler::maxValue() const? ist veraltet (deklariert bei /usr/include/kruler.h:180) [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 10%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkhtmlpart4.cpp: In function ?PyObject* meth_DOM_Node_toHTML(PyObject*, PyObject*)?: sipkhtmlpart4.cpp:7908: Warnung: ?QString DOM::Node::toHTML()? ist veraltet (deklariert bei /usr/include/dom/dom_node.h:930) sipkhtmlpart4.cpp: In function ?PyObject* meth_DOM_Node_getCursor(PyObject*, PyObject*)?: sipkhtmlpart4.cpp:7963: Warnung: ?void DOM::Node::getCursor(int, int&, int&, int&)? ist veraltet (deklariert bei /usr/include/dom/dom_node.h:935) [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /usr/include/dom/dom2_traversal.h:195: Warnung: ?virtual DOM::NodeFilter& DOM::NodeFilter::operator=(const DOM::NodeFilter&)? war versteckt sipkhtmlpart5.cpp:1564: Warnung: von ?sipDOM_NodeFilter& sipDOM_NodeFilter::operator=(const sipDOM_NodeFilter&)? [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_khtml.dir/sip/khtml/sipkhtmlpart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipAPIkhtml.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/khtml/sipkhtmlpart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Linking CXX shared library ../../lib/pykde/khtml.so [ 11%] Built target python_module_PyKDE4_khtml [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdeuipart3.cpp: In member function ?virtual void sipKRestrictedLine::setContextMenuEnabled(bool)?: sipkdeuipart3.cpp:14153: Warnung: ?virtual void KLineEdit::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/klineedit.h:224) sipkdeuipart3.cpp: In function ?PyObject* meth_KPushButton_setIcon(PyObject*, PyObject*)?: sipkdeuipart3.cpp:26059: Warnung: ?void KPushButton::setIcon(const QIcon&)? ist veraltet (deklariert bei /usr/include/kpushbutton.h:115) [ 11%] Generating sip/kio/sipkiopart0.cpp, sip/kio/sipkiopart1.cpp, sip/kio/sipkiopart2.cpp, sip/kio/sipkiopart3.cpp, sip/kio/sipkiopart4.cpp, sip/kio/sipkiopart5.cpp, sip/kio/sipkiopart6.cpp, sip/kio/sipkiopart7.cpp [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdeuipart4.cpp: In constructor ?sipKDoubleNumInput::sipKDoubleNumInput(KNumInput*, double, double, double, QWidget*, double, int)?: sipkdeuipart4.cpp:356: Warnung: ?KDoubleNumInput::KDoubleNumInput(KNumInput*, double, double, double, QWidget*, double, int)? ist veraltet (deklariert bei /usr/include/knuminput.h:507) sipkdeuipart4.cpp: In function ?PyObject* meth_KDoubleNumInput_setPrecision(PyObject*, PyObject*)?: sipkdeuipart4.cpp:3202: Warnung: ?void KDoubleNumInput::setPrecision(int)? ist veraltet (deklariert bei /usr/include/knuminput.h:586) sipkdeuipart4.cpp: In constructor ?sipKIntNumInput::sipKIntNumInput(KNumInput*, int, QWidget*, int)?: sipkdeuipart4.cpp:4215: Warnung: ?KIntNumInput::KIntNumInput(KNumInput*, int, QWidget*, int)? ist veraltet (deklariert bei /usr/include/knuminput.h:221) sipkdeuipart4.cpp: In function ?PyObject* meth_KIntNumInput_setRange(PyObject*, PyObject*)?: sipkdeuipart4.cpp:6867: Warnung: ?void KIntNumInput::setRange(int, int, int, bool)? ist veraltet (deklariert bei /usr/include/knuminput.h:274) sipkdeuipart4.cpp: In constructor ?sipKNumInput::sipKNumInput(QWidget*, KNumInput*)?: sipkdeuipart4.cpp:8005: Warnung: ?KNumInput::KNumInput(QWidget*, KNumInput*)? ist veraltet (deklariert bei /usr/include/knuminput.h:61) sipkdeuipart4.cpp: In member function ?virtual void sipKListWidgetSearchLine::setContextMenuEnabled(bool)?: sipkdeuipart4.cpp:42053: Warnung: ?virtual void KLineEdit::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/klineedit.h:224) sipkdeuipart4.cpp: In member function ?virtual void sipKLineEdit::setContextMenuEnabled(bool)?: sipkdeuipart4.cpp:45814: Warnung: ?virtual void KLineEdit::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/klineedit.h:224) sipkdeuipart4.cpp: In function ?PyObject* meth_KLineEdit_setContextMenuEnabled(PyObject*, PyObject*)?: sipkdeuipart4.cpp:48315: Warnung: ?virtual void KLineEdit::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/klineedit.h:224) sipkdeuipart4.cpp:48315: Warnung: ?virtual void KLineEdit::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/klineedit.h:224) sipkdeuipart4.cpp: In function ?PyObject* meth_KLineEdit_isContextMenuEnabled(PyObject*, PyObject*)?: sipkdeuipart4.cpp:48343: Warnung: ?bool KLineEdit::isContextMenuEnabled() const? ist veraltet (deklariert bei /usr/include/klineedit.h:230) sipkdeuipart4.cpp: In function ?PyObject* meth_KKeySequenceWidget_setCheckActionList(PyObject*, PyObject*)?: sipkdeuipart4.cpp:60865: Warnung: ?void KKeySequenceWidget::setCheckActionList(const QList&)? ist veraltet (deklariert bei /usr/include/kkeysequencewidget.h:229) Scanning dependencies of target python_module_PyKDE4_kio [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart0.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip: In function ?const sipTypeDef* sipSubClass_KAbstractFileModule(void**)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:165: Warnung: ?KCrashBookmarkImporter? ist veraltet (deklariert bei /usr/include/kbookmarkimporter_crash.h:36) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:181: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:323: Warnung: ?PasswordDialog? ist veraltet (deklariert bei /usr/include/kio/passworddialog.h:38) sipkiopart0.cpp: In function ?PyObject* meth_KIO_SlaveInterface_connection(PyObject*, PyObject*)?: sipkiopart0.cpp:11749: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart0.cpp: In function ?PyObject* meth_KIO_SlaveInterface_setConnection(PyObject*, PyObject*)?: sipkiopart0.cpp:11853: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart1.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart1.cpp: In function ?void* cast_KIO_PasswordDialog(void*, const sipTypeDef*)?: sipkiopart1.cpp:8468: Warnung: ?PasswordDialog? ist veraltet (deklariert bei /usr/include/kio/passworddialog.h:38) sipkiopart1.cpp: In function ?void release_KIO_PasswordDialog(void*, int)?: sipkiopart1.cpp:8484: Warnung: ?PasswordDialog? ist veraltet (deklariert bei /usr/include/kio/passworddialog.h:38) sipkiopart1.cpp: In function ?PyObject* meth_KIO_NetAccess_copy(PyObject*, PyObject*)?: sipkiopart1.cpp:8844: Warnung: ?static bool KIO::NetAccess::copy(const KUrl&, const KUrl&, QWidget*)? ist veraltet (deklariert bei /usr/include/kio/netaccess.h:194) sipkiopart1.cpp: In function ?PyObject* meth_KIO_NetAccess_move(PyObject*, PyObject*)?: sipkiopart1.cpp:8919: Warnung: ?static bool KIO::NetAccess::move(const KUrl&, const KUrl&, QWidget*)? ist veraltet (deklariert bei /usr/include/kio/netaccess.h:229) sipkiopart1.cpp:8936: Warnung: ?static bool KIO::NetAccess::move(const KUrl::List&, const KUrl&, QWidget*)? ist veraltet (deklariert bei /usr/include/kio/netaccess.h:236) sipkiopart1.cpp: In function ?PyObject* meth_KIO_NetAccess_exists(PyObject*, PyObject*)?: sipkiopart1.cpp:8965: Warnung: ?static bool KIO::NetAccess::exists(const KUrl&, bool, QWidget*)? ist veraltet (deklariert bei /usr/include/kio/netaccess.h:253) sipkiopart1.cpp: In function ?PyObject* meth_KUrlRequester_setPath(PyObject*, PyObject*)?: sipkiopart1.cpp:22059: Warnung: ?void KUrlRequester::setPath(const QString&)? ist veraltet (deklariert bei /usr/include/kurlrequester.h:233) sipkiopart1.cpp: In member function ?virtual void sipKUrlComboBox::setContextMenuEnabled(bool)?: sipkiopart1.cpp:26956: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) /usr/include/kshellcompletion.h: At global scope: /usr/include/kshellcompletion.h:63: Warnung: ?virtual void KShellCompletion::postProcessMatches(KCompletionMatches*) const? war versteckt sipkiopart1.cpp:35933: Warnung: von ?virtual void sipKShellCompletion::postProcessMatches(QStringList*) const? /usr/include/kurlcompletion.h:172: Warnung: ?virtual void KUrlCompletion::postProcessMatches(KCompletionMatches*) const? war versteckt sipkiopart1.cpp:36990: Warnung: von ?virtual void sipKUrlCompletion::postProcessMatches(QStringList*) const? [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdeuipart5.cpp: In member function ?virtual void sipKHistoryComboBox::setContextMenuEnabled(bool)?: sipkdeuipart5.cpp:3798: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) sipkdeuipart5.cpp: In function ?PyObject* meth_KGuiItem_hasIconSet(PyObject*, PyObject*)?: sipkdeuipart5.cpp:11257: Warnung: ?bool KGuiItem::hasIconSet() const? ist veraltet (deklariert bei /usr/include/kguiitem.h:73) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalSettings_contextMenuKey(PyObject*, PyObject*)?: sipkdeuipart5.cpp:13454: Warnung: ?static int KGlobalSettings::contextMenuKey()? ist veraltet (deklariert bei /usr/include/kglobalsettings.h:158) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_promptStealShortcutSystemwide(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15035: Warnung: ?static bool KGlobalAccel::promptStealShortcutSystemwide(QWidget*, const QStringList&, const QKeySequence&)? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:222) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_isEnabled(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15064: Warnung: ?bool KGlobalAccel::isEnabled() const? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:168) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_setEnabled(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15090: Warnung: ?void KGlobalAccel::setEnabled(bool)? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:175) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_overrideMainComponentData(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15117: Warnung: ?void KGlobalAccel::overrideMainComponentData(const KComponentData&)? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:193) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_allMainComponents(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15145: Warnung: ?QList KGlobalAccel::allMainComponents()? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:201) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_allActionsForComponent(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15174: Warnung: ?QList KGlobalAccel::allActionsForComponent(const QStringList&)? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:208) sipkdeuipart5.cpp: In function ?PyObject* meth_KGlobalAccel_findActionNameSystemwide(PyObject*, PyObject*)?: sipkdeuipart5.cpp:15203: Warnung: ?static QStringList KGlobalAccel::findActionNameSystemwide(const QKeySequence&)? ist veraltet (deklariert bei /usr/include/kglobalaccel.h:215) sipkdeuipart5.cpp: In member function ?virtual void sipKFontComboBox::setContextMenuEnabled(bool)?: sipkdeuipart5.cpp:24391: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) sipkdeuipart5.cpp: In constructor ?sipKEditListBox::sipKEditListBox(QWidget*, const char*, bool, QFlags)?: sipkdeuipart5.cpp:49502: Warnung: ?KEditListBox::KEditListBox(QWidget*, const char*, bool, QFlags)? ist veraltet (deklariert bei /usr/include/keditlistbox.h:124) sipkdeuipart5.cpp: In constructor ?sipKEditListBox::sipKEditListBox(const QString&, QWidget*, const char*, bool, QFlags)?: sipkdeuipart5.cpp:49507: Warnung: ?KEditListBox::KEditListBox(const QString&, QWidget*, const char*, bool, QFlags)? ist veraltet (deklariert bei /usr/include/keditlistbox.h:134) [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart2.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart2.cpp: In member function ?QTimer& sipKRun::sipProtect_timer()?: sipkiopart2.cpp:776: Warnung: ?QTimer& KRun::timer()? ist veraltet (deklariert bei /usr/include/krun.h:492) sipkiopart2.cpp: In member function ?void sipKRun::sipProtect_setDoScanFile(bool)?: sipkiopart2.cpp:781: Warnung: ?void KRun::setDoScanFile(bool)? ist veraltet (deklariert bei /usr/include/krun.h:498) sipkiopart2.cpp: In member function ?bool sipKRun::sipProtect_doScanFile() const?: sipkiopart2.cpp:786: Warnung: ?bool KRun::doScanFile() const? ist veraltet (deklariert bei /usr/include/krun.h:504) sipkiopart2.cpp: In member function ?void sipKRun::sipProtect_setIsDirecory(bool)?: sipkiopart2.cpp:791: Warnung: ?void KRun::setIsDirecory(bool)? ist veraltet (deklariert bei /usr/include/krun.h:510) sipkiopart2.cpp: In member function ?void sipKRun::sipProtect_setInitializeNextAction(bool)?: sipkiopart2.cpp:801: Warnung: ?void KRun::setInitializeNextAction(bool)? ist veraltet (deklariert bei /usr/include/krun.h:520) sipkiopart2.cpp: In member function ?bool sipKRun::sipProtect_initializeNextAction() const?: sipkiopart2.cpp:806: Warnung: ?bool KRun::initializeNextAction() const? ist veraltet (deklariert bei /usr/include/krun.h:525) sipkiopart2.cpp: In function ?PyObject* meth_KRun_shellQuote(PyObject*, PyObject*)?: sipkiopart2.cpp:1502: Warnung: ?static void KRun::shellQuote(QString&)? ist veraltet (deklariert bei /usr/include/krun.h:316) [ 11%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdeui/kcompletion.sip: In function ?PyObject* convertFrom_QMap_0100KCompletionBase_KeyBindingType_0100KShortcut(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kdeui/kcompletion.sip:185: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden /usr/include/kcompletion.h: At global scope: /usr/include/kcompletion.h:531: Warnung: ?virtual void KCompletion::postProcessMatches(KCompletionMatches*) const? war versteckt sipkdeuipart6.cpp:36875: Warnung: von ?virtual void sipKCompletion::postProcessMatches(QStringList*) const? sipkdeuipart6.cpp: In member function ?virtual void sipKComboBox::setContextMenuEnabled(bool)?: sipkdeuipart6.cpp:38869: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) sipkdeuipart6.cpp: In function ?PyObject* meth_KComboBox_insertURL(PyObject*, PyObject*)?: sipkdeuipart6.cpp:41521: Warnung: ?void KComboBox::insertURL(const KUrl&, int)? ist veraltet (deklariert bei /usr/include/kcombobox.h:184) sipkdeuipart6.cpp:41538: Warnung: ?void KComboBox::insertURL(const QPixmap&, const KUrl&, int)? ist veraltet (deklariert bei /usr/include/kcombobox.h:186) sipkdeuipart6.cpp: In function ?PyObject* meth_KComboBox_changeURL(PyObject*, PyObject*)?: sipkdeuipart6.cpp:41566: Warnung: ?void KComboBox::changeURL(const KUrl&, int)? ist veraltet (deklariert bei /usr/include/kcombobox.h:188) sipkdeuipart6.cpp:41583: Warnung: ?void KComboBox::changeURL(const QPixmap&, const KUrl&, int)? ist veraltet (deklariert bei /usr/include/kcombobox.h:190) sipkdeuipart6.cpp: In function ?PyObject* meth_KComboBox_setContextMenuEnabled(PyObject*, PyObject*)?: sipkdeuipart6.cpp:41853: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) sipkdeuipart6.cpp:41853: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) [ 12%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart3.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart3.cpp: In function ?PyObject* meth_KPropertiesDialogPlugin_isDesktopFile(PyObject*, PyObject*)?: sipkiopart3.cpp:22217: Warnung: ?static bool KPropertiesDialogPlugin::isDesktopFile(const KFileItem&)? ist veraltet (deklariert bei /usr/include/kpropertiesdialog.h:371) sipkiopart3.cpp: In function ?PyObject* meth_KFileItem_time(PyObject*, PyObject*)?: sipkiopart3.cpp:37433: Warnung: ?time_t KFileItem::time(unsigned int) const? ist veraltet (deklariert bei /usr/include/kfileitem.h:304) sipkiopart3.cpp: In function ?PyObject* meth_KFileItem_timeString(PyObject*, PyObject*)?: sipkiopart3.cpp:37477: Warnung: ?QString KFileItem::timeString(unsigned int) const? ist veraltet (deklariert bei /usr/include/kfileitem.h:314) sipkiopart3.cpp: In function ?PyObject* meth_KFileItem_acceptsDrops(PyObject*, PyObject*)?: sipkiopart3.cpp:37859: Warnung: ?bool KFileItem::acceptsDrops() const? ist veraltet (deklariert bei /usr/include/kfileitem.h:428) sipkiopart3.cpp: In function ?PyObject* meth_KFileItem_assign(PyObject*, PyObject*)?: sipkiopart3.cpp:38129: Warnung: ?void KFileItem::assign(const KFileItem&)? ist veraltet (deklariert bei /usr/include/kfileitem.h:562) sipkiopart3.cpp: In function ?PyObject* meth_KFileItem_setUDSEntry(PyObject*, PyObject*)?: sipkiopart3.cpp:38159: Warnung: ?void KFileItem::setUDSEntry(const KIO::UDSEntry&, const KUrl&, bool, bool)? ist veraltet (deklariert bei /usr/include/kfileitem.h:583) sipkiopart3.cpp: In member function ?virtual void sipKFileFilterCombo::setContextMenuEnabled(bool)?: sipkiopart3.cpp:39048: Warnung: ?virtual void KComboBox::setContextMenuEnabled(bool)? ist veraltet (deklariert bei /usr/include/kcombobox.h:291) [ 12%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart4.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart4.cpp: In constructor ?sipKDiskFreeSpace::sipKDiskFreeSpace(QObject*)?: sipkiopart4.cpp:9894: Warnung: ?KDiskFreeSpace::KDiskFreeSpace(QObject*)? ist veraltet (deklariert bei /usr/include/kdiskfreespace.h:43) sipkiopart4.cpp: In function ?PyObject* meth_KDiskFreeSpace_readDF(PyObject*, PyObject*)?: sipkiopart4.cpp:10272: Warnung: ?bool KDiskFreeSpace::readDF(const QString&)? ist veraltet (deklariert bei /usr/include/kdiskfreespace.h:63) sipkiopart4.cpp: In function ?PyObject* meth_KDiskFreeSpace_findUsageInfo(PyObject*, PyObject*)?: sipkiopart4.cpp:10301: Warnung: ?static KDiskFreeSpace* KDiskFreeSpace::findUsageInfo(const QString&)? ist veraltet (deklariert bei /usr/include/kdiskfreespace.h:72) sipkiopart4.cpp: In function ?PyObject* meth_KDirModel_indexForItem(PyObject*, PyObject*)?: sipkiopart4.cpp:26464: Warnung: ?QModelIndex KDirModel::indexForItem(const KFileItem*) const? ist veraltet (deklariert bei /usr/include/kdirmodel.h:78) sipkiopart4.cpp: In function ?PyObject* meth_KDataToolInfo_icon(PyObject*, PyObject*)?: sipkiopart4.cpp:34458: Warnung: ?QPixmap KDataToolInfo::icon() const? ist veraltet (deklariert bei /usr/include/kdatatool.h:106) sipkiopart4.cpp: In function ?PyObject* meth_KDataToolInfo_miniIcon(PyObject*, PyObject*)?: sipkiopart4.cpp:34485: Warnung: ?QPixmap KDataToolInfo::miniIcon() const? ist veraltet (deklariert bei /usr/include/kdatatool.h:112) [ 13%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kdeui.dir/sip/kdeui/sipkdeuipart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipAPIkdeui.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kdeui/sipkdeuipart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkdeuipart7.cpp: In constructor ?sipKCharSelect::sipKCharSelect(QWidget*, QFlags)?: sipkdeuipart7.cpp:4627: Warnung: ?KCharSelect::KCharSelect(QWidget*, QFlags)? ist veraltet (deklariert bei /usr/include/kcharselect.h:110) sipkdeuipart7.cpp: In member function ?virtual void sipKCategorizedView::rowsInsertedArtifficial(const QModelIndex&, int, int)?: sipkdeuipart7.cpp:9484: Warnung: ?virtual void KCategorizedView::rowsInsertedArtifficial(const QModelIndex&, int, int)? ist veraltet (deklariert bei /usr/include/kcategorizedview.h:283) sipkdeuipart7.cpp: In member function ?virtual void sipKCategorizedView::rowsRemoved(const QModelIndex&, int, int)?: sipkdeuipart7.cpp:9502: Warnung: ?virtual void KCategorizedView::rowsRemoved(const QModelIndex&, int, int)? ist veraltet (deklariert bei /usr/include/kcategorizedview.h:291) sipkdeuipart7.cpp: In member function ?void sipKCategorizedView::sipProtectVirt_rowsInsertedArtifficial(bool, const QModelIndex&, int, int)?: sipkdeuipart7.cpp:11163: Warnung: ?virtual void KCategorizedView::rowsInsertedArtifficial(const QModelIndex&, int, int)? ist veraltet (deklariert bei /usr/include/kcategorizedview.h:283) sipkdeuipart7.cpp: In member function ?void sipKCategorizedView::sipProtectVirt_rowsRemoved(bool, const QModelIndex&, int, int)?: sipkdeuipart7.cpp:11168: Warnung: ?virtual void KCategorizedView::rowsRemoved(const QModelIndex&, int, int)? ist veraltet (deklariert bei /usr/include/kcategorizedview.h:291) sipkdeuipart7.cpp: In function ?PyObject* meth_KCategorizedSortFilterProxyModel_naturalCompare(PyObject*, PyObject*)?: sipkdeuipart7.cpp:16763: Warnung: ?static int KCategorizedSortFilterProxyModel::naturalCompare(const QString&, const QString&)? ist veraltet (deklariert bei /usr/include/kcategorizedsortfilterproxymodel.h:114) sipkdeuipart7.cpp: In function ?PyObject* meth_KArrowButton_sizeHint(PyObject*, PyObject*)?: sipkdeuipart7.cpp:36442: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?PyObject* meth_KArrowButton_arrowType(PyObject*, PyObject*)?: sipkdeuipart7.cpp:36469: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?PyObject* meth_KArrowButton_arrowTp(PyObject*, PyObject*)?: sipkdeuipart7.cpp:36496: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?PyObject* meth_KArrowButton_setArrowTp(PyObject*, PyObject*)?: sipkdeuipart7.cpp:36524: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?PyObject* meth_KArrowButton_setArrowType(PyObject*, PyObject*)?: sipkdeuipart7.cpp:36551: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?void* cast_KArrowButton(void*, const sipTypeDef*)?: sipkdeuipart7.cpp:36608: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?void release_KArrowButton(void*, int)?: sipkdeuipart7.cpp:36624: Warnung: ?KArrowButton? ist veraltet (deklariert bei /usr/include/karrowbutton.h:42) sipkdeuipart7.cpp: In function ?PyObject* meth_KApplication_tempSaveName(PyObject*, PyObject*)?: sipkdeuipart7.cpp:37721: Warnung: ?static QString KApplication::tempSaveName(const QString&)? ist veraltet (deklariert bei /usr/include/kapplication.h:258) sipkdeuipart7.cpp: In function ?PyObject* meth_KActionMenu_remove(PyObject*, PyObject*)?: sipkdeuipart7.cpp:45935: Warnung: ?void KActionMenu::remove(KAction*)? ist veraltet (deklariert bei /usr/include/kactionmenu.h:62) sipkdeuipart7.cpp: In function ?PyObject* meth_KActionMenu_popupMenu(PyObject*, PyObject*)?: sipkdeuipart7.cpp:46100: Warnung: ?KMenu* KActionMenu::popupMenu()? ist veraltet (deklariert bei /usr/include/kactionmenu.h:75) sipkdeuipart7.cpp: In function ?PyObject* meth_KAction_globalShortcutAllowed(PyObject*, PyObject*)?: sipkdeuipart7.cpp:50426: Warnung: ?bool KAction::globalShortcutAllowed() const? ist veraltet (deklariert bei /usr/include/kaction.h:428) sipkdeuipart7.cpp: In function ?PyObject* meth_KAction_setGlobalShortcutAllowed(PyObject*, PyObject*)?: sipkdeuipart7.cpp:50453: Warnung: ?void KAction::setGlobalShortcutAllowed(bool, KAction::GlobalShortcutLoading)? ist veraltet (deklariert bei /usr/include/kaction.h:438) [ 13%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart5.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart5.cpp: In function ?PyObject* meth_KCrashBookmarkImporter_parseCrashBookmarks(PyObject*, PyObject*)?: sipkiopart5.cpp:12841: Warnung: ?KCrashBookmarkImporter? ist veraltet (deklariert bei /usr/include/kbookmarkimporter_crash.h:36) sipkiopart5.cpp: In function ?void* cast_KCrashBookmarkImporter(void*, const sipTypeDef*)?: sipkiopart5.cpp:12895: Warnung: ?KCrashBookmarkImporter? ist veraltet (deklariert bei /usr/include/kbookmarkimporter_crash.h:36) sipkiopart5.cpp: In function ?void release_KCrashBookmarkImporter(void*, int)?: sipkiopart5.cpp:12911: Warnung: ?KCrashBookmarkImporter? ist veraltet (deklariert bei /usr/include/kbookmarkimporter_crash.h:36) sipkiopart5.cpp: In function ?PyObject* meth_KBookmarkGroup_moveItem(PyObject*, PyObject*)?: sipkiopart5.cpp:20115: Warnung: ?bool KBookmarkGroup::moveItem(const KBookmark&, const KBookmark&)? ist veraltet (deklariert bei /usr/include/kbookmark.h:421) [ 13%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart6.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart6.cpp: In function ?PyObject* meth_KBookmark_List_fromMimeData(PyObject*, PyObject*)?: sipkiopart6.cpp:116: Warnung: ?static KBookmark::List KBookmark::List::fromMimeData(const QMimeData*)? ist veraltet (deklariert bei /usr/include/kbookmark.h:78) sipkiopart6.cpp: In function ?PyObject* meth_KIO_StatJob_setSide(PyObject*, PyObject*)?: sipkiopart6.cpp:13562: Warnung: ?void KIO::StatJob::setSide(bool)? ist veraltet (deklariert bei /usr/include/kio/jobclasses.h:467) [ 13%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kio.dir/sip/kio/sipkiopart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipAPIkio.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/kio/kabstractfilemodule.sip:28, from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kio/sipkiopart7.cpp:7: /usr/include/kio/connection.h:176: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) /usr/include/kio/connection.h:177: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) Linking CXX shared library ../../lib/pykde/kdeui.so [ 13%] Built target python_module_PyKDE4_kdeui [ 14%] Generating sip/knewstuff/sipknewstuffpart0.cpp, sip/knewstuff/sipknewstuffpart1.cpp, sip/knewstuff/sipknewstuffpart2.cpp, sip/knewstuff/sipknewstuffpart3.cpp, sip/knewstuff/sipknewstuffpart4.cpp, sip/knewstuff/sipknewstuffpart5.cpp, sip/knewstuff/sipknewstuffpart6.cpp, sip/knewstuff/sipknewstuffpart7.cpp sipkiopart7.cpp: In function ?PyObject* meth_KIO_TransferJob_setReportDataSent(PyObject*, PyObject*)?: sipkiopart7.cpp:7460: Warnung: ?void KIO::TransferJob::setReportDataSent(bool)? ist veraltet (deklariert bei /usr/include/kio/jobclasses.h:596) sipkiopart7.cpp: In function ?PyObject* meth_KIO_TransferJob_reportDataSent(PyObject*, PyObject*)?: sipkiopart7.cpp:7488: Warnung: ?bool KIO::TransferJob::reportDataSent() const? ist veraltet (deklariert bei /usr/include/kio/jobclasses.h:605) sipkiopart7.cpp: In function ?PyObject* meth_KIO_ConnectionServer_nextPendingConnection(PyObject*, PyObject*)?: sipkiopart7.cpp:9024: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_ConnectionServer_setNextPendingConnection(PyObject*, PyObject*)?: sipkiopart7.cpp:9047: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_connectToRemote(PyObject*, PyObject*)?: sipkiopart7.cpp:9673: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_close(PyObject*, PyObject*)?: sipkiopart7.cpp:9700: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_errorString(PyObject*, PyObject*)?: sipkiopart7.cpp:9726: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_isConnected(PyObject*, PyObject*)?: sipkiopart7.cpp:9753: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_inited(PyObject*, PyObject*)?: sipkiopart7.cpp:9780: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_send(PyObject*, PyObject*)?: sipkiopart7.cpp:9811: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_sendnow(PyObject*, PyObject*)?: sipkiopart7.cpp:9842: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_hasTaskAvailable(PyObject*, PyObject*)?: sipkiopart7.cpp:9870: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_waitForIncomingTask(PyObject*, PyObject*)?: sipkiopart7.cpp:9898: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_suspend(PyObject*, PyObject*)?: sipkiopart7.cpp:9925: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_resume(PyObject*, PyObject*)?: sipkiopart7.cpp:9951: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Connection_suspended(PyObject*, PyObject*)?: sipkiopart7.cpp:9977: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?void* cast_KIO_Connection(void*, const sipTypeDef*)?: sipkiopart7.cpp:10007: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?void release_KIO_Connection(void*, int)?: sipkiopart7.cpp:10023: Warnung: ?Connection? ist veraltet (deklariert bei /usr/include/kio/connection.h:49) sipkiopart7.cpp: In function ?PyObject* meth_KIO_Job_showErrorDialog(PyObject*, PyObject*)?: sipkiopart7.cpp:11678: Warnung: ?void KIO::Job::showErrorDialog(QWidget*)? ist veraltet (deklariert bei /usr/include/kio/jobclasses.h:178) sipkiopart7.cpp: In function ?PyObject* meth_KIO_stat(PyObject*, PyObject*)?: sipkiopart7.cpp:14942: Warnung: ?KIO::StatJob* KIO::stat(const KUrl&, bool, short int, KIO::JobFlags)? ist veraltet (deklariert bei /usr/include/kio/job.h:228) sipkiopart7.cpp: In function ?PyObject* meth_KIO_calculateRemaining(PyObject*, PyObject*)?: sipkiopart7.cpp:15554: Warnung: ?QTime KIO::calculateRemaining(KIO::filesize_t, KIO::filesize_t, KIO::filesize_t)? ist veraltet (deklariert bei /usr/include/kio/global.h:111) sipkiopart7.cpp:15554: Warnung: ?QTime KIO::calculateRemaining(KIO::filesize_t, KIO::filesize_t, KIO::filesize_t)? ist veraltet (deklariert bei /usr/include/kio/global.h:111) Linking CXX shared library ../../lib/pykde/kio.so [ 14%] Built target python_module_PyKDE4_kio [ 14%] Generating sip/kparts/sipkpartspart0.cpp, sip/kparts/sipkpartspart1.cpp, sip/kparts/sipkpartspart2.cpp, sip/kparts/sipkpartspart3.cpp, sip/kparts/sipkpartspart4.cpp, sip/kparts/sipkpartspart5.cpp, sip/kparts/sipkpartspart6.cpp, sip/kparts/sipkpartspart7.cpp Scanning dependencies of target python_module_PyKDE4_knewstuff [ 14%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipknewstuffpart4.cpp: In function ?PyObject* meth_KNS_Button_setProviderList(PyObject*, PyObject*)?: sipknewstuffpart4.cpp:3037: Warnung: ?Button? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffbutton.h:40) sipknewstuffpart4.cpp: In function ?PyObject* meth_KNS_Button_setResourceType(PyObject*, PyObject*)?: sipknewstuffpart4.cpp:3066: Warnung: ?Button? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffbutton.h:40) sipknewstuffpart4.cpp: In function ?PyObject* meth_KNS_Button_setButtonText(PyObject*, PyObject*)?: sipknewstuffpart4.cpp:3095: Warnung: ?Button? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffbutton.h:40) sipknewstuffpart4.cpp: In function ?void* cast_KNS_Button(void*, const sipTypeDef*)?: sipknewstuffpart4.cpp:3151: Warnung: ?Button? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffbutton.h:40) sipknewstuffpart4.cpp: In function ?void release_KNS_Button(void*, int)?: sipknewstuffpart4.cpp:3167: Warnung: ?Button? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffbutton.h:40) [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_knewstuff.dir/sip/knewstuff/sipknewstuffpart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipAPIknewstuff.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/knewstuff/sipknewstuffpart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In file included from /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/knewstuff/engine.sip:27: /usr/include/knewstuff2/engine.h:159: Warnung: ?Engine? ist veraltet /usr/include/knewstuff2/engine.h:159: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) /usr/include/knewstuff2/engine.h:159: Warnung: ?Engine? ist veraltet sipknewstuffpart7.cpp: In function ?PyObject* meth_KNS_Engine_downloadDialogModal(PyObject*, PyObject*)?: sipknewstuffpart7.cpp:37: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?PyObject* meth_KNS_Engine_uploadDialogModal(PyObject*, PyObject*)?: sipknewstuffpart7.cpp:91: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?PyObject* meth_KNS_Engine_downloadDialog(PyObject*, PyObject*)?: sipknewstuffpart7.cpp:148: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp:165: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?PyObject* meth_KNS_Engine_uploadDialog(PyObject*, PyObject*)?: sipknewstuffpart7.cpp:194: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?PyObject* meth_KNS_Engine_init(PyObject*, PyObject*)?: sipknewstuffpart7.cpp:223: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?void release_KNS_Engine(void*, int)?: sipknewstuffpart7.cpp:262: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?void* init_KNS_Engine(sipSimpleWrapper*, PyObject*, PyObject*, PyObject**, PyObject**, PyObject**)?: sipknewstuffpart7.cpp:281: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp:289: Warnung: ?Engine? ist veraltet (deklariert bei /usr/include/knewstuff2/engine.h:44) sipknewstuffpart7.cpp: In function ?PyObject* meth_KNS_standardAction(PyObject*, PyObject*)?: sipknewstuffpart7.cpp:396: Warnung: ?KAction* KNS::standardAction(const QString&, const QObject*, const char*, KActionCollection*, const char*)? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffaction.h:44) sipknewstuffpart7.cpp:396: Warnung: ?KAction* KNS::standardAction(const QString&, const QObject*, const char*, KActionCollection*, const char*)? ist veraltet (deklariert bei /usr/include/knewstuff2/ui/knewstuffaction.h:44) Linking CXX shared library ../../lib/pykde/knewstuff.so [ 15%] Built target python_module_PyKDE4_knewstuff [ 15%] Generating sip/ktexteditor/sipktexteditorpart0.cpp, sip/ktexteditor/sipktexteditorpart1.cpp, sip/ktexteditor/sipktexteditorpart2.cpp, sip/ktexteditor/sipktexteditorpart3.cpp, sip/ktexteditor/sipktexteditorpart4.cpp, sip/ktexteditor/sipktexteditorpart5.cpp, sip/ktexteditor/sipktexteditorpart6.cpp, sip/ktexteditor/sipktexteditorpart7.cpp Scanning dependencies of target python_module_PyKDE4_kparts [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkpartspart1.cpp: In static member function ?static KParts::Plugin* sipKParts_Plugin::sipProtect_loadPlugin(QObject*, const char*)?: sipkpartspart1.cpp:1968: Warnung: ?static KParts::Plugin* KParts::Plugin::loadPlugin(QObject*, const char*)? ist veraltet (deklariert bei /usr/include/kparts/plugin.h:173) sipkpartspart1.cpp: In static member function ?static KParts::Plugin* sipKParts_Plugin::sipProtect_loadPlugin(QObject*, const QByteArray&)?: sipkpartspart1.cpp:1973: Warnung: ?static KParts::Plugin* KParts::Plugin::loadPlugin(QObject*, const QByteArray&)? ist veraltet (deklariert bei /usr/include/kparts/plugin.h:179) [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkpartspart2.cpp: In member function ?bool sipKParts_ReadWritePart::sipProtect_isLocalFileTemporary() const?: sipkpartspart2.cpp:2625: Warnung: ?bool KParts::ReadOnlyPart::isLocalFileTemporary() const? ist veraltet (deklariert bei /usr/include/kparts/part.h:686) sipkpartspart2.cpp: In member function ?void sipKParts_ReadWritePart::sipProtect_setLocalFileTemporary(bool)?: sipkpartspart2.cpp:2630: Warnung: ?void KParts::ReadOnlyPart::setLocalFileTemporary(bool)? ist veraltet (deklariert bei /usr/include/kparts/part.h:691) sipkpartspart2.cpp: In member function ?bool sipKParts_ReadOnlyPart::sipProtect_isLocalFileTemporary() const?: sipkpartspart2.cpp:4861: Warnung: ?bool KParts::ReadOnlyPart::isLocalFileTemporary() const? ist veraltet (deklariert bei /usr/include/kparts/part.h:686) sipkpartspart2.cpp: In member function ?void sipKParts_ReadOnlyPart::sipProtect_setLocalFileTemporary(bool)?: sipkpartspart2.cpp:4866: Warnung: ?void KParts::ReadOnlyPart::setLocalFileTemporary(bool)? ist veraltet (deklariert bei /usr/include/kparts/part.h:691) [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkpartspart3.cpp: In constructor ?sipKParts_MainWindow::sipKParts_MainWindow(QWidget*, const char*, Qt::WindowFlags)?: sipkpartspart3.cpp:497: Warnung: ?KParts::MainWindow::MainWindow(QWidget*, const char*, Qt::WindowFlags)? ist veraltet (deklariert bei /usr/include/kparts/mainwindow.h:55) [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkpartspart4.cpp: In member function ?QTimer& sipKParts_BrowserRun::sipProtect_timer()?: sipkpartspart4.cpp:798: Warnung: ?QTimer& KRun::timer()? ist veraltet (deklariert bei /usr/include/krun.h:492) sipkpartspart4.cpp: In member function ?void sipKParts_BrowserRun::sipProtect_setDoScanFile(bool)?: sipkpartspart4.cpp:803: Warnung: ?void KRun::setDoScanFile(bool)? ist veraltet (deklariert bei /usr/include/krun.h:498) sipkpartspart4.cpp: In member function ?bool sipKParts_BrowserRun::sipProtect_doScanFile() const?: sipkpartspart4.cpp:808: Warnung: ?bool KRun::doScanFile() const? ist veraltet (deklariert bei /usr/include/krun.h:504) sipkpartspart4.cpp: In member function ?void sipKParts_BrowserRun::sipProtect_setIsDirecory(bool)?: sipkpartspart4.cpp:813: Warnung: ?void KRun::setIsDirecory(bool)? ist veraltet (deklariert bei /usr/include/krun.h:510) sipkpartspart4.cpp: In member function ?void sipKParts_BrowserRun::sipProtect_setInitializeNextAction(bool)?: sipkpartspart4.cpp:823: Warnung: ?void KRun::setInitializeNextAction(bool)? ist veraltet (deklariert bei /usr/include/krun.h:520) sipkpartspart4.cpp: In member function ?bool sipKParts_BrowserRun::sipProtect_initializeNextAction() const?: sipkpartspart4.cpp:828: Warnung: ?bool KRun::initializeNextAction() const? ist veraltet (deklariert bei /usr/include/krun.h:525) sipkpartspart4.cpp: In function ?PyObject* meth_KParts_BrowserRun_askSave(PyObject*, PyObject*)?: sipkpartspart4.cpp:1933: Warnung: ?static KParts::BrowserRun::AskSaveResult KParts::BrowserRun::askSave(const KUrl&, KSharedPtr, const QString&, const QString&)? ist veraltet (deklariert bei /usr/include/kparts/browserrun.h:91) sipkpartspart4.cpp: In function ?PyObject* meth_KParts_BrowserRun_askEmbedOrSave(PyObject*, PyObject*)?: sipkpartspart4.cpp:1969: Warnung: ?static KParts::BrowserRun::AskSaveResult KParts::BrowserRun::askEmbedOrSave(const KUrl&, const QString&, const QString&, int)? ist veraltet (deklariert bei /usr/include/kparts/browserrun.h:109) [ 15%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipAPIkparts.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kparts/sipkpartspart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkpartspart6.cpp: In member function ?virtual QObject* sipKParts_Factory::createObject(QObject*, const char*, const QStringList&)?: sipkpartspart6.cpp:1574: Warnung: ?virtual QObject* KPluginFactory::createObject(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:415) sipkpartspart6.cpp: In member function ?QObject* sipKParts_Factory::sipProtectVirt_createObject(bool, QObject*, const char*, const QStringList&)?: sipkpartspart6.cpp:1768: Warnung: ?virtual QObject* KPluginFactory::createObject(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:415) sipkpartspart6.cpp: In function ?PyObject* meth_KParts_Factory_create(PyObject*, PyObject*)?: sipkpartspart6.cpp:1984: Warnung: ?QObject* KPluginFactory::create(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:342) [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kparts.dir/sip/kparts/sipkpartspart7.o Linking CXX shared library ../../lib/pykde/kparts.so [ 16%] Built target python_module_PyKDE4_kparts [ 16%] Generating sip/kutils/sipkutilspart0.cpp, sip/kutils/sipkutilspart1.cpp, sip/kutils/sipkutilspart2.cpp, sip/kutils/sipkutilspart3.cpp, sip/kutils/sipkutilspart4.cpp, sip/kutils/sipkutilspart5.cpp, sip/kutils/sipkutilspart6.cpp, sip/kutils/sipkutilspart7.cpp Scanning dependencies of target python_module_PyKDE4_ktexteditor [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart0.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart1.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart2.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Scanning dependencies of target python_module_PyKDE4_kutils [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart3.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 16%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 17%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart4.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/ktexteditor/markinterface.sip: In function ?PyObject* convertFrom_QHash_1800_0101KTextEditor_Mark(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/ktexteditor/markinterface.sip:165: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden sipktexteditorpart4.cpp: In member function ?virtual QObject* sipKTextEditor_Factory::createObject(QObject*, const char*, const QStringList&)?: sipktexteditorpart4.cpp:1662: Warnung: ?virtual QObject* KPluginFactory::createObject(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:415) sipktexteditorpart4.cpp: In member function ?QObject* sipKTextEditor_Factory::sipProtectVirt_createObject(bool, QObject*, const char*, const QStringList&)?: sipktexteditorpart4.cpp:1856: Warnung: ?virtual QObject* KPluginFactory::createObject(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:415) sipktexteditorpart4.cpp: In function ?PyObject* meth_KTextEditor_Factory_create(PyObject*, PyObject*)?: sipktexteditorpart4.cpp:2072: Warnung: ?QObject* KPluginFactory::create(QObject*, const char*, const QStringList&)? ist veraltet (deklariert bei /usr/include/kpluginfactory.h:342) sipktexteditorpart4.cpp: In member function ?bool sipKTextEditor_Document::sipProtect_isLocalFileTemporary() const?: sipktexteditorpart4.cpp:8467: Warnung: ?bool KParts::ReadOnlyPart::isLocalFileTemporary() const? ist veraltet (deklariert bei /usr/include/kparts/part.h:686) sipktexteditorpart4.cpp: In member function ?void sipKTextEditor_Document::sipProtect_setLocalFileTemporary(bool)?: sipktexteditorpart4.cpp:8472: Warnung: ?void KParts::ReadOnlyPart::setLocalFileTemporary(bool)? ist veraltet (deklariert bei /usr/include/kparts/part.h:691) [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart5.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipkutilspart4.cpp: In function ?PyObject* meth_KCModuleLoader_showLastLoaderError(PyObject*, PyObject*)?: sipkutilspart4.cpp:4339: Warnung: ?void KCModuleLoader::showLastLoaderError(QWidget*)? ist veraltet (deklariert bei /usr/include/kcmoduleloader.h:102) sipkutilspart4.cpp:4339: Warnung: ?void KCModuleLoader::showLastLoaderError(QWidget*)? ist veraltet (deklariert bei /usr/include/kcmoduleloader.h:102) [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart6.o [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart6.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipAPIkutils.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/kutils/sipkutilspart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_ktexteditor.dir/sip/ktexteditor/sipktexteditorpart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipAPIktexteditor.h:28, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/ktexteditor/sipktexteditorpart7.cpp:24: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Linking CXX shared library ../../lib/pykde/ktexteditor.so [ 18%] Built target python_module_PyKDE4_ktexteditor [ 18%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_kutils.dir/sip/kutils/sipkutilspart7.o [ 18%] Generating sip/nepomuk/sipnepomukpart0.cpp, sip/nepomuk/sipnepomukpart1.cpp, sip/nepomuk/sipnepomukpart2.cpp, sip/nepomuk/sipnepomukpart3.cpp, sip/nepomuk/sipnepomukpart4.cpp, sip/nepomuk/sipnepomukpart5.cpp, sip/nepomuk/sipnepomukpart6.cpp, sip/nepomuk/sipnepomukpart7.cpp Linking CXX shared library ../../lib/pykde/kutils.so [ 18%] Built target python_module_PyKDE4_kutils [ 18%] Generating sip/phonon/sipphononpart0.cpp, sip/phonon/sipphononpart1.cpp, sip/phonon/sipphononpart2.cpp, sip/phonon/sipphononpart3.cpp, sip/phonon/sipphononpart4.cpp, sip/phonon/sipphononpart5.cpp, sip/phonon/sipphononpart6.cpp, sip/phonon/sipphononpart7.cpp Scanning dependencies of target python_module_PyKDE4_nepomuk [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Scanning dependencies of target python_module_PyKDE4_phonon [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_ResourceManager_createResourceFromUri(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1139: Warnung: ?Nepomuk::Resource Nepomuk::ResourceManager::createResourceFromUri(const QString&)? ist veraltet (deklariert bei /usr/include/nepomuk/resourcemanager.h:113) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_ResourceManager_allResourcesOfType(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1214: Warnung: ?QList Nepomuk::ResourceManager::allResourcesOfType(const QString&)? ist veraltet (deklariert bei /usr/include/nepomuk/resourcemanager.h:144) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_ResourceManager_allResourcesWithProperty(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1262: Warnung: ?QList Nepomuk::ResourceManager::allResourcesWithProperty(const QString&, const Nepomuk::Variant&)? ist veraltet (deklariert bei /usr/include/nepomuk/resourcemanager.h:162) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_ResourceManager_generateUniqueUri(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1290: Warnung: ?QString Nepomuk::ResourceManager::generateUniqueUri()? ist veraltet (deklariert bei /usr/include/nepomuk/resourcemanager.h:178) sipnepomukpart3.cpp: In constructor ?sipNepomuk_Resource::sipNepomuk_Resource(const QString&, const QString&)?: sipnepomukpart3.cpp:1650: Warnung: ?Nepomuk::Resource::Resource(const QString&, const QString&)? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:162) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_uri(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1708: Warnung: ?QString Nepomuk::Resource::uri() const? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:234) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_type(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1762: Warnung: ?QString Nepomuk::Resource::type() const? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:265) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_allProperties(PyObject*, PyObject*)?: sipnepomukpart3.cpp:1954: Warnung: ?QHash Nepomuk::Resource::allProperties() const? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:319) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_hasProperty(PyObject*, PyObject*)?: sipnepomukpart3.cpp:2026: Warnung: ?bool Nepomuk::Resource::hasProperty(const QString&) const? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:339) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_property(PyObject*, PyObject*)?: sipnepomukpart3.cpp:2072: Warnung: ?Nepomuk::Variant Nepomuk::Resource::property(const QString&) const? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:352) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_setProperty(PyObject*, PyObject*)?: sipnepomukpart3.cpp:2117: Warnung: ?void Nepomuk::Resource::setProperty(const QString&, const Nepomuk::Variant&)? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:375) sipnepomukpart3.cpp: In function ?PyObject* meth_Nepomuk_Resource_removeProperty(PyObject*, PyObject*)?: sipnepomukpart3.cpp:2205: Warnung: ?void Nepomuk::Resource::removeProperty(const QString&)? ist veraltet (deklariert bei /usr/include/nepomuk/resource.h:397) [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipnepomukpart5.cpp: In function ?PyObject* meth_KRatingWidget_setOnlyPaintFullSteps(PyObject*, PyObject*)?: sipnepomukpart5.cpp:5914: Warnung: ?void KRatingWidget::setOnlyPaintFullSteps(bool)? ist veraltet (deklariert bei /usr/include/nepomuk/kratingwidget.h:146) sipnepomukpart5.cpp: In function ?PyObject* meth_KRatingWidget_setPixmap(PyObject*, PyObject*)?: sipnepomukpart5.cpp:6078: Warnung: ?void KRatingWidget::setPixmap(const QPixmap&)? ist veraltet (deklariert bei /usr/include/nepomuk/kratingwidget.h:180) [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 20%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 21%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 22%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_nepomuk.dir/sip/nepomuk/sipnepomukpart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipAPInepomuk.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/nepomuk/sipnepomukpart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 22%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipnepomukpart7.cpp: In function ?PyObject* meth_Nepomuk_extractNamespace(PyObject*, PyObject*)?: sipnepomukpart7.cpp:266: Warnung: ?QUrl Nepomuk::extractNamespace(const QUrl&)? ist veraltet (deklariert bei /usr/include/nepomuk/global.h:29) sipnepomukpart7.cpp:266: Warnung: ?QUrl Nepomuk::extractNamespace(const QUrl&)? ist veraltet (deklariert bei /usr/include/nepomuk/global.h:29) Linking CXX shared library ../../lib/pykde/nepomuk.so [ 22%] Built target python_module_PyKDE4_nepomuk [ 22%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_phonon.dir/sip/phonon/sipphononpart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipAPIphonon.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/phonon/sipphononpart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 22%] Generating sip/plasma/sipplasmapart0.cpp, sip/plasma/sipplasmapart1.cpp, sip/plasma/sipplasmapart2.cpp, sip/plasma/sipplasmapart3.cpp, sip/plasma/sipplasmapart4.cpp, sip/plasma/sipplasmapart5.cpp, sip/plasma/sipplasmapart6.cpp, sip/plasma/sipplasmapart7.cpp Linking CXX shared library ../../lib/pykde/phonon.so [ 22%] Built target python_module_PyKDE4_phonon [ 23%] Generating sip/solid/sipsolidpart0.cpp, sip/solid/sipsolidpart1.cpp, sip/solid/sipsolidpart2.cpp, sip/solid/sipsolidpart3.cpp, sip/solid/sipsolidpart4.cpp, sip/solid/sipsolidpart5.cpp, sip/solid/sipsolidpart6.cpp, sip/solid/sipsolidpart7.cpp Scanning dependencies of target python_module_PyKDE4_solid [ 23%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/solid/predicate.sip: In function ?PyObject* convertFrom_QSet_0100Solid_DeviceInterface_Type(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/solid/predicate.sip:119: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/solid/powermanagement.sip: In function ?PyObject* convertFrom_QSet_0100Solid_PowerManagement_SleepState(void*, PyObject*)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/solid/powermanagement.sip:88: Warnung: es wird empfohlen, explizite geschweifte Klammern zu setzen, um mehrdeutiges ?else? zu vermeiden [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipAPIsolid.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/solid/sipsolidpart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_solid.dir/sip/solid/sipsolidpart7.o Linking CXX shared library ../../lib/pykde/solid.so [ 24%] Built target python_module_PyKDE4_solid [ 24%] Generating sip/soprano/sipsopranopart0.cpp, sip/soprano/sipsopranopart1.cpp, sip/soprano/sipsopranopart2.cpp, sip/soprano/sipsopranopart3.cpp, sip/soprano/sipsopranopart4.cpp, sip/soprano/sipsopranopart5.cpp, sip/soprano/sipsopranopart6.cpp, sip/soprano/sipsopranopart7.cpp Scanning dependencies of target python_module_PyKDE4_soprano [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Scanning dependencies of target python_module_PyKDE4_plasma [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart0.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart0.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/plasma/abstractrunner.sip: In function ?const sipTypeDef* sipSubClass_Plasma_AbstractRunner(void**)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/python/pykde4/sip/plasma/abstractrunner.sip:182: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart2.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart1.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart1.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipsopranopart3.cpp: In function ?PyObject* meth_Soprano_Node_createLiteralNode(PyObject*, PyObject*)?: sipsopranopart3.cpp:514: Warnung: ?static Soprano::Node Soprano::Node::createLiteralNode(const Soprano::LiteralValue&, const QString&)? ist veraltet (deklariert bei /usr/include/soprano/node.h:384) sipsopranopart3.cpp: In function ?void* init_Soprano_Node(sipSimpleWrapper*, PyObject*, PyObject*, PyObject**, PyObject**, PyObject**)?: sipsopranopart3.cpp:849: Warnung: ?Soprano::Node::Node(const Soprano::LiteralValue&, const QString&)? ist veraltet (deklariert bei /usr/include/soprano/node.h:120) [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 24%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 25%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition [ 25%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart2.o [ 25%] In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart2.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_soprano.dir/sip/soprano/sipsopranopart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipAPIsoprano.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/soprano/sipsopranopart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Linking CXX shared library ../../lib/pykde/soprano.so [ 25%] Built target python_module_PyKDE4_soprano Scanning dependencies of target compile_python_files [ 25%] Built target compile_python_files [ 26%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart3.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart3.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Scanning dependencies of target kpythonpluginfactory_automoc [ 26%] Built target kpythonpluginfactory_automoc [ 26%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart4.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart4.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Scanning dependencies of target csrcc [ 26%] Building CXX object csharp/qyoto/tools/csrcc/CMakeFiles/csrcc.dir/rcc.o [ 26%] Building CXX object csharp/qyoto/tools/csrcc/CMakeFiles/csrcc.dir/main.o Linking CXX executable csrcc [ 26%] Built target csrcc [ 26%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart5.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart5.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition Scanning dependencies of target uics_bin [ 26%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/customwidgetsinfo.o [ 26%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/databaseinfo.o [ 26%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/driver.o /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/csharp/qyoto/tools/uics/driver.cpp: In function ?bool isAnsiCCharacter(const QChar&)?: /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/csharp/qyoto/tools/uics/driver.cpp:162: Warnung: suggest parentheses around ?&&? within ?||? [ 26%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/treewalker.o [ 26%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/ui4.o [ 26%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart6.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart6.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipplasmapart6.cpp: In member function ?const QGraphicsItem* sipPlasma_Containment::sipProtect_toolBoxItem() const?: sipplasmapart6.cpp:4800: Warnung: ?const QGraphicsItem* Plasma::Containment::toolBoxItem() const? ist veraltet (deklariert bei /usr/include/plasma/containment.h:577) [ 26%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/uic.o sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_self(PyObject*, PyObject*)?: sipplasmapart6.cpp:21582: Warnung: ?static Plasma::Animator* Plasma::Animator::self()? ist veraltet (deklariert bei /usr/include/plasma/animator.h:88) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_animateItem(PyObject*, PyObject*)?: sipplasmapart6.cpp:21611: Warnung: ?int Plasma::Animator::animateItem(QGraphicsItem*, Plasma::Animator::Animation)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:104) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_stopItemAnimation(PyObject*, PyObject*)?: sipplasmapart6.cpp:21637: Warnung: ?void Plasma::Animator::stopItemAnimation(int)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:114) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_moveItem(PyObject*, PyObject*)?: sipplasmapart6.cpp:21668: Warnung: ?int Plasma::Animator::moveItem(QGraphicsItem*, Plasma::Animator::Movement, const QPoint&)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:124) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_stopItemMovement(PyObject*, PyObject*)?: sipplasmapart6.cpp:21694: Warnung: ?void Plasma::Animator::stopItemMovement(int)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:134) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_customAnimation(PyObject*, PyObject*)?: sipplasmapart6.cpp:21728: Warnung: ?int Plasma::Animator::customAnimation(int, int, Plasma::Animator::CurveShape, QObject*, const char*)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:154) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_stopCustomAnimation(PyObject*, PyObject*)?: sipplasmapart6.cpp:21755: Warnung: ?void Plasma::Animator::stopCustomAnimation(int)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:165) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_animateElement(PyObject*, PyObject*)?: sipplasmapart6.cpp:21785: Warnung: ?int Plasma::Animator::animateElement(QGraphicsItem*, Plasma::Animator::Animation)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:167) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_stopElementAnimation(PyObject*, PyObject*)?: sipplasmapart6.cpp:21811: Warnung: ?void Plasma::Animator::stopElementAnimation(int)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:168) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_setInitialPixmap(PyObject*, PyObject*)?: sipplasmapart6.cpp:21839: Warnung: ?void Plasma::Animator::setInitialPixmap(int, const QPixmap&)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:169) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_currentPixmap(PyObject*, PyObject*)?: sipplasmapart6.cpp:21868: Warnung: ?QPixmap Plasma::Animator::currentPixmap(int)? ist veraltet (deklariert bei /usr/include/plasma/animator.h:170) sipplasmapart6.cpp: In function ?PyObject* meth_Plasma_Animator_isAnimating(PyObject*, PyObject*)?: sipplasmapart6.cpp:21895: Warnung: ?bool Plasma::Animator::isAnimating() const? ist veraltet (deklariert bei /usr/include/plasma/animator.h:179) [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/validator.o [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/cs/cswritedeclaration.o [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/cs/cswriteincludes.o [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/cs/cswriteicondata.o [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/cs/cswriteicondeclaration.o [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/cs/cswriteiconinitialization.o [ 27%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/cs/cswriteinitialization.o /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/csharp/qyoto/tools/uics/cs/cswriteinitialization.cpp:117: Warnung: unbenutzter Parameter ?indent? /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/kdebindings-4.4.0/csharp/qyoto/tools/uics/cs/cswriteinitialization.cpp:117: Warnung: unbenutzter Parameter ?str? [ 27%] Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart7.o In Datei, eingef?gt von /usr/include/python2.6/Python.h:8, von /usr/include/python2.6/sip.h:33, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipAPIplasma.h:11, von /home/pierre/archlinux/packages/testing/kde-build/kde/build/kdebindings/trunk/src/build/python/pykde4/sip/plasma/sipplasmapart7.cpp:7: /usr/include/python2.6/pyconfig.h:1037:1: Warnung: ?_XOPEN_SOURCE? redefiniert : Warnung: dies ist die Stelle der vorherigen Definition sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_animationFps(PyObject*, PyObject*)?: sipplasmapart7.cpp:752: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_movementAnimationFps(PyObject*, PyObject*)?: sipplasmapart7.cpp:781: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_elementAnimationFps(PyObject*, PyObject*)?: sipplasmapart7.cpp:810: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_animationDuration(PyObject*, PyObject*)?: sipplasmapart7.cpp:839: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_movementAnimationDuration(PyObject*, PyObject*)?: sipplasmapart7.cpp:868: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_elementAnimationDuration(PyObject*, PyObject*)?: sipplasmapart7.cpp:897: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_animationCurve(PyObject*, PyObject*)?: sipplasmapart7.cpp:926: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_movementAnimationCurve(PyObject*, PyObject*)?: sipplasmapart7.cpp:955: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_elementAnimationCurve(PyObject*, PyObject*)?: sipplasmapart7.cpp:984: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_elementAppear(PyObject*, PyObject*)?: sipplasmapart7.cpp:1014: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_elementDisappear(PyObject*, PyObject*)?: sipplasmapart7.cpp:1044: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_itemAppear(PyObject*, PyObject*)?: sipplasmapart7.cpp:1074: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_itemDisappear(PyObject*, PyObject*)?: sipplasmapart7.cpp:1103: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_itemActivated(PyObject*, PyObject*)?: sipplasmapart7.cpp:1132: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_itemSlideIn(PyObject*, PyObject*)?: sipplasmapart7.cpp:1163: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?PyObject* meth_Plasma_AnimationDriver_itemSlideOut(PyObject*, PyObject*)?: sipplasmapart7.cpp:1194: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?void* cast_Plasma_AnimationDriver(void*, const sipTypeDef*)?: sipplasmapart7.cpp:1223: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function ?void release_Plasma_AnimationDriver(void*, int)?: sipplasmapart7.cpp:1239: Warnung: ?AnimationDriver? ist veraltet (deklariert bei /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: At global scope: sipplasmapart7.cpp:2324: Fehler: ?MoveDownLeft? is not a member of ?Plasma::Animation? sipplasmapart7.cpp:2325: Fehler: ?MoveDownRight? is not a member of ?Plasma::Animation? sipplasmapart7.cpp:2329: Fehler: ?MoveUpLeft? is not a member of ?Plasma::Animation? sipplasmapart7.cpp:2330: Fehler: ?MoveUpRight? is not a member of ?Plasma::Animation? sipplasmapart7.cpp:2333: Fehler: zu viele Initialisierer f?r ?sipEnumMemberDef? sipplasmapart7.cpp:2333: Fehler: zu viele Initialisierer f?r ?sipEnumMemberDef? sipplasmapart7.cpp:2333: Fehler: zu viele Initialisierer f?r ?sipEnumMemberDef? sipplasmapart7.cpp:2333: Fehler: zu viele Initialisierer f?r ?sipEnumMemberDef? make[2]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart7.o] Fehler 1 make[1]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/all] Fehler 2 make[1]: *** Warte auf noch nicht beendete Prozesse... [ 28%] Building CXX object csharp/qyoto/tools/uics/CMakeFiles/uics_bin.dir/main.o Linking CXX executable uics [ 28%] Built target uics_bin make: *** [all] Fehler 2 From trueg at kde.org Thu Feb 4 14:43:10 2010 From: trueg at kde.org (Sebastian Trueg) Date: Thu, 04 Feb 2010 14:43:10 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6AC859.4040300@math.unl.edu> References: <4B6AC859.4040300@math.unl.edu> Message-ID: <4B6ACEEE.5070303@kde.org> Rex Dieter wrote: > FYI, > http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter > > 1. The requirements for kde-4.4/nepomuk have changed pretty late in the > game (after all 4.4rc's). No, they did not. I always said that Virtuoso 6 would be the dependency for KDE 4.4. This is just a new version. Nepomuk also works with Virtuoso 5 but it is not recommended. Packaging efforts have been going on between Mandriva, Debian, SuSE, and OpenLink for a while now. > 2. I personally have had trouble downloading 6.1.0 for the past 24hrs > from sourceforge, if this is a continuing problem for others, perhaps we > could put it on kde mirrors somewhere? Probably high load after the release yesterday night. > 3. the aforementioned data conversion tool (from 5.0.x) as-is seems... > less than optimal. "less than optimal" is way too detailed for me to give any feedback on. ;) Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 who already tries Nepomuk with Virtuoso 5 (and thus, compile themselves!) to easily convert their data. Cheers, Sebastian From trueg at kde.org Thu Feb 4 17:42:36 2010 From: trueg at kde.org (Sebastian Trueg) Date: Thu, 04 Feb 2010 17:42:36 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6AE180.8070805@math.unl.edu> References: <4B6AC859.4040300@math.unl.edu> <4B6ACEEE.5070303@kde.org> <4B6AE180.8070805@math.unl.edu> Message-ID: <4B6AF8FC.6020304@kde.org> Well, if you want you can still ship Virtuoso 5.0.13. I can't make you change to V6 now. But I recommend it. Cheers, Sebastian Rex Dieter wrote: > On 02/04/2010 07:43 AM, Sebastian Trueg wrote: >> Rex Dieter wrote: >>> FYI, >>> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter >>> >>> 1. The requirements for kde-4.4/nepomuk have changed pretty late in the >>> game (after all 4.4rc's). >> No, they did not. I always said that Virtuoso 6 would be the dependency >> for KDE 4.4. > > That's all well and good. > > I had held off trying to use 6.0 myself, based on comments from you that > it was buggy and didn't work, ie, waiting for 6.0.1 or 6.1, which has > now landed. > > Fact is that we're in a bad situation of now requiring something that's > been untested and it's data is incompatible with what was tested. > >>> 3. the aforementioned data conversion tool (from 5.0.x) as-is seems... >>> less than optimal. >> "less than optimal" is way too detailed for me to give any feedback on. ;) >> >> Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 >> who already tries Nepomuk with Virtuoso 5 (and thus, compile >> themselves!) to easily convert their data. > > I get that. I was hoping we could do better. This is just a > consequence of (1), and not having ample time to adapt to the new stuff. > > -- Rex > _______________________________________________ > Nepomuk mailing list > Nepomuk at kde.org > https://mail.kde.org/mailman/listinfo/nepomuk > From trueg at kde.org Thu Feb 4 17:43:51 2010 From: trueg at kde.org (Sebastian Trueg) Date: Thu, 04 Feb 2010 17:43:51 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <2395293.dfDzQ7E0tU@kde.org> References: <2395293.dfDzQ7E0tU@kde.org> Message-ID: <4B6AF947.2030300@kde.org> There is no commit. There is no hard dependency. If you want stick with V5 although I would not recommend it. Cheers, Sebastian Tom Albers wrote: > Op Thursday 4 February 2010 14:15 schreef u: >> FYI, >> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter >> >> 1. The requirements for kde-4.4/nepomuk have changed pretty late in the >> game (after all 4.4rc's). > > That is not allowed. Please revert the offending commit. > > Best, > > Toma > > > ------------------------------------------------------------------------ > > _______________________________________________ > Nepomuk mailing list > Nepomuk at kde.org > https://mail.kde.org/mailman/listinfo/nepomuk From sebas at kde.org Thu Feb 4 21:58:46 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Thu, 4 Feb 2010 21:58:46 +0100 Subject: Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002041933.25882.mueller@kde.org> References: <201002041933.25882.mueller@kde.org> Message-ID: <201002042158.46900.sebas@kde.org> On Monday 01 February 2010 14:29:52 Arkadiusz Miskiewicz wrote: > https://bugs.kde.org/show_bug.cgi?id=211128 > https://bugs.kde.org/show_bug.cgi?id=222296 On Thursday 04 February 2010 19:33:25 Dirk Mueller wrote: > both seem to be present in 4.4.0 as well. does anyone know which commits > introduced those bugs? PIMsters, any idea? -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From arekm at maven.pl Thu Feb 4 22:51:48 2010 From: arekm at maven.pl (Arkadiusz Miskiewicz) Date: Thu, 4 Feb 2010 22:51:48 +0100 Subject: KDE 4.4.0 tagged In-Reply-To: References: Message-ID: <201002042251.48634.arekm@maven.pl> On Thursday 04 of February 2010, Pierre Schmitz wrote: > On Thu, 4 Feb 2010 11:34:54 +0100, Dirk Mueller wrote: > > Hi, > > > > I've created an initial KDE 4.4.0 tag from branches/KDE/4.4 > > kdebindings fails to compile. I have not much time right now, so I'll just > attach the buildlog for now. Fix is likely like this: http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/kde4-kdebindings/kde4- kdebindings-plasma.patch?rev=1.1.2.1;only_with_tag=DEVEL -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ From trueg at kde.org Thu Feb 4 23:18:18 2010 From: trueg at kde.org (Sebastian Trueg) Date: Thu, 04 Feb 2010 23:18:18 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <201002041742.33583.sebas@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002041742.33583.sebas@kde.org> Message-ID: <4B6B47AA.9050106@kde.org> Sebastian K?gler wrote: > On Thursday 04 February 2010 16:16:34 Tom Albers wrote: >> Op Thursday 4 February 2010 16:02 schreef u: >>> On 02/04/2010 07:43 AM, Sebastian Trueg wrote: >>>> Rex Dieter wrote: >>>>> FYI, >>>>> http://kde-apps.org/content/show.php/Nepomuk+Virtuoso+Converter >>>>> >>>>> 1. The requirements for kde-4.4/nepomuk have changed pretty late in >>>>> the game (after all 4.4rc's). >>>> No, they did not. I always said that Virtuoso 6 would be the dependency >>>> for KDE 4.4. >> You can not add a new dependency for KDE 4.4 the day before the release >> without testing. I consider it a new feature which is not allowed since >> ages. for KDE 4.5 I've planned to add it to the release schedule >> explicitly to make it even more clear. It is too late in the cycle for 4.4 >> to change this dependency. Really. Some packagers can not add a new >> dependency to their repository in one day and have prepared the KDE 4.4 >> packaging based on the 4.4 release candidates we have given them. Please >> don't do this. >> >>> Fact is that we're in a bad situation of now requiring something that's >>> been untested and it's data is incompatible with what was tested. >> +1 >> Unacceptable imho. > > What will happen is that distros will ship Virtuoso 6 anyway, because they don't want That has been the plan for a long time now and the major distros already knew that. Like I said: Debian, SuSE and Mandriva have been in contact with OpenLink for a long time to clean up the code tree (licence-wise) and figure out the best packaging scheme. > to introduce V5, and then have to convert users' data again (first time from the > sesame2) backend. I don't know in how far V6 is different from V5, other than the > dataformat, but we might consider recommending V6 anyway, because it has a clearer > road forward. > > It's a bit unfortunate that there was a bug in V6.0 that prevented us from testing > with it, that seems fixed in 6.1? > > I'd also be interested in more (dis)advantages of V6 over V5, and how different V5 > and 6 actually are from a "what can break KDE?"-point of view. Sebastian, can you > give more details? From bogus@does.not.exist.com Thu Feb 4 01:00:46 2010 From: bogus@does.not.exist.com () Date: Thu, 04 Feb 2010 00:00:46 -0000 Subject: No subject Message-ID: Better performance, lower mem footprint, more features, better support, ... >>>> Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 >>>> who already tries Nepomuk with Virtuoso 5 (and thus, compile >>>> themselves!) to easily convert their data. >> Distro's who have provided RC's to their users are now more or less obliged >> to run that script. Virtuoso was made a hard dependency (at least for >> anyone compiling kdepim) so all svn users also need to update. > > Bottom line is that distros will probably shop Virtuoso 6 to their end-users anyway, > so we need to make sure it works well with it. I don't think it's as easy as saying > "it's too late to require V6", because it's not. Note that I don't like the > situation, but to me it's more complex ... > > There's also the question what we require. As far as I know, KDE 4.4.0 works with > virtuoso 5 and 6, so what would be natural is requiring at least V5, recommending V6 > (for the upgrade path, BUT we haven't tested it yet). And that is exactly what is happening. It works with both v5 and v6 but nobody will package v5. Thus the converter. Cheers, Sebastian From sebas at kde.org Fri Feb 5 01:59:23 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Fri, 5 Feb 2010 01:59:23 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6B47AA.9050106@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002041742.33583.sebas@kde.org> <4B6B47AA.9050106@kde.org> Message-ID: <201002050159.31989.sebas@kde.org> On Thursday 04 February 2010 23:18:18 Sebastian Trueg wrote: > >>>> Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 > >>>> who already tries Nepomuk with Virtuoso 5 (and thus, compile > >>>> themselves!) to easily convert their data. > >> > >> Distro's who have provided RC's to their users are now more or less > >> obliged to run that script. Virtuoso was made a hard dependency (at > >> least for anyone compiling kdepim) so all svn users also need to > >> update. > > > > > > > > Bottom line is that distros will probably shop Virtuoso 6 to their > > end-users anyway, so we need to make sure it works well with it. I > > don't think it's as easy as saying "it's too late to require V6", > > because it's not. Note that I don't like the situation, but to me it's > > more complex ... > > > > There's also the question what we require. As far as I know, KDE 4.4.0 > > works with virtuoso 5 and 6, so what would be natural is requiring at > > least V5, recommending V6 (for the upgrade path, BUT we haven't tested > > it yet). > > And that is exactly what is happening. It works with both v5 and v6 but > nobody will package v5. Thus the converter. After using the converter, I don't get search results anymore. Listing tags works, but queries fail with "/home/sebas/kdesvn/install/bin/nepomukservicestub(30328)" Error in thread 2958723952 : "SQLExecDirect failed on query 'sparql select distinct ?p where { { ?p a . ?p ?l . ?l bif:contains "'hastag*'" . } UNION { ?p a . FILTER(REGEX(STR(?p),'hastag*','i')) . } }' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ200: Table referenced in contains does not have a text index)" Any hint? -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: neplog.zip Type: application/zip Size: 5445 bytes Desc: not available Url : http://mail.kde.org/pipermail/release-team/attachments/20100205/2c734e1a/attachment-0001.zip -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100205/2c734e1a/attachment-0001.sig From trueg at kde.org Fri Feb 5 09:05:10 2010 From: trueg at kde.org (Sebastian Trueg) Date: Fri, 05 Feb 2010 09:05:10 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <201002050159.31989.sebas@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002041742.33583.sebas@kde.org> <4B6B47AA.9050106@kde.org> <201002050159.31989.sebas@kde.org> Message-ID: <4B6BD136.9060105@kde.org> yeah... damn, apparently the text index is not enabled by default anymore. Still was in 6.0.x snapshots I had. This is fixed with a simple patch to the storage service though. Maybe we need to port that back to the 4.4.0 tag, too. Cheers, Sebastian Sebastian K?gler wrote: > On Thursday 04 February 2010 23:18:18 Sebastian Trueg wrote: >>>>>> Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 >>>>>> who already tries Nepomuk with Virtuoso 5 (and thus, compile >>>>>> themselves!) to easily convert their data. >>>> Distro's who have provided RC's to their users are now more or less >>>> obliged to run that script. Virtuoso was made a hard dependency (at >>>> least for anyone compiling kdepim) so all svn users also need to >>>> update. >>> >>> >>> Bottom line is that distros will probably shop Virtuoso 6 to their >>> end-users anyway, so we need to make sure it works well with it. I >>> don't think it's as easy as saying "it's too late to require V6", >>> because it's not. Note that I don't like the situation, but to me it's >>> more complex ... >>> >>> There's also the question what we require. As far as I know, KDE 4.4.0 >>> works with virtuoso 5 and 6, so what would be natural is requiring at >>> least V5, recommending V6 (for the upgrade path, BUT we haven't tested >>> it yet). >> And that is exactly what is happening. It works with both v5 and v6 but >> nobody will package v5. Thus the converter. > > After using the converter, I don't get search results anymore. Listing tags works, > but queries fail with > > "/home/sebas/kdesvn/install/bin/nepomukservicestub(30328)" Error in thread 2958723952 > : "SQLExecDirect failed on query 'sparql select distinct ?p where { { ?p a > . ?p > ?l . ?l bif:contains "'hastag*'" . } > UNION { ?p a . > FILTER(REGEX(STR(?p),'hastag*','i')) . } }' (iODBC Error: [OpenLink][Virtuoso iODBC > Driver][Virtuoso Server]SQ200: Table referenced in contains does not have a text > index)" > > Any hint? From trueg at kde.org Fri Feb 5 09:10:36 2010 From: trueg at kde.org (Sebastian Trueg) Date: Fri, 05 Feb 2010 09:10:36 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6BD136.9060105@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002041742.33583.sebas@kde.org> <4B6B47AA.9050106@kde.org> <201002050159.31989.sebas@kde.org> <4B6BD136.9060105@kde.org> Message-ID: <4B6BD27C.4080807@kde.org> Please try the attached patch in kdebase/runtime/nepomuk/services/storage. And if it helps, please apply as I am in the train all day. Starting nepomuk will take a long time probably since the whole index needs to be rebuilt. Cheers, Sebastian Sebastian Trueg wrote: > yeah... damn, apparently the text index is not enabled by default > anymore. Still was in 6.0.x snapshots I had. > This is fixed with a simple patch to the storage service though. > Maybe we need to port that back to the 4.4.0 tag, too. > > Cheers, > Sebastian > > Sebastian K?gler wrote: >> On Thursday 04 February 2010 23:18:18 Sebastian Trueg wrote: >>>>>>> Anyway, the converter is hacky tool allowing early adopters of KDE 4.4 >>>>>>> who already tries Nepomuk with Virtuoso 5 (and thus, compile >>>>>>> themselves!) to easily convert their data. >>>>> Distro's who have provided RC's to their users are now more or less >>>>> obliged to run that script. Virtuoso was made a hard dependency (at >>>>> least for anyone compiling kdepim) so all svn users also need to >>>>> update. >>>> >>>> Bottom line is that distros will probably shop Virtuoso 6 to their >>>> end-users anyway, so we need to make sure it works well with it. I >>>> don't think it's as easy as saying "it's too late to require V6", >>>> because it's not. Note that I don't like the situation, but to me it's >>>> more complex ... >>>> >>>> There's also the question what we require. As far as I know, KDE 4.4.0 >>>> works with virtuoso 5 and 6, so what would be natural is requiring at >>>> least V5, recommending V6 (for the upgrade path, BUT we haven't tested >>>> it yet). >>> And that is exactly what is happening. It works with both v5 and v6 but >>> nobody will package v5. Thus the converter. >> After using the converter, I don't get search results anymore. Listing tags works, >> but queries fail with >> >> "/home/sebas/kdesvn/install/bin/nepomukservicestub(30328)" Error in thread 2958723952 >> : "SQLExecDirect failed on query 'sparql select distinct ?p where { { ?p a >> . ?p >> ?l . ?l bif:contains "'hastag*'" . } >> UNION { ?p a . >> FILTER(REGEX(STR(?p),'hastag*','i')) . } }' (iODBC Error: [OpenLink][Virtuoso iODBC >> Driver][Virtuoso Server]SQ200: Table referenced in contains does not have a text >> index)" >> >> Any hint? > _______________________________________________ > Nepomuk mailing list > Nepomuk at kde.org > https://mail.kde.org/mailman/listinfo/nepomuk > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 1.diff Url: http://mail.kde.org/pipermail/release-team/attachments/20100205/edcfb98d/attachment.bat From simon at simonzone.com Fri Feb 5 11:33:09 2010 From: simon at simonzone.com (Simon Edwards) Date: Fri, 05 Feb 2010 10:33:09 +0000 Subject: branches/KDE/4.4/kdebindings/python/pykde4/sip/plasma Message-ID: <1265365989.659217.16855.nullmailer@svn.kde.org> SVN commit 1085468 by sedwards: Incorporate the changes introduced in revision 1084111 to kdelibs/plasma/animations/animation.h. This fixes PyKDE4 for 4.4.0. (Thanks to AiX 27/249 for the patch.) CCMAIL: release-team at kde.org CCMAIL: kde-packages at kde.org CCMAIL: kde-bindings at kde.org M +5 -6 animation.sip --- branches/KDE/4.4/kdebindings/python/pykde4/sip/plasma/animation.sip #1085467:1085468 @@ -27,7 +27,7 @@ public: int duration () const; - enum Reference + enum ReferenceFlag { Center, Up, @@ -35,6 +35,7 @@ Left, Right }; + explicit Animation (QObject* parent /TransferThis/ = 0); virtual ~Animation ()=0; protected: @@ -50,17 +51,15 @@ public: void setTargetWidget (QGraphicsWidget* widget); QGraphicsWidget* targetWidget () const; - enum MovementDirection + enum MovementDirectionFlag { + MoveAny, MoveUp, - MoveUpRight, MoveRight, - MoveDownRight, MoveDown, - MoveDownLeft, MoveLeft, - MoveUpLeft }; + void setEasingCurve (const QEasingCurve& curve); QEasingCurve easingCurve () const; }; From sebas at kde.org Fri Feb 5 11:53:29 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Fri, 5 Feb 2010 11:53:29 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B6BD27C.4080807@kde.org> References: <4235196.m1ciYH076x@kde.org> <4B6BD136.9060105@kde.org> <4B6BD27C.4080807@kde.org> Message-ID: <201002051153.30594.sebas@kde.org> Hey Sebastian, On Friday 05 February 2010 09:10:36 Sebastian Trueg wrote: > Please try the attached patch in kdebase/runtime/nepomuk/services/storage. > And if it helps, please apply as I am in the train all day. > Starting nepomuk will take a long time probably since the whole index > needs to be rebuilt. That doesn't seem to help. (I've only rebuilt/installed that particular directory.) The error is apparently the same still. I've attached an updated log from my nepomukserver (gave it some time to start up, the initial CPU load had definitely settled). I'll be on IRC all day and tonight, you can catch me there (or by email, of course). > Sebastian Trueg wrote: > > yeah... damn, apparently the text index is not enabled by default > > anymore. Still was in 6.0.x snapshots I had. > > This is fixed with a simple patch to the storage service though. > > Maybe we need to port that back to the 4.4.0 tag, too. Thanks, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: nepomuk.log.zip Type: application/zip Size: 3727 bytes Desc: not available Url : http://mail.kde.org/pipermail/release-team/attachments/20100205/59d78dc4/attachment.zip From mcguire at kde.org Fri Feb 5 11:10:19 2010 From: mcguire at kde.org (Thomas McGuire) Date: Fri, 5 Feb 2010 11:10:19 +0100 Subject: Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002042158.46900.sebas@kde.org> References: <201002041933.25882.mueller@kde.org> <201002042158.46900.sebas@kde.org> Message-ID: <201002051110.35105.mcguire@kde.org> Hi, On Thursday 04 February 2010 21:58:46 Sebastian K?gler wrote: > On Monday 01 February 2010 14:29:52 Arkadiusz Miskiewicz wrote: > > https://bugs.kde.org/show_bug.cgi?id=211128 > > https://bugs.kde.org/show_bug.cgi?id=222296 > > On Thursday 04 February 2010 19:33:25 Dirk Mueller wrote: > > both seem to be present in 4.4.0 as well. does anyone know which commits > > introduced those bugs? > > PIMsters, any idea? I commented on both bugs. While they might be annoying, they are hardly hat important and IMHO don't warrant posting to the release-team mailing list. Bug 211128 should be easy to fix if anyone is willing to have a look. Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100205/13243868/attachment-0001.sig From dagger at gentoo.org Fri Feb 5 14:09:10 2010 From: dagger at gentoo.org (Robert Piasek) Date: Fri, 5 Feb 2010 13:09:10 +0000 Subject: KDE 4.4.0 tarballs uploaded (try #1..) In-Reply-To: <201002041931.23553.mueller@kde.org> References: <201002041931.23553.mueller@kde.org> Message-ID: <201002051309.15557.dagger@gentoo.org> So far pykde-4.4.0 doesn't compile: Building CXX object python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart7.o In file included from /usr/include/python2.6/Python.h:8, from /usr/include/python2.6/sip.h:33, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIplasma.h:11, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasmapart0.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: "_XOPEN_SOURCE" redefined : warning: this is the location of the previous definition /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6/python/pykde4/sip/plasma/abstractrunner.sip: In function 'const sipTypeDef* sipSubClass_Plasma_AbstractRunner(void**)': /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6/python/pykde4/sip/plasma/abstractrunner.sip:182: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) In file included from /usr/include/python2.6/Python.h:8, from /usr/include/python2.6/sip.h:33, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIplasma.h:11, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasmapart4.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: "_XOPEN_SOURCE" redefined : warning: this is the location of the previous definition In file included from /usr/include/python2.6/Python.h:8, from /usr/include/python2.6/sip.h:33, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIplasma.h:11, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasmapart5.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: "_XOPEN_SOURCE" redefined : warning: this is the location of the previous definition In file included from /usr/include/python2.6/Python.h:8, from /usr/include/python2.6/sip.h:33, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIplasma.h:11, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasmapart2.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: "_XOPEN_SOURCE" redefined : warning: this is the location of the previous definition In file included from /usr/include/python2.6/Python.h:8, from /usr/include/python2.6/sip.h:33, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIplasma.h:11, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasmapart6.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: "_XOPEN_SOURCE" redefined : warning: this is the location of the previous definition sipplasmapart6.cpp: In member function 'const QGraphicsItem* sipPlasma_Containment::sipProtect_toolBoxItem() const': sipplasmapart6.cpp:4800: warning: 'const QGraphicsItem* Plasma::Containment::toolBoxItem() const' is deprecated (declared at /usr/include/plasma/containment.h:577) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_self(PyObject*, PyObject*)': sipplasmapart6.cpp:21582: warning: 'static Plasma::Animator* Plasma::Animator::self()' is deprecated (declared at /usr/include/plasma/animator.h:88) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_animateItem(PyObject*, PyObject*)': sipplasmapart6.cpp:21611: warning: 'int Plasma::Animator::animateItem(QGraphicsItem*, Plasma::Animator::Animation)' is deprecated (declared at /usr/include/plasma/animator.h:104) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_stopItemAnimation(PyObject*, PyObject*)': sipplasmapart6.cpp:21637: warning: 'void Plasma::Animator::stopItemAnimation(int)' is deprecated (declared at /usr/include/plasma/animator.h:114) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_moveItem(PyObject*, PyObject*)': sipplasmapart6.cpp:21668: warning: 'int Plasma::Animator::moveItem(QGraphicsItem*, Plasma::Animator::Movement, const QPoint&)' is deprecated (declared at /usr/include/plasma/animator.h:124) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_stopItemMovement(PyObject*, PyObject*)': sipplasmapart6.cpp:21694: warning: 'void Plasma::Animator::stopItemMovement(int)' is deprecated (declared at /usr/include/plasma/animator.h:134) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_customAnimation(PyObject*, PyObject*)': sipplasmapart6.cpp:21728: warning: 'int Plasma::Animator::customAnimation(int, int, Plasma::Animator::CurveShape, QObject*, const char*)' is deprecated (declared at /usr/include/plasma/animator.h:154) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_stopCustomAnimation(PyObject*, PyObject*)': sipplasmapart6.cpp:21755: warning: 'void Plasma::Animator::stopCustomAnimation(int)' is deprecated (declared at /usr/include/plasma/animator.h:165) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_animateElement(PyObject*, PyObject*)': sipplasmapart6.cpp:21785: warning: 'int Plasma::Animator::animateElement(QGraphicsItem*, Plasma::Animator::Animation)' is deprecated (declared at /usr/include/plasma/animator.h:167) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_stopElementAnimation(PyObject*, PyObject*)': sipplasmapart6.cpp:21811: warning: 'void Plasma::Animator::stopElementAnimation(int)' is deprecated (declared at /usr/include/plasma/animator.h:168) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_setInitialPixmap(PyObject*, PyObject*)': sipplasmapart6.cpp:21839: warning: 'void Plasma::Animator::setInitialPixmap(int, const QPixmap&)' is deprecated (declared at /usr/include/plasma/animator.h:169) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_currentPixmap(PyObject*, PyObject*)': sipplasmapart6.cpp:21868: warning: 'QPixmap Plasma::Animator::currentPixmap(int)' is deprecated (declared at /usr/include/plasma/animator.h:170) sipplasmapart6.cpp: In function 'PyObject* meth_Plasma_Animator_isAnimating(PyObject*, PyObject*)': sipplasmapart6.cpp:21895: warning: 'bool Plasma::Animator::isAnimating() const' is deprecated (declared at /usr/include/plasma/animator.h:179) In file included from /usr/include/python2.6/Python.h:8, from /usr/include/python2.6/sip.h:33, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIplasma.h:11, from /var/tmp/paludis/kde-base- pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasmapart7.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: "_XOPEN_SOURCE" redefined : warning: this is the location of the previous definition sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_animationFps(PyObject*, PyObject*)': sipplasmapart7.cpp:752: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_movementAnimationFps(PyObject*, PyObject*)': sipplasmapart7.cpp:781: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_elementAnimationFps(PyObject*, PyObject*)': sipplasmapart7.cpp:810: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_animationDuration(PyObject*, PyObject*)': sipplasmapart7.cpp:839: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_movementAnimationDuration(PyObject*, PyObject*)': sipplasmapart7.cpp:868: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_elementAnimationDuration(PyObject*, PyObject*)': sipplasmapart7.cpp:897: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_animationCurve(PyObject*, PyObject*)': sipplasmapart7.cpp:926: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_movementAnimationCurve(PyObject*, PyObject*)': sipplasmapart7.cpp:955: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_elementAnimationCurve(PyObject*, PyObject*)': sipplasmapart7.cpp:984: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_elementAppear(PyObject*, PyObject*)': sipplasmapart7.cpp:1014: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_elementDisappear(PyObject*, PyObject*)': sipplasmapart7.cpp:1044: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_itemAppear(PyObject*, PyObject*)': sipplasmapart7.cpp:1074: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_itemDisappear(PyObject*, PyObject*)': sipplasmapart7.cpp:1103: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_itemActivated(PyObject*, PyObject*)': sipplasmapart7.cpp:1132: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_itemSlideIn(PyObject*, PyObject*)': sipplasmapart7.cpp:1163: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'PyObject* meth_Plasma_AnimationDriver_itemSlideOut(PyObject*, PyObject*)': sipplasmapart7.cpp:1194: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'void* cast_Plasma_AnimationDriver(void*, const sipTypeDef*)': sipplasmapart7.cpp:1223: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: In function 'void release_Plasma_AnimationDriver(void*, int)': sipplasmapart7.cpp:1239: warning: 'AnimationDriver' is deprecated (declared at /usr/include/plasma/animationdriver.h:41) sipplasmapart7.cpp: At global scope: sipplasmapart7.cpp:2324: error: 'MoveDownLeft' is not a member of 'Plasma::Animation' sipplasmapart7.cpp:2325: error: 'MoveDownRight' is not a member of 'Plasma::Animation' sipplasmapart7.cpp:2329: error: 'MoveUpLeft' is not a member of 'Plasma::Animation' sipplasmapart7.cpp:2330: error: 'MoveUpRight' is not a member of 'Plasma::Animation' sipplasmapart7.cpp:2333: error: too many initializers for 'sipEnumMemberDef' sipplasmapart7.cpp:2333: error: too many initializers for 'sipEnumMemberDef' sipplasmapart7.cpp:2333: error: too many initializers for 'sipEnumMemberDef' sipplasmapart7.cpp:2333: error: too many initializers for 'sipEnumMemberDef' make[2]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart7.o] Error 1 make[1]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/all] Error 2 make: *** [all] Error 2 Thanks, On Thursday 04 February 2010 18:31:23 Dirk Mueller wrote: > Hi, > > I've just finished uploading the first set of 4.4.0 tarballs. Please use > the kde-4.4.0-blocker keyword in bugzilla and cc me on commits that should > end up in 4.4.0. > > Planned release is Tuesday next week. > > Greetings, > Dirk > _______________________________________________ > Kde-packager mailing list > Kde-packager at kde.org > https://mail.kde.org/mailman/listinfo/kde-packager > -- Robert Piasek Gentoo Linux Developer (KDE, Embedded, ARM) Email: dagger at gentoo.org GnuPG fingerprint: FA42 DEA9 58FA 78AD E7D5 069D BBCB 07C0 01AF 3A98 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100205/5cbad3cc/attachment-0001.sig From sebas at kde.org Fri Feb 5 16:16:44 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Fri, 5 Feb 2010 16:16:44 +0100 Subject: KDE 4.4.0 tarballs uploaded (try #1..) In-Reply-To: <201002051309.15557.dagger@gentoo.org> References: <201002041931.23553.mueller@kde.org> <201002051309.15557.dagger@gentoo.org> Message-ID: <201002051616.45517.sebas@kde.org> On Friday 05 February 2010 14:09:10 Robert Piasek wrote: > So far pykde-4.4.0 doesn't compile: The attached commit is supposed to fix this. Can you confirm? (It's not included in the tag yet, as Dirk is away.) > Building CXX object > python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplas > mapart7.o In file included from /usr/include/python2.6/Python.h:8, > from /usr/include/python2.6/sip.h:33, > from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIpla > sma.h:11, from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasma > part0.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: > "_XOPEN_SOURCE" redefined : warning: this is the location of > the previous definition /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6/python/pykde4/sip/plasma/abstractrunner. > sip: In function 'const sipTypeDef* > sipSubClass_Plasma_AbstractRunner(void**)': /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6/python/pykde4/sip/plasma/abstractrunner. > sip:182: warning: 'AnimationDriver' is deprecated (declared at > /usr/include/plasma/animationdriver.h:41) > In file included from /usr/include/python2.6/Python.h:8, > from /usr/include/python2.6/sip.h:33, > from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIpla > sma.h:11, from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasma > part4.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: > "_XOPEN_SOURCE" redefined : warning: this is the location of > the previous definition In file included from > /usr/include/python2.6/Python.h:8, > from /usr/include/python2.6/sip.h:33, > from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIpla > sma.h:11, from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasma > part5.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: > "_XOPEN_SOURCE" redefined : warning: this is the location of > the previous definition In file included from > /usr/include/python2.6/Python.h:8, > from /usr/include/python2.6/sip.h:33, > from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIpla > sma.h:11, from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasma > part2.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: > "_XOPEN_SOURCE" redefined : warning: this is the location of > the previous definition In file included from > /usr/include/python2.6/Python.h:8, > from /usr/include/python2.6/sip.h:33, > from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIpla > sma.h:11, from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasma > part6.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: > "_XOPEN_SOURCE" redefined : warning: this is the location of > the previous definition sipplasmapart6.cpp: In member function 'const > QGraphicsItem* > sipPlasma_Containment::sipProtect_toolBoxItem() const': > sipplasmapart6.cpp:4800: warning: 'const QGraphicsItem* > Plasma::Containment::toolBoxItem() const' is deprecated (declared at > /usr/include/plasma/containment.h:577) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_self(PyObject*, PyObject*)': > sipplasmapart6.cpp:21582: warning: 'static Plasma::Animator* > Plasma::Animator::self()' is deprecated (declared at > /usr/include/plasma/animator.h:88) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_animateItem(PyObject*, PyObject*)': > sipplasmapart6.cpp:21611: warning: 'int > Plasma::Animator::animateItem(QGraphicsItem*, Plasma::Animator::Animation)' > is deprecated (declared at /usr/include/plasma/animator.h:104) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_stopItemAnimation(PyObject*, PyObject*)': > sipplasmapart6.cpp:21637: warning: 'void > Plasma::Animator::stopItemAnimation(int)' is deprecated (declared at > /usr/include/plasma/animator.h:114) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_moveItem(PyObject*, PyObject*)': > sipplasmapart6.cpp:21668: warning: 'int > Plasma::Animator::moveItem(QGraphicsItem*, Plasma::Animator::Movement, > const QPoint&)' is deprecated (declared at > /usr/include/plasma/animator.h:124) sipplasmapart6.cpp: In function > 'PyObject* > meth_Plasma_Animator_stopItemMovement(PyObject*, PyObject*)': > sipplasmapart6.cpp:21694: warning: 'void > Plasma::Animator::stopItemMovement(int)' is deprecated (declared at > /usr/include/plasma/animator.h:134) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_customAnimation(PyObject*, PyObject*)': > sipplasmapart6.cpp:21728: warning: 'int > Plasma::Animator::customAnimation(int, int, Plasma::Animator::CurveShape, > QObject*, const char*)' is deprecated (declared at > /usr/include/plasma/animator.h:154) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_stopCustomAnimation(PyObject*, PyObject*)': > sipplasmapart6.cpp:21755: warning: 'void > Plasma::Animator::stopCustomAnimation(int)' is deprecated (declared at > /usr/include/plasma/animator.h:165) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_animateElement(PyObject*, PyObject*)': > sipplasmapart6.cpp:21785: warning: 'int > Plasma::Animator::animateElement(QGraphicsItem*, > Plasma::Animator::Animation)' is deprecated (declared at > /usr/include/plasma/animator.h:167) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_stopElementAnimation(PyObject*, PyObject*)': > sipplasmapart6.cpp:21811: warning: 'void > Plasma::Animator::stopElementAnimation(int)' is deprecated (declared at > /usr/include/plasma/animator.h:168) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_setInitialPixmap(PyObject*, PyObject*)': > sipplasmapart6.cpp:21839: warning: 'void > Plasma::Animator::setInitialPixmap(int, const QPixmap&)' is deprecated > (declared at /usr/include/plasma/animator.h:169) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_currentPixmap(PyObject*, PyObject*)': > sipplasmapart6.cpp:21868: warning: 'QPixmap > Plasma::Animator::currentPixmap(int)' is deprecated (declared at > /usr/include/plasma/animator.h:170) > sipplasmapart6.cpp: In function 'PyObject* > meth_Plasma_Animator_isAnimating(PyObject*, PyObject*)': > sipplasmapart6.cpp:21895: warning: 'bool Plasma::Animator::isAnimating() > const' is deprecated (declared at /usr/include/plasma/animator.h:179) > In file included from /usr/include/python2.6/Python.h:8, > from /usr/include/python2.6/sip.h:33, > from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipAPIpla > sma.h:11, from /var/tmp/paludis/kde-base- > pykde4-4.4.0/work/pykde4-4.4.0-2.6_build/python/pykde4/sip/plasma/sipplasma > part7.cpp:7: /usr/include/python2.6/pyconfig.h:1076:1: warning: > "_XOPEN_SOURCE" redefined : warning: this is the location of > the previous definition sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_animationFps(PyObject*, PyObject*)': > sipplasmapart7.cpp:752: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_movementAnimationFps(PyObject*, PyObject*)': > sipplasmapart7.cpp:781: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_elementAnimationFps(PyObject*, PyObject*)': > sipplasmapart7.cpp:810: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_animationDuration(PyObject*, PyObject*)': > sipplasmapart7.cpp:839: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_movementAnimationDuration(PyObject*, > PyObject*)': sipplasmapart7.cpp:868: warning: 'AnimationDriver' is > deprecated (declared at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_elementAnimationDuration(PyObject*, > PyObject*)': sipplasmapart7.cpp:897: warning: 'AnimationDriver' is > deprecated (declared at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_animationCurve(PyObject*, PyObject*)': > sipplasmapart7.cpp:926: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_movementAnimationCurve(PyObject*, PyObject*)': > sipplasmapart7.cpp:955: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_elementAnimationCurve(PyObject*, PyObject*)': > sipplasmapart7.cpp:984: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_elementAppear(PyObject*, PyObject*)': > sipplasmapart7.cpp:1014: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_elementDisappear(PyObject*, PyObject*)': > sipplasmapart7.cpp:1044: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_itemAppear(PyObject*, PyObject*)': > sipplasmapart7.cpp:1074: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_itemDisappear(PyObject*, PyObject*)': > sipplasmapart7.cpp:1103: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_itemActivated(PyObject*, PyObject*)': > sipplasmapart7.cpp:1132: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_itemSlideIn(PyObject*, PyObject*)': > sipplasmapart7.cpp:1163: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'PyObject* > meth_Plasma_AnimationDriver_itemSlideOut(PyObject*, PyObject*)': > sipplasmapart7.cpp:1194: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'void* cast_Plasma_AnimationDriver(void*, > const sipTypeDef*)': > sipplasmapart7.cpp:1223: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: In function 'void release_Plasma_AnimationDriver(void*, > int)': > sipplasmapart7.cpp:1239: warning: 'AnimationDriver' is deprecated (declared > at /usr/include/plasma/animationdriver.h:41) > sipplasmapart7.cpp: At global scope: > sipplasmapart7.cpp:2324: error: 'MoveDownLeft' is not a member of > 'Plasma::Animation' > sipplasmapart7.cpp:2325: error: 'MoveDownRight' is not a member of > 'Plasma::Animation' > sipplasmapart7.cpp:2329: error: 'MoveUpLeft' is not a member of > 'Plasma::Animation' > sipplasmapart7.cpp:2330: error: 'MoveUpRight' is not a member of > 'Plasma::Animation' > sipplasmapart7.cpp:2333: error: too many initializers for > 'sipEnumMemberDef' sipplasmapart7.cpp:2333: error: too many initializers > for 'sipEnumMemberDef' sipplasmapart7.cpp:2333: error: too many > initializers for 'sipEnumMemberDef' sipplasmapart7.cpp:2333: error: too > many initializers for 'sipEnumMemberDef' make[2]: *** > [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sippla > smapart7.o] Error 1 > make[1]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/all] > Error 2 > make: *** [all] Error 2 -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- An embedded message was scrubbed... From: Simon Edwards Subject: branches/KDE/4.4/kdebindings/python/pykde4/sip/plasma Date: Fri, 05 Feb 2010 10:33:09 +0000 Size: 3812 Url: http://mail.kde.org/pipermail/release-team/attachments/20100205/74b73750/attachment.eml From mueller at kde.org Fri Feb 5 16:53:16 2010 From: mueller at kde.org (Dirk Mueller) Date: Fri, 5 Feb 2010 16:53:16 +0100 Subject: KDE 4.4.0 tarballs uploaded (try #1..) In-Reply-To: <201002051309.15557.dagger@gentoo.org> References: <201002041931.23553.mueller@kde.org> <201002051309.15557.dagger@gentoo.org> Message-ID: <201002051653.16410.mueller@kde.org> On Friday 05 February 2010, Robert Piasek wrote: > So far pykde-4.4.0 doesn't compile: I've included the fix sebas pointed out. also updated kdebase* with fixes: fe9617eeb6430d12428d4bf1898bc955 kdebindings-4.4.0.tar.bz2 ddfc358aebe5dc8f5de6f5d1ff7cb018 kdebase-4.4.0.tar.bz2 08179cba422038d4bb6537d63186bb23 kdebase-workspace-4.4.0.tar.bz2 54b28d1ea9fc93953e1863c06d7b7780 kdebase-runtime-4.4.0.tar.bz2 Greetings, Dirk From sebas at kde.org Fri Feb 5 20:06:09 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Fri, 5 Feb 2010 20:06:09 +0100 Subject: release PR update Message-ID: <201002052006.11223.sebas@kde.org> Hi, A quick update on where we stand, release-PR-wise. The release announcement itself is done, and now being translated by various local teams, the first translations are already trickling in. I've sent a scoop (announcement text, screenshots, screencasts) out to our press two days ago, so that those people get some time to prepare their coverage, there was some feedback that it's useful already -- good. Meanwhile, Lydia and Alexandra are preparing our social networks campaign. buzz.kde.org will again feature a micro-blogging lifestream. (I'm not 100% up to date about the status here, but assume "on schedule"). The webteam is cracking away at the new website, which will be released shortly before the 4.4.0 release, so we're getting it all in a whole new fresh look, and what is more important: with a lot of updated, rewritten and better structured content around it. We're also still working on a more detailed visual feature guide, so people who want more in-depth, from the source information about KDE 4.4 can get some. The text is mostly there (g-docs), it's being html-ified and brushed up now. I think things are looking rather good. Thanks everybody involved for the hard work! Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From sebas at kde.org Sat Feb 6 02:54:55 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Sat, 6 Feb 2010 02:54:55 +0100 Subject: [Kde-pim] Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002052117.35626@thufir.ingo-kloecker.de> References: <201002041933.25882.mueller@kde.org> <201002051110.35105.mcguire@kde.org> <201002052117.35626@thufir.ingo-kloecker.de> Message-ID: <201002060254.55677.sebas@kde.org> On Friday 05 February 2010 21:17:30 Ingo Kl?cker wrote: > On Friday 05 February 2010, Thomas McGuire wrote: > > On Thursday 04 February 2010 21:58:46 Sebastian K?gler wrote: > > > On Monday 01 February 2010 14:29:52 Arkadiusz Miskiewicz wrote: > > > > https://bugs.kde.org/show_bug.cgi?id=211128 > > > > https://bugs.kde.org/show_bug.cgi?id=222296 > > Bug 222296 exists as long as Kontact exists, i.e. since KDE > 3.. > > > > On Thursday 04 February 2010 19:33:25 Dirk Mueller wrote: > > > > both seem to be present in 4.4.0 as well. does anyone know which > > > > commits introduced those bugs? > > > > > > PIMsters, any idea? > > > > I commented on both bugs. While they might be annoying, they are > > hardly hat important and IMHO don't warrant posting to the > > release-team mailing list. > > FWIW, I fully agree with Thomas's assessment. Alright, suppose those are not blockers then. Thanks for having a look at it (both). Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From kloecker at kde.org Fri Feb 5 21:17:30 2010 From: kloecker at kde.org (Ingo =?iso-8859-15?q?Kl=F6cker?=) Date: Fri, 05 Feb 2010 21:17:30 +0100 Subject: [Kde-pim] Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002051110.35105.mcguire@kde.org> References: <201002041933.25882.mueller@kde.org> <201002042158.46900.sebas@kde.org> <201002051110.35105.mcguire@kde.org> Message-ID: <201002052117.35626@thufir.ingo-kloecker.de> On Friday 05 February 2010, Thomas McGuire wrote: > Hi, > > On Thursday 04 February 2010 21:58:46 Sebastian K?gler wrote: > > On Monday 01 February 2010 14:29:52 Arkadiusz Miskiewicz wrote: > > > https://bugs.kde.org/show_bug.cgi?id=211128 > > > https://bugs.kde.org/show_bug.cgi?id=222296 Bug 222296 exists as long as Kontact exists, i.e. since KDE 3.. > > On Thursday 04 February 2010 19:33:25 Dirk Mueller wrote: > > > both seem to be present in 4.4.0 as well. does anyone know which > > > commits introduced those bugs? > > > > PIMsters, any idea? > > I commented on both bugs. While they might be annoying, they are > hardly hat important and IMHO don't warrant posting to the > release-team mailing list. FWIW, I fully agree with Thomas's assessment. Regards, Ingo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100205/f5cfff58/attachment.sig From sebastian at trueg.de Sat Feb 6 15:11:24 2010 From: sebastian at trueg.de (Sebastian Trueg) Date: Sat, 6 Feb 2010 15:11:24 +0100 (CET) Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <201002051153.30594.sebas@kde.org> References: <4235196.m1ciYH076x@kde.org> <4B6BD136.9060105@kde.org> <4B6BD27C.4080807@kde.org> <201002051153.30594.sebas@kde.org> Message-ID: the big problem is that I cannot reproduce this error. Even without the patch queries work... I need to look into that when I am back from the FOSDEM. Cheers, Sebastian > Hey Sebastian, > > On Friday 05 February 2010 09:10:36 Sebastian Trueg wrote: >> Please try the attached patch in >> kdebase/runtime/nepomuk/services/storage. >> And if it helps, please apply as I am in the train all day. >> Starting nepomuk will take a long time probably since the whole index >> needs to be rebuilt. > > That doesn't seem to help. (I've only rebuilt/installed that particular > directory.) > The error is apparently the same still. I've attached an updated log from > my > nepomukserver (gave it some time to start up, the initial CPU load had > definitely > settled). > > I'll be on IRC all day and tonight, you can catch me there (or by email, > of course). > >> Sebastian Trueg wrote: >> > yeah... damn, apparently the text index is not enabled by default >> > anymore. Still was in 6.0.x snapshots I had. >> > This is fixed with a simple patch to the storage service though. >> > Maybe we need to port that back to the 4.4.0 tag, too. > > Thanks, > -- > sebas > > http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > From alien at slackware.com Sat Feb 6 15:19:27 2010 From: alien at slackware.com (Eric Hameleers) Date: Sat, 6 Feb 2010 06:19:27 -0800 (PST) Subject: KDE 4.4.0 tarballs uploaded (try #1..) In-Reply-To: <201002051653.16410.mueller@kde.org> References: <201002041931.23553.mueller@kde.org> <201002051309.15557.dagger@gentoo.org> <201002051653.16410.mueller@kde.org> Message-ID: On Fri, 5 Feb 2010, Dirk Mueller wrote: > I've included the fix sebas pointed out. also updated kdebase* with fixes: > > fe9617eeb6430d12428d4bf1898bc955 kdebindings-4.4.0.tar.bz2 > ddfc358aebe5dc8f5de6f5d1ff7cb018 kdebase-4.4.0.tar.bz2 > 08179cba422038d4bb6537d63186bb23 kdebase-workspace-4.4.0.tar.bz2 > 54b28d1ea9fc93953e1863c06d7b7780 kdebase-runtime-4.4.0.tar.bz2 > > Greetings, > Dirk Everything compiled cleanly, including the l10n tarballs. I also created a Slackware package for Sebastian Trueg's virtuosoconverter, and patched kdebase-runtime to start this converter before nepomuk. Before installing virtuosoconverter, nepomuk refuses to start (naturally, because I still had the old v5 database of earlier 4.4.0 RC's) but after installing the converter and logging in again, the converter automatically and successfully migrated nepomuk's virtuoso database to the v6 format. When I release my KDE SC 4.4.0 packages, I want to leave the users of previous KDE release candidates a choice of installing that converter, or not. Will it be enough to remove the user's .kde/share/apps/nepomuk/repository/main directory or are there other requirements to clean out the old incompatible nepomuk database data? Cheers, Eric -- Eric Hameleers Jabber: alien at jabber.xs4all.nl From hein at kde.org Sat Feb 6 18:49:53 2010 From: hein at kde.org (Eike Hein) Date: Sat, 06 Feb 2010 18:49:53 +0100 Subject: [Kde-pim] Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002060254.55677.sebas@kde.org> References: <201002041933.25882.mueller@kde.org> <201002051110.35105.mcguire@kde.org> <201002052117.35626@thufir.ingo-kloecker.de> <201002060254.55677.sebas@kde.org> Message-ID: <4B6DABC1.5070600@kde.org> On 2/6/2010 2:54 AM, Sebastian K?gler wrote: > Alright, suppose those are not blockers then. Thanks for having a look at it (both). I have just flagged another bug as a release blocker, with Thiago's blessing: https://bugs.kde.org/show_bug.cgi?id=199485 The short version is that we have to add some payload screening to KNotify to avoid a nasty crash until the issue is tackled in either Qt (not until 4.6.3 at the earliest) or D-Bus (who knows). -- Best regards, Eike Hein From sebas at kde.org Sun Feb 7 01:48:58 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Sun, 7 Feb 2010 01:48:58 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: References: <4235196.m1ciYH076x@kde.org> <201002051153.30594.sebas@kde.org> Message-ID: <201002070149.06300.sebas@kde.org> Hey, On Saturday 06 February 2010 15:11:24 Sebastian Trueg wrote: > the big problem is that I cannot reproduce this error. > Even without the patch queries work... > I need to look into that when I am back from the FOSDEM. I've re-run the converter (backups FTW!), and while the first query doesn't return anything, it now works as expected -- and is much faster as well. :) -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100207/f40e46b7/attachment.sig From sebas at kde.org Sun Feb 7 01:55:52 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Sun, 7 Feb 2010 01:55:52 +0100 Subject: [Kde-pim] Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <4B6DABC1.5070600@kde.org> References: <201002041933.25882.mueller@kde.org> <201002060254.55677.sebas@kde.org> <4B6DABC1.5070600@kde.org> Message-ID: <201002070155.54871.sebas@kde.org> Added Olivier and k-c-d to CC:, maybe someone can help here? On Saturday 06 February 2010 18:49:53 Eike Hein wrote: > On 2/6/2010 2:54 AM, Sebastian K?gler wrote: > > Alright, suppose those are not blockers then. Thanks for having a look at > > it (both). > > I have just flagged another bug as a release blocker, > with Thiago's blessing: > > https://bugs.kde.org/show_bug.cgi?id=199485 > > The short version is that we have to add some payload > screening to KNotify to avoid a nasty crash until the > issue is tackled in either Qt (not until 4.6.3 at the > earliest) or D-Bus (who knows). -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100207/55fa69f8/attachment.sig From sebas at kde.org Sun Feb 7 01:56:33 2010 From: sebas at kde.org (=?utf-8?q?Sebastian=20K=C3=BCgler?=) Date: Sun, 07 Feb 2010 00:56:33 +0000 Subject: branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage Message-ID: <1265504193.309043.29482.nullmailer@svn.kde.org> SVN commit 1086360 by sebas: Always enable full-text indexing CCMAIL:trueg at kde.org CCMAIL:release-team at kde.org M +3 -0 repository.cpp --- branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage/repository.cpp #1086359:1086360 @@ -325,6 +325,9 @@ // lower the minimum transaction log size to make sure the checkpoints are actually executed settings << Soprano::BackendSetting( "MinAutoCheckpointSize", 200000 ); + // alwyays index literals + settings << Soprano::BackendSetting( "fulltextindex", "sync" ); + return settings; } From johnflux at gmail.com Sun Feb 7 04:06:43 2010 From: johnflux at gmail.com (John Tapsell) Date: Sun, 7 Feb 2010 03:06:43 +0000 Subject: branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage In-Reply-To: <1265504193.309043.29482.nullmailer@svn.kde.org> References: <1265504193.309043.29482.nullmailer@svn.kde.org> Message-ID: <43d8ce651002061906y2e0fcdadn84a4673acbd483f7@mail.gmail.com> alwyays? :-D On 7 February 2010 00:56, Sebastian K?gler wrote: > SVN commit 1086360 by sebas: > > Always enable full-text indexing > > CCMAIL:trueg at kde.org > CCMAIL:release-team at kde.org > > > ?M ?+3 -0 ? ? ?repository.cpp > > > --- branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage/repository.cpp #1086359:1086360 > @@ -325,6 +325,9 @@ > ? ? // lower the minimum transaction log size to make sure the checkpoints are actually executed > ? ? settings << Soprano::BackendSetting( "MinAutoCheckpointSize", 200000 ); > > + ? ?// alwyays index literals > + ? ?settings << Soprano::BackendSetting( "fulltextindex", "sync" ); > + > ? ? return settings; > ?} > > _______________________________________________ > release-team mailing list > release-team at kde.org > https://mail.kde.org/mailman/listinfo/release-team > From mueller at kde.org Sun Feb 7 21:46:37 2010 From: mueller at kde.org (Dirk Mueller) Date: Sun, 7 Feb 2010 21:46:37 +0100 Subject: branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage In-Reply-To: <1265504193.309043.29482.nullmailer@svn.kde.org> References: <1265504193.309043.29482.nullmailer@svn.kde.org> Message-ID: <201002072146.37214.mueller@kde.org> On Sunday 07 February 2010, Sebastian K?gler wrote: > SVN commit 1086360 by sebas: > > Always enable full-text indexing 54b28d1ea9fc93953e1863c06d7b7780 sources/kdebase-runtime-4.4.0.tar.bz2 Greetings, Dirk From sebas at kde.org Sun Feb 7 22:50:29 2010 From: sebas at kde.org (Sebastian =?iso-8859-15?q?K=FCgler?=) Date: Sun, 7 Feb 2010 22:50:29 +0100 Subject: [Kde-pim] Fwd: Re: KDE 4.4.98 (4.4 RC3) In-Reply-To: <201002072232.29106.thiago@kde.org> References: <201002041933.25882.mueller@kde.org> <201002072211.49655.sebas@kde.org> <201002072232.29106.thiago@kde.org> Message-ID: <201002072250.30660.sebas@kde.org> On Sunday 07 February 2010 22:32:18 Thiago Macieira wrote: > Em Domingo 7. Fevereiro 2010, ?s 22.11.43, Sebastian K?gler escreveu: > > On Sunday 07 February 2010 04:31:56 Eike Hein wrote: > > > Let me re-summarize the situation for clarity: Right > > > now you have to be careful about what's inside the > > > QString you pass to KNotification, because if it con- > > > tains characters in a certain Unicode character range > > > your application will crash as a result due to D-Bus > > > closing the connection. > > > > Is this actually a regression over 4.3? > > > > If not, there's no point in holding the release back for it, since it > > doesn't affect this bug (neither positively, nor negatively). > > No, it's not a regression. Good that it doesn't get in the way of releasing 4.4.0. > However, it is a remote crash exploit. It should be fixed immediately. I fully agree of course. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100207/2e227f95/attachment.sig From tobias.gerschner at gmail.com Mon Feb 8 03:52:02 2010 From: tobias.gerschner at gmail.com (Tobias Gerschner) Date: Mon, 8 Feb 2010 15:52:02 +1300 Subject: extragear and playground translations included in l10n tarballs of kde 4.4.0 ? Message-ID: Good Afternoon, I hope this is not too off topic, but could not find a more appropriate list. According to the svn tag 4.4.0 copy the kde-l10n directory ships extragear and playground translations. I went through the previous svn tag copies and did not see these translations included before. The inclusion of these translations causes quite a few file conflicts between extragear / playground applications that do not follow the KDE SC release schedule but have their translations shipped in kde 4.4.0 . ( At least that is what it's look like from here) I tried to get some information on #kde and went through the public list archives but did not see any relevant information. A clarification would be appreciated whether it is intended to ship translations of extragear and playground applications now with the KDE SC . Thank you. -- Tobias Gerschner Yoper Linux - www.yoper.com Knowing is not enough; we must apply. Willing is not enough; we must do. From jospoortvliet at gmail.com Mon Feb 8 11:14:38 2010 From: jospoortvliet at gmail.com (Jos Poortvliet) Date: Mon, 8 Feb 2010 11:14:38 +0100 Subject: [kde-promo] release PR update In-Reply-To: <41891b251002080026g74796640k9fadc28551752103@mail.gmail.com> References: <201002052006.11223.sebas@kde.org> <41891b251002080026g74796640k9fadc28551752103@mail.gmail.com> Message-ID: <201002081114.41306.jospoortvliet@gmail.com> On Monday 08 February 2010 09:26:44 Franz Keferb?ck wrote: > Hi all, > > this is a sign of life again from me (i've been virtually dead the > last year++, not just in KDE land) and i'd like to address the "buzz" > thing. > > Out of a notion - and the fact that i couldn't look at the current > buzz.kde.org site as it kept on killing my browser I tried to use my > "spare time" to reimplement something like it again - yet cleaner and > faster. I guess I managed to, sent the results to Lydia who also > included Tom Albers in the discussion on finishing it. Nuno blessed > the Design (mostly a copy of the orignial anyways, just a couple if > details he had to check, mainly with the item's layout and design). I > made it all GPL and included the license with all source files (those > I wrote, there's also one PHP from the web > [http://pear.php.net/pepr/pepr-proposal-show.php?id=198 BSD Licensed] > and of course mootools [http://www.mootools.net MIT License] included > as they are from the original websites). The code works fairly well > and i've not yet had any real issues since the last bugs Jos > Poortvliet found where ironed out. That was what i then committed to > svn (/home/kde/trun/www/sites/buzz) as that's where TomA pointed me > to. He was noticed by Lydia about it, i'll try to catch him today to > see what's still there. > > If you want to have a look on what it is like now, point your browser > to http://www.isis-marketing.at/buzz/ > > The last issue i can see is that the icons in the top row are all the > same - which is in fact the "dot" icon from planetkde. I'd appreciate > if you could point me to the correct icons for the other websites to > be included. > > I'll be on IRC all day long today (at least till 4pm CET, maybe > longer, no long travelling or flight planning or such today), channels > #kde-promo, #oxygen, #kde-www and #kde-devel (still fkefer there ;-). > > Good to find my way back again, really, i felt SO bad already, but i > couldn't help, my private life was going down for some time, and as > that stopped my company kept sending me to all different places all > over the world, with little internet for private use yet lots of > interesting things to see... nice tradeoff, yet not for KDE. > > So "Hi, i'm trying to find my way back" to ya all (instead of bye) I think you made quite a splash coming back like this, thanks for the great work ;-) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100208/544e17f1/attachment.sig From dmuell at gmx.net Mon Feb 8 15:54:01 2010 From: dmuell at gmx.net (Dirk Mueller) Date: Mon, 8 Feb 2010 15:54:01 +0100 Subject: branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage In-Reply-To: <201002072146.37214.mueller@kde.org> References: <1265504193.309043.29482.nullmailer@svn.kde.org> <201002072146.37214.mueller@kde.org> Message-ID: <201002081554.01596.dmuell@gmx.net> On Sunday 07 February 2010, Dirk Mueller wrote: > On Sunday 07 February 2010, Sebastian K?gler wrote: > > SVN commit 1086360 by sebas: > > > > Always enable full-text indexing > > 54b28d1ea9fc93953e1863c06d7b7780 sources/kdebase-runtime-4.4.0.tar.bz2 sorry, that was wrong, correct is: 066f1de9029e237aaa75d40c3bb3fcd2 kdebase-runtime-4.4.0.tar.bz2 Greetings, Dirk From hein at kde.org Mon Feb 8 16:29:01 2010 From: hein at kde.org (Eike Hein) Date: Mon, 08 Feb 2010 16:29:01 +0100 Subject: extragear and playground translations included in l10n tarballs of kde 4.4.0 ? In-Reply-To: References: Message-ID: <4B702DBD.8030408@kde.org> On 02/08/2010 03:52 AM, Tobias Gerschner wrote: > A clarification would be appreciated whether it is intended to ship > translations of extragear and playground applications now with the KDE > SC . This only applies to the SVN tag, and was presumably done by accident. The 4.4.0 tarballs don't contain the Extragear translations and there are no plans to include them there. -- Best regards, Eike Hein From aseigo at kde.org Mon Feb 8 18:15:25 2010 From: aseigo at kde.org (=?utf-8?q?Aaron=20J=2E=20Seigo?=) Date: Mon, 08 Feb 2010 17:15:25 +0000 Subject: branches/KDE/4.4/kdebase/workspace/plasma/desktop/applets/kickoff Message-ID: <1265649325.417728.28207.nullmailer@svn.kde.org> SVN commit 1087230 by aseigo: backport r1073143: * make the reading of disk usage actually async (e.g. we return between each device check) * don't check every 10s (wtf?!), but only when requested; this moves it into the hands of the visualization what this means is that plasma sleeps more, disks are accessed less, far fewer data members in the SystemModel class and far more readable code. probably too late for 4.4.0, which is unfortunate but my fault since it fell off my "to backport" list before it was actually backported. if there is movement in the tag in kdebase for other reasons, it would be nice if this was captured as well. distributions may also want to grab it for their 4.4 packages until 4.4.1 is out. CCBUG:200184 CCMAIL:release-team at kde.org M +46 -87 core/systemmodel.cpp M +3 -4 core/systemmodel.h M +5 -2 ui/launcher.cpp --- branches/KDE/4.4/kdebase/workspace/plasma/desktop/applets/kickoff/core/systemmodel.cpp #1087229:1087230 @@ -52,21 +52,22 @@ struct UsageInfo { UsageInfo() - : used(0), - available(0), - dirty(true) {} + : used(0), + available(0) + {} quint64 used; quint64 available; - bool dirty; }; class SystemModel::Private { public: Private(SystemModel *parent) - : q(parent) - , placesModel(new KFilePlacesModel(parent)) { + : q(parent), + placesModel(new KFilePlacesModel(parent)), + currentPlacesModelUsageIndex(0) + { q->setSourceModel(placesModel); connect(placesModel, SIGNAL(dataChanged(QModelIndex, QModelIndex)), @@ -84,44 +85,15 @@ << i18n("Places") << i18n("Removable Storage") << i18n("Storage"); - loadApplications(); - connect(&refreshTimer, SIGNAL(timeout()), - q, SLOT(startRefreshingUsageInfo())); - refreshTimer.start(10000); - QTimer::singleShot(0, q, SLOT(startRefreshingUsageInfo())); connect(KSycoca::self(), SIGNAL(databaseChanged(const QStringList&)), q, SLOT(reloadApplications())); } - void queryFreeSpace(const QString& mountPoint) { - KDiskFreeSpaceInfo freeSpace = KDiskFreeSpaceInfo::freeSpaceInfo(mountPoint); - if (freeSpace.isValid()) - q->freeSpaceInfoAvailable(freeSpace.mountPoint(), freeSpace.size() / 1024, - freeSpace.used() / 1024, freeSpace.available() / 1024); - } - - void loadApplications() { - const QStringList apps = Kickoff::systemApplicationList(); - appsList.clear(); - - foreach(const QString &app, apps) { - KService::Ptr service = KService::serviceByStorageId(app); - - if (!service) { - continue; - } - - appsList << service; - } - //kDebug() << "*************" << appsList; - } - SystemModel * const q; KFilePlacesModel *placesModel; QStringList topLevelSections; KService::List appsList; - QList mountPointsQueue; QMap usageByMountpoint; - QTimer refreshTimer; + int currentPlacesModelUsageIndex; }; SystemModel::SystemModel(QObject *parent) @@ -137,7 +109,9 @@ QModelIndex SystemModel::mapFromSource(const QModelIndex &sourceIndex) const { - if (!sourceIndex.isValid()) return QModelIndex(); + if (!sourceIndex.isValid()) { + return QModelIndex(); + } QModelIndex parent; @@ -356,75 +330,60 @@ } } -void SystemModel::startRefreshingUsageInfo() +void SystemModel::refreshUsageInfo() { - if (!d->mountPointsQueue.isEmpty()) { - return; - } - - int rowCount = d->placesModel->rowCount(); - for (int i = 0; i < rowCount; ++i) { - QModelIndex index = d->placesModel->index(i, 0); - if (d->placesModel->isDevice(index)) { - Solid::Device dev = d->placesModel->deviceForIndex(index); - Solid::StorageAccess *access = dev.as(); - - if (access && !access->filePath().isEmpty()) { - d->mountPointsQueue << access->filePath(); - } - } - } - - if (!d->mountPointsQueue.isEmpty()) { - d->queryFreeSpace(d->mountPointsQueue.takeFirst()); - } + d->currentPlacesModelUsageIndex = 0; + QTimer::singleShot(100, this, SLOT(refreshNextUsageInfo())); } -void SystemModel::reloadApplications() +void SystemModel::stopRefreshingUsageInfo() { - d->loadApplications(); + d->currentPlacesModelUsageIndex = d->placesModel->rowCount(); } -void SystemModel::freeSpaceInfoAvailable(const QString& mountPoint, quint64, - quint64 kbUsed, quint64 kbAvailable) +void SystemModel::refreshNextUsageInfo() { - UsageInfo info; - info.used = kbUsed; - info.available = kbAvailable; - - d->usageByMountpoint[mountPoint] = info; - - // More to process - if (!d->mountPointsQueue.isEmpty()) { - d->queryFreeSpace(d->mountPointsQueue.takeFirst()); + if (d->currentPlacesModelUsageIndex >= d->placesModel->rowCount()) { return; } - // We're done, let's emit the changes - int rowCount = d->placesModel->rowCount(); - for (int i = 0; i < rowCount; ++i) { - QModelIndex sourceIndex = d->placesModel->index(i, 0); - if (d->placesModel->isDevice(sourceIndex)) { - Solid::Device dev = d->placesModel->deviceForIndex(sourceIndex); - Solid::StorageAccess *access = dev.as(); + QModelIndex sourceIndex = d->placesModel->index(d->currentPlacesModelUsageIndex, 0); + if (d->placesModel->isDevice(sourceIndex)) { + Solid::Device dev = d->placesModel->deviceForIndex(sourceIndex); + Solid::StorageAccess *access = dev.as(); - if (access && d->usageByMountpoint.contains(access->filePath())) { - info = d->usageByMountpoint[access->filePath()]; + if (access && !access->filePath().isEmpty()) { + KDiskFreeSpaceInfo freeSpace = KDiskFreeSpaceInfo::freeSpaceInfo(access->filePath()); + if (freeSpace.isValid()) { + UsageInfo info; + info.used = freeSpace.used() / 1024; + info.available = freeSpace.available() / 1024; - if (info.dirty) { - info.dirty = false; - d->usageByMountpoint[access->filePath()] = info; - } else { - d->usageByMountpoint.remove(access->filePath()); - } - + d->usageByMountpoint[freeSpace.mountPoint()] = info; QModelIndex index = mapFromSource(sourceIndex); emit dataChanged(index, index); } } } + + ++d->currentPlacesModelUsageIndex; + QTimer::singleShot(0, this, SLOT(refreshNextUsageInfo())); } +void SystemModel::reloadApplications() +{ + const QStringList apps = Kickoff::systemApplicationList(); + d->appsList.clear(); + + foreach (const QString &app, apps) { + KService::Ptr service = KService::serviceByStorageId(app); + + if (service) { + d->appsList << service; + } + } +} + void Kickoff::SystemModel::sourceDataChanged(const QModelIndex &start, const QModelIndex &end) { if (start.parent().isValid()) return; --- branches/KDE/4.4/kdebase/workspace/plasma/desktop/applets/kickoff/core/systemmodel.h #1087229:1087230 @@ -48,13 +48,12 @@ virtual int columnCount(const QModelIndex &parent = QModelIndex()) const; virtual QVariant data(const QModelIndex &index, int role = Qt::DisplayRole) const; virtual QVariant headerData(int section, Qt::Orientation orientation, int role = Qt::DisplayRole) const; + void refreshUsageInfo(); + void stopRefreshingUsageInfo(); private Q_SLOTS: - void startRefreshingUsageInfo(); + void refreshNextUsageInfo(); void reloadApplications(); - void freeSpaceInfoAvailable(const QString& mountPoint, quint64 kbSize, - quint64 kbUsed, quint64 kbAvailable); - void sourceDataChanged(const QModelIndex &start, const QModelIndex &end); void sourceRowsAboutToBeInserted(const QModelIndex &parent, int start, int end); void sourceRowsInserted(const QModelIndex &parent, int start, int end); --- branches/KDE/4.4/kdebase/workspace/plasma/desktop/applets/kickoff/ui/launcher.cpp #1087229:1087230 @@ -228,7 +228,7 @@ void setupSystemView() { - SystemModel *model = new SystemModel(q); + systemModel = new SystemModel(q); UrlItemView *view = new UrlItemView(); ItemDelegate *delegate = new ItemDelegate(q); delegate->setRoleMapping(Plasma::Delegate::SubTitleRole, SubTitleRole); @@ -236,7 +236,7 @@ view->setItemDelegate(delegate); view->setItemStateProvider(delegate); - addView(i18n("Computer"), systemIcon(), model, view); + addView(i18n("Computer"), systemIcon(), systemModel, view); } void setupSearchView() @@ -448,6 +448,7 @@ ApplicationModel *applicationModel; RecentlyUsedModel *recentlyUsedModel; KRunnerModel *searchModel; + SystemModel *systemModel; LeaveModel *leaveModel; SearchBar *searchBar; QWidget *footer; @@ -807,6 +808,7 @@ { Q_UNUSED(event) reset(); + d->systemModel->stopRefreshingUsageInfo(); } void Launcher::keyPressEvent(QKeyEvent *event) @@ -828,6 +830,7 @@ void Launcher::showEvent(QShowEvent *e) { d->searchBar->setFocus(); + d->systemModel->refreshUsageInfo(); QWidget::showEvent(e); } From wstephenson at kde.org Mon Feb 8 20:46:27 2010 From: wstephenson at kde.org (Will Stephenson) Date: Mon, 8 Feb 2010 20:46:27 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: References: <4235196.m1ciYH076x@kde.org> <201002051153.30594.sebas@kde.org> Message-ID: <201002082046.29589.wstephenson@kde.org> On Saturday 06 February 2010 15:11:24 Sebastian Trueg wrote: > the big problem is that I cannot reproduce this error. > Even without the patch queries work... > I need to look into that when I am back from the FOSDEM. > I can reproduce it with 4.3.98, soprano 2.3.70, virtuoso 6.1. I asked Sebas, and since he got it working he is using soprano 2.3.73 out of kdesupport trunk, not the blessed for 4.4 2.3.70 version. Is the soprano version relevant? Log extract searching for a file by file name: "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : "SQLExecDirect failed on quer y 'sparql select distinct ?r where { { { ?r ?v1 ?v2 . ?v2 bif:contains "'Bread Sauce.pdf*'" . } U NION { ?r ?v1 ?v3 . ?v3 ?v4 ?v2 . ?v4 . ?v2 bif:contains "'Bread Sauce.pdf*'" . } . { ?r a ?v5 . ?v5 . } UNION { ?r a ?v6 . ?v6 . } . } . }' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ200: Table referenced in contains does not hav e a text index)" "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : "Invalid iterator." nepomukqueryservice(3215)/nepomuk (query service) Nepomuk::Query::SearchThread::run: 5 nepomukqueryservice(3215)/nepomuk (query service) Nepomuk::Query::SearchCore::slotFinished: I am for delaying the release until this is resolved. Will > Cheers, > Sebastian > > > Hey Sebastian, > > > > On Friday 05 February 2010 09:10:36 Sebastian Trueg wrote: > >> Please try the attached patch in > >> kdebase/runtime/nepomuk/services/storage. > >> And if it helps, please apply as I am in the train all day. > >> Starting nepomuk will take a long time probably since the whole index > >> needs to be rebuilt. > > > > That doesn't seem to help. (I've only rebuilt/installed that particular > > directory.) > > The error is apparently the same still. I've attached an updated log from > > my > > nepomukserver (gave it some time to start up, the initial CPU load had > > definitely > > settled). > > > > I'll be on IRC all day and tonight, you can catch me there (or by email, > > of course). > > > >> Sebastian Trueg wrote: > >> > yeah... damn, apparently the text index is not enabled by default > >> > anymore. Still was in 6.0.x snapshots I had. > >> > This is fixed with a simple patch to the storage service though. > >> > Maybe we need to port that back to the 4.4.0 tag, too. > > > > Thanks, > > -- > > sebas > > > > http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > > _______________________________________________ > release-team mailing list > release-team at kde.org > https://mail.kde.org/mailman/listinfo/release-team From trueg at kde.org Mon Feb 8 21:39:43 2010 From: trueg at kde.org (Sebastian Trueg) Date: Mon, 08 Feb 2010 21:39:43 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <201002082046.29589.wstephenson@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002051153.30594.sebas@kde.org> <201002082046.29589.wstephenson@kde.org> Message-ID: <4B70768F.2050900@kde.org> well, the index problem already is resolved. A real showstopper is the dbus problem though.... :( http://bugreports.qt.nokia.com/browse/QTBUG-7475 Cheers, Sebastian Will Stephenson wrote: > On Saturday 06 February 2010 15:11:24 Sebastian Trueg wrote: >> the big problem is that I cannot reproduce this error. >> Even without the patch queries work... >> I need to look into that when I am back from the FOSDEM. >> > > I can reproduce it with 4.3.98, soprano 2.3.70, virtuoso 6.1. I asked Sebas, > and since he got it working he is using soprano 2.3.73 out of kdesupport > trunk, not the blessed for 4.4 2.3.70 version. Is the soprano version > relevant? > > Log extract searching for a file by file name: > > "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : > "SQLExecDirect failed on quer y 'sparql select distinct ?r where { { { ?r > ?v1 ?v2 . ?v2 bif:contains "'Bread Sauce.pdf*'" . } U NION { ?r ?v1 ?v3 . ?v3 > ?v4 ?v2 . ?v4 www.w3.org/2000/01/rdf-schema#label> . ?v2 bif:contains "'Bread Sauce.pdf*'" . > } . { ?r a ?v5 . ?v5 > . > } UNION { ?r a ?v6 . ?v6 > . } . } . > }' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ200: > Table referenced in contains does not hav e a text index)" > "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : "Invalid > iterator." > nepomukqueryservice(3215)/nepomuk (query service) > Nepomuk::Query::SearchThread::run: 5 > nepomukqueryservice(3215)/nepomuk (query service) > Nepomuk::Query::SearchCore::slotFinished: > > I am for delaying the release until this is resolved. > > > Will > >> Cheers, >> Sebastian >> >>> Hey Sebastian, >>> >>> On Friday 05 February 2010 09:10:36 Sebastian Trueg wrote: >>>> Please try the attached patch in >>>> kdebase/runtime/nepomuk/services/storage. >>>> And if it helps, please apply as I am in the train all day. >>>> Starting nepomuk will take a long time probably since the whole index >>>> needs to be rebuilt. >>> That doesn't seem to help. (I've only rebuilt/installed that particular >>> directory.) >>> The error is apparently the same still. I've attached an updated log from >>> my >>> nepomukserver (gave it some time to start up, the initial CPU load had >>> definitely >>> settled). >>> >>> I'll be on IRC all day and tonight, you can catch me there (or by email, >>> of course). >>> >>>> Sebastian Trueg wrote: >>>>> yeah... damn, apparently the text index is not enabled by default >>>>> anymore. Still was in 6.0.x snapshots I had. >>>>> This is fixed with a simple patch to the storage service though. >>>>> Maybe we need to port that back to the 4.4.0 tag, too. >>> Thanks, >>> -- >>> sebas >>> >>> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 >> _______________________________________________ >> release-team mailing list >> release-team at kde.org >> https://mail.kde.org/mailman/listinfo/release-team > From wstephenson at kde.org Mon Feb 8 22:11:17 2010 From: wstephenson at kde.org (Will Stephenson) Date: Mon, 8 Feb 2010 22:11:17 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <4B70768F.2050900@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002082046.29589.wstephenson@kde.org> <4B70768F.2050900@kde.org> Message-ID: <201002082211.17365.wstephenson@kde.org> On Monday 08 February 2010 21:39:43 you wrote: > well, the index problem already is resolved. Sorry, I should have said that I started with a clean apps/nepomuk - no conversion. If you said the index problem resolved on the basis of Sebas' experience, I'm afraid mine contradicts that. Will > A real showstopper is the dbus problem though.... :( > > http://bugreports.qt.nokia.com/browse/QTBUG-7475 Yuck. > Cheers, > Sebastian > > Will Stephenson wrote: > > On Saturday 06 February 2010 15:11:24 Sebastian Trueg wrote: > >> the big problem is that I cannot reproduce this error. > >> Even without the patch queries work... > >> I need to look into that when I am back from the FOSDEM. > > > > I can reproduce it with 4.3.98, soprano 2.3.70, virtuoso 6.1. I asked > > Sebas, and since he got it working he is using soprano 2.3.73 out of > > kdesupport trunk, not the blessed for 4.4 2.3.70 version. Is the > > soprano version relevant? > > > > Log extract searching for a file by file name: > > > > "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : > > "SQLExecDirect failed on quer y 'sparql select distinct ?r where { { { > > ?r ?v1 ?v2 . ?v2 bif:contains "'Bread Sauce.pdf*'" . } U NION { ?r ?v1 > > ?v3 . ?v3 ?v4 ?v2 . ?v4 > > > www.w3.org/2000/01/rdf-schema#label> . ?v2 bif:contains "'Bread > > Sauce.pdf*'" . } . { ?r a ?v5 . ?v5 > > > > > 03/22/nfo#FileDataObject> . } UNION { ?r a ?v6 . ?v6 > > > > . } . > > } . }' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso > > Server]SQ200: Table referenced in contains does not hav e a text > > index)" > > "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : > > "Invalid iterator." > > nepomukqueryservice(3215)/nepomuk (query service) > > Nepomuk::Query::SearchThread::run: 5 > > nepomukqueryservice(3215)/nepomuk (query service) > > Nepomuk::Query::SearchCore::slotFinished: > > > > I am for delaying the release until this is resolved. > > > > > > Will > > > >> Cheers, > >> Sebastian > >> > >>> Hey Sebastian, > >>> > >>> On Friday 05 February 2010 09:10:36 Sebastian Trueg wrote: > >>>> Please try the attached patch in > >>>> kdebase/runtime/nepomuk/services/storage. > >>>> And if it helps, please apply as I am in the train all day. > >>>> Starting nepomuk will take a long time probably since the whole index > >>>> needs to be rebuilt. > >>> > >>> That doesn't seem to help. (I've only rebuilt/installed that particular > >>> directory.) > >>> The error is apparently the same still. I've attached an updated log > >>> from my > >>> nepomukserver (gave it some time to start up, the initial CPU load had > >>> definitely > >>> settled). > >>> > >>> I'll be on IRC all day and tonight, you can catch me there (or by > >>> email, of course). > >>> > >>>> Sebastian Trueg wrote: > >>>>> yeah... damn, apparently the text index is not enabled by default > >>>>> anymore. Still was in 6.0.x snapshots I had. > >>>>> This is fixed with a simple patch to the storage service though. > >>>>> Maybe we need to port that back to the 4.4.0 tag, too. > >>> > >>> Thanks, > >>> -- > >>> sebas > >>> > >>> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > >> > >> _______________________________________________ > >> release-team mailing list > >> release-team at kde.org > >> https://mail.kde.org/mailman/listinfo/release-team From trueg at kde.org Mon Feb 8 22:30:13 2010 From: trueg at kde.org (Sebastian Trueg) Date: Mon, 08 Feb 2010 22:30:13 +0100 Subject: [Nepomuk] kde-4.4, virtuoso-6.1.0, and virtuosoconverter In-Reply-To: <201002082211.17365.wstephenson@kde.org> References: <4235196.m1ciYH076x@kde.org> <201002082046.29589.wstephenson@kde.org> <4B70768F.2050900@kde.org> <201002082211.17365.wstephenson@kde.org> Message-ID: <4B708265.9090707@kde.org> You said KDE 4.3.98 aka rc3. It is solved in trunk, the branch, and the 4.4.0 tag. Will Stephenson wrote: > On Monday 08 February 2010 21:39:43 you wrote: >> well, the index problem already is resolved. > Sorry, I should have said that I started with a clean apps/nepomuk - no > conversion. If you said the index problem resolved on the basis of Sebas' > experience, I'm afraid mine contradicts that. > > Will > >> A real showstopper is the dbus problem though.... :( >> >> http://bugreports.qt.nokia.com/browse/QTBUG-7475 > > Yuck. > > >> Cheers, >> Sebastian >> >> Will Stephenson wrote: >>> On Saturday 06 February 2010 15:11:24 Sebastian Trueg wrote: >>>> the big problem is that I cannot reproduce this error. >>>> Even without the patch queries work... >>>> I need to look into that when I am back from the FOSDEM. >>> I can reproduce it with 4.3.98, soprano 2.3.70, virtuoso 6.1. I asked >>> Sebas, and since he got it working he is using soprano 2.3.73 out of >>> kdesupport trunk, not the blessed for 4.4 2.3.70 version. Is the >>> soprano version relevant? >>> >>> Log extract searching for a file by file name: >>> >>> "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : >>> "SQLExecDirect failed on quer y 'sparql select distinct ?r where { { { >>> ?r ?v1 ?v2 . ?v2 bif:contains "'Bread Sauce.pdf*'" . } U NION { ?r ?v1 >>> ?v3 . ?v3 ?v4 ?v2 . ?v4 >>> >> www.w3.org/2000/01/rdf-schema#label> . ?v2 bif:contains "'Bread >>> Sauce.pdf*'" . } . { ?r a ?v5 . ?v5 >>> >>> >> 03/22/nfo#FileDataObject> . } UNION { ?r a ?v6 . ?v6 >>> >>> . } . >>> } . }' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso >>> Server]SQ200: Table referenced in contains does not hav e a text >>> index)" >>> "/usr/bin/nepomukservicestub(3215)" Error in thread 139951182154000 : >>> "Invalid iterator." >>> nepomukqueryservice(3215)/nepomuk (query service) >>> Nepomuk::Query::SearchThread::run: 5 >>> nepomukqueryservice(3215)/nepomuk (query service) >>> Nepomuk::Query::SearchCore::slotFinished: >>> >>> I am for delaying the release until this is resolved. >>> >>> >>> Will >>> >>>> Cheers, >>>> Sebastian >>>> >>>>> Hey Sebastian, >>>>> >>>>> On Friday 05 February 2010 09:10:36 Sebastian Trueg wrote: >>>>>> Please try the attached patch in >>>>>> kdebase/runtime/nepomuk/services/storage. >>>>>> And if it helps, please apply as I am in the train all day. >>>>>> Starting nepomuk will take a long time probably since the whole index >>>>>> needs to be rebuilt. >>>>> That doesn't seem to help. (I've only rebuilt/installed that particular >>>>> directory.) >>>>> The error is apparently the same still. I've attached an updated log >>>>> from my >>>>> nepomukserver (gave it some time to start up, the initial CPU load had >>>>> definitely >>>>> settled). >>>>> >>>>> I'll be on IRC all day and tonight, you can catch me there (or by >>>>> email, of course). >>>>> >>>>>> Sebastian Trueg wrote: >>>>>>> yeah... damn, apparently the text index is not enabled by default >>>>>>> anymore. Still was in 6.0.x snapshots I had. >>>>>>> This is fixed with a simple patch to the storage service though. >>>>>>> Maybe we need to port that back to the 4.4.0 tag, too. >>>>> Thanks, >>>>> -- >>>>> sebas >>>>> >>>>> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 >>>> _______________________________________________ >>>> release-team mailing list >>>> release-team at kde.org >>>> https://mail.kde.org/mailman/listinfo/release-team > From faure at kde.org Tue Feb 9 09:39:49 2010 From: faure at kde.org (David Faure) Date: Tue, 9 Feb 2010 09:39:49 +0100 Subject: showstoppers Message-ID: <201002090939.49746.faure@kde.org> - The dbus registration leak (with nepomuk as prime suspect), possibly due to r1084698, cf the thread from that commit. No fix yet. - The polkit-qt-1 fix (r1086506). -- David Faure, faure at kde.org, http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org). From toma at kde.org Tue Feb 9 09:46:02 2010 From: toma at kde.org (Tom Albers) Date: Tue, 09 Feb 2010 09:46:02 +0100 Subject: showstoppers In-Reply-To: <201002090939.49746.faure@kde.org> Message-ID: <1288799.ue6dHzlSxI@kde.org> Op Tuesday 9 February 2010 09:39 schreef u: > - The dbus registration leak (with nepomuk as prime suspect), possibly > due to r1084698, cf the thread from that commit. No fix yet. Is there a bugreport where i can read more about this? Who is working on it? Solutions? Revert the commit? > - The polkit-qt-1 fix (r1086506). The latest tarball has that fix afaik: 6ee8c548e42b0bb65ebc4752c2493cc2 kdelibs-4.4.0.tar.bz2 Best, Toma From faure at kde.org Tue Feb 9 10:01:18 2010 From: faure at kde.org (David Faure) Date: Tue, 9 Feb 2010 10:01:18 +0100 Subject: showstoppers In-Reply-To: <1288799.ue6dHzlSxI@kde.org> References: <1288799.ue6dHzlSxI@kde.org> Message-ID: <201002091001.18739.faure@kde.org> On Tuesday 09 February 2010, Tom Albers wrote: > Op Tuesday 9 February 2010 09:39 schreef u: > > - The dbus registration leak (with nepomuk as prime suspect), possibly > > due to r1084698, cf the thread from that commit. No fix yet. > > Is there a bugreport where i can read more about this? > Who is working on it? Solutions? Revert the commit? http://lists.kde.org/?l=kde-commits&m=126535646013735&w=2 (plus "next thread" three times) -- David Faure, faure at kde.org, http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org). From johnflux at gmail.com Tue Feb 9 10:05:14 2010 From: johnflux at gmail.com (John Tapsell) Date: Tue, 9 Feb 2010 09:05:14 +0000 Subject: showstoppers In-Reply-To: <201002090939.49746.faure@kde.org> References: <201002090939.49746.faure@kde.org> Message-ID: <43d8ce651002090105k70346df4j92142ef81947767b@mail.gmail.com> On 9 February 2010 08:39, David Faure wrote: > - The dbus registration leak (with nepomuk as prime suspect), possibly > due to r1084698, cf the thread from that commit. No fix yet. > > - The polkit-qt-1 fix (r1086506). What about the transmitting-reserved-utf8-characters crash? I thought we agreed that that was a showstopper as well? https://bugs.kde.org/show_bug.cgi?id=199485 John From sebas at kde.org Tue Feb 9 10:26:05 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Tue, 9 Feb 2010 10:26:05 +0100 Subject: showstoppers In-Reply-To: <43d8ce651002090105k70346df4j92142ef81947767b@mail.gmail.com> References: <201002090939.49746.faure@kde.org> <43d8ce651002090105k70346df4j92142ef81947767b@mail.gmail.com> Message-ID: <201002091026.07321.sebas@kde.org> On Tuesday 09 February 2010 10:05:14 John Tapsell wrote: > On 9 February 2010 08:39, David Faure wrote: > > - The dbus registration leak (with nepomuk as prime suspect), possibly > > due to r1084698, cf the thread from that commit. No fix yet. > > > > - The polkit-qt-1 fix (r1086506). > > What about the transmitting-reserved-utf8-characters crash? I thought > we agreed that that was a showstopper as well? > https://bugs.kde.org/show_bug.cgi?id=199485 We didn't. It's not a regression over 4.3, so no use in holding the release back for that one. It needs fixing nevertheless, of course. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From arekm at maven.pl Sun Feb 7 21:56:27 2010 From: arekm at maven.pl (Arkadiusz Miskiewicz) Date: Sun, 7 Feb 2010 21:56:27 +0100 Subject: branches/KDE/4.4/kdebase/runtime/nepomuk/services/storage In-Reply-To: <201002072146.37214.mueller@kde.org> References: <1265504193.309043.29482.nullmailer@svn.kde.org> <201002072146.37214.mueller@kde.org> Message-ID: <201002072156.27645.arekm@maven.pl> On Sunday 07 of February 2010, Dirk Mueller wrote: > On Sunday 07 February 2010, Sebastian K?gler wrote: > > SVN commit 1086360 by sebas: > > > > Always enable full-text indexing > > 54b28d1ea9fc93953e1863c06d7b7780 sources/kdebase-runtime-4.4.0.tar.bz2 This is the same tarball that was announced at 5 feb. Doesn't sound right. > Greetings, > Dirk -- Arkadiusz Mi?kiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/ From franz.keferboeck at gmail.com Mon Feb 8 09:26:44 2010 From: franz.keferboeck at gmail.com (=?ISO-8859-1?Q?Franz_Keferb=F6ck?=) Date: Mon, 8 Feb 2010 09:26:44 +0100 Subject: [kde-promo] release PR update In-Reply-To: <201002052006.11223.sebas@kde.org> References: <201002052006.11223.sebas@kde.org> Message-ID: <41891b251002080026g74796640k9fadc28551752103@mail.gmail.com> Hi all, this is a sign of life again from me (i've been virtually dead the last year++, not just in KDE land) and i'd like to address the "buzz" thing. Out of a notion - and the fact that i couldn't look at the current buzz.kde.org site as it kept on killing my browser I tried to use my "spare time" to reimplement something like it again - yet cleaner and faster. I guess I managed to, sent the results to Lydia who also included Tom Albers in the discussion on finishing it. Nuno blessed the Design (mostly a copy of the orignial anyways, just a couple if details he had to check, mainly with the item's layout and design). I made it all GPL and included the license with all source files (those I wrote, there's also one PHP from the web [http://pear.php.net/pepr/pepr-proposal-show.php?id=198 BSD Licensed] and of course mootools [http://www.mootools.net MIT License] included as they are from the original websites). The code works fairly well and i've not yet had any real issues since the last bugs Jos Poortvliet found where ironed out. That was what i then committed to svn (/home/kde/trun/www/sites/buzz) as that's where TomA pointed me to. He was noticed by Lydia about it, i'll try to catch him today to see what's still there. If you want to have a look on what it is like now, point your browser to http://www.isis-marketing.at/buzz/ The last issue i can see is that the icons in the top row are all the same - which is in fact the "dot" icon from planetkde. I'd appreciate if you could point me to the correct icons for the other websites to be included. I'll be on IRC all day long today (at least till 4pm CET, maybe longer, no long travelling or flight planning or such today), channels #kde-promo, #oxygen, #kde-www and #kde-devel (still fkefer there ;-). Good to find my way back again, really, i felt SO bad already, but i couldn't help, my private life was going down for some time, and as that stopped my company kept sending me to all different places all over the world, with little internet for private use yet lots of interesting things to see... nice tradeoff, yet not for KDE. So "Hi, i'm trying to find my way back" to ya all (instead of bye) On 5 February 2010 20:06, Sebastian K?gler wrote: > Hi, > > A quick update on where we stand, release-PR-wise. The release announcement itself is > done, and now being translated by various local teams, the first translations are > already trickling in. I've sent a scoop (announcement text, screenshots, screencasts) > out to our press two days ago, so that those people get some time to prepare their > coverage, there was some feedback that it's useful already -- good. > > Meanwhile, Lydia and Alexandra are preparing our social networks campaign. > buzz.kde.org will again feature a micro-blogging lifestream. (I'm not 100% up to date > about the status here, but assume "on schedule"). > > The webteam is cracking away at the new website, which will be released shortly > before the 4.4.0 release, so we're getting it all in a whole new fresh look, and what > is more important: with a lot of updated, rewritten and better structured content > around it. > > We're also still working on a more detailed visual feature guide, so people who want > more in-depth, from the source information about KDE 4.4 can get some. The text is > mostly there (g-docs), it's being html-ified and brushed up now. > > I think things are looking rather good. Thanks everybody involved for the hard work! > > Cheers, > -- > sebas > > http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > > _______________________________________________ > This message is from the kde-promo mailing list. > > Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription. > -- Franz Keferb?ck Phone: +43 650 86 22 555 http://franz.keferboeck.info | http://www.kde.org From mail at milianw.de Mon Feb 8 20:43:16 2010 From: mail at milianw.de (Milian Wolff) Date: Mon, 8 Feb 2010 20:43:16 +0100 Subject: Last-Minute API-Change to 4.4 Kate Interface possible? Message-ID: <201002082043.16524.mail@milianw.de> Hello Team! I sadly have to admit that I messed up a new API in the HighlightInterface for Kate which was not spotted in the review period until just now by Jowenn: KTextEditor::Document has the methods mode() and modes() and also highlightingMode() and highlightingModes() the new Interface now has currently the two methods embeddedModes() and modeAt() These two should be renamed to embeddedHighlightingModes() and highlightingModeAt() Would this still be possible or is the change too minor to justify this last- minute hickup? See Patch attached. If it doesn't get in I'll simply deprecate the Interface for 4.5 and do it properly then. It's just a huge inconvenience for anybody (== Developer) that would like to use the new API. As you can see it is very confusing already (it got me already while implementing it :D) and I don't want to make it even more confusing with the new Interface I'm really sorry! Maybe if something more important turns up that also requires a change, you could push this one in as well? Anyway... I just wanted to try! Good night -- Milian Wolff mail at milianw.de http://milianw.de -------------- next part -------------- A non-text attachment was scrubbed... Name: highlightingModes-HighlightInterface-rename.patch Type: text/x-patch Size: 2740 bytes Desc: not available Url : http://mail.kde.org/pipermail/release-team/attachments/20100208/65cbb195/attachment-0001.patch -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100208/65cbb195/attachment-0001.sig From drf54321 at gmail.com Mon Feb 8 21:05:13 2010 From: drf54321 at gmail.com (Dario Freddi) Date: Mon, 8 Feb 2010 21:05:13 +0100 Subject: Porting r1086506 to 4.4.0 tag Message-ID: <201002082105.13751.drf54321@gmail.com> As in the subject. The commit above (r1086506) is critical for KAuth + polkit- qt-1 to work, and it should be ported to 4.4.0 tag before release. See the commit log message. Thanks, -- ------------------- Dario Freddi KDE Developer GPG Key Signature: 511A9A3B -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100208/ad9f12f4/attachment.sig From johnflux at gmail.com Tue Feb 9 10:37:55 2010 From: johnflux at gmail.com (John Tapsell) Date: Tue, 9 Feb 2010 09:37:55 +0000 Subject: showstoppers In-Reply-To: <201002091026.07321.sebas@kde.org> References: <201002090939.49746.faure@kde.org> <43d8ce651002090105k70346df4j92142ef81947767b@mail.gmail.com> <201002091026.07321.sebas@kde.org> Message-ID: <43d8ce651002090137kbafdc4bg11a44398f5a05cbd@mail.gmail.com> On 9 February 2010 09:26, Sebastian K?gler wrote: > On Tuesday 09 February 2010 10:05:14 John Tapsell wrote: >> On 9 February 2010 08:39, David Faure wrote: >> > - The dbus registration leak (with nepomuk as prime suspect), possibly >> > due to r1084698, cf the thread from that commit. No fix yet. >> > >> > - The polkit-qt-1 fix (r1086506). >> >> What about the transmitting-reserved-utf8-characters crash? ?I thought >> we agreed that that was a showstopper as well? >> https://bugs.kde.org/show_bug.cgi?id=199485 > > We didn't. It's not a regression over 4.3, so no use in holding the release back for > that one. It needs fixing nevertheless, of course. I object to this way of thinking. Such an easy remote-exploit should not be allowed - especially one that seems straight forward to fix. John From faure at kde.org Tue Feb 9 10:59:20 2010 From: faure at kde.org (David Faure) Date: Tue, 09 Feb 2010 09:59:20 +0000 Subject: kdesupport/akonadi/server/src/search Message-ID: <1265709560.077355.13997.nullmailer@svn.kde.org> SVN commit 1087524 by dfaure: Fix the dbus connection leak (every time I switched mails in kmail, a new dbus connection would be made and would stay). Sorry for suspecting r1084698, it was not guilty. The bug -was- related to nepomuk, but wasn't -in- nepomuk :-) CCMAIL: sebastian at trueg.de, release-team at kde.org, thiago at kde.org M +1 -0 queryserviceclient.cpp --- trunk/kdesupport/akonadi/server/src/search/queryserviceclient.cpp #1087523:1087524 @@ -143,6 +143,7 @@ Nepomuk::Search::QueryServiceClient::~QueryServiceClient() { + delete d->queryServiceInterface; close(); delete d; } From toma at kde.org Tue Feb 9 11:06:25 2010 From: toma at kde.org (Tom Albers) Date: Tue, 09 Feb 2010 11:06:25 +0100 Subject: Porting r1086506 to 4.4.0 tag In-Reply-To: <201002082105.13751.drf54321@gmail.com> Message-ID: <2331795.R049rQrLto@kde.org> PleasOp Monday 8 February 2010 21:05 schreef u: > As in the subject. The commit above (r1086506) is critical for KAuth + polkit- > qt-1 to work, and it should be ported to 4.4.0 tag before release. See the > commit log message. > > Thanks, Can you please check if the tag contains the fix? AFIACS this is already in the tarballs... Best, Toma From mueller at kde.org Tue Feb 9 11:10:00 2010 From: mueller at kde.org (Dirk Mueller) Date: Tue, 9 Feb 2010 11:10:00 +0100 Subject: Porting r1086506 to 4.4.0 tag In-Reply-To: <201002082105.13751.drf54321@gmail.com> References: <201002082105.13751.drf54321@gmail.com> Message-ID: <201002091110.00644.mueller@kde.org> On Monday 08 February 2010, Dario Freddi wrote: > As in the subject. The commit above (r1086506) is critical for KAuth + > polkit- qt-1 to work, and it should be ported to 4.4.0 tag before release. > See the commit log message. I've added it to the tarball now, thanks for your notification. Greetings, Dirk From mueller at kde.org Tue Feb 9 11:17:22 2010 From: mueller at kde.org (Dirk Mueller) Date: Tue, 9 Feb 2010 11:17:22 +0100 Subject: showstoppers In-Reply-To: <43d8ce651002090137kbafdc4bg11a44398f5a05cbd@mail.gmail.com> References: <201002090939.49746.faure@kde.org> <201002091026.07321.sebas@kde.org> <43d8ce651002090137kbafdc4bg11a44398f5a05cbd@mail.gmail.com> Message-ID: <201002091117.22494.mueller@kde.org> On Tuesday 09 February 2010, John Tapsell wrote: > >> What about the transmitting-reserved-utf8-characters crash? I thought > >> we agreed that that was a showstopper as well? > >> https://bugs.kde.org/show_bug.cgi?id=199485 > > We didn't. It's not a regression over 4.3, so no use in holding the > > release back for that one. It needs fixing nevertheless, of course. > > I object to this way of thinking. Such an easy remote-exploit should > not be allowed - especially one that seems straight forward to fix. Hi, the bugreport you mention is about a krunner crash that has no patch attached. are we talking about the same thing? Greetings, Dirk From johnflux at gmail.com Tue Feb 9 11:33:03 2010 From: johnflux at gmail.com (John Tapsell) Date: Tue, 9 Feb 2010 10:33:03 +0000 Subject: showstoppers In-Reply-To: <201002091117.22494.mueller@kde.org> References: <201002090939.49746.faure@kde.org> <201002091026.07321.sebas@kde.org> <43d8ce651002090137kbafdc4bg11a44398f5a05cbd@mail.gmail.com> <201002091117.22494.mueller@kde.org> Message-ID: <43d8ce651002090233scc07c40uab4d716d8c9e5538@mail.gmail.com> On 9 February 2010 10:17, Dirk Mueller wrote: > On Tuesday 09 February 2010, John Tapsell wrote: > >> >> What about the transmitting-reserved-utf8-characters crash? ?I thought >> >> we agreed that that was a showstopper as well? >> >> https://bugs.kde.org/show_bug.cgi?id=199485 >> > We didn't. It's not a regression over 4.3, so no use in holding the >> > release back for that one. It needs fixing nevertheless, of course. >> >> I object to this way of thinking. ?Such an easy remote-exploit should >> not be allowed - especially one that seems straight forward to fix. > > Hi, > > the bugreport you mention is about a krunner crash that has no patch attached. > are we talking about the same thing? Yes - note that the bug has the keywords "kde-4.4.0-blocker", signed off by Thiago. Although the more "useful" bug report is actually http://bugs.kde.org/show_bug.cgi?id=219985 which has been fixed on konversation side, but not on the knotify side. From faure at kde.org Tue Feb 9 11:53:58 2010 From: faure at kde.org (David Faure) Date: Tue, 09 Feb 2010 10:53:58 +0000 Subject: kdesupport/akonadi/server/src/search Message-ID: <1265712838.400716.24175.nullmailer@svn.kde.org> SVN commit 1087546 by dfaure: And now the real fix for the dbus connection leak problem :/ Next step: doing the same (but not the same) in kdelibs/nepomuk. But at least the akonadiserver leak (triggered by kmail) is fixed by this. CCMAIL: release-team at kde.org M +23 -10 queryserviceclient.cpp --- trunk/kdesupport/akonadi/server/src/search/queryserviceclient.cpp #1087545:1087546 @@ -40,21 +40,34 @@ { public: QDBusConnectionPerThreadHelper() - : m_counter( 0 ) { + : m_connection( QDBusConnection::connectToBus( + QDBusConnection::SessionBus, + QString::fromLatin1("NepomukQueryServiceConnection%1").arg(newNumber()) ) ) + { } - - QDBusConnection newConnection() { - QMutexLocker lock( &m_mutex ); - return QDBusConnection::connectToBus( QDBusConnection::SessionBus, - QString::fromLatin1("NepomukQueryServiceConnection%1").arg(++m_counter) ); + ~QDBusConnectionPerThreadHelper() { + QDBusConnection::disconnectFromBus( m_connection.name() ); } + static QDBusConnection threadConnection(); + private: - int m_counter; - QMutex m_mutex; + int newNumber() { + return m_counter.fetchAndAddAcquire(1); + } + QAtomicInt m_counter; + QDBusConnection m_connection; }; - Q_GLOBAL_STATIC(QDBusConnectionPerThreadHelper, s_globalDBusConnectionPerThreadHelper) + QThreadStorage s_perThreadConnection; + + QDBusConnection QDBusConnectionPerThreadHelper::threadConnection() + { + if (!s_perThreadConnection.hasLocalData()) { + s_perThreadConnection.setLocalData(new QDBusConnectionPerThreadHelper); + } + return s_perThreadConnection.localData()->m_connection; + } } @@ -64,7 +77,7 @@ Private() : queryServiceInterface( 0 ), queryInterface( 0 ), - dbusConnection( s_globalDBusConnectionPerThreadHelper()->newConnection() ), + dbusConnection( QDBusConnectionPerThreadHelper::threadConnection() ), loop( 0 ) { } From sebas at kde.org Tue Feb 9 12:22:37 2010 From: sebas at kde.org (Sebastian =?utf-8?q?K=C3=BCgler?=) Date: Tue, 9 Feb 2010 12:22:37 +0100 Subject: showstoppers In-Reply-To: <43d8ce651002090233scc07c40uab4d716d8c9e5538@mail.gmail.com> References: <201002090939.49746.faure@kde.org> <201002091117.22494.mueller@kde.org> <43d8ce651002090233scc07c40uab4d716d8c9e5538@mail.gmail.com> Message-ID: <201002091222.40152.sebas@kde.org> On Tuesday 09 February 2010 11:33:03 John Tapsell wrote: > On 9 February 2010 10:17, Dirk Mueller wrote: > > On Tuesday 09 February 2010, John Tapsell wrote: > >> >> What about the transmitting-reserved-utf8-characters crash? I > >> >> thought we agreed that that was a showstopper as well? > >> >> https://bugs.kde.org/show_bug.cgi?id=199485 > >> > > >> > We didn't. It's not a regression over 4.3, so no use in holding the > >> > release back for that one. It needs fixing nevertheless, of course. > >> > >> I object to this way of thinking. Such an easy remote-exploit should > >> not be allowed - especially one that seems straight forward to fix. > > the bugreport you mention is about a krunner crash that has no patch > > attached. are we talking about the same thing? > > Yes - note that the bug has the keywords "kde-4.4.0-blocker", signed > off by Thiago. Although the more "useful" bug report is actually > http://bugs.kde.org/show_bug.cgi?id=219985 which has been fixed on > konversation side, but not on the knotify side. Note that I fully agree that it needs fixing ASAP, but it just makes no sense to hold up 4.4.0 for it, as it's not a regression. Not releasing 4.4.0 now does not have any influence on fixing this bug. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 From faure at kde.org Tue Feb 9 12:26:06 2010 From: faure at kde.org (David Faure) Date: Tue, 9 Feb 2010 12:26:06 +0100 Subject: showstoppers In-Reply-To: <201002091001.18739.faure@kde.org> References: <1288799.ue6dHzlSxI@kde.org> <201002091001.18739.faure@kde.org> Message-ID: <201002091226.07115.faure@kde.org> On Tuesday 09 February 2010, David Faure wrote: > On Tuesday 09 February 2010, Tom Albers wrote: > > Op Tuesday 9 February 2010 09:39 schreef u: > > > - The dbus registration leak (with nepomuk as prime suspect), possibly > > > due to r1084698, cf the thread from that commit. No fix yet. > > > > Is there a bugreport where i can read more about this? > > Who is working on it? Solutions? Revert the commit? > > http://lists.kde.org/?l=kde-commits&m=126535646013735&w=2 > (plus "next thread" three times) OK here's the final status on this issue (sorry for the confusing emails I previously sent or cc'ed). For KDE-SC-4.4.0, we need * a 1.3.1 akonadi release that contains r1087546 (Volker is working on this) * a kdelibs tarball that includes r1087561 (and merging that commit to the tag of course, I'll let Dirk do that) -- David Faure, faure at kde.org, http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org). From vkrause at kde.org Tue Feb 9 12:38:00 2010 From: vkrause at kde.org (Volker Krause) Date: Tue, 9 Feb 2010 12:38:00 +0100 Subject: kdesupport/akonadi/server/src/search In-Reply-To: <1265712838.400716.24175.nullmailer@svn.kde.org> References: <1265712838.400716.24175.nullmailer@svn.kde.org> Message-ID: <201002091238.11079.vkrause@kde.org> On Tuesday 09 February 2010 11:53:58 David Faure wrote: > SVN commit 1087546 by dfaure: > > And now the real fix for the dbus connection leak problem :/ > > Next step: doing the same (but not the same) in kdelibs/nepomuk. > But at least the akonadiserver leak (triggered by kmail) is fixed by this. there is a new Akonadi server release containing these fixes, version 1.3.1, to be found on http://download.akonadi-project.org/, as usual. regards Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100209/399197c0/attachment.sig From mueller at kde.org Tue Feb 9 13:37:46 2010 From: mueller at kde.org (Dirk Mueller) Date: Tue, 9 Feb 2010 13:37:46 +0100 Subject: Last minute KDE 4.4.0 tarball update (kdelibs) Message-ID: <201002091337.46843.mueller@kde.org> Hi, to fix a severe dbus connection leak and a BIC api problem in highlighterinterface we've decided on irc after a long discussion to update kdelibs again: 957bca85de744a9ddd316fd85e882b40 kdelibs-4.4.0.tar.bz2 Sorry for the last minute changes, and thanks to all who helped with this. Greetings, Dirk From sebas at kde.org Tue Feb 9 15:05:56 2010 From: sebas at kde.org (=?utf-8?q?Sebastian=20K=C3=BCgler?=) Date: Tue, 09 Feb 2010 14:05:56 +0000 Subject: www/sites/www Message-ID: <1265724356.536189.19062.nullmailer@svn.kde.org> SVN commit 1087757 by sebas: Release KDE Software Compilation 4.4.0 Congrats, everyone! CCMAIL:release-team at kde.org M +7 -6 announcements/4.4/index-sl.php M +0 -4 announcements/4.4/index.php M +6 -0 announcements/index.php M +4 -4 index.php M +4 -2 info/releases.php --- trunk/www/sites/www/announcements/4.4/index-sl.php #1087756:1087757 @@ -94,7 +94,7 @@ Vmesnik GetHotNewStuff je bil v tej izdaji KDE Software Compilation mo?no izbolj?an. To ogrodje je bilo na?rtovano z vizijo, da bi ogromni skupnosti prispevkarjev v KDE olaj?al povezovanje z milijoni uporabniki njihovih prispevkov. Uporabniki lahko s pomo?jo GetHotNewStuff neposredno iz samega programa prenesejo nove stopnje za KAtomic in druge igre, nove kataloge nebesnih objektov za KStars, ali pa skripte, ki dodajo nove funkcije. V tej izdaji so dodane nove dru?abne zmo?nosti, kot sta na primer komentiranje in ocenjevanje prispevka. Uporabnik pa lahko postane tudi obo?evalec prispevka, kar pomeni, da bo uporabnik v gradniku Aktivnost openDesktop za ta prispevek lahko videl posodobitve. Uporabniki lahko iz ve? programov svoje sadove ustvarjanja po?ljejo kar neposredno, brez porebe po dolgo?asnem procesu pakiranja in ro?nega po?iljanja na spletno stran.
  • - V tej izdaji sta obrodila sadove ?e dva dolgoro?na projekta skupnosti KDE. Nepomuk, mednarodni raziskovalni projekt na temo semanti?nega namizja, ki ga financira Evropska Unija, je kon?no postal dovolj stabilen in hiter za uporabo. Integracija namiznega iskanja v upravljalnik datotek Dolphin uporablja Nepomuk in je uporabniku v pomo? pri iskanju in organiziranju datotek. Novi ?asovni prikaz nedavno uporabljene datoteke prika?e razvr??ene po ?asu. Ekipa KDE PIM je prenovila svoj prvi program, tako da le ta sedaj uporablja sistem Akonadi za hranjenje in pridobivanje podatkov. KDE-jev adresar je bil napisan na novo in je sedaj razdeljen na 3 podokna, z mo?nostjo preklopa na zelo preprost izgled. Obse?nej?i prenos preostalih programov na te nove tehnologije bo na voljo v prihodnjih izdajah KDE Software Compilation. + V tej izdaji sta obrodila sadove ?e dva dolgoro?na projekta skupnosti KDE. Nepomuk, mednarodni raziskovalni projekt na temo semanti?nega namizja, ki ga financira Evropska Unija, je kon?no postal dovolj stabilen in hiter za uporabo. Integracija namiznega iskanja v upravljalnik datotek Dolphin uporablja Nepomuk in je uporabniku v pomo? pri iskanju in organiziranju datotek. Novi ?asovni prikaz nedavno uporabljene datoteke prika?e razvr??ene po ?asu. Ekipa KDE PIM je prenovila svoj prvi program, tako da le ta sedaj uporablja sistem Akonadi za hranjenje in pridobivanje podatkov. KDE-jev adresar je bil napisan na novo in je sedaj razdeljen na 3 podokna, z mo?nostjo preklopa na zelo preprost izgled. Obse?nej?i prenos preostalih programov na te nove tehnologije bo na voljo v prihodnjih izdajah KDE Software Compilation.
  • Poleg integracije prej omenjenih tehnologij so razvijalske ekipe na ve? na?inov izbolj?ale svoje programe. KGet je dobil podporo za preverjanje digitalnih podpisov in prena?anje datotek iz ve?ih virov hkrati. Gwenview sedaj premore orodje za uva?anje fotografij, ki je preprosto za uporabo. V tej izdaji so na voljo tudi povsem novi ali prenovljeni programi. Palapeli je igra, v kateri na svojem ra?unalniku sestavljate sliko, ki je razrezana na ko??ke. Uporabniki lahko ustvarijo in na spletu delijo tudi sestavljanke, ki jih ustvarijo sami. Cantor je preprost in intuitiven vmesnik za zmogljivo statisti?no in znanstveno programsko opremo (R, SAGE in Maxima). Rocs je ?tudentom v pomo? pri u?enju teorije grafov. V zbirko KDE PIM je bil dodan program Blogilo za pisanje spletnih dnevnikov (blogov). @@ -159,21 +159,21 @@ Reddit - Twitter + Twitter - Identi.ca + Identi.ca - Flickr + Flickr Youtube - Facebook + Facebook del.icio.us @@ -184,6 +184,7 @@ +

    Namestitev KDE SC 4.4.0

    @@ -218,6 +219,6 @@

    Stiki z mediji

    --- trunk/www/sites/www/announcements/4.4/index.php #1087756:1087757 @@ -1,8 +1,4 @@

    + +9th February 2010 - KDE SC 4.4.0 Released +
    +"KDE Ships New KDE SC 4.4.0." +

    + 1st February 2010 - KDE SC 4.4 RC3 Released
    --- trunk/www/sites/www/index.php #1087756:1087757 @@ -12,12 +12,12 @@ $page_title = "Experience Freedom!"; $templatepath = "chihuahua/"; $teaser = true; -include "header.inc"; +include "header.inc"; ?>

    Get KDE Software

    - +

    Latest News

    Read More

    @@ -52,8 +52,8 @@

    -KDE Software Compilation 4.4 Release Candidate 3 released
    -On 1st February 2010, KDE Software Compilation 4.4 RC3 was released. KDE SC 4.4 RC3 is the third release candidate of a new major release in the KDE 4 series, aimed at testers to identify show-stopper bugs.

    +KDE Software Compilation 4.4.0 Released
    +On 9th February 2010, KDE Software Compilation 4.4.0 was released. KDE Software Compilation 4.4.0 introduces a new netbook interface, native window tabbing and the KAuth authentication Framework, among other improvements and new applications.

    KDE Software Compilation 4.3.5 released
    --- trunk/www/sites/www/info/releases.php #1087756:1087757 @@ -8,7 +8,7 @@

    Current KDE Releases

    -KDE 4.3.5 (stable version, suitable for everyone) +KDE 4.4.0 (stable version, suitable for everyone)

    @@ -16,13 +16,15 @@ very conservative users, but showing its age)

    +

    Previous KDE Releases

      +
    • KDE 4.3.5
    • KDE 4.3.4
    • KDE 4.3.3
    • KDE 4.3.2
    • From aacid at kde.org Wed Feb 10 01:12:53 2010 From: aacid at kde.org (Albert Astals Cid) Date: Wed, 10 Feb 2010 00:12:53 +0000 Subject: extragear and playground translations included in l10n tarballs of kde 4.4.0 ? In-Reply-To: <4B702DBD.8030408@kde.org> References: <4B702DBD.8030408@kde.org> Message-ID: <201002100012.53423.aacid@kde.org> A Dilluns, 8 de febrer de 2010, Eike Hein va escriure: > On 02/08/2010 03:52 AM, Tobias Gerschner wrote: > > A clarification would be appreciated whether it is intended to ship > > translations of extragear and playground applications now with the KDE > > SC . > > This only applies to the SVN tag, and was presumably done > by accident. The 4.4.0 tarballs don't contain the Extragear > translations and there are no plans to include them there. > Dirk are you going to fix this or want me to do it? Albert From tobias.gerschner at gmail.com Wed Feb 10 01:18:41 2010 From: tobias.gerschner at gmail.com (Tobias Gerschner) Date: Wed, 10 Feb 2010 13:18:41 +1300 Subject: extragear and playground translations included in l10n tarballs of kde 4.4.0 ? In-Reply-To: <4B702DBD.8030408@kde.org> References: <4B702DBD.8030408@kde.org> Message-ID: 2010/2/9 Eike Hein : > On 02/08/2010 03:52 AM, Tobias Gerschner wrote: >> A clarification would be appreciated whether it is intended to ship >> translations of extragear and playground applications now with the KDE >> SC . > > This only applies to the SVN tag, and was presumably done > by accident. The 4.4.0 tarballs don't contain the Extragear > translations and there are no plans to include them there. > Hi Eike, Thanks for the clarification. All sorted now here. -- Tobias Gerschner Yoper Linux - www.yoper.com Knowing is not enough; we must apply. Willing is not enough; we must do. From sebastian at trueg.de Tue Feb 9 11:10:59 2010 From: sebastian at trueg.de (Sebastian Trueg) Date: Tue, 09 Feb 2010 10:10:59 +0000 Subject: KDE/kdelibs/nepomuk/query Message-ID: <1265710259.107695.15109.nullmailer@svn.kde.org> SVN commit 1087529 by trueg: Ported mem/dbus connection leak from Akonadi. CCMAIL: faure at kde.org, release-team at kde.org, thiago at kde.org M +1 -0 queryserviceclient.cpp --- trunk/KDE/kdelibs/nepomuk/query/queryserviceclient.cpp #1087528:1087529 @@ -177,6 +177,7 @@ Nepomuk::Query::QueryServiceClient::~QueryServiceClient() { close(); + delete d->queryServiceInterface; delete d; } From sebastian at trueg.de Tue Feb 9 11:11:27 2010 From: sebastian at trueg.de (Sebastian Trueg) Date: Tue, 09 Feb 2010 10:11:27 +0000 Subject: branches/KDE/4.4/kdelibs/nepomuk/query Message-ID: <1265710287.741250.15190.nullmailer@svn.kde.org> SVN commit 1087530 by trueg: Backport of mem/dbus connection leak. CCMAIL: faure at kde.org, release-team at kde.org, thiago at kde.org M +1 -0 queryserviceclient.cpp --- branches/KDE/4.4/kdelibs/nepomuk/query/queryserviceclient.cpp #1087529:1087530 @@ -177,6 +177,7 @@ Nepomuk::Query::QueryServiceClient::~QueryServiceClient() { close(); + delete d->queryServiceInterface; delete d; } From bald at smail.ee Tue Feb 9 15:15:23 2010 From: bald at smail.ee (Marek Laane) Date: Tue, 9 Feb 2010 16:15:23 +0200 Subject: www/sites/www In-Reply-To: <1265724356.536189.19062.nullmailer@svn.kde.org> References: <1265724356.536189.19062.nullmailer@svn.kde.org> Message-ID: <201002091615.24269.bald@smail.ee> teisip?ev, 09. veebruar 2010 16:05:56 kirjutas Sebastian K?gler: > SVN commit 1087757 by sebas: > > Release KDE Software Compilation 4.4.0 > > Congrats, everyone! > > CCMAIL:release-team at kde.org > > > M +7 -6 announcements/4.4/index-sl.php > M +0 -4 announcements/4.4/index.php > M +6 -0 announcements/index.php > M +4 -4 index.php > M +4 -2 info/releases.php > It'd be even better if you had at once deleted from translations that "cheap hiding trick", too, whuch is preventing to see translation now... From mitchell at kde.org Mon Feb 15 08:21:15 2010 From: mitchell at kde.org (Jeff Mitchell) Date: Mon, 15 Feb 2010 02:21:15 -0500 Subject: Contacting the release coordinators re: critical security vuln Message-ID: <4B78F5EB.1000802@kde.org> As you guys probably know by now, we have a patch for a critical security vuln. Although it was disclosed publicly, the packagers were notified on the kde-packager list today and we're giving packagers a couple of days to roll new packages (Monday is a holiday here in the US). However, the security policy says to contact the release coordinators in the event of a situation where an immediate fix is necessary. I'm not sure whether this is simply so one of you guys can put it out on kde-announce or whether it's because we're supposed to roll new, patched tarballs. So consider this my notification to you guys that whatever it is that is supposed to be done needs to start getting done :-) Sorry to be vague, but I'll answer any direct questions if possible. --Jeff -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature Url : http://mail.kde.org/pipermail/release-team/attachments/20100215/c01a8941/attachment.sig From mpyne at kde.org Mon Feb 15 22:08:24 2010 From: mpyne at kde.org (Michael Pyne) Date: Mon, 15 Feb 2010 16:08:24 -0500 Subject: Fwd: Am I the only person that ever checks sha1sums? :) Message-ID: <201002151608.31098.mpyne@kde.org> Release Team, Apparently SHA1 sums are wrong on some of the tarballs? (See below) Regards, - Michael Pyne ---------- Forwarded Message ---------- Subject: Am I the only person that ever checks sha1sums? :) Date: Monday 15 February 2010, 14:54:53 From: Charles Johnston To: kde-devel at kde.org The two files: kdebase-4.4.0.tar.bz2 and oxygen-icons-4.3.5.tar.bz2 do not match the sha1sums that are listed for them. Either the sums or the files are messed up. Any idea why? Did they get re-rolled and somebody forget to update the sums? Thanks Charles Johnston charles at infoplatter.com >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << ----------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100215/d10de9dd/attachment.sig From hubnerd at ntlworld.com Tue Feb 16 04:31:32 2010 From: hubnerd at ntlworld.com (David Hubner) Date: Tue, 16 Feb 2010 03:31:32 +0000 Subject: Fwd: Re: Dependencies on Solid::Control Message-ID: <4B7A1194.3040205@ntlworld.com> Hi, Just forwarding a discussion to the release-team mailing list. Is it possible to move KInfoCenter to kdebase-workspace? Thanks ( PS: Been having mail problems all day so I hope this does not get sent twice ) -------- Original Message -------- Subject: Re: Dependencies on Solid::Control Date: Sun, 14 Feb 2010 22:07:48 -0800 From: Aaron J. Seigo Reply-To: kde-core-devel at kde.org To: kde-core-devel at kde.org On February 14, 2010, David Hubner wrote: > Who would I talk to, to get it moved to kdebase-workspace? I don't want > to move it in SVN and then get told off by the build team :) more the release team. the build is easy :) maybe ask on kde-packagers@ and release-team@; otherwise, as one of the occupants of workspace i'd welcome kinfocenter there. personally i think it's the kind of app that makes sense as part of the workspace. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From winter at kde.org Tue Feb 16 13:29:43 2010 From: winter at kde.org (Allen Winter) Date: Tue, 16 Feb 2010 07:29:43 -0500 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <4B7A1194.3040205@ntlworld.com> References: <4B7A1194.3040205@ntlworld.com> Message-ID: <201002160729.43688.winter@kde.org> On Monday 15 February 2010 10:31:32 pm David Hubner wrote: > Hi, > > Just forwarding a discussion to the release-team mailing list. Is it > possible to move KInfoCenter to kdebase-workspace? > > Thanks > > ( PS: Been having mail problems all day so I hope this does not get sent > twice ) > > -------- Original Message -------- > Subject: Re: Dependencies on Solid::Control > Date: Sun, 14 Feb 2010 22:07:48 -0800 > From: Aaron J. Seigo > Reply-To: kde-core-devel at kde.org > To: kde-core-devel at kde.org > > On February 14, 2010, David Hubner wrote: > > Who would I talk to, to get it moved to kdebase-workspace? I don't want > > to move it in SVN and then get told off by the build team :) > > more the release team. the build is easy :) > > maybe ask on kde-packagers@ and release-team@; otherwise, as one of the > occupants of workspace i'd welcome kinfocenter there. personally i think > it's > the kind of app that makes sense as part of the workspace. > > No objections from me. Seems like a fine idea. -Allen From sebas at kde.org Tue Feb 16 09:21:06 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Tue, 16 Feb 2010 09:21:06 +0100 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <4B7A1194.3040205@ntlworld.com> References: <4B7A1194.3040205@ntlworld.com> Message-ID: <201002160921.29443.sebas@kde.org> Am Dienstag 16 Februar 2010 04:31:32 schrieb David Hubner: > Just forwarding a discussion to the release-team mailing list. Is it > possible to move KInfoCenter to kdebase-workspace? > > Thanks > > ( PS: Been having mail problems all day so I hope this does not get sent > twice ) > > -------- Original Message -------- > Subject: Re: Dependencies on Solid::Control > Date: Sun, 14 Feb 2010 22:07:48 -0800 > From: Aaron J. Seigo > Reply-To: kde-core-devel at kde.org > To: kde-core-devel at kde.org > > On February 14, 2010, David Hubner wrote: > > Who would I talk to, to get it moved to kdebase-workspace? I don't want > > to move it in SVN and then get told off by the build team :) > > more the release team. the build is easy :) > > maybe ask on kde-packagers@ and release-team@; otherwise, as one of the > occupants of workspace i'd welcome kinfocenter there. personally i think > it's > the kind of app that makes sense as part of the workspace. I think so, too. I do notice workspace becoming rather large, though. The wallpaper package (which has been split out by Kubuntu) is 60MB alone. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100216/334b410e/attachment.sig From toma at kde.org Tue Feb 16 21:39:22 2010 From: toma at kde.org (Tom Albers) Date: Tue, 16 Feb 2010 21:39:22 +0100 Subject: kdereview maintainership In-Reply-To: <200907231604.07711.aseigo@kde.org> Message-ID: <1464041.SHII8HfyCc@kde.org> Op Friday 24 July 2009 00:04 schreef u: > On Thursday 23 July 2009, Tom Albers wrote: > > In any case preventing kdereview becomes a dumping ground. Which will > > happen without maintainer. So, another fun job up for taking. > > i watch over kdereview/plasma already and plasma-related stuff that goes in > there.... having another person to help with the rest of the stuff would be > great, but i'm willing to spend a bit more time in kdereview. it's already > part of my weekly workflow as it is. > Aaron, Can you update: http://techbase.kde.org/Projects/Release_Team ? Best, Toma -- KDE Developer From hubnerd at ntlworld.com Tue Feb 16 23:13:00 2010 From: hubnerd at ntlworld.com (David Hubner) Date: Tue, 16 Feb 2010 22:13:00 +0000 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <201002160729.43688.winter@kde.org> References: <4B7A1194.3040205@ntlworld.com> <201002160729.43688.winter@kde.org> Message-ID: <4B7B186C.6050604@ntlworld.com> On 16/02/2010 12:29, Allen Winter wrote: > On Monday 15 February 2010 10:31:32 pm David Hubner wrote: >> Hi, >> >> Just forwarding a discussion to the release-team mailing list. Is it >> possible to move KInfoCenter to kdebase-workspace? >> >> Thanks >> >> ( PS: Been having mail problems all day so I hope this does not get sent >> twice ) >> >> -------- Original Message -------- >> Subject: Re: Dependencies on Solid::Control >> Date: Sun, 14 Feb 2010 22:07:48 -0800 >> From: Aaron J. Seigo >> Reply-To: kde-core-devel at kde.org >> To: kde-core-devel at kde.org >> >> On February 14, 2010, David Hubner wrote: >>> Who would I talk to, to get it moved to kdebase-workspace? I don't want >>> to move it in SVN and then get told off by the build team :) >> >> more the release team. the build is easy :) >> >> maybe ask on kde-packagers@ and release-team@; otherwise, as one of the >> occupants of workspace i'd welcome kinfocenter there. personally i think >> it's >> the kind of app that makes sense as part of the workspace. >> >> > No objections from me. > Seems like a fine idea. > > -Allen > As its all good, can someone from the release team move KInfoCenter into kdebase-workspace as I not completely confident in my SVN abilities when it comes to moving stuff around. :) Being my first month of maintaining stuff for KDE I am trying to avoid breaking it :) Thanks David Hubner From toma at kde.org Tue Feb 16 23:23:35 2010 From: toma at kde.org (Tom Albers) Date: Tue, 16 Feb 2010 23:23:35 +0100 Subject: Fwd: Am I the only person that ever checks sha1sums? :) In-Reply-To: <201002151608.31098.mpyne@kde.org> Message-ID: <3728012.x6eZPF9oBC@kde.org> Both are fixed now. Best, Toma Op Monday 15 February 2010 22:08 schreef u: > Release Team, > > Apparently SHA1 sums are wrong on some of the tarballs? (See below) > > Regards, > - Michael Pyne > ---------- Forwarded Message ---------- > > Subject: Am I the only person that ever checks sha1sums? :) > Date: Monday 15 February 2010, 14:54:53 > From: Charles Johnston > To: kde-devel at kde.org > > The two files: > > kdebase-4.4.0.tar.bz2 > > and > > oxygen-icons-4.3.5.tar.bz2 > > do not match the sha1sums that are listed for them. > Either the sums or the files are messed up. > > Any idea why? Did they get re-rolled and somebody forget > to update the sums? > > > Thanks > > Charles Johnston > charles at infoplatter.com > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > << > > ----------------------------------------- Toma -- KDE Developer From aseigo at kde.org Wed Feb 17 00:36:57 2010 From: aseigo at kde.org (Aaron J. Seigo) Date: Tue, 16 Feb 2010 15:36:57 -0800 Subject: kdereview maintainership In-Reply-To: <1464041.SHII8HfyCc@kde.org> References: <1464041.SHII8HfyCc@kde.org> Message-ID: <201002161536.59447.aseigo@kde.org> On February 16, 2010, Tom Albers wrote: > Op Friday 24 July 2009 00:04 schreef u: > > On Thursday 23 July 2009, Tom Albers wrote: > > > In any case preventing kdereview becomes a dumping ground. Which will > > > happen without maintainer. So, another fun job up for taking. > > > > i watch over kdereview/plasma already and plasma-related stuff that goes > > in there.... having another person to help with the rest of the stuff > > would be great, but i'm willing to spend a bit more time in kdereview. > > it's already part of my weekly workflow as it is. > > Aaron, > > Can you update: http://techbase.kde.org/Projects/Release_Team ? done :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From aseigo at kde.org Wed Feb 17 00:38:09 2010 From: aseigo at kde.org (Aaron J. Seigo) Date: Tue, 16 Feb 2010 15:38:09 -0800 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <4B7B186C.6050604@ntlworld.com> References: <4B7A1194.3040205@ntlworld.com> <201002160729.43688.winter@kde.org> <4B7B186C.6050604@ntlworld.com> Message-ID: <201002161538.10043.aseigo@kde.org> On February 16, 2010, David Hubner wrote: > As its all good, can someone from the release team move KInfoCenter into > kdebase-workspace as I not completely confident in my SVN abilities when > it comes to moving stuff around. :) i'll do this today for you :) > Being my first month of maintaining stuff for KDE I am trying to avoid > breaking it :) pfft, where's your sense of adventure? ;P -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From aseigo at kde.org Wed Feb 17 03:09:56 2010 From: aseigo at kde.org (Aaron J. Seigo) Date: Tue, 16 Feb 2010 18:09:56 -0800 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <201002161538.10043.aseigo@kde.org> References: <4B7A1194.3040205@ntlworld.com> <4B7B186C.6050604@ntlworld.com> <201002161538.10043.aseigo@kde.org> Message-ID: <201002161809.57761.aseigo@kde.org> On February 16, 2010, Aaron J. Seigo wrote: > On February 16, 2010, David Hubner wrote: > > As its all good, can someone from the release team move KInfoCenter into > > kdebase-workspace as I not completely confident in my SVN abilities when > > it comes to moving stuff around. :) > > i'll do this today for you :) ok, done, and hopefully even in a way that the localization teams won't be searching for me with a baseball bat ;) cheers ... -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From hubnerd at ntlworld.com Wed Feb 17 09:30:44 2010 From: hubnerd at ntlworld.com (David Hubner) Date: Wed, 17 Feb 2010 08:30:44 +0000 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <201002161538.10043.aseigo@kde.org> References: <4B7A1194.3040205@ntlworld.com> <201002160729.43688.winter@kde.org> <4B7B186C.6050604@ntlworld.com> <201002161538.10043.aseigo@kde.org> Message-ID: <4B7BA934.6020107@ntlworld.com> On 16/02/2010 23:38, Aaron J. Seigo wrote: > On February 16, 2010, David Hubner wrote: >> As its all good, can someone from the release team move KInfoCenter into >> kdebase-workspace as I not completely confident in my SVN abilities when >> it comes to moving stuff around. :) > > i'll do this today for you :) > Thanks, I am going to write some proposals today and submit them to kde-core-devel it get input. >> Being my first month of maintaining stuff for KDE I am trying to avoid >> breaking it :) > > pfft, where's your sense of adventure? ;P > Most of my friends use KDE and they are bigger than me :) Thanks David Hubner From hubnerd at ntlworld.com Wed Feb 17 09:31:49 2010 From: hubnerd at ntlworld.com (David Hubner) Date: Wed, 17 Feb 2010 08:31:49 +0000 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <201002161538.10043.aseigo@kde.org> References: <4B7A1194.3040205@ntlworld.com> <201002160729.43688.winter@kde.org> <4B7B186C.6050604@ntlworld.com> <201002161538.10043.aseigo@kde.org> Message-ID: <4B7BA975.1090207@ntlworld.com> On 16/02/2010 23:38, Aaron J. Seigo wrote: > On February 16, 2010, David Hubner wrote: >> As its all good, can someone from the release team move KInfoCenter into >> kdebase-workspace as I not completely confident in my SVN abilities when >> it comes to moving stuff around. :) > > i'll do this today for you :) > Thanks, I am going to write some proposals today and submit them to kde-core-devel so I can get some input. >> Being my first month of maintaining stuff for KDE I am trying to avoid >> breaking it :) > > pfft, where's your sense of adventure? ;P > Most of my friends use KDE and they are bigger than me :) Thanks David Hubner From hubnerd at ntlworld.com Wed Feb 17 09:34:00 2010 From: hubnerd at ntlworld.com (David Hubner) Date: Wed, 17 Feb 2010 08:34:00 +0000 Subject: Fwd: Re: Dependencies on Solid::Control In-Reply-To: <4B7BA934.6020107@ntlworld.com> References: <4B7A1194.3040205@ntlworld.com> <201002160729.43688.winter@kde.org> <4B7B186C.6050604@ntlworld.com> <201002161538.10043.aseigo@kde.org> <4B7BA934.6020107@ntlworld.com> Message-ID: <4B7BA9F8.10503@ntlworld.com> On 17/02/2010 08:30, David Hubner wrote: > On 16/02/2010 23:38, Aaron J. Seigo wrote: >> On February 16, 2010, David Hubner wrote: >>> As its all good, can someone from the release team move KInfoCenter into >>> kdebase-workspace as I not completely confident in my SVN abilities when >>> it comes to moving stuff around. :) >> >> i'll do this today for you :) >> > > Thanks, I am going to write some proposals today and submit them to > kde-core-devel it get input. > >>> Being my first month of maintaining stuff for KDE I am trying to avoid >>> breaking it :) >> >> pfft, where's your sense of adventure? ;P >> > > Most of my friends use KDE and they are bigger than me :) > > Thanks > David Hubner > > > _______________________________________________ > release-team mailing list > release-team at kde.org > https://mail.kde.org/mailman/listinfo/release-team > Dammit did not click cancel fast enough, nothing to see here but bad spelling in the morning.. move along! :) Thanks David Hubner From neversfelde at kubuntu.org Thu Feb 18 00:12:22 2010 From: neversfelde at kubuntu.org (Christian Mangold) Date: Thu, 18 Feb 2010 00:12:22 +0100 Subject: kmldonkey version problem Message-ID: <201002180012.30885.neversfelde@kubuntu.org> Hello, in the kmldonkey about dialog it says it is version 2.0.5, but on ktown there is 2.0.2. So something is wrong here and as advised in #kde-devel, I post it to this list. Regards Christian -- neversfelde at jabber.neversfelde.de neversfelde on irc.freenode.net http://launchpad.net/~neversfelde -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100218/2d08f057/attachment.sig From hubnerd at ntlworld.com Mon Feb 15 19:03:05 2010 From: hubnerd at ntlworld.com (David Hubner) Date: Mon, 15 Feb 2010 18:03:05 +0000 Subject: Fwd: Re: Dependencies on Solid::Control Message-ID: <4B798C59.4030700@ntlworld.com> Hi, Just forwarding a discussion to the release-team mailing list. Is it possible to move KInfoCenter to kdebase-workspace? Thanks -------- Original Message -------- Subject: Re: Dependencies on Solid::Control Date: Sun, 14 Feb 2010 22:07:48 -0800 From: Aaron J. Seigo Reply-To: kde-core-devel at kde.org To: kde-core-devel at kde.org On February 14, 2010, David Hubner wrote: > Who would I talk to, to get it moved to kdebase-workspace? I don't want > to move it in SVN and then get told off by the build team :) more the release team. the build is easy :) maybe ask on kde-packagers@ and release-team@; otherwise, as one of the occupants of workspace i'd welcome kinfocenter there. personally i think it's the kind of app that makes sense as part of the workspace. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks From andresbajotierra at gmail.com Mon Feb 15 21:45:04 2010 From: andresbajotierra at gmail.com (=?ISO-8859-1?B?RGFy7W8gQW5kculz?=) Date: Mon, 15 Feb 2010 17:45:04 -0300 Subject: Fwd: Am I the only person that ever checks sha1sums? :) In-Reply-To: <4B79A68D.7030904@infoplatter.com> References: <4B79A68D.7030904@infoplatter.com> Message-ID: ---------- Forwarded message ---------- From: Charles Johnston Date: Mon, Feb 15, 2010 at 4:54 PM Subject: Am I the only person that ever checks sha1sums? :) To: kde-devel at kde.org The two files: kdebase-4.4.0.tar.bz2 and oxygen-icons-4.3.5.tar.bz2 do not match the sha1sums that are listed for them. Either the sums or the files are messed up. Any idea why? ?Did they get re-rolled and somebody forget to update the sums? Thanks Charles Johnston charles at infoplatter.com >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << From toma at kde.org Thu Feb 18 20:43:02 2010 From: toma at kde.org (Tom Albers) Date: Thu, 18 Feb 2010 20:43:02 +0100 Subject: kmldonkey version problem In-Reply-To: <201002180012.30885.neversfelde@kubuntu.org> Message-ID: <1552092.D0DYfHjCRj@kde.org> Dear KMLDonkey devels, We received below message. You probably have done a 2.0.5 release your self and have not updated the createtarball script. In that script 2.0.2 is indicated as the current version number. If you are making your own releases, do you want to stop us making them? If so please turn of the kde_release=yes bit to no in that same config. Let us know. Best, Toma KDE Release Team Member. Op Thursday 18 February 2010 00:12 schreef u: > Hello, > > in the kmldonkey about dialog it says it is version 2.0.5, but on ktown there > is 2.0.2. So something is wrong here and as advised in #kde-devel, I post it > to this list. > > Regards Christian > From toma at kde.org Fri Feb 19 01:29:14 2010 From: toma at kde.org (Tom Albers) Date: Fri, 19 Feb 2010 01:29:14 +0100 Subject: kmldonkey version problem In-Reply-To: <201002190125.12745.gmazzurco89@gmail.com> Message-ID: <2658995.NRx48fBzlc@kde.org> Op Friday 19 February 2010 01:25 schreef u: > >If you are making your own releases, do you want to stop us making them? > No we aren't doing release by us own, i think some error occurred in numbering > of version, please continue to manage release and tell me how to fix this > numbering issue Hi, Thanks for your mail. Please update trunk/KDE/kdesdk/scripts/createtarball/config.ini to reflect the correct version number in that case. Best, Toma -- KDE Developer From neversfelde at kubuntu.org Fri Feb 19 02:22:04 2010 From: neversfelde at kubuntu.org (Christian Mangold) Date: Fri, 19 Feb 2010 02:22:04 +0100 Subject: kmldonkey version problem In-Reply-To: <201002190156.50232.gmazzurco89@gmail.com> References: <2658995.NRx48fBzlc@kde.org> <201002190156.50232.gmazzurco89@gmail.com> Message-ID: <201002190222.16179.neversfelde@kubuntu.org> Am Freitag, 19. Februar 2010 01:56:50 schrieben Sie: > fixed thanks ;) So which is the correct version for this cycle? 2.0.2 or 2.0.5? Kubuntu has 4:2.0.3-kde4.4.0really2.0.2-kde4.4.0-0ubuntu1, which is a bit too long :). Regards Christian -- neversfelde at jabber.neversfelde.de neversfelde on irc.freenode.net http://launchpad.net/~neversfelde -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100219/32d2d346/attachment.sig From toma at kde.org Fri Feb 19 10:06:08 2010 From: toma at kde.org (Tom Albers) Date: Fri, 19 Feb 2010 10:06:08 +0100 Subject: kmldonkey version problem In-Reply-To: <201002190222.16179.neversfelde@kubuntu.org> Message-ID: <2686726.fSdjeBohA5@kde.org> Op Friday 19 February 2010 02:22 schreef u: > Am Freitag, 19. Februar 2010 01:56:50 schrieben Sie: > > fixed thanks ;) > > So which is the correct version for this cycle? 2.0.2 or 2.0.5? > Kubuntu has 4:2.0.3-kde4.4.0really2.0.2-kde4.4.0-0ubuntu1, which is a bit too > long :). At KDE SC 4.4.1 which will appear in two weeks or so, we will ship 2.0.5. I don't care much how ubuntu calls it, I assume that will be fixed to after this change. Toma -- KDE Developer From gmazzurco89 at gmail.com Fri Feb 19 01:25:12 2010 From: gmazzurco89 at gmail.com (Gioacchino) Date: Fri, 19 Feb 2010 01:25:12 +0100 Subject: kmldonkey version problem In-Reply-To: <1552092.D0DYfHjCRj@kde.org> References: <1552092.D0DYfHjCRj@kde.org> Message-ID: <201002190125.12745.gmazzurco89@gmail.com> >If you are making your own releases, do you want to stop us making them? No we aren't doing release by us own, i think some error occurred in numbering of version, please continue to manage release and tell me how to fix this numbering issue very thanks! On Thursday 18 February 2010 20:43:02 Tom Albers wrote: > Dear KMLDonkey devels, > > We received below message. You probably have done a 2.0.5 release your self > and have not updated the createtarball script. In that script 2.0.2 is > indicated as the current version number. > > If you are making your own releases, do you want to stop us making them? If > so please turn of the kde_release=yes bit to no in that same config. > > Let us know. > > Best, > > Toma > KDE Release Team Member. > > Op Thursday 18 February 2010 00:12 schreef u: > > Hello, > > > > in the kmldonkey about dialog it says it is version 2.0.5, but on ktown > > there is 2.0.2. So something is wrong here and as advised in #kde-devel, > > I post it to this list. > > > > Regards Christian From gmazzurco89 at gmail.com Fri Feb 19 01:56:50 2010 From: gmazzurco89 at gmail.com (Gioacchino) Date: Fri, 19 Feb 2010 01:56:50 +0100 Subject: kmldonkey version problem In-Reply-To: <2658995.NRx48fBzlc@kde.org> References: <2658995.NRx48fBzlc@kde.org> Message-ID: <201002190156.50232.gmazzurco89@gmail.com> fixed thanks ;) On Friday 19 February 2010 01:29:14 Tom Albers wrote: > Op Friday 19 February 2010 01:25 schreef u: > > >If you are making your own releases, do you want to stop us making them? > > > > No we aren't doing release by us own, i think some error occurred in > > numbering of version, please continue to manage release and tell me how > > to fix this numbering issue > > Hi, > > Thanks for your mail. Please update > trunk/KDE/kdesdk/scripts/createtarball/config.ini to reflect the correct > version number in that case. > > Best, > > Toma From mueller at kde.org Sat Feb 20 17:48:10 2010 From: mueller at kde.org (Dirk Mueller) Date: Sat, 20 Feb 2010 17:48:10 +0100 Subject: KDE 4.4.1 tagging Message-ID: <201002201748.10248.mueller@kde.org> Hi, how about Feb 25th for tagging KDE 4.4.1 and March 2nd for 4.4.1 release? Does this match expectations? Greetings, Dirk From winter at kde.org Sun Feb 21 13:51:04 2010 From: winter at kde.org (Allen Winter) Date: Sun, 21 Feb 2010 07:51:04 -0500 Subject: KDE 4.4.1 tagging In-Reply-To: <201002201748.10248.mueller@kde.org> References: <201002201748.10248.mueller@kde.org> Message-ID: <201002210751.04772.winter@kde.org> On Saturday 20 February 2010 11:48:10 am Dirk Mueller wrote: > > Hi, > > how about Feb 25th for tagging KDE 4.4.1 and March 2nd for 4.4.1 release? Does > this match expectations? > Yes. I added these dates to the 4.4 Schedule [1] and also added dates for the 4.4.2 and 4.4.3 releases. As follows: February 25th, 2010: Tag KDE 4.4.1 March 2nd, 2010: Release KDE 4.4.1 March 25th, 2010: Tag KDE 4.4.2 March 30th, 2010: Release KDE 4.4.2 April 29th, 2010: Tag KDE 4.4.3 May 4th, 2010: Release KDE 4.4.3 [1] http://techbase.kde.org/Schedules/KDE4/4.4_Release_Schedule From mueller at kde.org Mon Feb 22 17:38:36 2010 From: mueller at kde.org (Dirk Mueller) Date: Mon, 22 Feb 2010 17:38:36 +0100 Subject: KDE 4.4.1 tagging In-Reply-To: <201002210751.04772.winter@kde.org> References: <201002201748.10248.mueller@kde.org> <201002210751.04772.winter@kde.org> Message-ID: <201002221738.37029.mueller@kde.org> On Sunday 21 February 2010, Allen Winter wrote: > Yes. I added these dates to the 4.4 Schedule [1] and also added dates > for the 4.4.2 and 4.4.3 releases. As follows: Great, thank you! Greetings, Dirk From wstephenson at kde.org Wed Feb 24 12:05:03 2010 From: wstephenson at kde.org (Will Stephenson) Date: Wed, 24 Feb 2010 12:05:03 +0100 Subject: 4.5 schedule on Techbase? Message-ID: <201002241205.03837.wstephenson@kde.org> Hi team Is there a 4.5 schedule that can be published on Techbase? People here at SUSE are asking me. Will From sebas at kde.org Wed Feb 24 12:25:15 2010 From: sebas at kde.org (Sebastian =?iso-8859-1?q?K=FCgler?=) Date: Wed, 24 Feb 2010 12:25:15 +0100 Subject: 4.5 schedule on Techbase? In-Reply-To: <201002241205.03837.wstephenson@kde.org> References: <201002241205.03837.wstephenson@kde.org> Message-ID: <201002241225.15444.sebas@kde.org> On Wednesday 24 February 2010 12:05:03 Will Stephenson wrote: > Is there a 4.5 schedule that can be published on Techbase? People here at > SUSE are asking me. We haven't discussed exact dates yet, but assuming we stick to the 6 months schedule (and I think we should), it will be end of July. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/release-team/attachments/20100224/c8f08d0c/attachment.sig From toma at kde.org Wed Feb 24 12:32:24 2010 From: toma at kde.org (Tom Albers) Date: Wed, 24 Feb 2010 12:32:24 +0100 Subject: 4.5 schedule on Techbase? In-Reply-To: <201002241205.03837.wstephenson@kde.org> Message-ID: <3492952.BUmIsVbFMT@kde.org> Op Wednesday 24 February 2010 12:05 schreef u: > Hi team > > Is there a 4.5 schedule that can be published on Techbase? People here at > SUSE are asking me. > > Will Roughly look at 4.4 and add 6 months. I hope I find a minute this week to make the detailled schedule. I've very limited time the next 3-4 weeks. Any special wishes let me know! Toma From mueller at kde.org Wed Feb 24 22:37:04 2010 From: mueller at kde.org (Dirk Mueller) Date: Wed, 24 Feb 2010 22:37:04 +0100 Subject: Contacting the release coordinators re: critical security vuln In-Reply-To: <4B78F5EB.1000802@kde.org> References: <4B78F5EB.1000802@kde.org> Message-ID: <201002242237.04556.mueller@kde.org> On Monday 15 February 2010, Jeff Mitchell wrote: > However, the security policy says to contact the release coordinators in > the event of a situation where an immediate fix is necessary. I'm not > sure whether this is simply so one of you guys can put it out on > kde-announce or whether it's because we're supposed to roll new, patched > tarballs. Hi Jeff, thanks. I think its fine for this fix to wait for 4.4.1, which is tagged on friday. Greetings, Dirk From apaku at gmx.de Thu Feb 25 21:33:30 2010 From: apaku at gmx.de (Andreas Pakulat) Date: Thu, 25 Feb 2010 21:33:30 +0100 Subject: Where to branch from extragear? Message-ID: <20100225203330.GA17143@barmbek> Hi, I just wrote up the release schedule for KDevelop4.0 and wanted to include to where we'll branch the release. Unfortunately I can't quite find the right spot in branches/. So where should a extragear app put its stable branches? Andreas -- You will be reincarnated as a toad; and you will be much happier. From aacid at kde.org Thu Feb 25 21:50:06 2010 From: aacid at kde.org (Albert Astals Cid) Date: Thu, 25 Feb 2010 20:50:06 +0000 Subject: Where to branch from extragear? In-Reply-To: <20100225203330.GA17143@barmbek> References: <20100225203330.GA17143@barmbek> Message-ID: <201002252050.07644.aacid@kde.org> A Dijous, 25 de febrer de 2010, Andreas Pakulat va escriure: > Hi, > > I just wrote up the release schedule for KDevelop4.0 and wanted to > include to where we'll branch the release. Unfortunately I can't quite > find the right spot in branches/. So where should a extragear app put > its stable branches? http://websvn.kde.org/branches/stable/extragear-kde4/ Albert > > Andreas From apaku at gmx.de Thu Feb 25 22:15:58 2010 From: apaku at gmx.de (Andreas Pakulat) Date: Thu, 25 Feb 2010 22:15:58 +0100 Subject: Where to branch from extragear? In-Reply-To: <201002252050.07644.aacid@kde.org> References: <20100225203330.GA17143@barmbek> <201002252050.07644.aacid@kde.org> Message-ID: <20100225211558.GA2931@trinity.apaku.dnsalias.org> On 25.02.10 20:50:06, Albert Astals Cid wrote: > A Dijous, 25 de febrer de 2010, Andreas Pakulat va escriure: > > Hi, > > > > I just wrote up the release schedule for KDevelop4.0 and wanted to > > include to where we'll branch the release. Unfortunately I can't quite > > find the right spot in branches/. So where should a extragear app put > > its stable branches? > > http://websvn.kde.org/branches/stable/extragear-kde4/ Thanks. Andreas -- Today is National Existential Ennui Awareness Day. From apaku at gmx.de Thu Feb 25 22:16:37 2010 From: apaku at gmx.de (Andreas Pakulat) Date: Thu, 25 Feb 2010 22:16:37 +0100 Subject: KDevelop4 Release Schedule finalized Message-ID: <20100225211637.GB2931@trinity.apaku.dnsalias.org> Hi, for those interest, we've settled on a final schedule for the 4.0 release of KDevelop4: http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/4.0_Release_Schedule Andreas -- Stay away from hurricanes for a while. From aacid at kde.org Fri Feb 26 00:51:23 2010 From: aacid at kde.org (Albert Astals Cid) Date: Thu, 25 Feb 2010 23:51:23 +0000 Subject: About KDE l10n 4.4.1 tagging Message-ID: <201002252351.25823.aacid@kde.org> I've tried to run a validation over i18n compilation but my 4.4.x instalattion is in a worrysome state and have run into some problems with the pt_BR and sk dirs but couldn't say if it was my fault or their fault. so if at the end it was not a problem in my side you might have to delete some index.docbook files in those dirs to make sure it compiles. Sorry about not being able to tell more. Albert From lueck at hube-lueck.de Fri Feb 26 08:19:22 2010 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Fri, 26 Feb 2010 08:19:22 +0100 Subject: About KDE l10n 4.4.1 tagging In-Reply-To: <201002252351.25823.aacid@kde.org> References: <201002252351.25823.aacid@kde.org> Message-ID: <201002260819.23133.lueck@hube-lueck.de> Am Freitag, 26. Februar 2010 00:51:23 schrieb Albert Astals Cid: > I've tried to run a validation over i18n compilation but my 4.4.x > instalattion is in a worrysome state and have run into some problems with > the pt_BR and sk dirs but couldn't say if it was my fault or their fault. > so if at the end it was not a problem in my side you might have to delete > some index.docbook files in those dirs to make sure it compiles. > Fixed them (sk only ONE broken docbook, pt_BR 3 broken docbooks) Time to switch to language docs autogeneration. -- Burkhard L?ck From mueller at kde.org Fri Feb 26 21:21:08 2010 From: mueller at kde.org (Dirk Mueller) Date: Fri, 26 Feb 2010 21:21:08 +0100 Subject: KDE 4.4.1 tarballs (try#1) uploaded Message-ID: <201002262121.08730.mueller@kde.org> Hi, just finished uploading the 1st set of 4.4.1 tarballs. hopefully nothing went wrong, I haven't tested them yet. Please let me know of any blocking issues. kde-l10n tarballs are still generating, later tonight/tomorrow. Greetings, Dirk From apaku at gmx.de Sat Feb 27 18:26:21 2010 From: apaku at gmx.de (Andreas Pakulat) Date: Sat, 27 Feb 2010 18:26:21 +0100 Subject: How to release an extragear app? Message-ID: <20100227172621.GC27181@trinity.apaku.dnsalias.org> Hi, KDevelop4 is approaching its first stable release from extragear and I'm not fully sure how the procedure is for an extragear app for this. In particular how does the whole translation-stuff work? Should we have a kdevelop-i18n.tar.gz or should it be inside the normal kdevelop.tar.gz? Where and how do I get the translations and how to build them? I didn't find any pointers to this on techbase, but would be happy to contribute them once I know the details. Besides tagging, tarballing, branching, notifying packagers and writing a dot-announcement is there anything else I need to take care of? Andreas -- Think twice before speaking, but don't say "think think click click". From hein at kde.org Sat Feb 27 18:51:56 2010 From: hein at kde.org (Eike Hein) Date: Sat, 27 Feb 2010 18:51:56 +0100 Subject: How to release an extragear app? In-Reply-To: <20100227172621.GC27181@trinity.apaku.dnsalias.org> References: <20100227172621.GC27181@trinity.apaku.dnsalias.org> Message-ID: <4B895BBC.2050507@kde.org> On 02/27/2010 06:26 PM, Andreas Pakulat wrote: > Besides tagging, tarballing, branching, notifying packagers and writing > a dot-announcement is there anything else I need to take care of? Here's some mails about this I wrote recently: http://lists.kde.org/?l=kde-extra-gear&m=124927007024432&w=2 http://lists.kde.org/?l=kde-extra-gear&m=124928664908058&w=2 The checklist has changed a bit recently, e.g. because the tarballs are now on download.kde.org which implies 6h or so of mirror syncing before being able to do the public announcements, and because there are new commu- nication channels like Facebook that the release is also announced on, and because of the move to git (now using a homecooked tool rather than create_tarball atm), but that's basically it. > Andreas -- Best regards, Eike Hein From jospoortvliet at gmail.com Sun Feb 28 00:32:00 2010 From: jospoortvliet at gmail.com (Jos Poortvliet) Date: Sun, 28 Feb 2010 00:32:00 +0100 Subject: How to release an extragear app? In-Reply-To: <4B895BBC.2050507@kde.org> References: <20100227172621.GC27181@trinity.apaku.dnsalias.org> <4B895BBC.2050507@kde.org> Message-ID: <201002280032.01060.jospoortvliet@gmail.com> On Saturday 27 February 2010 18:51:56 Eike Hein wrote: > On 02/27/2010 06:26 PM, Andreas Pakulat wrote: > > Besides tagging, tarballing, branching, notifying packagers and writing > > a dot-announcement is there anything else I need to take care of? > > Here's some mails about this I wrote recently: > http://lists.kde.org/?l=kde-extra-gear&m=124927007024432&w=2 > http://lists.kde.org/?l=kde-extra-gear&m=124928664908058&w=2 > > The checklist has changed a bit recently, e.g. because > the tarballs are now on download.kde.org which implies > 6h or so of mirror syncing before being able to do the > public announcements, and because there are new commu- > nication channels like Facebook that the release is > also announced on, and because of the move to git (now > using a homecooked tool rather than create_tarball atm), > but that's basically it. > > > Andreas Please let the promo team know at least a few days beforehand when the release will be. If you want us we can try and help you write the announcement (pls give us a week) and maybe a feature guide (but of course a feature guide would take more than a week, think more like a month). We'll also help promote the release to facebook, youtube (if you have video's) and other channels. The dot editors also need a heads-up a few days before if you want a timely release announcement on the dot. Cheers, Jos From Sune at vuorela.dk Sun Feb 28 01:17:04 2010 From: Sune at vuorela.dk (Sune Vuorela) Date: Sun, 28 Feb 2010 01:17:04 +0100 Subject: KDE 4.4.1 tarballs (try#1) uploaded In-Reply-To: <201002262121.08730.mueller@kde.org> References: <201002262121.08730.mueller@kde.org> Message-ID: <201002280117.07696.Sune@vuorela.dk> On Friday 26 February 2010 21:21:08 Dirk Mueller wrote: > Hi, > > just finished uploading the 1st set of 4.4.1 tarballs. hopefully nothing > went wrong, I haven't tested them yet. Please let me know of any blocking > issues. Can we get r1096627 and 1096628 put into the tag? there is a .so file installed into data dir, which is fixed in these two revisions. Thanks /Sune -- How might I overclock the processor? The point is that from the file inside Photoshop XP you either should debug a terminale to a controller, or have to telnet to the URL on the periferic of the modem to a Ultra SCSI firewall for resetting the jumper.