Re: Journalktl: A new journald log viewer for KDE

On Wednesday, April 15, 2015 10:46:23 PM Luigi Toscano wrote: > David Edmundson ha scritto: > > On Wed, Apr 15, 2015 at 10:18 PM, Albert Astals Cid > > > > wrote: > > El Dimecres, 15 d'abril de 2015, a les 15:09:03, Luigi Toscano va escriure: > > > On Wednesday 15 o

Re: [kde-promo] The name of Applications 4.14 + 1

On Thursday, July 17, 2014 20:54:57 Albert Astals Cid wrote: > El Dimecres, 16 de juliol de 2014, a les 16:50:18, > grantksupp...@operamail.com > va escriure: > > > Anyone has another suggestion? > > > > > > Do we go with "KDE Applications $YEAR.$MONTH"? > > > > .MM so it's completely obvious

Re: Query regarding building kdelibs

On May 12, 2014 8:36:55 PM EDT, Aaron Zakhrov wrote: >the link you mentioned is for fedora not for kubuntu. I suggest you >uprade >to kubuntu 14.04 LTS. It has kde 4.12 Actually it has 4.13. Scott K >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: Baloo Indexer and options

On Monday, April 21, 2014 21:20:49 Vishesh Handa wrote: > On Monday, April 21, 2014 03:54:34 PM Roney Gomes wrote: > > Em seg 21 abr 2014, às 20:19:30, Vishesh Handa escreveu: > > > What's the name of the process? If it's baloo_file_cleaner, then that's > > > probably cause it's removing all the in

Re: Upcoming changes to CI system

Ben Cooksley wrote: >Hi all, > >In order to improve the maintainability and cleanliness of the "shared >dependencies" the way they will be handled on the CI system will be >changing. > >The nature of this change is that all projects which need a "shared >dependency" will now need to declare a de

Re: Problem installing kdelibs

On Sunday, April 07, 2013 06:17:38 AM Ashish Singh wrote: > Hey everyone, > > I am trying to install kdelibs[1] on Ubuntu 12.10 but it so happens that > every time i give the cmake command i get an error of some dependency not > found and this has been happening for quite some time now. I have als

Re: Inclusion of kio-mtp in KDE SC Release 4.11

Kubuntu is shipping kio-mtp along side KDE SC 4.10 in our next release and it would be nice to have a release. Scott K On Saturday, March 16, 2013 12:31:27 AM Àlex Fiestas wrote: > You may want to make a release before merging it to kde-workspace so > distributions can ship it without having to

Re: backup system for KDE

On Saturday, January 05, 2013 04:55:24 PM Adrien wrote: > Hi, > > I am looking for a backup system, well integrated into KDE. MacOS has > TimeMachine, but for KDE I only found backintime-kde, which is developped > but not well integrated, and timevault, which is well integrated and very > promisin

Re: [Nepomuk] Nepomuk - Moving away from Strigi

On Monday, October 08, 2012 09:06:04 PM Albert Astals Cid wrote: > El Dilluns, 8 d'octubre de 2012, a les 20:59:49, Martin Sandsmark va escriure: > > On Monday 8. October 2012 20.06.47 Reindl Harald wrote: > > > this argumentation is invalid > > > with this argumentation you could smoke crack ever

Re: Moving kde-workspace -> scriptengines/python to python 3

On Thursday, March 01, 2012 09:39:25 PM Frank Reininghaus wrote: > Hi, > > Am 27. Februar 2012 04:29 schrieb Wolfgang Mader: > > Dear kde-devel list, > > > > I tried to compile kde-workspace in a python 3 environment and > > encountered statements which are only valid for python 2. For example >

Re: KDE 4.8 Thoughts

On Friday, January 27, 2012 09:26:35 AM Lindsay Mathieson wrote: > On Fri, 27 Jan 2012 09:28:20 AM Andrew Mason wrote: > > KDE 4.8 is rocking for me too.Using the Kubuntu PPA's on Sandy Bridge > > system and it's just lightning fast to do anything. > > do you get accelerated 3D and visual effects

Re: Problem building kde-workspace

There is a draft PEP that's been circulated for consideration, but /usr/bin/python2 is also (at least for now) a distro specific change from Python upstream. Scott K > Got that same problem and a simple ln -s /usr/bin/python2 > $KDE_INST_DIR/bin/python solved it for me. Kind of a workaround, but

Re: Problem building kde-workspace

> On 17.10.11 16:06:01, Tomaz Canabrava wrote: >> probably has something to do with my python version, but ... >> >> Generating singleview.moc >> File >> "/kde/kde-workspace/plasma/generic/scriptengines/python//plasma_importer.py", >> line 107 >> exec code in mod.__dict__ >> ^ >>

Re: Bug triage process needs help

On Saturday, October 01, 2011 09:33:58 AM Martin Gräßlin wrote: ... > Downstreams do not backport fixes. We see that quite clearly. There is no > need to assume that this would change. They also don't know what bugs > exists and what has to be backported. For really critical fixes I do inform > th

Re: Bug triage process needs help

On Friday, September 30, 2011 10:19:40 PM Sven Burmeister wrote: > Am Freitag, 30. September 2011, 17:12:01 schrieb Martin Gräßlin: > > The bugtracker in it's current state does not help to increase the > > quality of the software. In fact the quality decreases as the > > developers have to spend t

Re: Bug triage process needs help

On Friday, September 30, 2011 09:10:22 PM Andras Mantia wrote: > I agree. There is a common complaint by developers, that they waste > their time on bug report reading/asnwering instead of coding. While this > seems reasonable, you have to understand that developing a software > product involve

Re: Bug triage process needs help

On Friday, September 30, 2011 02:29:47 PM todd rme wrote: > On Fri, Sep 30, 2011 at 11:56 AM, Sven Burmeister > > wrote: > > Am Donnerstag, 29. September 2011, 13:25:49 schrieb Sebastian Kügler: > >> > It's frustrating for users submitting bug reports when an easily > >> > reproducible bug sits i

Re: No more release schedules.

On Thursday, June 09, 2011 06:08:56 PM Tom Albers wrote: > > Having KDE's own packages also released in an uncoordinated > > fashion > > Wow. Who suggested that? That would make a mess indeed. I certainly did not > ever suggest that. If you think so, pleas reread all my mails. I've > suggested th

Re: No more release schedules.

Kevin Kofler wrote: >OK, since a lot of context apparently got lost during the message >passing, let >me just state my (personal) position clearly: > >What I think is acceptable: >* Module X wants feature Y, which is non-invasive and well-tested and >does not >change the user experience nor t

Re: Releases of the thing that was KDE

On Thursday, June 09, 2011 07:22:32 AM Sebastian Kügler wrote: > Hi Scott, > > On Tuesday, June 07, 2011 03:13:43 Scott Kitterman wrote: > > It may be that there was more to the release implications of the git > > transition than "we're sure it'll get figured

Re: Releases of the thing that was KDE

Nicolas Alvarez wrote: >Scott Kitterman wrote: >> New thread as requested. >> >> I've been told on IRC that we will still have an integrated release >of >> what used to be KDE (I've no clue what to call it now since I think I >read >> KDE SC w

Re: Releases of the thing that was KDE

John Layt wrote: >On 6 June 2011 23:36, Scott Kitterman wrote: >> >> I get we need to modularize for a number of important reasons, but I >don't >> see >> the companion story for how this all gets released as something >coherent >> and >>

Releases of the thing that was KDE

New thread as requested. I've been told on IRC that we will still have an integrated release of what used to be KDE (I've no clue what to call it now since I think I read KDE SC was deprecated). All I see in the messaging from the platform sprint seems to be about further deconstruction and de