KDE SC 4.8.4 important problems

[José Manuel Santamaría Lema]

Hello,

firstly, to be honest, let me say I'm doing huge effort to write this mail in a 
way that I don't look like a clueless cretin who reports bugs to the mailing 
lists instead of the proper place (bugs.kde.org) just to "cheat" and get "my" 
bugs fixed. I promise I'm not that kind of person, I have a git/svn KDE account 
and I'm already doing a very modest contribution. In my honest opinion I know 
a bit how things work in KDE with regarding to the bug reporting stuff.

Also I'm packaging KDE for Debian in a team collaborating with other people 
since some time ago (I've been involved in 4.5.x, 4.6.x, 4.7.x and 4.8.x) and 
that's why I am writing here: when testing the latest point release of KDE SC 
(4.8.4), we are getting several crashes, and most of them are the kind of bugs 
(called release-critical in Debian) which would prevent us to release packages 
in the next stable release or migrate them to the "testing" branch. 

Most of these crashes follow this pattern (sorry for the vagueness, I 
hope to gather more information this night or so, I'll try to keep you posted 
but I can't promise anything):
1. Can't be reproduced with Nepomuk disabled.
2. Can't be reproduced with kdelibs 4.8.3
3. Can't be reproduced with KDE SC 4.9.
4. Could also be reproduced by various users and developers from other 
distributions.
5. They are not 100% reproducible; however they happen everytime in some 
computers, on others just very often; so often that make certain KDE programs 
unusuable.
6. I _feel_ backtraces might be invalid.

Since I have been packaging KDE (more or less since 4.5 as said above) I never 
got 7 potential RC bugs in a release (not even a .0 one) after just ~2 days of 
use. Read again the characteristics 2. 3. and .4; that in conjunction with the 
fact that some people just discovered today how you are managing git 
branches/freeze for kdelibs (myself included) is why I think we are getting 
some people in other thread questioning -with or without reason- the kdelibs 
development model. I don't want to discuss the kdelibs development model in 
this thread (I would really prefer to keep any possible "omfg kdelibs 
developers are using the same branch for 4.9 and 4.8" messages in the other 
thread) I'm just explaining the situation, I hope you get now why you are 
reading the things you are reading in the other thread.

That being said, in this thread I want to focus on the actual grave problem(s) 
of 4.8.4, this is the list of crashes I have been experiencing:

#1 dolphin:
I can reproduce it right now in one of my computers just opening it, in other 
sometimes it crashes just clicking a file or folder. Eshat Cakar -a fellow 
Debian packager- also got other crash just clicking a folder, however he can't 
reproduce it anymore after he rebooted his computer.
Backtraces:
http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_dolphin_santa.kcrash.
http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_dolphin_eshat.txt

#2 gwenview 
I can reproduce it just clicking an image and sometimes even just starting the 
application.
Backtrace:
http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_gwenview_santa.kcrash

#3 kontact executing the kaddressbook component
I can reproduce it very oftenly just clicking the kaddressbok component in 
kontact.
Backtrace:
http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_kontact_santa.kcrash

#4 kmail executed outside kontact
I can reproduce it just executing kmail outside kontact
Backtrace:
http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug_kmail_santa.kcrash

#5 kmail marking messages as read
I think this one got fixed by a commit in kdepimlibs, which I included in the 
debian packaging. Please ignore for now.

#6 kontact executing various components: calendar, to-do list, journal
When clicking on various kontact component I'm getting a segmentation fault, 
always with the same backtrace:
http://alioth.debian.org/~santa-guest/4.8.4_crashes/bug2_kontact_santa.kcrash

#7 kmail links
I can reproduce this one just opening a message with an url. Just clicking 
that url, which would it open it in konqueror given my local configuration 
crashes kmail:
Backtrace:
http://alioth.debian.org/~santa-guest/4.8.4_crashes/kmail_links.kcrash


signature.asc
Description: This is a digitally signed message part.

Re: KDE SC 4.8.4 important problems

[Aaron J. Seigo]

On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:
> #1 dolphin:
> #2 gwenview
> #6 kontact executing various components: calendar, to-do list, journal
> #7 kmail links

these are all the same crash, or at least related to each other. it is
crashing in KServiceTypeTrader::defaultOffers or KMimeTypeTrader::query
apparently at times in KSycocaDict::find_string.

> #3 kontact executing the kaddressbook component
> #4 kmail executed outside kontact

these need to be sent to the kdepim team as they are crashes in kdepim
components (address book library, kmail editor, ...)

--
Aaron J. Seigo

signature.asc
Description: This is a digitally signed message part.

Re: KDE SC 4.8.4 important problems

[Aaron J. Seigo]

On Sunday, June 10, 2012 11:20:09 Aaron J. Seigo wrote:
> On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:
> > #1 dolphin:
> > #2 gwenview
> > #6 kontact executing various components: calendar, to-do list, journal
> > #7 kmail links
>
> these are all the same crash, or at least related to each other. it is
> crashing in KServiceTypeTrader::defaultOffers or KMimeTypeTrader::query
> apparently at times in KSycocaDict::find_string.

curious: on an affected system, if you delete

`kde4-config --localprefix`/cache-freedom/ksycoca4*

do the crashes go away?

possible culprit commits:

1a07fea2eaa69d571d5818812502edcc1d680d9c
e91e5fed6b1aad365e12e919f430c3e8147552d3

neither are super recent, but they both touch the relevant code. there was one
change to kmimetype by dfaure but it is not implicated by the backtraces nor
can i see how it would be (it added a required method, did not change existing
code paths and definitely not the ksycoca code underneath it)

--
Aaron J. Seigo

signature.asc
Description: This is a digitally signed message part.

Re: KDE SC 4.8.4 important problems

[Peter Penz]

On 06/10/2012 11:20 AM, Aaron J. Seigo wrote:

On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:

#1 dolphin:
#2 gwenview
#6 kontact executing various components: calendar, to-do list, journal
#7 kmail links


these are all the same crash, or at least related to each other. it is
crashing in KServiceTypeTrader::defaultOffers or KMimeTypeTrader::query
apparently at times in KSycocaDict::find_string.


The issue has been tracked at
https://bugs.kde.org/show_bug.cgi?id=268064 - updating Soprano to the 
latest master resolves the crash. But I don't know more about the 
root-cause of this. Probably a Nepomuk-related update missed a proper 
versioning-check of Soprano?



#3 kontact executing the kaddressbook component
#4 kmail executed outside kontact


these need to be sent to the kdepim team as they are crashes in kdepim
components (address book library, kmail editor, ...)

Re: KDE SC 4.8.4 important problems

[Anders Lund]

Den 10-06-2012 11:38, Peter Penz skrev:

The issue has been tracked at
https://bugs.kde.org/show_bug.cgi?id=268064 - updating Soprano to the 
latest master resolves the crash. But I don't know more about the 
root-cause of this. Probably a Nepomuk-related update missed a proper 
versioning-check of Soprano? 
I run a fully updated archlinux, and get these crashes too. So using kde 
4.8.4 requires unreleased soprano ? :0


Anders

Re: KDE SC 4.8.4 important problems

[Andreas Pakulat]

Hi,

Am Sonntag, 10. Juni 2012 schrieb Peter Penz :

> On 06/10/2012 11:20 AM, Aaron J. Seigo wrote:
>
>> On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:
>>
>>> #1 dolphin:
>>> #2 gwenview
>>> #6 kontact executing various components: calendar, to-do list, journal
>>> #7 kmail links
>>>
>>
>> these are all the same crash, or at least related to each other. it is
>> crashing in KServiceTypeTrader::**defaultOffers or KMimeTypeTrader::query
>> apparently at times in KSycocaDict::find_string.
>>
>
> The issue has been tracked at
> https://bugs.kde.org/show_bug.**cgi?id=268064-
>  updating Soprano to the latest master resolves the crash. But I don't
> know more about the root-cause of this. Probably a Nepomuk-related update
> missed a proper versioning-check of Soprano?


There has been an abi breakage in soparano's latest release (fixed in the
repository already), so updating to that soprano release requires
rebuilding all other code that uses it. I've seen backtraces ending in
qstring::ref having such abi incompatibilities as cause, so it would fit at
least those cases.

Andreas

Re: KDE SC 4.8.4 important problems

[Modestas Vainius]

Hello,

On sekmadienis 10 Birželis 2012 13:57:09 Andreas Pakulat wrote:
> There has been an abi breakage in soparano's latest release (fixed in the
> repository already), so updating to that soprano release requires
> rebuilding all other code that uses it. I've seen backtraces ending in
> qstring::ref having such abi incompatibilities as cause, so it would fit at
> least those cases.

We have never had soprano 2.5.76 or other alpha, only stable 2.7.6. And 
kdelibs 4.8.4 is completely broken for us.

-- 
Modestas Vainius 


signature.asc
Description: This is a digitally signed message part.

Re: KDE SC 4.8.4 important problems

[Albert Astals Cid]

El Diumenge, 10 de juny de 2012, a les 11:30:13, Aaron J. Seigo va escriure:
> On Sunday, June 10, 2012 11:20:09 Aaron J. Seigo wrote:
> > On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:
> > > #1 dolphin:
> > > #2 gwenview
> > > #6 kontact executing various components: calendar, to-do list, journal
> > > #7 kmail links
> > 
> > these are all the same crash, or at least related to each other. it is
> > crashing in KServiceTypeTrader::defaultOffers or KMimeTypeTrader::query
> > apparently at times in KSycocaDict::find_string.
> 
> curious: on an affected system, if you delete
> 
>   `kde4-config --localprefix`/cache-freedom/ksycoca4*
> 
> do the crashes go away?

No they don't

Cheers,
  Albert

> 
> possible culprit commits:
> 
>   1a07fea2eaa69d571d5818812502edcc1d680d9c
>   e91e5fed6b1aad365e12e919f430c3e8147552d3
> 
> neither are super recent, but they both touch the relevant code. there was
> one change to kmimetype by dfaure but it is not implicated by the
> backtraces nor can i see how it would be (it added a required method, did
> not change existing code paths and definitely not the ksycoca code
> underneath it)

Re: KDE SC 4.8.4 important problems

[Albert Astals Cid]

El Diumenge, 10 de juny de 2012, a les 12:57:09, Andreas Pakulat va escriure:
> Hi,
> 
> Am Sonntag, 10. Juni 2012 schrieb Peter Penz :
> > On 06/10/2012 11:20 AM, Aaron J. Seigo wrote:
> >> On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:
> >>> #1 dolphin:
> >>> #2 gwenview
> >>> #6 kontact executing various components: calendar, to-do list, journal
> >>> #7 kmail links
> >> 
> >> these are all the same crash, or at least related to each other. it is
> >> crashing in KServiceTypeTrader::**defaultOffers or KMimeTypeTrader::query
> >> apparently at times in KSycocaDict::find_string.
> > 
> > The issue has been tracked at
> > https://bugs.kde.org/show_bug.**cgi?id=268064 > g.cgi?id=268064>- updating Soprano to the latest master resolves the
> > crash. But I don't know more about the root-cause of this. Probably a
> > Nepomuk-related update missed a proper versioning-check of Soprano?
> 
> There has been an abi breakage in soparano's latest release (fixed in the
> repository already), so updating to that soprano release requires
> rebuilding all other code that uses it. I've seen backtraces ending in
> qstring::ref having such abi incompatibilities as cause, so it would fit at
> least those cases.

As Modestias says, this has nothing to do with those ABI changes since it 
fails with stable soprano.

Albert

> 
> Andreas

Re: KDE SC 4.8.4 important problems

[Albert Astals Cid]

El Diumenge, 10 de juny de 2012, a les 11:49:38, Anders Lund va escriure:
> Den 10-06-2012 11:38, Peter Penz skrev:
> > The issue has been tracked at
> > https://bugs.kde.org/show_bug.cgi?id=268064 - updating Soprano to the
> > latest master resolves the crash. But I don't know more about the
> > root-cause of this. Probably a Nepomuk-related update missed a proper
> > versioning-check of Soprano?
> 
> I run a fully updated archlinux, and get these crashes too. So using kde
> 4.8.4 requires unreleased soprano ? :0

It should not, but seems something bad slipped in.

Cheers,
  Albert

> 
> Anders

Re: KDE SC 4.8.4 important problems

[Albert Astals Cid]

El Diumenge, 10 de juny de 2012, a les 11:20:09, Aaron J. Seigo va escriure:
> On Sunday, June 10, 2012 03:23:04 José Manuel Santamaría Lema wrote:
> > #1 dolphin:
> > #2 gwenview
> > #6 kontact executing various components: calendar, to-do list, journal
> > #7 kmail links
> 
> these are all the same crash, or at least related to each other. it is
> crashing in KServiceTypeTrader::defaultOffers or KMimeTypeTrader::query
> apparently at times in KSycocaDict::find_string.

FWIW if i add

Q_ASSERT(!m_factories.hasLocalData());

to KSycocaFactorySingleton constructor in ksycocafactory.h if does assert, 
don't ask me why since it makes no sense, and it doesn't make any sense either 
that it does not assert if nepomukserver is not running.

I tried to do some debugging yesterday and the only conclusion i found is that 
something is writing very off memory, but totally failed which could be the 
culprit and gdb/valgrind did not point me in the right direction either (or i 
cculd not read their hints if there was any :D)

Cheers,
  Albert

> 
> > #3 kontact executing the kaddressbook component
> > #4 kmail executed outside kontact
> 
> these need to be sent to the kdepim team as they are crashes in kdepim
> components (address book library, kmail editor, ...)

Please subscribe to release-team@ if your project is part of the KDE SC release

[Myriam Schweingruber]

Hi all,

The recent problems with various components of the KDE SC beta release
has shown one major barrier in problem solving:

When the distribution packagers get aware of problems they need to go
through hoops to actually reach the project people to notify the
problems. They need to go individually to the various mailing lists,
subscribe, wait for authorization etc.

Instead of asking all packagers to subscribe to the various project
mailing lists it would be much easier if the project people would
subscribe to the release-team@ mailing list.

So please, all project leads, subscribe to release-t...@kde.org here:

https://mail.kde.org/mailman/listinfo/release-team

And please, be around on release times, as it is equaly difficult for
the release-team if they have to run after various people to make a
release actually happen. Remember, we have clearly defined schedules:
http://techbase.kde.org/Schedules

It is a small step for each of you and a big leap to a better KDE Quality :)

Regards, Myriam

-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)

Re: Review Request: khtml: Fix memleak in DOMStringImpl::lower usage

[Maks Orlovich]

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105099/#review14587
---

Ship it!


Ship It!

- Maks Orlovich


On May 29, 2012, 6:05 p.m., Bernd Buschinski wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/105099/
> ---
> 
> (Updated May 29, 2012, 6:05 p.m.)
> 
> 
> Review request for kdelibs.
> 
> 
> Description
> ---
> 
> khtml: Fix memleak in DOMStringImpl::lower usage
> 
> DOMStringImpl::lower() returns a new lower DOMStringImp*, which needs to be 
> freed.
> While it does make sense for all other places, and in all other places we 
> keep proper track of it, this is not the case in 
> khtml::ProspectiveTokenizer::processAttribute() 
> (htmlprospectivetokenizer.cpp:720)
> 
> 
> This fixed memleaks like:
> 
> ==17681== 728 (512 direct, 216 indirect) bytes in 16 blocks are definitely 
> lost in loss record 2,907 of 3,059
> ==17681==at 0x4C2ABE7: operator new(unsigned long) 
> (vg_replace_malloc.c:287)
> ==17681==by 0x1A7D38E9: DOM::DOMStringImpl::lower() const 
> (dom_stringimpl.cpp:396)
> ==17681==by 0x1A802734: khtml::ProspectiveTokenizer::processAttribute() 
> (htmlprospectivetokenizer.cpp:720)
> ==17681==by 0x1A803DEF: 
> khtml::ProspectiveTokenizer::tokenize(khtml::TokenizerString const&) 
> (htmlprospectivetokenizer.cpp:540)
> ==17681==by 0x1A7FD0D7: khtml::HTMLTokenizer::scriptHandler() 
> (htmltokenizer.cpp:497)
> ==17681==by 0x1A7FD4DC: 
> khtml::HTMLTokenizer::parseRawContent(khtml::TokenizerString&) 
> (htmltokenizer.cpp:379)
> ==17681==by 0x1A7FE972: 
> khtml::HTMLTokenizer::parseTag(khtml::TokenizerString&) 
> (htmltokenizer.cpp:1528)
> ==17681==by 0x1A7FF15D: 
> khtml::HTMLTokenizer::write(khtml::TokenizerString const&, bool) 
> (htmltokenizer.cpp:1797)
> ==17681==by 0x1A74AC77: KHTMLPart::write(char const*, int) 
> (khtml_part.cpp:2096)
> ==17681==by 0x1A740E71: KHTMLPart::slotRestoreData(QByteArray const&) 
> (khtml_part.cpp:1763)
> ==17681==by 0x1A76610E: KHTMLPart::qt_static_metacall(QObject*, 
> QMetaObject::Call, int, void**) (khtml_part.moc:255)
> ==17681==by 0x78B8306: QMetaObject::activate(QObject*, QMetaObject 
> const*, int, void**) (qobject.cpp:3547)
> 
> 
> Diffs
> -
> 
>   khtml/html/htmlprospectivetokenizer.cpp 0e58709 
> 
> Diff: http://git.reviewboard.kde.org/r/105099/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Bernd Buschinski
> 
>

Re: Review Request: kjs: FunctionObject prototype attribute should be [[Writable]]: true, [[Enumerable]]: false, [[Configurable]]: false

[Maks Orlovich]

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105122/#review14588
---

Ship it!


Did you test function expressions (as in x = function foo()) as well?
The constructor is used for stuff like x = new Function(), if I get what you 
were referring to.


- Maks Orlovich


On May 31, 2012, 9 p.m., Bernd Buschinski wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/105122/
> ---
> 
> (Updated May 31, 2012, 9 p.m.)
> 
> 
> Review request for kdelibs.
> 
> 
> Description
> ---
> 
> kjs: FunctionObject prototype attribute should be [[Writable]]: true, 
> [[Enumerable]]: false, [[Configurable]]: false
> ECMA Edition 5.1r6 - 15.3.5.2
> 
> the prototype must have DontEnum property otherwise it shows up as enumerable 
> key.
> 
> 
> I expected that this must be fixed in the function_object.cpp constructor, 
> but its never used in for code like
> 
> function foo() {};
> 
> 
> Diffs
> -
> 
>   kjs/nodes.cpp 0b0749a 
> 
> Diff: http://git.reviewboard.kde.org/r/105122/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Bernd Buschinski
> 
>

Re: Review Request: kjs: Implement JSON.parse

[Maks Orlovich]

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105056/#review14590
---



kjs/json_object.cpp


What namespace do the symbols for this end up in?




kjs/json_object.cpp


What happens if the call threw an exception?




kjs/json_object.cpp


I think it's true, but needs one more proviso: the check on line 89.



kjs/json_object.cpp


I think if you don't put in a space between * and /* some Windows compiler 
will whine.
(Warnings only, I think, but someone was bothered by it enough in the past 
to ask us to change a bunch)



kjs/json_object.cpp


What happens if toObject throws? (I think it can.. but I might be wrong).




kjs/jsonlexer.h


explicit



kjs/jsonlexer.h


explicit



kjs/jsonlexer.h


What's the return value on failure?



kjs/jsonlexer.cpp


static




kjs/jsonlexer.cpp


static



kjs/jsonlexer.cpp


static, comment pareameters?




kjs/jsonlexer.cpp


I don't think this is needed anymore?
(Nor the similar one in arrays)



kjs/jsonlexer.cpp


This looks like it will run out of stack space pretty quickly. I think it 
would be better to instead of firstArrayRun to have something more like what 
you have for objects. (Or just use propAdded in the same way)




kjs/jsonlexer.cpp


So JSON doesn't have 'strings'?




kjs/jsonlexer.cpp


Where did the -? go?




kjs/jsonlexer.cpp


Comment method?


- Maks Orlovich


On May 28, 2012, 7:52 p.m., Bernd Buschinski wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/105056/
> ---
> 
> (Updated May 28, 2012, 7:52 p.m.)
> 
> 
> Review request for kdelibs.
> 
> 
> Description
> ---
> 
> kjs: Implement JSON.parse
> 
> 
> Diffs
> -
> 
>   kjs/CMakeLists.txt 1188064 
>   kjs/interpreter.cpp cf1acf1 
>   kjs/json_object.h PRE-CREATION 
>   kjs/json_object.cpp PRE-CREATION 
>   kjs/jsonlexer.h PRE-CREATION 
>   kjs/jsonlexer.cpp PRE-CREATION 
>   kjs/libkjs.map e9f679f 
> 
> Diff: http://git.reviewboard.kde.org/r/105056/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Bernd Buschinski
> 
>

Re: Review Request: implement support for window.onhashchange

[Maks Orlovich]

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104946/#review14592
---

Ship it!


Looks good, except for a few nitpicks.


khtml/ecma/kjs_events.cpp


5, not 7



khtml/ecma/kjs_window.h


Add HashChangeEventCtor as well?


- Maks Orlovich


On May 15, 2012, 12:56 p.m., Martin Tobias Holmedahl Sandsmark wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/104946/
> ---
> 
> (Updated May 15, 2012, 12:56 p.m.)
> 
> 
> Review request for kdelibs.
> 
> 
> Description
> ---
> 
> Implement a custom hashchange event, and make the khtml kpart emit it
> when we are asked to navigate to another anchor, and the ref is
> different.
> 
> 
> Diffs
> -
> 
>   khtml/ecma/kjs_events.h 3727b94 
>   khtml/ecma/kjs_events.cpp e7c7e5b 
>   khtml/ecma/kjs_html.h 089b550 
>   khtml/ecma/kjs_html.cpp d64e07c 
>   khtml/ecma/kjs_window.h 416b045 
>   khtml/ecma/kjs_window.cpp e75e6e7 
>   khtml/html/html_baseimpl.cpp baa13b5 
>   khtml/khtml_part.cpp 24589e4 
>   khtml/misc/htmlattrs.in 21a2363b 
>   khtml/misc/htmlnames.h e3adbe7 
>   khtml/misc/htmlnames.cpp 3b22b6d 
>   khtml/xml/dom2_eventsimpl.h 5b452d2 
>   khtml/xml/dom2_eventsimpl.cpp f01a533 
> 
> Diff: http://git.reviewboard.kde.org/r/104946/diff/
> 
> 
> Testing
> ---
> 
> tested extensively against http://lolcats.iskrembilen.com/
> 
> 
> Thanks,
> 
> Martin Tobias Holmedahl Sandsmark
> 
>

Re: Re: ALERT: KDElibs (at least) 4.8.4 is actually 4.8.80+

[Sebastian Kügler]

Kevin,

On Saturday, June 09, 2012 23:20:16 Kevin Kofler wrote:
>  you are hurting everyone else trying to package Plasma Active.

You should start considering that we're actually creating the thing. If we had 
promised you it was fit for general consumption by any distro packager, you 
might have a point. We have not, and you know the reason, it's right there, in 
front of you.

That said, we've greatly reduced the delta already and merged back most of our 
work into released branches. For reasons that go beyond the scope of this 
thread, that work is not finished, but will be at some point in the future. 

Until then, you can either use the fine Mer or Balsam packages. Don't knock on 
our door for support until you've changed your general attitude to be positive 
and constructive, however.

There is no entitlement that we need to make it as easy for you as possible, 
if you want to package this new stuff, you'll have to work with what we have 
(or in a wider sense, you have to work *with* us). If you just feel like a 
consumer waiting for perfection to be served to you fresh, you'll have to have 
patience.

Cheers,
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9