Nabble - kde-devel

Re: KDevelop, KDevPlatform, Quanta moved to extragear

2009-11-29T22:35:47Z

On Sunday 29 November 2009 21:24:07 Andreas Pakulat wrote:

> Hi everybody,
>
> Toma just executed the following moves for us (the kdevelop team):
>
> trunk/KDE/kdevplatform
> trunk/KDE/kdevelop
> trunk/KDE/kdewebdev/quanta
>
> to
>
> trunk/extragear/sdk/
>
> I've adjusted the kdewebdev buildsystem to not build quanta anymore and
> also added a pointer to where it is now. It needed to be moved as
> kdevplatform is a dependency of it.
>
> @i18n-team: If you could move the translations that would be great, if
> you need anything from me/us then let me know.
>
> Anybody who checked out kdevplatform or kdevelop from trunk you can
> easily switch to the new location by using
>
> svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/extragear/sdk/kdevplatform
>
> (replace svn:// with https:// as apropriate).
>
> For those wondering: Yes this means we won't be ready for release with
> KDE 4.4, sorry :(

What does it mean regarding feature freezes and deadlines?

- Volodya

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDE Promo proposal

2009-11-29T22:04:38Z

On November 28, 2009, John Tapsell wrote:
> Well, perhaps they should? If the default theme for KDE is going to
> change, then it would be nice to have discussions about that. I
> wouldn't like to first find out about a default theme change from a
> news website/twitter either.

there are discussions. they just may not happen on lists you are on. decisions
happen all the time in KDE, including ones that affect a lot of us on the
coding level, that aren't discussed with every person involved with kde. this
really strikes me as desiring control over things which aren't ours to
control.

as for the appropriateness for everyone to involved in everything, i don't
think many people have what it takes to make good calls when it comes to
artwork, let alone have the ability to create it. same for most things people
do in KDE these days; there are special skills and interests at play. promo is
no different, in fact it's probably even more specialized a skill amongst the
people who are part of KDE.

and i know i sure don't want to see kde's participation based model be thrown
out just so that coders can play micro-manager over others.

> > The release team doesn't need majority
> > approval from the community to delay the tagging of the beta.
>
> If it's a delay that is so significant that it's going to be on news
> sites, then that should probably also be discussed.

now we're just making issues up where they don't exist. :)

if there was to be a big delay ... we do discuss it. on kde-core-devel.
the re-branding was similarly broadly discussed.

promo didn't get everyone to sign off on it explicitly, but then that's not
how things work, never have and never can as long as we wish to remain a
participation driven community.

> > KDE isn't a democracy.
>
> That's a shame :-(

shall we take a vote on what feature you should work on next, then? ;)

democracy is awesome, but it isn't the best answer for every case.

> > "The one who does the work decides." That
> > applies to more than just code.
>
> Code can be removed, changed etc, before a release. It's out in the
> open somewhat (mostly). If there was a major change (of the sort that
> would be in the news) then yeah, I'd like that mentioned too.

and this is what happened, but unfortunately you simply missed it. that sucks,
but it happens.

also, please send questions / comments / ideas / concerns about promo to kde-
promo. that's where they belong, much as questions about kmail's code belong
on the kde pim list :)

--
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

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

signature.asc (204 bytes) Download Attachment

Re: KDE Promo proposal

2009-11-29T21:56:22Z

On November 29, 2009, Patrick Spendrin wrote:
> Lydia Pintscher schrieb:
> > You are free to join the kde-promo mailing list right now and start
> > following what we do and even get involved yourself. And as other said
> > the promo people don't need to be consulted for code changes either.
>
> This is rather bad since you are making promo for the code of the
> programmers right?

and the developers are making the stuff that the promo team has to communicate
in a positive light. some of the decisions developers make pose significant
challenges to that end, not to mention some of the stuff we see developers
post on planet.kde.org. it cuts both ways, and right now there's a pretty good
balance being kept imho. but i'd be very careful with making assumptions that
it's the promo people who have some indebtedness to the developers, or that
the developers have the ability to make good promo calls.

> When it comes to other areas like l10n e.g.
> programmers also need to ask and vice versa.

when there is functional overlap, yes. and promo does that as well (promo is
much more involved in tracking the release plans and schedules than
previously, for instance).

> Even though I read the planet and the dot, I am kind of disappointed by
> the latest rebranding. There was no, "Hey, see what the promo people
> made up!" but rather a public announcement in the name of everybody
> (which leads to news articles etc.).

first, it wasn't just "made up". it was over 2 years in the making. second, it
was shared within the community before announcements were made.

> Programmers do have alphas and
> betas and rcs to get more and more feedback from their users; maybe an
> equivalent way to the public can be found for promo aspects.

those happen on kde-promo. please join us there.

> There
> should be a step in between joining the promo mailing list and the final
> announcement on the dot I'd think.

so that it's convenient for people who would like to be backseat drivers, but
who can't be bothered to actually get involved? no thanks.

if you think kde-promo is having issues

> > The rebranding was on mailinglists and planet before it was made
> > official and it was made official on the dot and planet before any
> > other news site on the net. It's a bit unfortunate that you read
> > OSNews first.
>
> But this means this already happened when it was announced on the dot
> right?

no. it means you can read kde-promo or for really big issues kde-core-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

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

signature.asc (204 bytes) Download Attachment

Re: KDE Promo proposal

2009-11-29T21:49:49Z

On November 28, 2009, John Tapsell wrote:
> The KDE promo team discuss internally about their plans, come up
> with proposals etc as usual, but that those proposals then have to
> checked by the kde-devel or kde-core-devel or a vote on planet.kde.org
> or whatever. The purpose being that things that are going to affect
> the image of all us are at least agreed upon by a majority.

others have addressed various aspects of this already, especially how this
particular issue was discussed extensively and openly.

while the promo team has grown increasingly open and is indeed available for
all to keep up with and participate in, expecting everyone to have relevant
skills and know-how is unrealistic and asking promo to get approval for even a
sizable percentage of the projects underway will so severely hamper the effort
with endless discussion and other slowdowns that it would be huge mistake to
do this.

if you disagree with something or just have questions, take it to kde-promo
where people are always happy to discuss and share. it's a very open group
with a great atmosphere.

we each have responsibilities we take on in this project and it's not possible
for any one of us to do it all. and we need to respect each other's
responsibilities; putting external managers in place, which is what you
suggest amounts to, is not how we have ever done things in kde.

--
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

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

signature.asc (204 bytes) Download Attachment

Re: KDE Promo proposal

2009-11-29T17:40:38Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lydia Pintscher schrieb:
> You are free to join the kde-promo mailing list right now and start
> following what we do and even get involved yourself. And as other said
> the promo people don't need to be consulted for code changes either.
This is rather bad since you are making promo for the code of the
programmers right? When it comes to other areas like l10n e.g.
programmers also need to ask and vice versa.
Even though I read the planet and the dot, I am kind of disappointed by
the latest rebranding. There was no, "Hey, see what the promo people
made up!" but rather a public announcement in the name of everybody
(which leads to news articles etc.). Programmers do have alphas and
betas and rcs to get more and more feedback from their users; maybe an
equivalent way to the public can be found for promo aspects. There
should be a step in between joining the promo mailing list and the final
announcement on the dot I'd think.
>
> The rebranding was on mailinglists and planet before it was made
> official and it was made official on the dot and planet before any
> other news site on the net. It's a bit unfortunate that you read
> OSNews first.
But this means this already happened when it was announced on the dot right?
>
>
> Cheers
> Lydia
>

regards,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAksTIpYACgkQi49rfdk/G3YwHgCdH3tJMxcwgmysnBaj9OFptVlB
1qkAn21F5KZ6H7DGgVIAyWVH+89FwRgd
=Qre1
-----END PGP SIGNATURE-----

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDevelop, KDevPlatform, Quanta moved to extragear

2009-11-29T15:49:58Z

A Diumenge, 29 de novembre de 2009, Andreas Pakulat va escriure:

> On 29.11.09 19:24:07, Andreas Pakulat wrote:
> > Hi everybody,
> >
> > Toma just executed the following moves for us (the kdevelop team):
> >
> > trunk/KDE/kdevplatform
> > trunk/KDE/kdevelop
> > trunk/KDE/kdewebdev/quanta
> >
> > to
> >
> > trunk/extragear/sdk/
> >
> > I've adjusted the kdewebdev buildsystem to not build quanta anymore and
> > also added a pointer to where it is now. It needed to be moved as
> > kdevplatform is a dependency of it.
> >
> > @i18n-team: If you could move the translations that would be great, if
> > you need anything from me/us then let me know.
>
> @i18n-team: I also needed to move kxsldbg from kdewebdev as quanta
> depends on its source files.

I think i've done all the movements correctly now.

I have not moved/deleted desktop_ files of kdevelop/kdevplatform because it
doesn't make sense, tomorrow i'll merge them into refreshed desktop_ of
extragear-sdk and remove them.

Tell me if you find something wrong.

Albert

>
> > Anybody who checked out kdevplatform or kdevelop from trunk you can
> > easily switch to the new location by using
> >
> > svn switch --relocate
> > svn://anonsvn.kde.org/home/kde/trunk/extragear/sdk/kdevplatform
>
> Leave out the --relocate from that, I was confused by the documentation.
>
> Andreas
>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDevelop, KDevPlatform, Quanta moved to extragear

2009-11-29T10:46:15Z

On 29.11.09 19:24:07, Andreas Pakulat wrote:

@i18n-team: I also needed to move kxsldbg from kdewebdev as quanta
depends on its source files.

> Anybody who checked out kdevplatform or kdevelop from trunk you can
> easily switch to the new location by using
>
> svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/extragear/sdk/kdevplatform

Leave out the --relocate from that, I was confused by the documentation.

Andreas

--
You will be awarded some great honor.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

KDevelop, KDevPlatform, Quanta moved to extragear

2009-11-29T10:24:07Z

Hi everybody,

Toma just executed the following moves for us (the kdevelop team):

trunk/KDE/kdevplatform
trunk/KDE/kdevelop
trunk/KDE/kdewebdev/quanta

to

trunk/extragear/sdk/

I've adjusted the kdewebdev buildsystem to not build quanta anymore and
also added a pointer to where it is now. It needed to be moved as
kdevplatform is a dependency of it.

@i18n-team: If you could move the translations that would be great, if
you need anything from me/us then let me know.

Anybody who checked out kdevplatform or kdevelop from trunk you can
easily switch to the new location by using

svn switch --relocate svn://anonsvn.kde.org/home/kde/trunk/extragear/sdk/kdevplatform

(replace svn:// with https:// as apropriate).

For those wondering: Yes this means we won't be ready for release with
KDE 4.4, sorry :(

If anybody runs into problems caused by the move: Send me a mail and/or
complain to me on irc in #kdevelop.

Andreas

--
Your lucky number has been disconnected.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDE Promo proposal

2009-11-29T07:18:09Z

On Sunday 29 November 2009 John Tapsell wrote:
>
> I would like to see a bit more openness from the KDE promo team.

The promo team actually has made great strides in terms of openness. It has
evolved from a small group discussing things privately to an impressively
strong and active group doing most of its work transparently on the kde-promo
list. I can't think of any time in KDE where this happened more openly.

> The KDE promo team discuss internally about their plans, come up
> with proposals etc as usual, but that those proposals then have to
> checked by the kde-devel or kde-core-devel or a vote on planet.kde.org
> or whatever. The purpose being that things that are going to affect
> the image of all us are at least agreed upon by a majority.

This process actually happens all the time. We don't have formal votes of the
whole community as this won't be practical. We are too big to have everybody
know about everything. But we have strong teams following the "those who do
the work decide" rule as we always have. The teams are open for involvement
from other community members, the promo team just like every other team.

For those decisions where buy-in of the whole community is important like the
rebranding the promo team does reach out to the rest of the community. In this
particular case the proposal was discussed in various places, including the
kde-core-devel mailing list.

> I realise that it's a bit more bureaucratic overhead, and I don't
> mean for this to apply to everything. But I don't want to read about
> "KDE rebranding" first on osnews.com.

You could have read about it on the promo list, or on kde-core-devel, some
other mailing lists, various blogs, and finally on the dot. I'm not sure we
can do a lot here. KDE has grown to a size where I think we just have to
accept that we can't know about everything what is going on anymore all the
time, and we have to trust in other teams that they do the right thing, guided
by the identity of the KDE community, our common goals and common values.

--
Cornelius Schumacher <schumacher@...>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDE Promo proposal

2009-11-29T01:49:16Z

You are free to join the kde-promo mailing list right now and start
following what we do and even get involved yourself. And as other said
the promo people don't need to be consulted for code changes either.

The rebranding was on mailinglists and planet before it was made
official and it was made official on the dot and planet before any
other news site on the net. It's a bit unfortunate that you read
OSNews first.

Cheers
Lydia

--
Lydia Pintscher
Amarok community manager
kde.org - amarok.kde.org - kubuntu.org
claimid.com/nightrose

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDE Promo proposal

2009-11-28T22:28:38Z

2009/11/29 Parker Coates <parker.coates@...>:

> On Sat, Nov 28, 2009 at 19:20, John Tapsell wrote:
>> Hi,
>>
>> I would like to see a bit more openness from the KDE promo team. I
>> would like to propose that:
>>
>> The KDE promo team discuss internally about their plans, come up
>> with proposals etc as usual, but that those proposals then have to
>> checked by the kde-devel or kde-core-devel or a vote on planet.kde.org
>> or whatever. The purpose being that things that are going to affect
>> the image of all us are at least agreed upon by a majority.
>>
>> I feel that I keep being blindsighted, but rather than just
>> complain, I'd like to come up with a way to improve this.
>>
>> I realise that it's a bit more bureaucratic overhead, and I don't
>> mean for this to apply to everything. But I don't want to read about
>> "KDE rebranding" first on osnews.com.
>
> When it comes to getting a majority approval, I don't think the promo
> team should be any different than any other KDE team. The artists
> aren't required to get a majority approval from the community to
> change the default theme.

Well, perhaps they should? If the default theme for KDE is going to
change, then it would be nice to have discussions about that. I
wouldn't like to first find out about a default theme change from a
news website/twitter either.

> The release team doesn't need majority
> approval from the community to delay the tagging of the beta.

If it's a delay that is so significant that it's going to be on news
sites, then that should probably also be discussed.

> KDE isn't a democracy.
That's a shame :-(

> "The one who does the work decides." That
> applies to more than just code.

Code can be removed, changed etc, before a release. It's out in the
open somewhat (mostly). If there was a major change (of the sort that
would be in the news) then yeah, I'd like that mentioned too.

John

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDE Promo proposal

2009-11-28T21:37:49Z

On Sat, Nov 28, 2009 at 19:20, John Tapsell wrote:

> Hi,
>
> I would like to see a bit more openness from the KDE promo team. I
> would like to propose that:
>
> The KDE promo team discuss internally about their plans, come up
> with proposals etc as usual, but that those proposals then have to
> checked by the kde-devel or kde-core-devel or a vote on planet.kde.org
> or whatever. The purpose being that things that are going to affect
> the image of all us are at least agreed upon by a majority.
>
> I feel that I keep being blindsighted, but rather than just
> complain, I'd like to come up with a way to improve this.
>
> I realise that it's a bit more bureaucratic overhead, and I don't
> mean for this to apply to everything. But I don't want to read about
> "KDE rebranding" first on osnews.com.

When it comes to getting a majority approval, I don't think the promo
team should be any different than any other KDE team. The artists
aren't required to get a majority approval from the community to
change the default theme. The release team doesn't need majority
approval from the community to delay the tagging of the beta.

KDE isn't a democracy. "The one who does the work decides." That
applies to more than just code. Do I see room for improvement with the
new terms chosen by the promo team? Yes. Do I have the right to
complain? No. A group of knowledgeable people, who are much more
passionate about promo than me, came up with this rebranding. If I
wanted a say, I should have joined the promo team (or at least
followed the mailing list).

Or course, that's just my personal opinion.

Parker

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDE Promo proposal

2009-11-28T18:39:34Z

On Sunday 29 November 2009 11:20:27 John Tapsell wrote:
> I would like to see a bit more openness from the KDE promo team. I
> would like to propose that:
Perhaps this needs to go to the promo team list?

Brad

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Dealing with a memory leak

2009-11-28T17:02:32Z

yupp, germany - but rumors about or secretary of family affairs having shut
down the internet are largely exaggerated... as yet ;-)

i'm trapped in 159.18.52.2 and (though i can ping it) get an NXDOMAIN on host

whois knows it:
----------------
OrgName: Allstream Corp.
OrgID: ACCA-2
Address: 200 Wellington Street West
Address: 16th Floor
City: Toronto
StateProv: ON
PostalCode: M5V-3G2
Country: CA

NetRange: 159.18.0.0 - 159.18.255.255
--------

imagebin.ca is 208.68.18.102

traceroute ( 1-8 is local/ISP internal stuff )
---
9 tge-2-2.bbr1.dus1.de.inetbone.net (213.203.213.13) 20.545 ms 17.340 ms
15.903 ms
10 xe-2-3.bbr1.dus1.de.inetbone.net (213.203.213.237) 18.246 ms 18.268 ms
16.124 ms
11 rc2ec.il.shawcable.net (195.69.144.148) 174.984 ms 172.112 ms 171.555
ms
12 rc1nr-tge0-1-5-0.wp.shawcable.net (66.163.77.126) 152.109 ms 151.432 ms
168.389 ms
13 rc2sc-tge0-7-1-0.wp.shawcable.net (66.163.73.186) 148.392 ms 147.579 ms
143.883 ms
14 rc1we-tge0-15-0-0.ed.shawcable.net (66.163.76.109) 161.367 ms 159.142
ms 156.895 ms
15 ra1ar-ge1-1.ed.shawcable.net (66.163.70.42) 157.899 ms 157.451 ms
157.955 ms
16 rx0ar-thinktel-communications.ed.bigpipeinc.com (64.141.127.114) 159.067
ms 157.702 ms 157.633 ms
17 159.18.52.2 (159.18.52.2) 163.544 ms 161.614 ms 161.623 ms
18 * * *
19 * * *
20 * * *
21 * * *
---

Am Sunday 29 November 2009 schrieb Parker Coates:

> On Sat, Nov 28, 2009 at 18:37, Ian Wadham wrote:
> > On Sunday 29 November 2009 6:35:47 am Thomas Lübking wrote:
> >> Unfortunately imagebin.ca remained unreachable from here until now.
> >
> > I routinely experience the same unreachability of imagebin.ca BTW.
> > Thomas is in Germany I believe and I am in Australia. Maybe you
> > or Parker can take it up with imagebin.ca when you are not too busy.
>
> Do either of you happen to be behind a content filter? Imagebin lets
> anyone upload anything, so it's not all that uncommon to see
> pornographic images in the queue there. I wouldn't be surprised if
> some filters blocked it for that reason.
>
> Parker
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

KDE Promo proposal

2009-11-28T16:20:27Z

Hi,

I would like to see a bit more openness from the KDE promo team. I
would like to propose that:

The KDE promo team discuss internally about their plans, come up
with proposals etc as usual, but that those proposals then have to
checked by the kde-devel or kde-core-devel or a vote on planet.kde.org
or whatever. The purpose being that things that are going to affect
the image of all us are at least agreed upon by a majority.

I feel that I keep being blindsighted, but rather than just
complain, I'd like to come up with a way to improve this.

I realise that it's a bit more bureaucratic overhead, and I don't
mean for this to apply to everything. But I don't want to read about
"KDE rebranding" first on osnews.com.

John

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Dealing with a memory leak

2009-11-28T16:03:34Z

On Sat, Nov 28, 2009 at 18:37, Ian Wadham wrote:
> On Sunday 29 November 2009 6:35:47 am Thomas Lübking wrote:
>> Unfortunately imagebin.ca remained unreachable from here until now.
>>
> I routinely experience the same unreachability of imagebin.ca BTW.
> Thomas is in Germany I believe and I am in Australia. Maybe you
> or Parker can take it up with imagebin.ca when you are not too busy.

Do either of you happen to be behind a content filter? Imagebin lets
anyone upload anything, so it's not all that uncommon to see
pornographic images in the queue there. I wouldn't be surprised if
some filters blocked it for that reason.

Parker

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Dealing with a memory leak

2009-11-28T15:36:53Z

On Sunday 29 November 2009 6:35:47 am Thomas Lübking wrote:
> Unfortunately imagebin.ca remained unreachable from here until now.
>
I routinely experience the same unreachability of imagebin.ca BTW.
Thomas is in Germany I believe and I am in Australia. Maybe you
or Parker can take it up with imagebin.ca when you are not too busy.

Cheers, Ian W.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Upstream bugs... (Qt)

2009-11-28T14:31:37Z

On Sunday 29 November 2009 01:01:19 Alexis Ménard wrote:
> If you report the bug i think you get the mail whenever it is modified...

Well, that definitely wasn't the case back then :)

I reported the bug and it was fixed on the next day, but as I said, I heard
about that from Parker, no email was received.

I saw the "watch" option, but I didn't enabled it exactly because I thought I
don't need this as a reporter.

Maybe that got fixed since then, dunno.

Cheers,
Dmitry.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Upstream bugs... (Qt)

2009-11-28T14:01:19Z

If you report the bug i think you get the mail whenever it is modified...

On Sat, Nov 28, 2009 at 4:07 PM, Dmitry Suzdalev <dimsuz@...> wrote:

On Saturday 28 November 2009 17:04:14 Parker Coates wrote:
> Is there a good reason why this isn't automatic? Having to remember
> this extra step is a bit of a pain. I can't really imagine a situation
> where someone cares enough to report a bug, but would would be
> bothered by receiving an email when the bug is fixed.

+1

This is what happened to me and I was really surprised when it was Parker who
informed me that bug is already fixed rather than auto-generated email :)

Cheers,
Dmitry.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Error building Qt 4.6

2009-11-28T13:38:07Z

I'm getting an error at the start of building Qt, using the recommended ./configure line from README.kde-qt. It's an up to date 4.6-stable-patched branch. Is there something basic going wrong here?

The relevant output from ./configure (truncated - there are lots more similar errors) is:

Creating qmake. Please wait...
g++ -c -o project.o -m32 -pipe -DQMAKE_OPENSOURCE_EDITION -g -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -Igenerators/symbian -I/home/david/src/git/kde-qt/include -I/home/david/src/git/kde-qt/include/QtCore -I/home/david/src/git/kde-qt/src/corelib/global -I/home/david/src/git/kde-qt/src/corelib/xml -DQT_NO_PCRE -DQT_BUILD_QMAKE -DQT_BOOTSTRAPPED -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/home/david/src/git/kde-qt/mkspecs/linux-g++-32 -DHAVE_QCONFIG_CPP -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT project.cpp
In file included from /home/david/src/git/kde-qt/include/QtCore/qdatastream.h:1,
from /home/david/src/git/kde-qt/include/QtCore/../../src/corelib/tools/qstringlist.h:46,
from /home/david/src/git/kde-qt/include/QtCore/qstringlist.h:1,
from project.h:45,
from project.cpp:42:
/home/david/src/git/kde-qt/include/QtCore/../../src/corelib/io/qdatastream.h:45:35: error: QtCore/qscopedpointer.h: No such file or directory
In file included from /home/david/src/git/kde-qt/include/QtCore/qdebug.h:1,
from project.cpp:57:
/home/david/src/git/kde-qt/include/QtCore/../../src/corelib/io/qdebug.h:54:37: error: QtCore/qcontiguouscache.h: No such file or directory

--
David Jarvie.
KDE developer.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Dealing with a memory leak

2009-11-28T12:09:53Z

On Saturday 28 November 2009 19:35:47 Thomas Lübking wrote:
> Unfortunately imagebin.ca remained unreachable from here until now.
>
I'll attach the .png - it might just creep in under the size limit

> However, you're not alone and apparently it's not in the driver:
>
> http://lists.freedesktop.org/archives/xorg/2009-November/048190.html
>
> have a look at that thread, there're two links to debian and fedora
> bugtrackers.
>
Thanks for that. I'm using Fedora 11, so I've added my 2p-worth and will be
tracking the report :-)

Anne
--
KDE Community Working Group
New to KDE4? - get help from http://userbase.kde.org

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

xrestop1.png (53K) Download Attachment
signature.asc (205 bytes) Download Attachment

Re: Dealing with a memory leak

2009-11-28T11:35:47Z

Unfortunately imagebin.ca remained unreachable from here until now.

However, you're not alone and apparently it's not in the driver:

http://lists.freedesktop.org/archives/xorg/2009-November/048190.html

have a look at that thread, there're two links to debian and fedora
bugtrackers.

Thomas

Am Saturday 28 November 2009 schrieb Anne Wilson:

> On Friday 27 November 2009 17:55:23 Thomas Lübking wrote:
> > That's not unusual - plasma sucks some memory esp. for the wallpaper, the
> > kwin value will grow with the amount of visible windows, suspending
> > compositing (shift+alt+f12) should drastically reduce it.
> > Please nevertheless check xrestop again when your memory usage is high
> > again (to see whether the pixmaps flow ofer into your RAM)
>
> I got taken by surprise this afternoon, so didn't have time to think, other
> than trying to grab a screenshot of xrestop before I lost things. It's at
> http://imagebin.ca/view/eIgUzR5.html
>
> I managed to shut down Kontact, then killed plasma and restarted it. That
> was enough for me to get a measure of control back and save the document I
> was working on.
>
> Compositing is currently disabled, and X is still taking 55.1% of MEM,
> according to top.
>
> Anne
>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDELIBS and Soprano issues

2009-11-28T09:21:03Z

Your pretty good with those stabs in the dark. That was it. I hadn't been at the Prerequisite page in a while. Thanks for your help

-David

On Sat, Nov 28, 2009 at 9:03 AM, David Nadlinger <david.nadlinger@...> wrote:

Just a stab in the dark: did you forget installing the librdf package
as described in the »Prerequisites« techbase page[1]?

David

[1] http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDELIBS and Soprano issues

2009-11-28T09:03:00Z

Just a stab in the dark: did you forget installing the librdf package
as described in the »Prerequisites« techbase page[1]?

David

[1] http://techbase.kde.org/Getting_Started/Build/KDE4/Prerequisites

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Add System Activity to menu

2009-11-28T08:40:16Z

On Saturday 28 November 2009 16:38:18 Miha Čančula wrote:
> There is K => Programs => System Monitor which opens the same window. Maybe
> I have something installed that you don't.
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
>
thats a diffrent thing top what he means. the system monitor canmonitor
virtually any hardware interface it can get a hand on. an the ctrl+esc thingy
is just a prozess table. More on that: the ctrl+esc thingie has no tabs with
other stuff.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDELIBS and Soprano issues

2009-11-28T08:38:43Z

Thanks, but what is the redland storage backend. I do not see a pakage for it, at least not by typing

apt-get install red <tab>

The only thing available is redland-utils   for which I did install.I tried apt-get install libred <tab> but nothing came up that looked like a good candidate.

I then downloaded and built redland-1.0.9 and its dependency rasqal-0.9.16, but still get the same message when I build kdesupport:

- Soprano Components that will NOT be built:
   * Redland storage backend
   * Raptor RDF serializer

If anyone can provide with the packages to install or compile, I would appreciate it very much.

-David

On Sat, Nov 28, 2009 at 7:35 AM, David Nadlinger <david.nadlinger@...> wrote:

> What packages must I install or build to resolve this issue. Thanks in

> advance for any advise.
The Redland storage backend is needed for KDE, afaik.

David

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Dealing with a memory leak

2009-11-28T08:29:35Z

On Friday 27 November 2009 17:55:23 Thomas Lübking wrote:
> That's not unusual - plasma sucks some memory esp. for the wallpaper, the
> kwin value will grow with the amount of visible windows, suspending
> compositing (shift+alt+f12) should drastically reduce it.
> Please nevertheless check xrestop again when your memory usage is high
> again (to see whether the pixmaps flow ofer into your RAM)
>
I got taken by surprise this afternoon, so didn't have time to think, other
than trying to grab a screenshot of xrestop before I lost things. It's at
http://imagebin.ca/view/eIgUzR5.html

I managed to shut down Kontact, then killed plasma and restarted it. That was
enough for me to get a measure of control back and save the document I was
working on.

Compositing is currently disabled, and X is still taking 55.1% of MEM,
according to top.

Anne
--
KDE Community Working Group
New to KDE4? - get help from http://userbase.kde.org

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

signature.asc (205 bytes) Download Attachment

Re: Add System Activity to menu

2009-11-28T07:38:18Z

There is K => Programs => System Monitor which opens the same window. Maybe I
have something installed that you don't.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: KDELIBS and Soprano issues

2009-11-28T07:35:19Z

> What packages must I install or build to resolve this issue. Thanks in
> advance for any advise.
The Redland storage backend is needed for KDE, afaik.

David

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

KDELIBS and Soprano issues

2009-11-28T07:30:39Z

Hi..

I cannot get kdelibs to build now. I have issues with Soprano. cmakekde on kdelibs produces the following:

Could NOT find Soprano (missing: SOPRANO_PLUGIN_REDLANDBACKEND_FOUND)
Call Stack (most recent call first):
cmake/modules/FindSoprano.cmake:207 (find_package_handle_standard_args)

When I build kdesupport I get the messages below. Could not find any kubuntu 9.10 packages that would resolve the missing components for Redland and Raptor.

-- Soprano Components that will be built:
   * Sesame2 storage backend (java-based)
   * Virtuoso storage backend (Run-time dependancy: Virtuoso)
   * Raptor RDF parser
     (including TriG parser)
   * The CLucene-based full-text search index library
   * D-Bus server/client support

- Soprano Components that will NOT be built:
   * Redland storage backend
   * Raptor RDF serializer

What packages must I install or build to resolve this issue. Thanks in advance for any advise

-David
-

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Upstream bugs... (Qt)

2009-11-28T07:07:38Z

On Saturday 28 November 2009 17:04:14 Parker Coates wrote:
> Is there a good reason why this isn't automatic? Having to remember
> this extra step is a bit of a pain. I can't really imagine a situation
> where someone cares enough to report a bug, but would would be
> bothered by receiving an email when the bug is fixed.

+1

This is what happened to me and I was really surprised when it was Parker who
informed me that bug is already fixed rather than auto-generated email :)

Cheers,
Dmitry.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Upstream bugs... (Qt)

2009-11-28T06:04:14Z

On Fri, Nov 27, 2009 at 02:39, Olivier Goffart wrote:
> This is not automatic, in order to receive the emails, you have to register to
> JIRA, and then you can watch your issue and be notified by emails of changes,
> just like with bugzilla.

Is there a good reason why this isn't automatic? Having to remember
this extra step is a bit of a pain. I can't really imagine a situation
where someone cares enough to report a bug, but would would be
bothered by receiving an email when the bug is fixed.

Parker

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Add System Activity to menu

2009-11-28T04:34:07Z

On Saturday 28 November 2009 12:35:18 Anne Wilson wrote:

> On Saturday 28 November 2009 10:57:07 John Tapsell wrote:
> > Hi all,
> >
> > One of the biggest 'complaints' that I had about System Activity was
> > that people did not even know it existed! It pops up when you press
> > ctrl+esc, but it is not discoverable at all.
>
> +1000 :-) Thanks for pointing to it
>
> > I want to add this shortcut to the krunner button that launches it,
> > but one of the other suggestions was to add it to the main KDE menu in
> > the thing-previously-known-as-kicker. There's a section there already
> > for system stuff, so it would seem to be a natural fit there.
> >
> > What do people think?
>
> Excellent idea, IMO. I'm sure that many of our more experienced users
> would appreciate it.
>
> Anne
>

Maybe a nice idea for the plasma desktop so you can have a look at it at
times? We have a monitoring section not for nothing

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Add System Activity to menu

2009-11-28T03:35:18Z

On Saturday 28 November 2009 10:57:07 John Tapsell wrote:
> Hi all,
>
> One of the biggest 'complaints' that I had about System Activity was
> that people did not even know it existed! It pops up when you press
> ctrl+esc, but it is not discoverable at all.
>
+1000 :-) Thanks for pointing to it

> I want to add this shortcut to the krunner button that launches it,
> but one of the other suggestions was to add it to the main KDE menu in
> the thing-previously-known-as-kicker. There's a section there already
> for system stuff, so it would seem to be a natural fit there.
>
> What do people think?
>
Excellent idea, IMO. I'm sure that many of our more experienced users would
appreciate it.

Anne
--
KDE Community Working Group
New to KDE4? - get help from http://userbase.kde.org

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

signature.asc (205 bytes) Download Attachment

Add System Activity to menu

2009-11-28T02:57:07Z

Hi all,

One of the biggest 'complaints' that I had about System Activity was
that people did not even know it existed! It pops up when you press
ctrl+esc, but it is not discoverable at all.

I want to add this shortcut to the krunner button that launches it,
but one of the other suggestions was to add it to the main KDE menu in
the thing-previously-known-as-kicker. There's a section there already
for system stuff, so it would seem to be a natural fit there.

What do people think?

John

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<