Re: KDE Frameworks 5.28.0

2016-11-06 Thread Aleix Pol 
On Sun, Nov 6, 2016 at 11:19 PM, David Faure  wrote:
> On dimanche 6 novembre 2016 23:00:26 CET Aleix Pol wrote:
>> It is, on the other hand it's because KConfig cmake scripts were
>> parsing wrongly a desktop file. If you want I can take another
>> approach that will solve this specific case, but in the end it's an
>> error we weren't catching.
>
> That might be, but we can't really release a version of KF5 that breaks
> compilation of the latest plasma release.
>
> As wrong as it was, it "worked" from a plasma point of view.
>
>> The Plasma/5.8 branch has been fixed, maybe we can rush another stable
>> release of 5.8?
>
> No idea how doable that is. Maybe we can "release" a patch? :-)
>
>> I'm don't think we want to maintain the old behavior for KConfig, TBH.
>
> Not for long, but maybe just until the next plasma release?

This will do:
https://phabricator.kde.org/D3287

Aleix

Re: kde-baseapps split up

2016-11-06 Thread Albert Astals Cid 
El dilluns, 7 de novembre de 2016, a les 0:18:59 CET, David Faure va escriure:
> On lundi 7 novembre 2016 00:07:57 CET Albert Astals Cid wrote:
> > What happens with kdepasswd then?
> 
> Dead.
> 
> > We stop releasing it?
> 
> Yes.
> 
> > Where was this discussed?
> 
> plasma-devel, because I suggested moving it next to the useraccount KCM (the
> only user of kdepasswd), and the reply was "that KCM is dead, it's not even
> compiled in, user-manager replaced it".
> So kdepasswd is now completely unused.

I mean it's still an app people can use form the command line, but ok.

https://quickgit.kde.org/?p=sysadmin%2Frelease-tools.git=commit=7f0c50781f26b9dec2ba6fd6399d7dcc29df3168

Cheers,
  Albert

Re: Re: kde-baseapps split up

2016-11-06 Thread Andreas Sturmlechner 
On Monday, 7 November 2016 at 00:07, Albert Astals Cid wrote:
> What happens with kdepasswd then? We stop releasing it? Where was this 
> discussed?

*Some* discussion appears to have happened here: https://mail.kde.org/
pipermail/plasma-devel/2016-October/061215.html

If I understand it correctly, the last user of kdepasswd would have been a 
dead Plasma kcm.

Regards,
Andreas

Re: kde-baseapps split up

2016-11-06 Thread David Faure 
On lundi 7 novembre 2016 00:07:57 CET Albert Astals Cid wrote:
> What happens with kdepasswd then?

Dead.

> We stop releasing it? 

Yes.

> Where was this discussed?

plasma-devel, because I suggested moving it next to the useraccount KCM (the 
only user of kdepasswd), and the reply was "that KCM is dead, it's not even 
compiled in, user-manager replaced it".
So kdepasswd is now completely unused.

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

Re: K3b 2.10.0 Applications/16.12

2016-11-06 Thread Albert Astals Cid 
El divendres, 4 de novembre de 2016, a les 10:39:44 CET, Leslie Zhai va 
escriure:
> I am so sorry to break the dependency freeze oflibkcddb
> regarding the Applications/16.08
> release! I should pay more attention to deadline - Nov 09 is freeze?

Yes, you should pay more attention.

https://community.kde.org/Schedules/Applications/16.12_Release_Schedule

> > On other kind of news, http://k3b.org/ looks like it has very old stuff
> > and is unamtained, maybe you could go over it, see if there's anything
> > worth keeping and if not we can just redirect it to
> > https://userbase.kde.org/K3b or https://
> > www.kde.org/applications/multimedia/k3b/ or something?
> 
> Sebastian Trüg, the original author of K3b, asked my sourceforge
> identity, and tried to grant me privileges
> https://sourceforge.net/p/k3b/admin/ but still Error 403 - Admin access
> required! the same story to http://k3b.org/
> so maybe we just redirect to https://userbase.kde.org/K3b I can Edit it ;-)

We can do the redirect if we want (i think), the important question is as I 
said, is "is there anything useful on k3b.org" or is it all "too old" and it 
doesn't matter if it gets lots?

Cheers,
  Albert

> 
> > Cheers,
> > 
> >Albert
> >>> 
> >>> Cheers,
> >>> 
> >>> Albert

Re: kde-baseapps split up

2016-11-06 Thread Albert Astals Cid 
El diumenge, 6 de novembre de 2016, a les 23:25:48 CET, David Faure va 
escriure:
> On dimanche 6 novembre 2016 22:47:18 CET Aleix Pol wrote:
> > On Sun, Nov 6, 2016 at 1:36 PM, David Faure  wrote:
> > > On dimanche 6 novembre 2016 12:42:10 CET Albert Astals Cid wrote:
> > >> El dissabte, 5 de novembre de 2016, a les 15:59:39 CET, David Faure va
> > >> 
> > >> escriure:
> > >> > I have split up kde-baseapps into four repos:
> > >> > 
> > >> > kdialog
> > >> > keditbookmarks
> > >> > kfind
> > >> > konqueror
> > >> 
> > >> But the kde-baseapps repo still has those contents too?
> > > 
> > > It's dead.
> > > 
> > >> Should the kde-baseapps repo be released at all?
> > > 
> > > No.
> > > 
> > >> Should we move it to unmaintained?
> > > 
> > > Well, technically all of its contents are still maintained, except for
> > > kdepasswd.
> > > unmaintained is for stuff that can be resurrected/picked-up,
> > > which makes no sense for soon-old
> > > kdialog|keditbookmarks|kfind|konqueror.
> > > 
> > > How was it done for kdepim?
> > 
> > Moving to unmaintained could work, I wouldn't remove it because git
> > history preservation.
> 
> OK, kdepimlibs was moved to unmaintained, with the same reasoning I suppose.
> I'll request that kde-baseapps has the same fate.

Please only after KDE Applications 16.08.3 this week.

Cheers,
  Albert

> 
> I certainly wasn't advocating removal, but you made me realize that moving
> to unmaintained is the only other option.

Re: kde-baseapps split up

2016-11-06 Thread Albert Astals Cid 
El diumenge, 6 de novembre de 2016, a les 13:36:07 CET, David Faure va 
escriure:
> On dimanche 6 novembre 2016 12:42:10 CET Albert Astals Cid wrote:
> > El dissabte, 5 de novembre de 2016, a les 15:59:39 CET, David Faure va
> > 
> > escriure:
> > > I have split up kde-baseapps into four repos:
> > > 
> > > kdialog
> > > keditbookmarks
> > > kfind
> > > konqueror
> > 
> > But the kde-baseapps repo still has those contents too?
> 
> It's dead.
> 
> > Should the kde-baseapps repo be released at all?
> 
> No.
> 
> > Should we move it to unmaintained?
> 
> Well, technically all of its contents are still maintained, except for
> kdepasswd.

What happens with kdepasswd then? We stop releasing it? Where was this 
discussed?

Cheers,
  Albert

kuser - release once more, or drop for 16.12?

2016-11-06 Thread Andreas Sturmlechner 
Hi,

This one has seen the last actual code change in... 2011. No one has bothered 
to even make it independent from kdepimlibs-4, which itself has not been 
released anymore since 4.14.10, more than a year ago. There is no frameworks 
branch. I'd say, for anyone still depending on user/group management by kuser, 
they can always pick it from 16.08. And maybe then that someone decides to 
pick up development once again.

Regards,
Andreas

Re: kde-baseapps split up

2016-11-06 Thread David Faure 
On dimanche 6 novembre 2016 22:47:18 CET Aleix Pol wrote:
> On Sun, Nov 6, 2016 at 1:36 PM, David Faure  wrote:
> > On dimanche 6 novembre 2016 12:42:10 CET Albert Astals Cid wrote:
> >> El dissabte, 5 de novembre de 2016, a les 15:59:39 CET, David Faure va
> >> 
> >> escriure:
> >> > I have split up kde-baseapps into four repos:
> >> > 
> >> > kdialog
> >> > keditbookmarks
> >> > kfind
> >> > konqueror
> >> 
> >> But the kde-baseapps repo still has those contents too?
> > 
> > It's dead.
> > 
> >> Should the kde-baseapps repo be released at all?
> > 
> > No.
> > 
> >> Should we move it to unmaintained?
> > 
> > Well, technically all of its contents are still maintained, except for
> > kdepasswd.
> > unmaintained is for stuff that can be resurrected/picked-up,
> > which makes no sense for soon-old kdialog|keditbookmarks|kfind|konqueror.
> > 
> > How was it done for kdepim?
> 
> Moving to unmaintained could work, I wouldn't remove it because git
> history preservation.

OK, kdepimlibs was moved to unmaintained, with the same reasoning I suppose.
I'll request that kde-baseapps has the same fate.

I certainly wasn't advocating removal, but you made me realize that moving to
unmaintained is the only other option.

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

Re: KDE Frameworks 5.28.0

2016-11-06 Thread David Faure 
On dimanche 6 novembre 2016 23:00:26 CET Aleix Pol wrote:
> It is, on the other hand it's because KConfig cmake scripts were
> parsing wrongly a desktop file. If you want I can take another
> approach that will solve this specific case, but in the end it's an
> error we weren't catching.

That might be, but we can't really release a version of KF5 that breaks 
compilation of the latest plasma release.

As wrong as it was, it "worked" from a plasma point of view.
 
> The Plasma/5.8 branch has been fixed, maybe we can rush another stable
> release of 5.8?

No idea how doable that is. Maybe we can "release" a patch? :-)

> I'm don't think we want to maintain the old behavior for KConfig, TBH.

Not for long, but maybe just until the next plasma release?

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

Re: KDEPIM (16.12) and Gpgme minimum requirement

2016-11-06 Thread Andreas Sturmlechner 
On Thursday, 3 November 2016 at 11:45, Sandro Knauß wrote:
> You may got the notice, that the cpp(gpgme++) and qt (QGpgme) interface, 
> previously build by KDEPIM in the libgpgmepp package, moved down to GpgME 
> directly. That's why KDEPIM depends on very recent GpgME.
> 
> Together with Andre we came to the conclusion, that we want to support:
> 
> GpgME >= 1.7.1

This decision also affects kde-runtime (more specifically, kwalletd-4), which 
is still released as part of KDE Applications even in 16.12. kwalletd (when 
built with gpg support) to this date is depending on the gpgmepp version of 
kdepimlibs-4, which is now conflicting with >=Gpgmepp-1.7.0. But someone has 
been working on a patch to port it to Gpgmepp as well:

https://git.reviewboard.kde.org/r/129339/

I think it would make a lot of sense to get it in for 16.12.

Regards,
Andreas

Re: KDE Frameworks 5.28.0

2016-11-06 Thread Aleix Pol 
On Sun, Nov 6, 2016 at 3:18 PM, šumski  wrote:
> On Saturday 05 of November 2016 19:37:23 David Faure wrote:
>> Dear packagers,
>>
>> KDE Frameworks 5.28.0 has been uploaded to the usual place.
>>
>> New framework:
>> * syntax-highlighting
>>(which ktexteditor now depends upon)
>>
>> Prison was supposed to be released but it's not ready so it's not part of
>> this release at the moment.
>>
>> Public release next Saturday.
>>
>> Thanks for the packaging work!
>
>
> There seems to be a regression in kconfig. Oxygen fails to build against
> 5.28.0:
>
> [   78s] CMake Warning at /usr/lib64/cmake/KF5Config/KF5ConfigMacros.cmake:75
> (message):
> [   78s]   Couldn't read the "File" field in
> [   78s]
> /home/abuild/rpmbuild/BUILD/oxygen-5.8.3/liboxygen/oxygenactiveshadowconfiguration.kcfgc
> [   78s] Call Stack (most recent call first):
> [   78s]   liboxygen/CMakeLists.txt:43 (kconfig_add_kcfg_files)
> [   78s]
> [   78s]
> [   78s] CMake Error at /usr/lib64/cmake/KF5Config/KF5ConfigMacros.cmake:87
> (message):
> [   78s]   oxygenactiveshadowconfiguration.kcfg not found; tried in
> [   78s]   /home/abuild/rpmbuild/BUILD/oxygen-5.8.3/liboxygen and
> [   78s]   /home/abuild/rpmbuild/BUILD/oxygen-5.8.3/build/liboxygen
> [   78s] Call Stack (most recent call first):
> [   78s]   liboxygen/CMakeLists.txt:43 (kconfig_add_kcfg_files)

It is, on the other hand it's because KConfig cmake scripts were
parsing wrongly a desktop file. If you want I can take another
approach that will solve this specific case, but in the end it's an
error we weren't catching.

The Plasma/5.8 branch has been fixed, maybe we can rush another stable
release of 5.8?

I'm don't think we want to maintain the old behavior for KConfig, TBH.

Aleix

Re: kde-baseapps split up

2016-11-06 Thread Aleix Pol 
On Sun, Nov 6, 2016 at 1:36 PM, David Faure  wrote:
> On dimanche 6 novembre 2016 12:42:10 CET Albert Astals Cid wrote:
>> El dissabte, 5 de novembre de 2016, a les 15:59:39 CET, David Faure va
>>
>> escriure:
>> > I have split up kde-baseapps into four repos:
>> >
>> > kdialog
>> > keditbookmarks
>> > kfind
>> > konqueror
>>
>> But the kde-baseapps repo still has those contents too?
>
> It's dead.
>
>> Should the kde-baseapps repo be released at all?
>
> No.
>
>> Should we move it to unmaintained?
>
> Well, technically all of its contents are still maintained, except for
> kdepasswd.
> unmaintained is for stuff that can be resurrected/picked-up,
> which makes no sense for soon-old kdialog|keditbookmarks|kfind|konqueror.
>
> How was it done for kdepim?

Moving to unmaintained could work, I wouldn't remove it because git
history preservation.

Aleix

Re: KDE Frameworks 5.28.0

2016-11-06 Thread šumski 
On Saturday 05 of November 2016 19:37:23 David Faure wrote:
> Dear packagers,
> 
> KDE Frameworks 5.28.0 has been uploaded to the usual place.
> 
> New framework:
> * syntax-highlighting
>(which ktexteditor now depends upon)
> 
> Prison was supposed to be released but it's not ready so it's not part of
> this release at the moment.
> 
> Public release next Saturday.
> 
> Thanks for the packaging work!


There seems to be a regression in kconfig. Oxygen fails to build against 
5.28.0:

[   78s] CMake Warning at /usr/lib64/cmake/KF5Config/KF5ConfigMacros.cmake:75 
(message):
[   78s]   Couldn't read the "File" field in
[   78s]   
/home/abuild/rpmbuild/BUILD/oxygen-5.8.3/liboxygen/oxygenactiveshadowconfiguration.kcfgc
[   78s] Call Stack (most recent call first):
[   78s]   liboxygen/CMakeLists.txt:43 (kconfig_add_kcfg_files)
[   78s] 
[   78s] 
[   78s] CMake Error at /usr/lib64/cmake/KF5Config/KF5ConfigMacros.cmake:87 
(message):
[   78s]   oxygenactiveshadowconfiguration.kcfg not found; tried in
[   78s]   /home/abuild/rpmbuild/BUILD/oxygen-5.8.3/liboxygen and
[   78s]   /home/abuild/rpmbuild/BUILD/oxygen-5.8.3/build/liboxygen
[   78s] Call Stack (most recent call first):
[   78s]   liboxygen/CMakeLists.txt:43 (kconfig_add_kcfg_files)

Re: kde-baseapps split up

2016-11-06 Thread David Faure 
On dimanche 6 novembre 2016 12:42:10 CET Albert Astals Cid wrote:
> El dissabte, 5 de novembre de 2016, a les 15:59:39 CET, David Faure va
> 
> escriure:
> > I have split up kde-baseapps into four repos:
> > 
> > kdialog
> > keditbookmarks
> > kfind
> > konqueror
> 
> But the kde-baseapps repo still has those contents too?

It's dead.

> Should the kde-baseapps repo be released at all? 

No.

> Should we move it to unmaintained?

Well, technically all of its contents are still maintained, except for 
kdepasswd.
unmaintained is for stuff that can be resurrected/picked-up,
which makes no sense for soon-old kdialog|keditbookmarks|kfind|konqueror.

How was it done for kdepim?

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

Re: kde-baseapps split up

2016-11-06 Thread Albert Astals Cid 
El dissabte, 5 de novembre de 2016, a les 15:59:39 CET, David Faure va 
escriure:
> I have split up kde-baseapps into four repos:
> 
> kdialog
> keditbookmarks
> kfind
> konqueror

But the kde-baseapps repo still has those contents too?

Should the kde-baseapps repo be released at all? Should we move it to 
unmaintained?

> 
> Albert, can you include them in the next applications release?
> (I suppose you'll create the Applications/16.12 branch in all repos in one
> go?)

Yes, the branches will be created in the near future in all repos at the same 
time.

Cheers,
  Albert

> 
> 
> The status of these new repos is:
> 
> Done:
> - history cleaned up and pushed
> - file layout reorganized, it all builds (for me at least)
> - added to kde-build-metadata/logical-module-structure
> - added to kdesrc-build files
> 
> Planned:
> - Burkhard Lück will take care of the translations
> - I have asked the sysadmins for CI jobs
> 
> Anything I forgot?

Re: KDE Frameworks 5.28.0

2016-11-06 Thread David Faure 
On samedi 5 novembre 2016 21:14:07 CET David Faure wrote:
> On samedi 5 novembre 2016 19:37:23 CET David Faure wrote:
> > New framework:
> > * syntax-highlighting
> > 
> >(which ktexteditor now depends upon)
> 
> Hold on, it will be renamed ksyntax-highlighting tomorrow, for better
> namespacing.

The above was quite incorrect. 
* the tarball name didn't change, only the contents
* ktexteditor doesn't yet use syntax-highlighting

Anyway it's ready now:

syntax-highlighting v5.28.0-rc2
5eea9c2285bcfe1ed8c62c6c1a0900a1edac6bcf
be3d4f730e8bfde843de393eeb6bd4842a052f0c438455de325b3d3269a3c13d  
sources/syntax-highlighting-5.28.0.tar.xz

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5