Re: Sysadmin Load Reduction: Subversion Infrastructure

[Luigi Toscano]

Ben Cooksley ha scritto:
> Hi all,
> 
> When KDE committed to performing a migration to Git back in 2010, one
> of the things that was agreed at the time was that translators could
> remain on Subversion to avoid disrupting their workflows.
> 
> This however has led to a certain amount of additional infrastructure
> which Sysadmin needs to continue to maintain.
> 
> In recognition of the fact that with few exceptions, everything has
> now migrated from Subversion aside from Translations, i'd like to
> reduce the level of infrastructure supporting our Subversion
> repository to the bare minimum necessary.
> 
> This would include the shutdown of WebSVN in particular, which when
> coupled with the shutdown of our two CGit instances would also allow
> for us to eliminate an entire virtual machine from our systems.

As websvn has proven to be useful, would it help the sysadmin (pending
agreement with aacid and the other people with root access on rosetta) to move
websvn to rosetta and under localization team's responsibility?

Ciao
-- 
Luigi

D24957: Add new baloo icons

[Alexander Stippich]

astippich updated this revision to Diff 69501.
astippich added a comment.


  - tweak icon and shadows

REPOSITORY
  R266 Breeze Icons

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D24957?vs=68777=69501

BRANCH
  newBalooIcon

REVISION DETAIL
  https://phabricator.kde.org/D24957

AFFECTED FILES
  icons-dark/apps/48/baloo.svg
  icons-dark/preferences/32/preferences-desktop-baloo.svg
  icons/apps/48/baloo.svg
  icons/preferences/32/preferences-desktop-baloo.svg

To: astippich, #vdg, ngraham, bruns
Cc: trickyricky26, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, 
bruns

Re: Sysadmin Load Reduction: Code Related Services

[Luigi Toscano]

Ben Cooksley ha scritto:
> Hi all,
> 
> In the category of code related services, Sysadmin currently supports
> a wide-ranging number of services (which makes sense given the nature
> of the community). Some of these however may no longer be in use or
> will be duplicative of other services following the transition to
> Gitlab.
> 
> In the category of duplicative, we have our two CGit instances at
> cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these were
> justifiable as there was no other way of browsing scratch/clone
> repositories over the web.
> 
> With the migration to Gitlab however all repositories will become
> browsable through it, meaning it no longer makes sense to offer two
> browsers that provide the exact same information (with Gitlab having
> greater capabilities). I'd therefore like to shut both of these down
> once Code Hosting has transitioned to Gitlab.

Luckily we tried to use commits.kde.org as generic redirect. Will the generic
redirect commits.kde.org be updated to point to the proper repository? It may
be complicated if the new structure contains the namespaces for each
repository, but we need to keep it working.

> 
> In the category of no longer in use, we have the compatibility
> generator for the kde_projects.xml file. This was introduced when we
> shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> keeping services that needed to discover a list of KDE Projects
> functional.
> 
> As we've since migrated to using YAML files within the
> sysadmin/repo-metadata repository for both the CI System and
> kdesrc-build (and with LXR using kdesrc-build to do it's code
> checkouts) there shouldn't to my knowledge be anything still relying
> on this (aside from perhaps scripty).>
> I'd therefore like to shut this generator down as well, along with the
> compaibility redirector running at projects.kde.org (given that it has
> been some time since we were using that site, and many projects have
> moved around in the virtual structure since then, making the redirects
> it is able to offer useless)

Two points:
- scripty still uses the XML file and we may need some time to migrate.
- we may have a few links around which still points to projects.kde.org (for
example, the "Consistency" goal listed a few of them), so we may need to go
through all of them before doing that.
Do we have measures that shows how much projects.kde.org is hit by services
which are not scripty?

-- 
Luigi

Re: General Infrastructure Maintainability: API and EBN

[Elvis Angelaccio]

On 09/11/19 01:33, Ben Cooksley wrote:
> Hi all,

Hi Ben

> 
> Over the past number of years one of the tasks the Sysadmin team has
> worked on has been improving the overall maintainability of our
> systems, with a significant number of specialised cronjobs, exceptions
> and hidden linkages being eliminated.
> 
> That is with one great exception: api.kde.org and ebn.kde.org.
> 
> Both of these are suffering from an extreme amount of digital bitrot
> and special casing and in general are now in a condition where I
> cannot say for certain whether it would be possible to replicate the
> setup on a new system without us experiencing some degree of breakage
> (some of which we may not discover until weeks/months afterwards).
> 
> In addition, the current setup relies on an old-fashioned overnight
> reprocessing of all repositories, which is inefficient and resource
> expensive. A more modern approach would have the various projects api
> documentation generated on a delayed cycle from relevant branches as
> part of something like a CI job (but not part of the actual CI
> workflow itself).
> 
> For this one, i'm not certain on the best path forward at this stage,
> however the current state of affairs cannot continue. We have tried
> over the past few years to find people to work on a replacement for
> the tooling involved, but alas we've yet to have success here.
> 
> Thoughts anyone?

I'd say api.kde.org is too important to let it go. The EBN is less
important but still useful, I still see people pushing EBN-based fixes
once in a while.

Have we ever tried to use a GSoC project to modernize either of them? If
not, would it make sense to try next year?

> 
> Regards,
> Ben

Cheers,
Elvis

Re: Quick Charts in KDE Review

[David Edmundson]

> If one restricts oneself to use only libraries part of KDE Frameworks, but not
> from the "Extragear" domain, one should reconsider it, this does not make much
> sense as long one also uses non-KDE-party libraries (which also do not follow
> KF rules).

Plasma effectively has such a rule.

Treating this as a more meta discussion about libs, sure, with KDE
rules in extragear you can change ABI/API but the consequences still
mean in reality you can't.
Release an incompatible lib, things explode until recompiled.

If we use a lib in plasma and in an application and then change the
lib API we always have a window where either applications latest
release or plasma latest release won't compile against the released
lib. Even if you bump the .so version the headers aren't
co-installable. Being in this situation where we break ourselves means
every packager would murder you on sight.

Due to this release problem Plasma has previously made any use of
extragear (or unstable 3rd party) #ifdef'd and always not in core
functionality.

>But I recommend to do as others and not bind to
current first ABI for some time to come

Note this is all somewhat moot for this specific case. There is only a
QML import. It can change ABI all it wants. Changing API is also
doable as long as QML import bumps and the old version still works.

D24980: Port ssl_cert_errors meta data from KSslError to QSslError

[Ahmad Samir]

ahmadsamir added inline comments.

INLINE COMMENTS

> vkrause wrote in jobuidelegate.cpp:365
> sslMetaData is a QMap, ie. value() has no QLatin1String 
> overload, calling it with a QLatin1String will work but convert to a QString 
> at runtime (involving a memory allocation), using QStringLiteral avoids that.

Right, value() is what matters here, thanks for explaining.

> vkrause wrote in ksslinfodialog.cpp:263
> In theory, yes. However, changing this here and now would trigger quite some 
> ripple effect through the code, which currently is using QList everywhere, so 
> I'd suggest to do that as a separate change (if at all), to not hide 
> security-relevant changes under lots of QList -> QVector porting noise. The 
> other thing to consider the consistency in this code if we change just a 
> single use from QList to QVector, especially if that's not a 
> performance-sensitive path and Qt6 is supposed to change all this anyway 
> (QList's implementation going away).

OK, thanks for explaining.

(But I think there still should be a "// static" comment for that method).

REPOSITORY
  R241 KIO

BRANCH
  next

REVISION DETAIL
  https://phabricator.kde.org/D24980

To: vkrause, nicolasfella
Cc: ahmadsamir, nicolasfella, kde-frameworks-devel, LeGast00n, GB_2, michaelh, 
ngraham, bruns

Re: Quick Charts in KDE Review

[Friedrich W. H. Kossebau]

Am Donnerstag, 7. November 2019, 16:21:40 CET schrieb Nate Graham:
> On 11/7/19 7:34 AM, Friedrich W. H. Kossebau wrote:
> > Am Montag, 21. Oktober 2019, 15:22:23 CET schrieb Arjen Hiemstra:
> >> Quick Charts is a QML module that implements a set of high-performance,
> >> GPU accelerated
> >> charts. Currently the main user of it is a new KSysGuard UI I have been
> >> working on, but
> >> once it is part of Frameworks I also hope to convert several bits of
> >> Plasma to using it.
> > 
> > If there is only one user currently, might it perhaps be a better idea to
> > do some independent releases for a while to get more feedback on the API,
> > before settling to the API freeze by being part of KDE Frameworks? It
> > will be at least a year until KF6 is there to properly fix up any
> > potential API inconveniences which users might find.
> > I would at least recommend to first get some API shaping by real-world
> > exposure.
> 
> Seems like a chicken-egg problem: more exposure would be provided by
> getting it through the review process, no? I can see us porting the
> graphs in KInfoCenter to use this, for example. But since that's
> shipping code, we might not want to do that until it's formally a framework.

If one restricts oneself to use only libraries part of KDE Frameworks, but not 
from the "Extragear" domain, one should reconsider it, this does not make much 
sense as long one also uses non-KDE-party libraries (which also do not follow 
KF rules).

Review process is about passing something from playground into the set of no-
longer-playground repos. Which for libs can be KDE Frameworks domain, but also 
the "Extragear" domain. Both are equally post-review.
And "Extragear" gives the flexibility to do another product version with 
different ABI, once there has been more feedback from more users.
An approach e.g. taken by KUserFeedback. But also compare the concept of Qt 
labs modules.
Having an API mainly done for one user only right now runs a good chance to 
miss the API needs of other potential candidates. Everyone needs a different 
20 % of the API concepts, they say when throwing with numbers ;)

Np chicken-egg problem here. Release-often-and-early should be simply applied 
to KChickCharts as well. But I recommend to do as others and not bind to 
current first ABI for some time to come, like begin of KF6, instead plan for 
some optional ABI-breaking releases in the near future. So be under the rules 
of Extragear, not yet Frameworks.
But people learn best from own mistakes, so feel free to ignore some old 
person's comment-from-experience. ;)
If the API proves to be not perfect and one knows how it would be better, ~12 
months (to KF6) can be very long :P

Cheers
Friedrich

New Framework Review: KDAV

[Volker Krause]

Hi,

during Akademy there was a request to promote KDAV from KDE PIM to Frameworks 
for use by Plasma Mobile. KDAV is a framework that implements the CalDav/
CardDav/GroupDav protocol on top of KIO's WebDav support. It would be 
classified as a functional tier 3 framework.

So far we have fixed a number of obvious ABI-compatibility issues, removed 
QtXml[Patterns] usage from the public interface and relicensed GPL parts 
(apart from a bit of test code) to LGPL. The next step would be a more 
thorough review to identify changes necessary before becoming a Framework.

To avoid the last minute invasive changes we ended up doing for KCalendarCore, 
I'd propose the following timeline:

- identify and implement all necessary changes to the API and ABI until the 
20.04 Application release (that includes the still necessary move to the KF5 
library namespace).
- release KDAV with 20.04 with the final API/ABI that the first KF5 release 
will provide as well
- become part of the KF5 release in May or June 2020, release as a drop-in 
replacement of the last application release

In general this is following the same transition process that has been used 
for Syndication, KHolidays, KContacts and KCalendarCore as that should cause 
minimal disruptions for distributors, but if there's better ideas on how to 
handle this, now is a good time to bring this up :)

Feedback?

Thanks,
Volker

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

D24046: Allow triggering sort from QML

[Jonah Brüchert]

jbbgameich added a comment.


  Can we get one of the two ways accepted so we can progress on the phonebook 
merge request?

REPOSITORY
  R307 KPeople

REVISION DETAIL
  https://phabricator.kde.org/D24046

To: nicolasfella, apol
Cc: jbbgameich, broulik, kde-frameworks-devel, LeGast00n, GB_2, michaelh, 
ngraham, bruns

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Ben Cooksley]

On Sun, Nov 10, 2019 at 12:20 AM Luigi Toscano  wrote:
>
> Ben Cooksley ha scritto:
> > Hi all,
> >
> > When KDE committed to performing a migration to Git back in 2010, one
> > of the things that was agreed at the time was that translators could
> > remain on Subversion to avoid disrupting their workflows.
> >
> > This however has led to a certain amount of additional infrastructure
> > which Sysadmin needs to continue to maintain.
> >
> > In recognition of the fact that with few exceptions, everything has
> > now migrated from Subversion aside from Translations, i'd like to
> > reduce the level of infrastructure supporting our Subversion
> > repository to the bare minimum necessary.
> >
> > This would include the shutdown of WebSVN in particular, which when
> > coupled with the shutdown of our two CGit instances would also allow
> > for us to eliminate an entire virtual machine from our systems.
>
> As websvn has proven to be useful, would it help the sysadmin (pending
> agreement with aacid and the other people with root access on rosetta) to move
> websvn to rosetta and under localization team's responsibility?

Unfortunately Rosetta does not have the necessary free disk space, as
the Subversion repository is approximately 80GB these days in size,
and operating WebSVN requires a full copy of the Subversion repository
locally in order to operate.

>
> Ciao
> --
> Luigi

Cheers,
Ben

Re: Looking for Subtitle Composer sponsor

[Nate Graham]

One thing I forgot before we set up the git repo: you will need a 
developer account. Please apply for one at 
https://community.kde.org/Infrastructure/Get_a_Developer_Account


Nate


On 11/7/19 12:58 PM, Nate Graham wrote:

On 11/7/19 12:55 PM, Mladen Milinkovic wrote:

Hello Nate,

On 11/7/19 3:31 PM, Nate Graham wrote:

I would be happy to be your sponsor!

Thank you!

Per https://community.kde.org/Incubator#Candidate, we need you to 
provide the following information:


- A list of the people regularly committing to the project
That would be only me I believe. Right now I'm the only one with write 
permissions to repository.
There are occasional pull requests, but nothing regular. Most pull 
requests are translations which since recently are

pulled from crowdin.com.
This should be the list of contributors since Nov 2011: 
https://github.com/maxrd2/SubtitleComposer/graphs/contributors


- A plan to be in compliance with the KDE manifesto 
(https://manifesto.kde.org/index.html). In particular, you'll need
to be okay moving your source code repo and other infrastructure away 
from GitHub and into KDE's GitLab instance at

https://invent.kde.org.
Have already created account on 
https://invent.kde.org/users/milinkovic. Should I create a personal 
repository there for

the project?


Sysadmin will get one set up for you.

Sysadmin, can we have a repo to host 
https://github.com/maxrd2/SubtitleComposer on KDE's infrastructure?


Nate

Re: Quick Charts in KDE Review

[Friedrich W. H. Kossebau]

Am Samstag, 9. November 2019, 14:16:08 CET schrieb David Edmundson:
> > If one restricts oneself to use only libraries part of KDE Frameworks, but
> > not from the "Extragear" domain, one should reconsider it, this does not
> > make much sense as long one also uses non-KDE-party libraries (which also
> > do not follow KF rules).
> 
> Plasma effectively has such a rule.
> 
> Treating this as a more meta discussion about libs, sure, with KDE
> rules in extragear you can change ABI/API but the consequences still
> mean in reality you can't.
> Release an incompatible lib, things explode until recompiled.

I am confused this is assuming one releases an incompatible library not using 
respective versioning schemes and not allowing parallel install?
But people do that properly, no?
 
> If we use a lib in plasma and in an application and then change the
> lib API we always have a window where either applications latest
> release or plasma latest release won't compile against the released
> lib. Even if you bump the .so version

Why the "even"? One should. That's what the purpose of the so version is.

> the headers aren't
> co-installable.

Some projects do proper version namespaces also for include path on changed 
ABI. If projects do not, they should start to do IMHO.
Even without, normally developers only work against one version of the 
library, so just having one variant of headers installed works good enough.

> Due to this release problem Plasma has previously made any use of
> extragear (or unstable 3rd party) #ifdef'd and always not in core
> functionality.

Given Plasma requires recent versions of KF on .0 releases, the same can be 
done also for newer versions of non-KF libraries, where one then switches to 
the new API series. No need for #ifdef.

> >But I recommend to do as others and not bind to
> 
> current first ABI for some time to come
> 
> Note this is all somewhat moot for this specific case. There is only a
> QML import. It can change ABI all it wants. Changing API is also
> doable as long as QML import bumps and the old version still works.

That is no different to normal compiled library symbols, no?
One also cannot break "ABI" (not sure what the respective name would be in 
dynamic languages), i.e. change names of symbols or their types at QML layer.

Think QQC 1 and QQC 2.

Of course this comes at cost. But personally I am willing to pay that price 
over having to stick with API which proved to be not good enough and thus 
makes my own code worse.
Thus my 2 cent recommendation to stay flexible for now :) But everyone has 
different priorities, just wanted to make you consider this.

Cheers
Friedrich

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Albert Astals Cid]

El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va 
escriure:
> On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev  
> wrote:
> >
> > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > This would include the shutdown of WebSVN in particular, which when
> > > coupled with the shutdown of our two CGit instances would also allow
> > > for us to eliminate an entire virtual machine from our systems.
> >
> > Will there be any web interface for SVN after shutdown of WebSVN?
> >
> > Can we assume https://phabricator.kde.org/source/svn/ remains
> > available during the next 10 years?
> >
> 
> Phabricator's browser will be retired as part of the shutdown of
> Phabricator, which will take place once Gitlab has assumed
> responsibility for code hosting and review, and the tasks have been
> migrated from Phabricator.
> 
> Should WebSVN be shutdown as well, then there would be no web
> interface to our SVN repository.

That's not acceptable.

Cheers,
  Albert

> 
> >
> > I'm not sure what use case Luigi has in mind, but among Russian l10n
> > team we often use WebSVN to refer to specific SVN revisions, for
> > example: https://websvn.kde.org/?view=revision=1555342
> >
> > --
> > Alexander Potashev
> 
> Regards,
> Ben
> 

Re: Sysadmin Load Reduction: Code Related Services

[Albert Astals Cid]

El dissabte, 9 de novembre de 2019, a les 18:47:57 CET, Ben Cooksley va 
escriure:
> On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano  
> wrote:
> >
> > Ben Cooksley ha scritto:
> > > Hi all,
> > >
> > > In the category of code related services, Sysadmin currently supports
> > > a wide-ranging number of services (which makes sense given the nature
> > > of the community). Some of these however may no longer be in use or
> > > will be duplicative of other services following the transition to
> > > Gitlab.
> > >
> > > In the category of duplicative, we have our two CGit instances at
> > > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these were
> > > justifiable as there was no other way of browsing scratch/clone
> > > repositories over the web.
> > >
> > > With the migration to Gitlab however all repositories will become
> > > browsable through it, meaning it no longer makes sense to offer two
> > > browsers that provide the exact same information (with Gitlab having
> > > greater capabilities). I'd therefore like to shut both of these down
> > > once Code Hosting has transitioned to Gitlab.
> >
> > Luckily we tried to use commits.kde.org as generic redirect. Will the 
> > generic
> > redirect commits.kde.org be updated to point to the proper repository? It 
> > may
> > be complicated if the new structure contains the namespaces for each
> > repository, but we need to keep it working.
> 
> The commits.kde.org redirector is intended to provide permanent links,
> so yes it will be updated to redirect people to Gitlab instead once
> the switch to Gitlab is completed.
> 
> >
> > >
> > > In the category of no longer in use, we have the compatibility
> > > generator for the kde_projects.xml file. This was introduced when we
> > > shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> > > keeping services that needed to discover a list of KDE Projects
> > > functional.
> > >
> > > As we've since migrated to using YAML files within the
> > > sysadmin/repo-metadata repository for both the CI System and
> > > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > > checkouts) there shouldn't to my knowledge be anything still relying
> > > on this (aside from perhaps scripty).>
> > > I'd therefore like to shut this generator down as well, along with the
> > > compaibility redirector running at projects.kde.org (given that it has
> > > been some time since we were using that site, and many projects have
> > > moved around in the virtual structure since then, making the redirects
> > > it is able to offer useless)
> >
> > Two points:
> > - scripty still uses the XML file and we may need some time to migrate.
> 
> I feared this may have been the case. What sort of timeline are we
> looking at in terms of switching scripty over?

Over to what?

Cheers,
  Albert

Re: New Framework Review: KDAV

[Volker Krause]

On Saturday, 9 November 2019 18:45:17 CET Christoph Feck wrote:
> Hi Volker,
> 
> On 11/09/19 12:33, Volker Krause wrote:
> > during Akademy there was a request to promote KDAV from KDE PIM to
> > Frameworks for use by Plasma Mobile. KDAV is a framework that implements
> > the CalDav/ CardDav/GroupDav protocol on top of KIO's WebDav support. It
> > would be classified as a functional tier 3 framework.
> 
> Could you clarify if the review is about
> https://api.kde.org/kdepim/kdav/html/index.html or
> https://api.kde.org/kdepim/kdav2/html/index.html ?

good point, sorry about forgetting to add the corresponding links :)

Code: https://phabricator.kde.org/source/kdav/
API docs: https://api.kde.org/kdepim/kdav/html/index.html

Regards,
Volker

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

Re: General Infrastructure Maintainability: API and EBN

[Michael Reeves]

Some of what ebn is doing in terms of linting c/c++ code would be better
moved to clazy/clang-tidy plugins. The current scan for functions such open
false positives for strings and comments. This is just open example of the
limits imposed by not having a compilers eye view of the code. I personally
don't care for having an extra place to check for errors. Clazy can run
automatically on each build so warnings show up in your ide not just on
some website.

On Sat, Nov 9, 2019, 10:28 AM Elvis Angelaccio 
wrote:

>
>
> On 09/11/19 01:33, Ben Cooksley wrote:
> > Hi all,
>
> Hi Ben
>
> >
> > Over the past number of years one of the tasks the Sysadmin team has
> > worked on has been improving the overall maintainability of our
> > systems, with a significant number of specialised cronjobs, exceptions
> > and hidden linkages being eliminated.
> >
> > That is with one great exception: api.kde.org and ebn.kde.org.
> >
> > Both of these are suffering from an extreme amount of digital bitrot
> > and special casing and in general are now in a condition where I
> > cannot say for certain whether it would be possible to replicate the
> > setup on a new system without us experiencing some degree of breakage
> > (some of which we may not discover until weeks/months afterwards).
> >
> > In addition, the current setup relies on an old-fashioned overnight
> > reprocessing of all repositories, which is inefficient and resource
> > expensive. A more modern approach would have the various projects api
> > documentation generated on a delayed cycle from relevant branches as
> > part of something like a CI job (but not part of the actual CI
> > workflow itself).
> >
> > For this one, i'm not certain on the best path forward at this stage,
> > however the current state of affairs cannot continue. We have tried
> > over the past few years to find people to work on a replacement for
> > the tooling involved, but alas we've yet to have success here.
> >
> > Thoughts anyone?
>
> I'd say api.kde.org is too important to let it go. The EBN is less
> important but still useful, I still see people pushing EBN-based fixes
> once in a while.
>
> Have we ever tried to use a GSoC project to modernize either of them? If
> not, would it make sense to try next year?
>
> >
> > Regards,
> > Ben
>
> Cheers,
> Elvis
>
>

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Ben Cooksley]

On Sun, Nov 10, 2019 at 9:32 AM Albert Vaca Cintora
 wrote:
>
> On Sat, Nov 9, 2019 at 6:53 PM Ben Cooksley  wrote:
> >
> > Unfortunately Rosetta does not have the necessary free disk space, as
> > the Subversion repository is approximately 80GB these days in size,
> > and operating WebSVN requires a full copy of the Subversion repository
> > locally in order to operate.
>
> Is this also the case if you run WebSVN next to the SVN server itself
> (ie: on the same machine)? If a single repo copy can be shared by
> WebSVN and the actual SVN server, that would reduce the storage needs.

Running WebSVN on the same machine is not safe for us to do, because
certain requests cause WebSVN to generate a substantial amount of
system load, and have caused out of memory events on systems running
it in the past.

This poses an unacceptable risk to the canonical copy of our
repositories, as well as to Gitlab (which will be hosted on the same
machine as the master Subversion repository)

>
> Albert

Regards,
Ben

Re: Sysadmin Load Reduction: Code Related Services

[Ben Cooksley]

On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano  wrote:
>
> Ben Cooksley ha scritto:
> > Hi all,
> >
> > In the category of code related services, Sysadmin currently supports
> > a wide-ranging number of services (which makes sense given the nature
> > of the community). Some of these however may no longer be in use or
> > will be duplicative of other services following the transition to
> > Gitlab.
> >
> > In the category of duplicative, we have our two CGit instances at
> > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these were
> > justifiable as there was no other way of browsing scratch/clone
> > repositories over the web.
> >
> > With the migration to Gitlab however all repositories will become
> > browsable through it, meaning it no longer makes sense to offer two
> > browsers that provide the exact same information (with Gitlab having
> > greater capabilities). I'd therefore like to shut both of these down
> > once Code Hosting has transitioned to Gitlab.
>
> Luckily we tried to use commits.kde.org as generic redirect. Will the generic
> redirect commits.kde.org be updated to point to the proper repository? It may
> be complicated if the new structure contains the namespaces for each
> repository, but we need to keep it working.

The commits.kde.org redirector is intended to provide permanent links,
so yes it will be updated to redirect people to Gitlab instead once
the switch to Gitlab is completed.

>
> >
> > In the category of no longer in use, we have the compatibility
> > generator for the kde_projects.xml file. This was introduced when we
> > shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> > keeping services that needed to discover a list of KDE Projects
> > functional.
> >
> > As we've since migrated to using YAML files within the
> > sysadmin/repo-metadata repository for both the CI System and
> > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > checkouts) there shouldn't to my knowledge be anything still relying
> > on this (aside from perhaps scripty).>
> > I'd therefore like to shut this generator down as well, along with the
> > compaibility redirector running at projects.kde.org (given that it has
> > been some time since we were using that site, and many projects have
> > moved around in the virtual structure since then, making the redirects
> > it is able to offer useless)
>
> Two points:
> - scripty still uses the XML file and we may need some time to migrate.

I feared this may have been the case. What sort of timeline are we
looking at in terms of switching scripty over?

> - we may have a few links around which still points to projects.kde.org (for
> example, the "Consistency" goal listed a few of them), so we may need to go
> through all of them before doing that.
> Do we have measures that shows how much projects.kde.org is hit by services
> which are not scripty?

I've reviewed the logs for the past 24 hours and it would appear the
majority of the legitimate hits now are for the RSS/ATOM feeds that
Chiliproject used to offer and which have no corresponding replacement
(amazingly, these are still configured in people's feed readers).

After excluding bots and spiders, and people running automated tools
against old URL sets, very little in the way of hits remained.
The remainder are a very small proportion of hits from places such as
the Archlinux wiki, which we can likely request to be updated
(referencing Bluedevil in particular it would seem).

>
> --
> Luigi

Cheers,
Ben

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Luigi Toscano]

Ben Cooksley ha scritto:
> On Sun, Nov 10, 2019 at 12:20 AM Luigi Toscano  
> wrote:
>>
>> Ben Cooksley ha scritto:
>>> Hi all,
>>>
>>> When KDE committed to performing a migration to Git back in 2010, one
>>> of the things that was agreed at the time was that translators could
>>> remain on Subversion to avoid disrupting their workflows.
>>>
>>> This however has led to a certain amount of additional infrastructure
>>> which Sysadmin needs to continue to maintain.
>>>
>>> In recognition of the fact that with few exceptions, everything has
>>> now migrated from Subversion aside from Translations, i'd like to
>>> reduce the level of infrastructure supporting our Subversion
>>> repository to the bare minimum necessary.
>>>
>>> This would include the shutdown of WebSVN in particular, which when
>>> coupled with the shutdown of our two CGit instances would also allow
>>> for us to eliminate an entire virtual machine from our systems.
>>
>> As websvn has proven to be useful, would it help the sysadmin (pending
>> agreement with aacid and the other people with root access on rosetta) to 
>> move
>> websvn to rosetta and under localization team's responsibility?
> 
> Unfortunately Rosetta does not have the necessary free disk space, as
> the Subversion repository is approximately 80GB these days in size,
> and operating WebSVN requires a full copy of the Subversion repository
> locally in order to operate.

Can we extend rosetta's disk then, or add an external volume?

In case it's not clear, I'd like to do everything possible to have websvn
still up.

-- 
Luigi

D25215: Fix a couple of broken links, update links to https://kde.org/applications/

[Albert Astals Cid]

aacid added subscribers: jriddell, aacid.
aacid added a comment.


  If the old links don't work this is a problem and should be fixed in the web 
we can't break URLs just because
  
  Paging @jriddell

REPOSITORY
  R304 KNewStuff

REVISION DETAIL
  https://phabricator.kde.org/D25215

To: meven, leinir, ngraham
Cc: aacid, jriddell, ngraham, kde-frameworks-devel, LeGast00n, GB_2, michaelh, 
bruns

D24980: Port ssl_cert_errors meta data from KSslError to QSslError

[Volker Krause]

vkrause added inline comments.

INLINE COMMENTS

> ahmadsamir wrote in jobuidelegate.cpp:365
> Nitpick, wouldn't QLatin1String be better here?
> 
> c.f. Marc Mutz's talk about QStringLiteral and QLatin1String: 
> https://youtu.be/Ov7s0GgBbOQ?t=2806

sslMetaData is a QMap, ie. value() has no QLatin1String overload, 
calling it with a QLatin1String will work but convert to a QString at runtime 
(involving a memory allocation), using QStringLiteral avoids that.

> ahmadsamir wrote in ksslinfodialog.cpp:263
> Nitpick, shouldn't there be a "// static" comment like the other method?
> 
> Wouldn't a QVector be better here (QVector>)? that 
> is IIUC what the QList docs and [1] are saying.
> 
> [1]https://marcmutz.wordpress.com/effective-qt/containers/

In theory, yes. However, changing this here and now would trigger quite some 
ripple effect through the code, which currently is using QList everywhere, so 
I'd suggest to do that as a separate change (if at all), to not hide 
security-relevant changes under lots of QList -> QVector porting noise. The 
other thing to consider the consistency in this code if we change just a single 
use from QList to QVector, especially if that's not a performance-sensitive 
path and Qt6 is supposed to change all this anyway (QList's implementation 
going away).

REPOSITORY
  R241 KIO

BRANCH
  next

REVISION DETAIL
  https://phabricator.kde.org/D24980

To: vkrause, nicolasfella
Cc: ahmadsamir, nicolasfella, kde-frameworks-devel, LeGast00n, GB_2, michaelh, 
ngraham, bruns

D25117: file ioslave: stop copying as soon as the ioslave is killed

[Méven Car]

meven added a reviewer: apol.

REPOSITORY
  R241 KIO

REVISION DETAIL
  https://phabricator.kde.org/D25117

To: meven, #frameworks, dfaure, ngraham, apol
Cc: apol, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns

Re: New Framework Review: KDAV

[Christoph Feck]

Hi Volker,

On 11/09/19 12:33, Volker Krause wrote:

during Akademy there was a request to promote KDAV from KDE PIM to Frameworks
for use by Plasma Mobile. KDAV is a framework that implements the CalDav/
CardDav/GroupDav protocol on top of KIO's WebDav support. It would be
classified as a functional tier 3 framework.


Could you clarify if the review is about 
https://api.kde.org/kdepim/kdav/html/index.html or 
https://api.kde.org/kdepim/kdav2/html/index.html ?


Christoph Feck

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Ben Cooksley]

On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid  wrote:
>
> El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va 
> escriure:
> > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev  
> > wrote:
> > >
> > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > > This would include the shutdown of WebSVN in particular, which when
> > > > coupled with the shutdown of our two CGit instances would also allow
> > > > for us to eliminate an entire virtual machine from our systems.
> > >
> > > Will there be any web interface for SVN after shutdown of WebSVN?
> > >
> > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > available during the next 10 years?
> > >
> >
> > Phabricator's browser will be retired as part of the shutdown of
> > Phabricator, which will take place once Gitlab has assumed
> > responsibility for code hosting and review, and the tasks have been
> > migrated from Phabricator.
> >
> > Should WebSVN be shutdown as well, then there would be no web
> > interface to our SVN repository.
>
> That's not acceptable.

Mind explaining why?

Bear in mind that there is a cost both in terms of infrastructure, and
people time to maintain a service such as WebSVN.
This includes having to maintain a mirror of the repository on the
machine that runs WebSVN, along with the associated infrastructure for
allowing that mirroring to happen on the master server.

>
> Cheers,
>   Albert

Regards,
Ben

>
> >
> > >
> > > I'm not sure what use case Luigi has in mind, but among Russian l10n
> > > team we often use WebSVN to refer to specific SVN revisions, for
> > > example: https://websvn.kde.org/?view=revision=1555342
> > >
> > > --
> > > Alexander Potashev
> >
> > Regards,
> > Ben
> >
>
>
>
>

Re: Sysadmin Load Reduction: Code Related Services

[Ben Cooksley]

On Sun, Nov 10, 2019 at 8:43 AM Albert Astals Cid  wrote:
>
> El dissabte, 9 de novembre de 2019, a les 18:47:57 CET, Ben Cooksley va 
> escriure:
> > On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano  
> > wrote:
> > >
> > > Ben Cooksley ha scritto:
> > > > Hi all,
> > > >
> > > > In the category of code related services, Sysadmin currently supports
> > > > a wide-ranging number of services (which makes sense given the nature
> > > > of the community). Some of these however may no longer be in use or
> > > > will be duplicative of other services following the transition to
> > > > Gitlab.
> > > >
> > > > In the category of duplicative, we have our two CGit instances at
> > > > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these were
> > > > justifiable as there was no other way of browsing scratch/clone
> > > > repositories over the web.
> > > >
> > > > With the migration to Gitlab however all repositories will become
> > > > browsable through it, meaning it no longer makes sense to offer two
> > > > browsers that provide the exact same information (with Gitlab having
> > > > greater capabilities). I'd therefore like to shut both of these down
> > > > once Code Hosting has transitioned to Gitlab.
> > >
> > > Luckily we tried to use commits.kde.org as generic redirect. Will the 
> > > generic
> > > redirect commits.kde.org be updated to point to the proper repository? It 
> > > may
> > > be complicated if the new structure contains the namespaces for each
> > > repository, but we need to keep it working.
> >
> > The commits.kde.org redirector is intended to provide permanent links,
> > so yes it will be updated to redirect people to Gitlab instead once
> > the switch to Gitlab is completed.
> >
> > >
> > > >
> > > > In the category of no longer in use, we have the compatibility
> > > > generator for the kde_projects.xml file. This was introduced when we
> > > > shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> > > > keeping services that needed to discover a list of KDE Projects
> > > > functional.
> > > >
> > > > As we've since migrated to using YAML files within the
> > > > sysadmin/repo-metadata repository for both the CI System and
> > > > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > > > checkouts) there shouldn't to my knowledge be anything still relying
> > > > on this (aside from perhaps scripty).>
> > > > I'd therefore like to shut this generator down as well, along with the
> > > > compaibility redirector running at projects.kde.org (given that it has
> > > > been some time since we were using that site, and many projects have
> > > > moved around in the virtual structure since then, making the redirects
> > > > it is able to offer useless)
> > >
> > > Two points:
> > > - scripty still uses the XML file and we may need some time to migrate.
> >
> > I feared this may have been the case. What sort of timeline are we
> > looking at in terms of switching scripty over?
>
> Over to what?

To using the YAML files within sysadmin/repo-metadata, which is what
the legacy kde_projects.xml file is generated from currently.
(Originally the kde_projects.xml file was generated from the
Redmine/Chiliproject database - those YAML files just replaced it)

>
> Cheers,
>   Albert
>
>

Thanks,
Ben

D25123: [WIP] New yakuake logo/icon

[Noah Davis]

ndavis added a comment.


  I think I prefer C the most now that I've seen it next to other icons. It has 
a similar level of detail to other Breeze icons.

REPOSITORY
  R266 Breeze Icons

REVISION DETAIL
  https://phabricator.kde.org/D25123

To: mglb, #vdg, #yakuake, hein
Cc: ndavis, KonqiDragon, ognarb, ngraham, hein, kde-frameworks-devel, 
vmarinescu, ryanmccoskrie, LeGast00n, GB_2, michaelh, bruns

D25015: Update breeze theme shadows

[Niccolò Venerandi]

niccolove added a comment.


  In D25015#559344 , @filipf wrote:
  
  > I'd prefer the shadows to have equal strength all around, I couldn't get 
used to weaker shadows in the corners.
  
  
  Oh! That's a pity, I really liked them. I will update it as soon as I have 
time.
  
  In D25015#559687 , @ngraham wrote:
  
  > Ah, pixel-perfect before-and-after images make it much easier to see. I 
will reiterate my belief that the shadows now need to be bigger if we're going 
to make them lighter and weaker.
  
  
  Uhm, I will try something and get back to you.
  
  In D25015#559765 , @ndavis wrote:
  
  > Rather than painstakingly making shadows by hand in Inkscape, perhaps we 
should be using KWin for the shadows?
  
  
  Remember that there are third party desktop themes with SVG that we probably 
want to support. Wouldn't using KWin for shadows break those?

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D25015

To: niccolove, #vdg
Cc: ndavis, manueljlin, ngraham, filipf, kde-frameworks-devel, LeGast00n, GB_2, 
michaelh, bruns

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Alexander Potashev]

сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> This would include the shutdown of WebSVN in particular, which when
> coupled with the shutdown of our two CGit instances would also allow
> for us to eliminate an entire virtual machine from our systems.

Will there be any web interface for SVN after shutdown of WebSVN?

Can we assume https://phabricator.kde.org/source/svn/ remains
available during the next 10 years?


I'm not sure what use case Luigi has in mind, but among Russian l10n
team we often use WebSVN to refer to specific SVN revisions, for
example: https://websvn.kde.org/?view=revision=1555342

-- 
Alexander Potashev

Re: plasma-nano and plasma-phone-components are now in kdereview

[Albert Astals Cid]

El divendres, 8 de novembre de 2019, a les 8:09:33 CET, Bhushan Shah va 
escriure:
> Hello!
> 
> plasma-nano: https://invent.kde.org/kde/plasma-nano
> plasma-phone-components: https://invent.kde.org/kde/plasma-phone-components
> 
> Two repos have been moved to kdereview, with final intended destinition
> being kde/workspace.
> 
> plasma-nano is a minimal shell package which other shell package can
> extend, while plasma-phone-components is a shell package, look and feel
> and several other components which makes Plasma Mobile.

In the future, can we please have one email per component so it gets easier to 
track what has been said about what?

Cheers,
  Albert

> 
> Thanks
> 

D25123: [WIP] New yakuake logo/icon

[Mariusz Glebocki]

mglb updated this revision to Diff 69507.
mglb added a comment.


  In D25123#558363 , @ndavis wrote:
  
  > switching to that system means we would need to change many icons.
  
  
  Let's just keep this in mind when making new icons. At least when it doesn't 
stand out too much, i.e. we shouldn't make new square icons smaller than other 
square icons just to match circles, but also don't try to fill all available 
space when there is no need to.
  
  I've aligned icons vertically. There are two new varians of "A":
  
  - A1 - Uses all available space, with larger top bar
  - A2 - Folder-icon sized, also with larger top bar. Dolphin/folder, 
system-run, and some other rectangular icons do not use full available area, 
even though they could just by scaling them up proportionally - they have 4px 
side margins and 6px up/down margins.
  
  F7750328: yakuake-icon.png 
  
  A, A1:
  F7750323: Screenshot_20191109_205001.png 
F7750324: Screenshot_20191109_205010.png 

  A2, C:
  F7750325: Screenshot_20191109_205036.png 
F7750326: Screenshot_20191109_205050.png 


REPOSITORY
  R266 Breeze Icons

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D25123?vs=69202=69507

BRANCH
  yakuake

REVISION DETAIL
  https://phabricator.kde.org/D25123

AFFECTED FILES
  icons-dark/apps/48/yakuake-a.svg
  icons-dark/apps/48/yakuake-a1.svg
  icons-dark/apps/48/yakuake-a2.svg
  icons-dark/apps/48/yakuake-b.svg
  icons-dark/apps/48/yakuake-c.svg
  icons-dark/apps/48/yakuake-d.svg
  icons-dark/apps/48/yakuake-e.svg
  icons-dark/apps/48/yakuake-f.svg
  icons-dark/apps/48/yakuake-g.svg
  icons/apps/48/yakuake-a.svg
  icons/apps/48/yakuake-a1.svg
  icons/apps/48/yakuake-a2.svg
  icons/apps/48/yakuake-b.svg
  icons/apps/48/yakuake-c.svg
  icons/apps/48/yakuake-d.svg
  icons/apps/48/yakuake-e.svg
  icons/apps/48/yakuake-f.svg
  icons/apps/48/yakuake-g.svg

To: mglb, #vdg, #yakuake, hein
Cc: ndavis, KonqiDragon, ognarb, ngraham, hein, kde-frameworks-devel, 
vmarinescu, ryanmccoskrie, LeGast00n, GB_2, michaelh, bruns

Re: General Infrastructure Maintainability: API and EBN

[Ben Cooksley]

On Sun, Nov 10, 2019 at 4:28 AM Elvis Angelaccio
 wrote:
>
>
>
> On 09/11/19 01:33, Ben Cooksley wrote:
> > Hi all,
>
> Hi Ben

Hi Elvis,

>
> >
> > Over the past number of years one of the tasks the Sysadmin team has
> > worked on has been improving the overall maintainability of our
> > systems, with a significant number of specialised cronjobs, exceptions
> > and hidden linkages being eliminated.
> >
> > That is with one great exception: api.kde.org and ebn.kde.org.
> >
> > Both of these are suffering from an extreme amount of digital bitrot
> > and special casing and in general are now in a condition where I
> > cannot say for certain whether it would be possible to replicate the
> > setup on a new system without us experiencing some degree of breakage
> > (some of which we may not discover until weeks/months afterwards).
> >
> > In addition, the current setup relies on an old-fashioned overnight
> > reprocessing of all repositories, which is inefficient and resource
> > expensive. A more modern approach would have the various projects api
> > documentation generated on a delayed cycle from relevant branches as
> > part of something like a CI job (but not part of the actual CI
> > workflow itself).
> >
> > For this one, i'm not certain on the best path forward at this stage,
> > however the current state of affairs cannot continue. We have tried
> > over the past few years to find people to work on a replacement for
> > the tooling involved, but alas we've yet to have success here.
> >
> > Thoughts anyone?
>
> I'd say api.kde.org is too important to let it go. The EBN is less
> important but still useful, I still see people pushing EBN-based fixes
> once in a while.
>
> Have we ever tried to use a GSoC project to modernize either of them? If
> not, would it make sense to try next year?
>

My only concern there would be whether the project is large enough in
scope to justify the amount of time commitment a GSoC project normally
spans.
>From my understanding of the problem in question it quite probably
does not meet those requirements.

> >
> > Regards,
> > Ben
>
> Cheers,
> Elvis
>

Cheers,
Ben

Re: New Framework Review: KDAV

[Alexander Potashev]

сб, 9 нояб. 2019 г. в 14:37, Volker Krause :
> during Akademy there was a request to promote KDAV from KDE PIM to Frameworks
> for use by Plasma Mobile. KDAV is a framework that implements the CalDav/
> CardDav/GroupDav protocol on top of KIO's WebDav support. It would be
> classified as a functional tier 3 framework.

Hi Volker,

The name "KDAV" suggests that it might implement WebDAV. Do you think
if it should be renamed to something like "DAVExtensions" or let's say
"AnyDAV"?

-- 
Alexander Potashev

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Albert Vaca Cintora]

On Sat, Nov 9, 2019 at 6:53 PM Ben Cooksley  wrote:
>
> Unfortunately Rosetta does not have the necessary free disk space, as
> the Subversion repository is approximately 80GB these days in size,
> and operating WebSVN requires a full copy of the Subversion repository
> locally in order to operate.

Is this also the case if you run WebSVN next to the SVN server itself
(ie: on the same machine)? If a single repo copy can be shared by
WebSVN and the actual SVN server, that would reduce the storage needs.

Albert

D25123: [WIP] New yakuake logo/icon

[Björn Feber]

GB_2 added a comment.


  In D25123#560491 , @ndavis wrote:
  
  > I think I prefer C the most now that I've seen it next to other icons. It 
has a similar level of detail to other Breeze icons.
  
  
  +1

REPOSITORY
  R266 Breeze Icons

REVISION DETAIL
  https://phabricator.kde.org/D25123

To: mglb, #vdg, #yakuake, hein
Cc: GB_2, ndavis, KonqiDragon, ognarb, ngraham, hein, kde-frameworks-devel, 
vmarinescu, ryanmccoskrie, LeGast00n, michaelh, bruns

Re: Sysadmin Load Reduction: Code Related Services

[Albert Astals Cid]

El dissabte, 9 de novembre de 2019, a les 21:52:13 CET, Ben Cooksley va 
escriure:
> On Sun, Nov 10, 2019 at 8:43 AM Albert Astals Cid  wrote:
> >
> > El dissabte, 9 de novembre de 2019, a les 18:47:57 CET, Ben Cooksley va 
> > escriure:
> > > On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano  
> > > wrote:
> > > >
> > > > Ben Cooksley ha scritto:
> > > > > Hi all,
> > > > >
> > > > > In the category of code related services, Sysadmin currently supports
> > > > > a wide-ranging number of services (which makes sense given the nature
> > > > > of the community). Some of these however may no longer be in use or
> > > > > will be duplicative of other services following the transition to
> > > > > Gitlab.
> > > > >
> > > > > In the category of duplicative, we have our two CGit instances at
> > > > > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these were
> > > > > justifiable as there was no other way of browsing scratch/clone
> > > > > repositories over the web.
> > > > >
> > > > > With the migration to Gitlab however all repositories will become
> > > > > browsable through it, meaning it no longer makes sense to offer two
> > > > > browsers that provide the exact same information (with Gitlab having
> > > > > greater capabilities). I'd therefore like to shut both of these down
> > > > > once Code Hosting has transitioned to Gitlab.
> > > >
> > > > Luckily we tried to use commits.kde.org as generic redirect. Will the 
> > > > generic
> > > > redirect commits.kde.org be updated to point to the proper repository? 
> > > > It may
> > > > be complicated if the new structure contains the namespaces for each
> > > > repository, but we need to keep it working.
> > >
> > > The commits.kde.org redirector is intended to provide permanent links,
> > > so yes it will be updated to redirect people to Gitlab instead once
> > > the switch to Gitlab is completed.
> > >
> > > >
> > > > >
> > > > > In the category of no longer in use, we have the compatibility
> > > > > generator for the kde_projects.xml file. This was introduced when we
> > > > > shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> > > > > keeping services that needed to discover a list of KDE Projects
> > > > > functional.
> > > > >
> > > > > As we've since migrated to using YAML files within the
> > > > > sysadmin/repo-metadata repository for both the CI System and
> > > > > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > > > > checkouts) there shouldn't to my knowledge be anything still relying
> > > > > on this (aside from perhaps scripty).>
> > > > > I'd therefore like to shut this generator down as well, along with the
> > > > > compaibility redirector running at projects.kde.org (given that it has
> > > > > been some time since we were using that site, and many projects have
> > > > > moved around in the virtual structure since then, making the redirects
> > > > > it is able to offer useless)
> > > >
> > > > Two points:
> > > > - scripty still uses the XML file and we may need some time to migrate.
> > >
> > > I feared this may have been the case. What sort of timeline are we
> > > looking at in terms of switching scripty over?
> >
> > Over to what?
> 
> To using the YAML files within sysadmin/repo-metadata, which is what
> the legacy kde_projects.xml file is generated from currently.

Well, someone has to change the code that parses the xml to code that gets 
stuff from git and parses yaml, it's not hard, but has to be done.

> (Originally the kde_projects.xml file was generated from the
> Redmine/Chiliproject database - those YAML files just replaced it)

Yes i know :)

Cheers,
  Albert

> 
> >
> > Cheers,
> >   Albert
> >
> >
> 
> Thanks,
> Ben
> 

kde-devel mailing list archive

[Alexander Potashev]

Hi,

How do I access kde-devel mailing list archive?

The archive linked at https://mail.kde.org/mailman/listinfo/kde-devel
appears empty.

-- 
Alexander Potashev

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Friedrich W. H. Kossebau]

Am Samstag, 9. November 2019, 21:22:16 CET schrieb Ben Cooksley:
> On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid  wrote:
> > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va 
escriure:
> > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev 
 wrote:
> > > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > > > This would include the shutdown of WebSVN in particular, which when
> > > > > coupled with the shutdown of our two CGit instances would also allow
> > > > > for us to eliminate an entire virtual machine from our systems.
> > > > 
> > > > Will there be any web interface for SVN after shutdown of WebSVN?
> > > > 
> > > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > > available during the next 10 years?
> > > 
> > > Phabricator's browser will be retired as part of the shutdown of
> > > Phabricator, which will take place once Gitlab has assumed
> > > responsibility for code hosting and review, and the tasks have been
> > > migrated from Phabricator.
> > > 
> > > Should WebSVN be shutdown as well, then there would be no web
> > > interface to our SVN repository.
> > 
> > That's not acceptable.
> 
> Mind explaining why?

FWIW, everytime I had to deal with translations as developer (like checking 
pot files as well as .po files contents) I found having the web interface and 
its browsing feature very valuable to quickly find what I was looking for, 
over having to locally mess around with svn commands and juggling between 
commandline & file viewers. Including url bookmarks for quick access to 
browsing certain sets of files.

Incidents which I remember right now included:
* finding out whether extraction scripts were working as intended
* comparing translations seen by users over what they should see

Are there any other KDE clients of the svn repos still around, besides 
translation system?
Perhaps the "full clone" needed for WebSVN could be reduced to the translation 
subtrees, would that improve situation to a degree if possible? (well, you 
surely thought of this yourself, just in case)

For me as developer contributor to projects in KDE spheres, losing the web 
browsing interface for raw translation files would be a regression in 
developer experience.

Cheers
Friedrich

D25015: Update breeze theme shadows

[Noah Davis]

ndavis added a comment.


  In D25015#560498 , @niccolove 
wrote:
  
  > In D25015#559344 , @filipf wrote:
  >
  > > I'd prefer the shadows to have equal strength all around, I couldn't get 
used to weaker shadows in the corners.
  >
  >
  > Oh! That's a pity, I really liked them. I will update it as soon as I have 
time.
  >
  > In D25015#559687 , @ngraham 
wrote:
  >
  > > Ah, pixel-perfect before-and-after images make it much easier to see. I 
will reiterate my belief that the shadows now need to be bigger if we're going 
to make them lighter and weaker.
  >
  >
  > Uhm, I will try something and get back to you.
  >
  > In D25015#559765 , @ndavis wrote:
  >
  > > Rather than painstakingly making shadows by hand in Inkscape, perhaps we 
should be using KWin for the shadows?
  >
  >
  > Remember that there are third party desktop themes with SVG that we 
probably want to support. Wouldn't using KWin for shadows break those?
  
  
  If we remove the code for using those SVG shadows, it won't break them in the 
sense that they will stop working. It'll just mean those parts of the desktop 
themes won't be used. I suppose that could be seen as a form of visual breakage.
  
  For complete theme sets, this shouldn't be such a problem since they also 
typically come with their own window decorations and recommend a specific 
widget style. For people who just want to get rid of the shadows we should 
probably provide an option somewhere to disable them rather than making them 
edit the plasma theme. I suppose we could wait until Plasma 6 to make that kind 
of change, but that's a ways away.
  
  Regardless of the method we use to achieve it (including continuing to use 
SVGs), I think it might be best to make Plasmashell's shadows match the shadows 
cast by menus (such as context menus) in applications. These are defined in the 
Breeze widget style and have different sizes to match the different window 
shadow sizes.

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D25015

To: niccolove, #vdg
Cc: ndavis, manueljlin, ngraham, filipf, kde-frameworks-devel, LeGast00n, GB_2, 
michaelh, bruns

Re: kde-devel mailing list archive

[Alexander Potashev]

Thanks!

вс, 10 нояб. 2019 г. в 02:30, Albert Astals Cid :
>
> El dissabte, 9 de novembre de 2019, a les 23:45:30 CET, Alexander Potashev va 
> escriure:
> > Hi,
> >
> > How do I access kde-devel mailing list archive?
>
> https://marc.info/?l=kde-devel=1=2
>
> Cheers,
>   Albert
>
> >
> > The archive linked at https://mail.kde.org/mailman/listinfo/kde-devel
> > appears empty.
> >
> >
>
>
>
>


-- 
Alexander Potashev

Re: Sysadmin Load Reduction: Code Related Services

[Ben Cooksley]

On Sun, Nov 10, 2019 at 11:22 AM Albert Astals Cid  wrote:
>
> El dissabte, 9 de novembre de 2019, a les 21:52:13 CET, Ben Cooksley va 
> escriure:
> > On Sun, Nov 10, 2019 at 8:43 AM Albert Astals Cid  wrote:
> > >
> > > El dissabte, 9 de novembre de 2019, a les 18:47:57 CET, Ben Cooksley va 
> > > escriure:
> > > > On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano 
> > > >  wrote:
> > > > >
> > > > > Ben Cooksley ha scritto:
> > > > > > Hi all,
> > > > > >
> > > > > > In the category of code related services, Sysadmin currently 
> > > > > > supports
> > > > > > a wide-ranging number of services (which makes sense given the 
> > > > > > nature
> > > > > > of the community). Some of these however may no longer be in use or
> > > > > > will be duplicative of other services following the transition to
> > > > > > Gitlab.
> > > > > >
> > > > > > In the category of duplicative, we have our two CGit instances at
> > > > > > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these were
> > > > > > justifiable as there was no other way of browsing scratch/clone
> > > > > > repositories over the web.
> > > > > >
> > > > > > With the migration to Gitlab however all repositories will become
> > > > > > browsable through it, meaning it no longer makes sense to offer two
> > > > > > browsers that provide the exact same information (with Gitlab having
> > > > > > greater capabilities). I'd therefore like to shut both of these down
> > > > > > once Code Hosting has transitioned to Gitlab.
> > > > >
> > > > > Luckily we tried to use commits.kde.org as generic redirect. Will the 
> > > > > generic
> > > > > redirect commits.kde.org be updated to point to the proper 
> > > > > repository? It may
> > > > > be complicated if the new structure contains the namespaces for each
> > > > > repository, but we need to keep it working.
> > > >
> > > > The commits.kde.org redirector is intended to provide permanent links,
> > > > so yes it will be updated to redirect people to Gitlab instead once
> > > > the switch to Gitlab is completed.
> > > >
> > > > >
> > > > > >
> > > > > > In the category of no longer in use, we have the compatibility
> > > > > > generator for the kde_projects.xml file. This was introduced when we
> > > > > > shutdown Redmine/Chiliproject and migrated to Phabricator, as a way 
> > > > > > of
> > > > > > keeping services that needed to discover a list of KDE Projects
> > > > > > functional.
> > > > > >
> > > > > > As we've since migrated to using YAML files within the
> > > > > > sysadmin/repo-metadata repository for both the CI System and
> > > > > > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > > > > > checkouts) there shouldn't to my knowledge be anything still relying
> > > > > > on this (aside from perhaps scripty).>
> > > > > > I'd therefore like to shut this generator down as well, along with 
> > > > > > the
> > > > > > compaibility redirector running at projects.kde.org (given that it 
> > > > > > has
> > > > > > been some time since we were using that site, and many projects have
> > > > > > moved around in the virtual structure since then, making the 
> > > > > > redirects
> > > > > > it is able to offer useless)
> > > > >
> > > > > Two points:
> > > > > - scripty still uses the XML file and we may need some time to 
> > > > > migrate.
> > > >
> > > > I feared this may have been the case. What sort of timeline are we
> > > > looking at in terms of switching scripty over?
> > >
> > > Over to what?
> >
> > To using the YAML files within sysadmin/repo-metadata, which is what
> > the legacy kde_projects.xml file is generated from currently.
>
> Well, someone has to change the code that parses the xml to code that gets 
> stuff from git and parses yaml, it's not hard, but has to be done.

*nod*

I do recall that at one point in our conversations that scripty only
used the kde_projects.xml file as a check against it's own internal
data.
Has that since been changed?

>
> > (Originally the kde_projects.xml file was generated from the
> > Redmine/Chiliproject database - those YAML files just replaced it)
>
> Yes i know :)
>
> Cheers,
>   Albert

Cheers,
Ben

>
> >
> > >
> > > Cheers,
> > >   Albert
> > >
> > >
> >
> > Thanks,
> > Ben
> >
>
>
>
>

Re: Sysadmin Load Reduction: Code Related Services

[Ben Cooksley]

On Sun, Nov 10, 2019 at 11:37 AM Alexander Potashev
 wrote:
>
> сб, 9 нояб. 2019 г. в 02:51, Ben Cooksley :
> > In the category of no longer in use, we have the compatibility
> > generator for the kde_projects.xml file. This was introduced when we
> > shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> > keeping services that needed to discover a list of KDE Projects
> > functional.
> >
> > As we've since migrated to using YAML files within the
> > sysadmin/repo-metadata repository for both the CI System and
> > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > checkouts) there shouldn't to my knowledge be anything still relying
> > on this (aside from perhaps scripty).
> >
> > I'd therefore like to shut this generator down as well, along with the
> > compaibility redirector running at projects.kde.org (given that it has
> > been some time since we were using that site, and many projects have
> > moved around in the virtual structure since then, making the redirects
> > it is able to offer useless)
>
> Hi Ben,

Hi Alexander,

>
> I am developing a new version of the "opensrc" plugin for Lokalize [1]
> and it currently depends on kde_projects.xml. Of course I can add new
> code to scan the Git repo instead of just fetching kde_projects.xml,
> however it would be more complicated.
>
>
> Is there any good reason for killing kde_projects.xml? Would that
> really reduce the workload on Sysadmin team?
> I can't suspect any "moving parts" in the generator that may require
> maintenance.
>

This is mostly a case of another (small) thing that needs to be kept
running, and fixed should it break.
All of the reductions i've proposed will have a quite small effect,
however cumulatively they will have a much larger effect.

Given that it is duplicative of what we have in the YAML files (which
are substantially easier to maintain) it makes more sense to
standardise on the original source of the information and remove the
legacy compatibility XML file.

>
> [1] https://cgit.kde.org/scratch/aspotashev/lokalize-opensrc-py.git/
>
> --
> Alexander Potashev

Cheers,
Ben

KDE Frameworks 5.64.0 released

[David Faure]

10th November 2019. KDE today announces the release of KDE Frameworks 5.64.0.

KDE Frameworks are 81 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https://kde.org/products/frameworks/


Attica

  Add some std::move in setter functions

Baloo

  Make it compile against qt5.15
  Use propertymap to store properties in Baloo::Result
  Add standalone conversion functions for PropertyMap to Json and vice versa
  [Database] Rework handling environment flags
  Replace recursion in FilteredDirIterator with loop iteration

Breeze Icons

  Center-align the non-square 64px audio mimetype icons (bug 393550)
  Delete remnants of nepomuk icon
  Move colorful 32px help-about icon into actions (bug 396626)
  Improve draw icons (bug 399665)
  Delete nepomuk icon
  Fill middle mouse button area
  Add folder-recent, extend hand of clock in folder-temp
  Use a more correct and appropriate visual metaphor for "get hot new stuff" 
icon (bug 400500)
  Update elisa icon
  Use css instead of scss as output format
  Fix incorrect rendering of 22px edit-opacity icon
  Add edit-opacity icons (bug 408283)
  Icons for windy weather (bug 412718)
  Fix incorrect margins in 16/22px media icons
  Use the text rather than highlight color for rating/star emblem
  Add draw-arrow icons (bug 408283)
  Add draw-highlight action icons (bug 408283)
  Add PATH/LD_LIBRARY_PATH to qrcAlias invocation
  Add applications-network icon for renaming Internet category to Network
  Add edit-line-width icons (bug 408283)

Extra CMake Modules

  Don't set C/C++ standards if already set
  Use modern way to set the C/CXX standad
  Raise CMake requirements to 3.5
  ECMAddQch: support PREDEFINED_MACROS/BLANK_MACROS with blanks & quotes

Framework Integration

  Add standard icons to support to all entries in QDialogButtonBox (bug 398973)
  ensure winId() not called on non-native widgets (bug 412675)

KActivitiesStats

  tests: fix macos build failure
  Windows MSVC compile fix
  Add a utility accessor to get a QUrl from a ResultSet::Result

KArchive

  Fix memory leak in KXzFilter::init
  Fix null pointer reference when extraction fails
  decodeBCJ2: Fix assert with broken files
  KXzFilter::Private: remove unused props
  K7Zip: Fix memory use in readAndDecodePackedStreams

KCalendarCore #

  Add libical version too
  Explicitly define the Journal copy ctor

KCMUtils

  Conditionally show navigation buttons in the header for multi-page KCMs
  don't use a custom header height (bug 404396)
  add extra include
  Fix memory leak of KQuickAddons::ConfigModule objects (bug 412998)
  [KCModuleLoader] Show error when QML fails to load

KConfig

  kconfig_compiler: Move the KSharedConfig::Ptr when using them
  Make it compile against qt5.15 without deprecated method
  Expose isImmutable to introspection (e.g. QML)
  Add convenience for defaults/dirty states to KCoreConfigSkeleton
  Make kconfig_compiler generate ctors with the optional parent arg
  Make preferences() a public function

KConfigWidgets

  Avoid overloading KCModule::changed

KContacts

  Install translations

KCoreAddons

  KProcessInfoList -- add proclist backend for FreeBSD

KDeclarative

  Use compile time checked connect
  Make the settingChanged() slot protected
  Get KQuickAddons::ConfigModule to expose if we're in the defaults state
  Grab the keyboard when KeySequenceItem is recording
  Add ManagedConfigModule
  Remove outdated comment about [$e] expansion
  [ConfigModule] Expose mainUi component status and error string

KDELibs 4 Support

  KLocale api docs: make it easier to find how to port code away from it

KDocTools

  man: use  instead of 

KFileMetaData

  Fix crash in writer collection and cleanup

KHTML

  Extend KHtmlView::print() to use a predefined QPrinter instance (bug 405011)

KI18n

  Add KLocalizedString::untranslatedText
  Replace all qWarning and related calls with categorised logging

KIconThemes

  Fix usage of the new deprecation macros for assignIconsToContextMenu
  Deprecate KIconTheme::assignIconsToContextMenu

KIO

  Const & signature of new introduced SlaveBase::configValue
  Port to the QSslError variant of KSslInfoDialog
  Port KSSLD internals from KSslError to QSslError
  Make non-ignorable SSL errors explicit
  auto-enable KIO_ASSERT_SLAVE_STATES also for from-git builds
  Port (most of) KSslInfoDialog from KSslError to QSslError
  kio_http: avoid double Content-Type and Depth when used by KDAV
  Port the KSSLD D-Bus interface from KSslError to QSslError
  Replace usage of SlaveBase::config()->readEntry by SlaveBase::configValue
  Remove two unused member variables using KSslError
  Avoid sending KDirNotify::emitFilesAdded when the emptytrashjob finishes
  Deprecate the KTcpSocket-based variant of SslUi::askIgnoreSslErrors
  Treat "application/x-ms-dos-executable" as executable on all platforms (bug 
412694)
  Replace usage of 

KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 SUSEQt5.12 - Build # 74 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.12/74/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 02:06:32 +
 Build duration:
21 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 18 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ECMPoQmToolsTestFailed: projectroot.tests.GenerateSipBindingsName: projectroot.tests Failed: 0 test(s), Passed: 61 test(s), Skipped: 0 test(s), Total: 61 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  Cobertura Coverage Report

KDE CI: Frameworks » kservice » kf5-qt5 FreeBSDQt5.13 - Build # 51 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20FreeBSDQt5.13/51/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:22:54 +
 Build duration:
1 hr 34 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 9 test(s)Failed: projectroot.autotests.kmimeassociationstestFailed: projectroot.autotests.ksycoca_xdgdirstestName: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » extra-cmake-modules » kf5-qt5 SUSEQt5.13 - Build # 40 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.13/40/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Sun, 10 Nov 2019 02:06:32 +
 Build duration:
1 hr 50 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 18 test(s), Skipped: 0 test(s), Total: 20 test(s)Failed: projectroot.tests.ECMPoQmToolsTestFailed: projectroot.tests.GenerateSipBindingsName: projectroot.tests Failed: 0 test(s), Passed: 61 test(s), Skipped: 0 test(s), Total: 61 test(s)Name: projectroot.tests.ECMAddTests Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  Cobertura Coverage Report

KDE CI: Frameworks » networkmanager-qt » kf5-qt5 SUSEQt5.12 - Build # 62 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/networkmanager-qt/job/kf5-qt5%20SUSEQt5.12/62/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 03:45:02 +
 Build duration:
12 min and counting
   BUILD ARTIFACTS
  acc/KF5NetworkManagerQt-5.65.0.xmllogs/KF5NetworkManagerQt/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(6/6)53%
(164/311)53%
(164/311)58%
(8198/14152)36%
(1960/5408)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(3/3)100%
(3/3)100%
(239/239)47%
(108/232)autotests.settings100%
(37/37)100%
(37/37)99%
(1907/1915)76%
(254/336)src25%
(26/102)25%
(26/102)27%
(972/3634)21%
(418/1964)src.dbus20%
(16/80)20%
(16/80)10%
(94/924)100%
(0/0)src.fakenetwork75%
(6/8)75%
(6/8)75%
(503/674)46%
(52/114)src.settings94%
(76/81)94%
(76/81)66%
(4483/6766)41%
(1128/2762)

KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.13 - Build # 78 - Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20SUSEQt5.13/78/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Sun, 10 Nov 2019 02:18:53 +
 Build duration:
1 hr 54 min and counting
   BUILD ARTIFACTS
  acc/KF5Purpose-5.65.0.xml
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.menutest
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report23%
(5/22)30%
(14/47)30%
(14/47)22%
(441/2035)17%
(164/939)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(2/2)100%
(2/2)92%
(135/146)51%
(47/92)src100%
(8/8)100%
(8/8)68%
(226/334)49%
(89/183)src.externalprocess0%
(0/2)0%
(0/2)0%
(0/137)0%
(0/98)src.fileitemactionplugin0%
(0/1)0%
(0/1)0%
(0/24)0%
(0/18)src.plugins.bluetooth0%
(0/1)0%
(0/1)0%
(0/33)0%
(0/8)src.plugins.email0%
(0/1)0%
(0/1)0%
(0/64)0%
(0/24)src.plugins.imgur0%
(0/2)0%
(0/2)0%
(0/184)0%
(0/63)src.plugins.kdeconnect0%
(0/1)0%
(0/1)0%
(0/31)0%
(0/6)src.plugins.kdeconnect_sms0%
(0/1)0%
(0/1)0%
(0/16)0%
(0/2)src.plugins.ktp-sendfile0%
(0/1)0%
(0/1)0%
(0/28)0%
(0/6)src.plugins.pastebin0%
(0/1)0%
(0/1)0%
(0/54)0%
(0/23)src.plugins.phabricator0%
(0/3)0%
(0/3)0%
(0/216)0%
(0/74)src.plugins.phabricator.quick0%
(0/5)0%
(0/5)0%
(0/93)0%
(0/48)src.plugins.phabricator.tests0%
(0/1)0%
(0/1)0%
(0/60)0%
(0/22)src.plugins.reviewboard0%
(0/3)0%
(0/3)0%
(0/229)0%
(0/70)src.plugins.reviewboard.quick0%
(0/7)0%
(0/7)0%
(0/153)0%
(0/80)src.plugins.saveas100%
(1/1)100%
(1/1)57%
(29/51)61%
(23/38)src.plugins.telegram0%
  

KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.13 - Build # 33 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.13/33/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:36:07 +
 Build duration:
1 hr 37 min and counting
   JUnit Tests
  Name: projectroot.autotests Failed: 13 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 42 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testRemoteAccessFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay

Stopping the "KDE Applications" brand

[Albert Astals Cid]

We're planning to stop using the "KDE Applications" brand

Phabricator:
  https://phabricator.kde.org/T11933

Release-team threads:
  https://mail.kde.org/pipermail/release-team/2019-October/011582.html

  https://mail.kde.org/pipermail/release-team/2019-September/011512.html


Please contribute to the discussion in those channels :)

Cheers,
  Albert

Re: Sysadmin Load Reduction: Code Related Services

[Alexander Potashev]

сб, 9 нояб. 2019 г. в 02:51, Ben Cooksley :
> In the category of no longer in use, we have the compatibility
> generator for the kde_projects.xml file. This was introduced when we
> shutdown Redmine/Chiliproject and migrated to Phabricator, as a way of
> keeping services that needed to discover a list of KDE Projects
> functional.
>
> As we've since migrated to using YAML files within the
> sysadmin/repo-metadata repository for both the CI System and
> kdesrc-build (and with LXR using kdesrc-build to do it's code
> checkouts) there shouldn't to my knowledge be anything still relying
> on this (aside from perhaps scripty).
>
> I'd therefore like to shut this generator down as well, along with the
> compaibility redirector running at projects.kde.org (given that it has
> been some time since we were using that site, and many projects have
> moved around in the virtual structure since then, making the redirects
> it is able to offer useless)

Hi Ben,

I am developing a new version of the "opensrc" plugin for Lokalize [1]
and it currently depends on kde_projects.xml. Of course I can add new
code to scan the Git repo instead of just fetching kde_projects.xml,
however it would be more complicated.


Is there any good reason for killing kde_projects.xml? Would that
really reduce the workload on Sysadmin team?
I can't suspect any "moving parts" in the generator that may require
maintenance.


[1] https://cgit.kde.org/scratch/aspotashev/lokalize-opensrc-py.git/

-- 
Alexander Potashev

D25015: Update breeze theme shadows

[Noah Davis]

ndavis added a comment.


  One thing we might need to do in order to finally stop changing the shadows 
is come up with a system for deciding how shadows should look based on the 
elevation we want certain UI elements to have. We could copy Material Design 
shadows, but I don't think we should. MD's shadows get darker the larger they 
are, but that's not how real shadows work. Real shadows get darker the smaller 
they are because light bounces around.

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D25015

To: niccolove, #vdg
Cc: ndavis, manueljlin, ngraham, filipf, kde-frameworks-devel, LeGast00n, GB_2, 
michaelh, bruns

D25015: Update breeze theme shadows

[Carson Black]

cblack added a comment.


  In D25015#560515 , @ndavis wrote:
  
  > One thing we might need to do in order to finally stop changing the shadows 
is come up with a math based system for deciding how shadows should look based 
on the elevation we want certain UI elements to have. We could copy Material 
Design shadows, but I don't think we should. MD's shadows get darker the larger 
they are, but that's not how real shadows work. Real shadows get darker the 
smaller they are because light bounces around.
  
  
  Material shadows get more voluminous, not darker.

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D25015

To: niccolove, #vdg
Cc: cblack, ndavis, manueljlin, ngraham, filipf, kde-frameworks-devel, 
LeGast00n, GB_2, michaelh, bruns

Re: Sysadmin Load Reduction: Code Related Services

[Albert Astals Cid]

El diumenge, 10 de novembre de 2019, a les 1:04:04 CET, Ben Cooksley va 
escriure:
> On Sun, Nov 10, 2019 at 11:22 AM Albert Astals Cid  wrote:
> >
> > El dissabte, 9 de novembre de 2019, a les 21:52:13 CET, Ben Cooksley va 
> > escriure:
> > > On Sun, Nov 10, 2019 at 8:43 AM Albert Astals Cid  wrote:
> > > >
> > > > El dissabte, 9 de novembre de 2019, a les 18:47:57 CET, Ben Cooksley va 
> > > > escriure:
> > > > > On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano 
> > > > >  wrote:
> > > > > >
> > > > > > Ben Cooksley ha scritto:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > In the category of code related services, Sysadmin currently 
> > > > > > > supports
> > > > > > > a wide-ranging number of services (which makes sense given the 
> > > > > > > nature
> > > > > > > of the community). Some of these however may no longer be in use 
> > > > > > > or
> > > > > > > will be duplicative of other services following the transition to
> > > > > > > Gitlab.
> > > > > > >
> > > > > > > In the category of duplicative, we have our two CGit instances at
> > > > > > > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these 
> > > > > > > were
> > > > > > > justifiable as there was no other way of browsing scratch/clone
> > > > > > > repositories over the web.
> > > > > > >
> > > > > > > With the migration to Gitlab however all repositories will become
> > > > > > > browsable through it, meaning it no longer makes sense to offer 
> > > > > > > two
> > > > > > > browsers that provide the exact same information (with Gitlab 
> > > > > > > having
> > > > > > > greater capabilities). I'd therefore like to shut both of these 
> > > > > > > down
> > > > > > > once Code Hosting has transitioned to Gitlab.
> > > > > >
> > > > > > Luckily we tried to use commits.kde.org as generic redirect. Will 
> > > > > > the generic
> > > > > > redirect commits.kde.org be updated to point to the proper 
> > > > > > repository? It may
> > > > > > be complicated if the new structure contains the namespaces for each
> > > > > > repository, but we need to keep it working.
> > > > >
> > > > > The commits.kde.org redirector is intended to provide permanent links,
> > > > > so yes it will be updated to redirect people to Gitlab instead once
> > > > > the switch to Gitlab is completed.
> > > > >
> > > > > >
> > > > > > >
> > > > > > > In the category of no longer in use, we have the compatibility
> > > > > > > generator for the kde_projects.xml file. This was introduced when 
> > > > > > > we
> > > > > > > shutdown Redmine/Chiliproject and migrated to Phabricator, as a 
> > > > > > > way of
> > > > > > > keeping services that needed to discover a list of KDE Projects
> > > > > > > functional.
> > > > > > >
> > > > > > > As we've since migrated to using YAML files within the
> > > > > > > sysadmin/repo-metadata repository for both the CI System and
> > > > > > > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > > > > > > checkouts) there shouldn't to my knowledge be anything still 
> > > > > > > relying
> > > > > > > on this (aside from perhaps scripty).>
> > > > > > > I'd therefore like to shut this generator down as well, along 
> > > > > > > with the
> > > > > > > compaibility redirector running at projects.kde.org (given that 
> > > > > > > it has
> > > > > > > been some time since we were using that site, and many projects 
> > > > > > > have
> > > > > > > moved around in the virtual structure since then, making the 
> > > > > > > redirects
> > > > > > > it is able to offer useless)
> > > > > >
> > > > > > Two points:
> > > > > > - scripty still uses the XML file and we may need some time to 
> > > > > > migrate.
> > > > >
> > > > > I feared this may have been the case. What sort of timeline are we
> > > > > looking at in terms of switching scripty over?
> > > >
> > > > Over to what?
> > >
> > > To using the YAML files within sysadmin/repo-metadata, which is what
> > > the legacy kde_projects.xml file is generated from currently.
> >
> > Well, someone has to change the code that parses the xml to code that gets 
> > stuff from git and parses yaml, it's not hard, but has to be done.
> 
> *nod*
> 
> I do recall that at one point in our conversations that scripty only
> used the kde_projects.xml file as a check against it's own internal
> data.

Yes and no, we have our i18n branch data hardcoded, but we don't have a list of 
repos, so we need the list of repos from somewhere (and we use the branch data 
from kde_projects.xml to compare it to our hardcoded one to see if there's some 
mismatch).

Cheers,
  Albert

> Has that since been changed?
> 
> >
> > > (Originally the kde_projects.xml file was generated from the
> > > Redmine/Chiliproject database - those YAML files just replaced it)
> >
> > Yes i know :)
> >
> > Cheers,
> >   Albert
> 
> Cheers,
> Ben
> 
> >
> > >
> > > >
> > > > Cheers,
> > > >   Albert
> > > >
> > > >
> > >
> > > Thanks,
> > > Ben
> > >
> >
> >
> >
> >
> 

Re: plasma-nano and plasma-phone-components are now in kdereview

[Albert Astals Cid]

El divendres, 8 de novembre de 2019, a les 8:09:33 CET, Bhushan Shah va 
escriure:
> Hello!
> 
> plasma-nano: https://invent.kde.org/kde/plasma-nano

Please mark PlasmaMiniShellPrivatePlugin::registerTypes as override


What's the point of this?
   connect(this, ::activeChanged, this, 
::activeChanged);
You're double sending the signal?


Cheers,
  Albert

Re: plasma-nano and plasma-phone-components are now in kdereview

[Albert Astals Cid]

El divendres, 8 de novembre de 2019, a les 8:09:33 CET, Bhushan Shah va 
escriure:
> Hello!
> 
> plasma-phone-components: https://invent.kde.org/kde/plasma-phone-components

clazy found a crasher
 const char* country = countrycode.toUtf8().constData();

other minor clazy stuff in http://paste.debian.net/1115558/

And other minor clang-tidy stuff in http://paste.debian.net/1115559/

Cheers,
  Albert

KDE CI: Frameworks » kpty » kf5-qt5 FreeBSDQt5.13 - Build # 19 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kpty/job/kf5-qt5%20FreeBSDQt5.13/19/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:36:12 +
 Build duration:
44 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 0 test(s), Skipped: 0 test(s), Total: 1 test(s)Failed: projectroot.autotests.kptyprocesstest

KDE CI: Frameworks » kservice » kf5-qt5 FreeBSDQt5.13 - Build # 50 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20FreeBSDQt5.13/50/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:36:43 +
 Build duration:
46 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 9 test(s)Failed: projectroot.autotests.kmimeassociationstestFailed: projectroot.autotests.ksycoca_xdgdirstestName: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » solid » kf5-qt5 FreeBSDQt5.13 - Build # 35 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/solid/job/kf5-qt5%20FreeBSDQt5.13/35/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:40:03 +
 Build duration:
58 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 4 test(s)Failed: projectroot.autotests.halbasictest

KDE CI: Frameworks » kdelibs4support » kf5-qt5 FreeBSDQt5.13 - Build # 41 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/kdelibs4support/job/kf5-qt5%20FreeBSDQt5.13/41/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:10:00 +
 Build duration:
1 hr 3 min and counting
   CONSOLE OUTPUT
  [...truncated 82 lines...][2019-11-09T10:42:08.008Z] Fetching upstream changes from https://anongit.kde.org/kde-build-metadata[2019-11-09T10:42:08.008Z]  > git fetch --tags --force --progress -- https://anongit.kde.org/kde-build-metadata +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-09T10:42:08.304Z]  > git rev-parse origin/master^{commit} # timeout=10[2019-11-09T10:42:08.447Z]  > git config core.sparsecheckout # timeout=10[2019-11-09T10:42:08.511Z]  > git checkout -f ea1bcfbb32bb0a7a7aa9a70c5d31c34b7d9fbd11 # timeout=10[2019-11-10T03:13:07.203Z] Commit message: "Update from dependency-data-kf5-qt5 for release/19.12"[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Setup Dependencies)[Pipeline] sh[2019-11-10T03:13:08.509Z] + python3 -u ci-tooling/helpers/prepare-dependencies.py --product Frameworks --project kdelibs4support --branchGroup kf5-qt5 --environment production --platform FreeBSDQt5.13 --installTo /home/jenkins/install-prefix/[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-extra-cmake-modules-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-karchive-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-ki18n-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-kcoreaddons-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-kwindowsystem-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-kconfig-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-kcrash-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-kdbusaddons-kf5-qt5[2019-11-10T03:13:12.692Z] Retrieving: Frameworks-kdoctools-kf5-qt5[2019-11-10T03:13:12.950Z] Retrieving: Frameworks-kservice-kf5-qt5[2019-11-10T03:13:12.950Z] Retrieving: Frameworks-kcodecs-kf5-qt5[2019-11-10T03:13:12.950Z] Retrieving: Frameworks-phonon-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kauth-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kguiaddons-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kwidgetsaddons-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kconfigwidgets-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kitemviews-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kcompletion-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-kiconthemes-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-sonnet-kf5-qt5[2019-11-10T03:13:13.209Z] Retrieving: Frameworks-attica-kf5-qt5[2019-11-10T03:13:13.630Z] Retrieving: Frameworks-kglobalaccel-kf5-qt5[2019-11-10T03:13:13.630Z] Retrieving: Frameworks-ktextwidgets-kf5-qt5[2019-11-10T03:13:13.630Z] Retrieving: Frameworks-breeze-icons-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-knotifications-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kxmlgui-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-solid-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kjobwidgets-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kbookmarks-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kwallet-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kio-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kinit-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kunitconversion-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kded-kf5-qt5[2019-11-10T03:13:17.835Z] Retrieving: Frameworks-kemoticons-kf5-qt5[2019-11-10T03:13:17.835Z] Traceback (most recent call last):[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/urllib/request.py", line 1318, in do_open[2019-11-10T03:13:17.835Z] encode_chunked=req.has_header('Transfer-encoding'))[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/http/client.py", line 1254, in request[2019-11-10T03:13:17.835Z] self._send_request(method, url, body, headers, encode_chunked)[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/http/client.py", line 1300, in _send_request[2019-11-10T03:13:17.835Z] self.endheaders(body, encode_chunked=encode_chunked)[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/http/client.py", line 1249, in endheaders[2019-11-10T03:13:17.835Z] self._send_output(message_body, encode_chunked=encode_chunked)[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/http/client.py", line 1036, in _send_output[2019-11-10T03:13:17.835Z] self.send(msg)[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/http/client.py", line 974, in send[2019-11-10T03:13:17.835Z] self.connect()[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/http/client.py", line 1415, in connect[2019-11-10T03:13:17.835Z] server_hostname=server_hostname)[2019-11-10T03:13:17.835Z]   File "/usr/local/lib/python3.6/ssl.py", line 407, in 

KDE CI: Frameworks » kcoreaddons » kf5-qt5 FreeBSDQt5.13 - Build # 58 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.13/58/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:09:15 +
 Build duration:
1 hr 2 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 26 test(s), Skipped: 0 test(s), Total: 27 test(s)Failed: projectroot.autotests.kdirwatch_inotify_unittest

KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.12 - Build # 306 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.12/306/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 02:12:52 +
 Build duration:
58 min and counting
   BUILD ARTIFACTS
  acc/KF5KIO-5.65.0.xmllogs/KF5KIO/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 53 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report67%
(24/36)67%
(271/404)67%
(271/404)56%
(34814/61644)40%
(17621/43550)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(58/58)100%
(58/58)95%
(9656/10118)47%
(4500/9556)autotests.http100%
(5/5)100%
(5/5)99%
(581/582)68%
(108/160)autotests.kcookiejar100%
(1/1)100%
(1/1)91%
(179/197)72%
(49/68)src100%
(1/1)100%
(1/1)86%
(6/7)67%
(4/6)src.core89%
(104/117)89%
(104/117)60%
(8797/14545)52%
(4568/8831)src.core.kssl100%
(1/1)100%
(1/1)40%
(35/88)50%
(3/6)src.filewidgets68%
(26/38)68%
(26/38)56%
(4670/8289)43%
(2023/4745)src.gui100%
(2/2)100%
(2/2)94%
(102/108)74%
(49/66)src.ioslaves.file100%
(7/7)100%
(7/7)56%
(680/1208)40%
(386/954)src.ioslaves.file.kauth0%
(0/2)0%
(0/2)0%
(0/168)0%
(0/89)src.ioslaves.ftp100%
(2/2)100%
(2/2)47%
(644/1370)37%
(522/1414)src.ioslaves.help0%
(0/5)0%
(0/5)0%
(0/247)0%
(0/148)src.ioslaves.http88%
(7/8)88%
(7/8)42%
(1794/4291)36%
(1311/3636)src.ioslaves.http.kcookiejar40%
(2/5)40%
(2/5)47%
(631/1330)56%
(576/1027)src.ioslaves.remote100%
(2/2)100%
(2/2)27%
(73/267)8%
(14/184)src.ioslaves.remote.kdedmodule0%
(0/2)0%
(0/2)0%

KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.13 - Build # 175 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.13/175/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:12:52 +
 Build duration:
1 hr 20 min and counting
   JUnit Tests
  Name: projectroot Failed: 3 test(s), Passed: 49 test(s), Skipped: 0 test(s), Total: 52 test(s)Failed: projectroot.autotests.kiocore_kmountpointtestFailed: projectroot.autotests.kiowidgets_kdirlistertestFailed: projectroot.autotests.kiowidgets_kdirmodeltestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.12 - Build # 144 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20SUSEQt5.12/144/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 03:45:01 +
 Build duration:
4 min 1 sec and counting
   BUILD ARTIFACTS
  acc/KF5Purpose-5.65.0.xml
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report23%
(5/22)30%
(14/47)30%
(14/47)22%
(453/2036)18%
(170/939)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(2/2)100%
(2/2)98%
(143/146)57%
(52/92)src100%
(8/8)100%
(8/8)68%
(226/334)49%
(89/183)src.externalprocess0%
(0/2)0%
(0/2)0%
(0/137)0%
(0/98)src.fileitemactionplugin0%
(0/1)0%
(0/1)0%
(0/24)0%
(0/18)src.plugins.bluetooth0%
(0/1)0%
(0/1)0%
(0/33)0%
(0/8)src.plugins.email0%
(0/1)0%
(0/1)0%
(0/64)0%
(0/24)src.plugins.imgur0%
(0/2)0%
(0/2)0%
(0/184)0%
(0/63)src.plugins.kdeconnect0%
(0/1)0%
(0/1)0%
(0/31)0%
(0/6)src.plugins.kdeconnect_sms0%
(0/1)0%
(0/1)0%
(0/16)0%
(0/2)src.plugins.ktp-sendfile0%
(0/1)0%
(0/1)0%
(0/28)0%
(0/6)src.plugins.pastebin0%
(0/1)0%
(0/1)0%
(0/54)0%
(0/23)src.plugins.phabricator0%
(0/3)0%
(0/3)0%
(0/216)0%
(0/74)src.plugins.phabricator.quick0%
(0/5)0%
(0/5)0%
(0/93)0%
(0/48)src.plugins.phabricator.tests0%
(0/1)0%
(0/1)0%
(0/60)0%
(0/22)src.plugins.reviewboard0%
(0/3)0%
(0/3)0%
(0/229)0%
(0/70)src.plugins.reviewboard.quick0%
(0/7)0%
(0/7)0%
(0/153)0%
(0/80)src.plugins.saveas100%
(1/1)100%
(1/1)57%
(29/51)61%
(23/38)src.plugins.telegram0%
(0/1)0%

KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.13 - Build # 36 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.13/36/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Sun, 10 Nov 2019 01:37:44 +
 Build duration:
2 hr 10 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5Wayland-5.65.0.xmllogs/KF5Wayland/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 46 test(s), Skipped: 0 test(s), Total: 46 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report63%
(5/8)90%
(240/268)90%
(240/268)85%
(27187/32074)53%
(10946/20609)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.client100%
(43/43)100%
(43/43)99%
(12499/12573)50%
(6587/13095)autotests.server100%
(5/5)100%
(5/5)99%
(373/376)49%
(177/360)src.client96%
(73/76)96%
(73/76)85%
(6341/7481)64%
(1826/2836)src.compat100%
(2/2)100%
(2/2)100%
(81/81)100%
(0/0)src.server95%
(117/123)95%
(117/123)84%
(7893/9364)64%
(2356/3687)src.tools0%
(0/2)0%
(0/2)0%
(0/785)0%
(0/302)src.tools.testserver0%
(0/3)0%
(0/3)0%
(0/119)0%
(0/14)tests0%
(0/14)0%
(0/14)0%
(0/1295)0%
(0/315)

KDE CI: Frameworks » threadweaver » kf5-qt5 SUSEQt5.12 - Build # 48 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/threadweaver/job/kf5-qt5%20SUSEQt5.12/48/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 03:44:59 +
 Build duration:
4 min 8 sec and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5ThreadWeaver-5.65.0.xmlcompat_reports/KF5ThreadWeaver_compat_report.htmllogs/KF5ThreadWeaver/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report29%
(2/7)71%
(55/78)71%
(55/78)73%
(2447/3344)41%
(2484/6100)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(13/13)100%
(13/13)99%
(1226/1231)51%
(1748/3454)benchmarks0%
(0/1)0%
(0/1)0%
(0/125)0%
(0/60)examples.HelloInternet0%
(0/5)0%
(0/5)0%
(0/118)0%
(0/264)examples.HelloWorld0%
(0/1)0%
(0/1)0%
(0/3)100%
(0/0)examples.HelloWorldRaw0%
(0/1)0%
(0/1)0%
(0/13)100%
(0/0)examples.ThumbNailer0%
(0/14)0%
(0/14)0%
(0/458)0%
(0/880)src98%
(42/43)98%
(42/43)87%
(1221/1396)51%
(736/1442)

KDE CI: Frameworks » kpackage » kf5-qt5 FreeBSDQt5.13 - Build # 28 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kpackage/job/kf5-qt5%20FreeBSDQt5.13/28/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:18:06 +
 Build duration:
1 hr 28 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_packagestructuretest

KDE CI: Frameworks » kio » kf5-qt5 SUSEQt5.13 - Build # 190 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.13/190/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Sun, 10 Nov 2019 02:12:52 +
 Build duration:
1 hr 59 min and counting
   BUILD ARTIFACTS
  acc/KF5KIO-5.65.0.xmllogs/KF5KIO/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 52 test(s), Skipped: 0 test(s), Total: 53 test(s)Failed: projectroot.autotests.kiowidgets_kdirlistertestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report67%
(24/36)67%
(271/404)67%
(271/404)56%
(34802/61643)40%
(17594/43546)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(58/58)100%
(58/58)95%
(9643/10118)47%
(4474/9556)autotests.http100%
(5/5)100%
(5/5)99%
(581/582)68%
(108/160)autotests.kcookiejar100%
(1/1)100%
(1/1)91%
(179/197)72%
(49/68)src100%
(1/1)100%
(1/1)86%
(6/7)67%
(4/6)src.core89%
(104/117)89%
(104/117)60%
(8795/14545)52%
(4570/8831)src.core.kssl100%
(1/1)100%
(1/1)40%
(35/88)50%
(3/6)src.filewidgets68%
(26/38)68%
(26/38)56%
(4674/8288)43%
(2025/4741)src.gui100%
(2/2)100%
(2/2)94%
(102/108)74%
(49/66)src.ioslaves.file100%
(7/7)100%
(7/7)56%
(680/1208)40%
(386/954)src.ioslaves.file.kauth0%
(0/2)0%
(0/2)0%
(0/168)0%
(0/89)src.ioslaves.ftp100%
(2/2)100%
(2/2)47%
(644/1370)37%
(522/1414)src.ioslaves.help0%
(0/5)0%
(0/5)0%
(0/247)0%
(0/148)src.ioslaves.http88%
(7/8)88%
(7/8)42%
(1799/4291)36%
(1309/3636)src.ioslaves.http.kcookiejar40%
(2/5)40%
(2/5)47%
(631/1330)56%
(576/1027)src.ioslaves.remote100%
(2/2)100%
(2/2)27%
(73/267)8%
(14/184)src.ioslaves.remote.kdedmodule0%
(0/2)0%
   

KDE CI: Frameworks » solid » kf5-qt5 FreeBSDQt5.13 - Build # 36 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/solid/job/kf5-qt5%20FreeBSDQt5.13/36/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:38:39 +
 Build duration:
1 hr 32 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 4 test(s)Failed: projectroot.autotests.halbasictest

KDE CI: Frameworks » kdelibs4support » kf5-qt5 FreeBSDQt5.13 - Build # 42 - Still unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdelibs4support/job/kf5-qt5%20FreeBSDQt5.13/42/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 03:45:04 +
 Build duration:
38 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 39 test(s)Failed: projectroot.autotests.kmimetypetestFailed: projectroot.autotests.kstandarddirstest

D25123: [WIP] New yakuake logo/icon

[Nathaniel Graham]

ngraham added a comment.


  Agreed, C for me too.

REPOSITORY
  R266 Breeze Icons

REVISION DETAIL
  https://phabricator.kde.org/D25123

To: mglb, #vdg, #yakuake, hein
Cc: GB_2, ndavis, ognarb, ngraham, hein, kde-frameworks-devel, vmarinescu, 
ryanmccoskrie, LeGast00n, michaelh, bruns

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Albert Astals Cid]

El dissabte, 9 de novembre de 2019, a les 21:22:16 CET, Ben Cooksley va 
escriure:
> On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid  wrote:
> >
> > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va 
> > escriure:
> > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev  
> > > wrote:
> > > >
> > > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > > > This would include the shutdown of WebSVN in particular, which when
> > > > > coupled with the shutdown of our two CGit instances would also allow
> > > > > for us to eliminate an entire virtual machine from our systems.
> > > >
> > > > Will there be any web interface for SVN after shutdown of WebSVN?
> > > >
> > > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > > available during the next 10 years?
> > > >
> > >
> > > Phabricator's browser will be retired as part of the shutdown of
> > > Phabricator, which will take place once Gitlab has assumed
> > > responsibility for code hosting and review, and the tasks have been
> > > migrated from Phabricator.
> > >
> > > Should WebSVN be shutdown as well, then there would be no web
> > > interface to our SVN repository.
> >
> > That's not acceptable.
> 
> Mind explaining why?

Because we use it in l10n.kde.org to link to po files.

> Bear in mind that there is a cost both in terms of infrastructure, and
> people time to maintain a service such as WebSVN.

We have money, we don't have to shut down things we use because there is a cost.

Cheers,
  Albert

> This includes having to maintain a mirror of the repository on the
> machine that runs WebSVN, along with the associated infrastructure for
> allowing that mirroring to happen on the master server.
> 
> >
> > Cheers,
> >   Albert
> 
> Regards,
> Ben
> 
> >
> > >
> > > >
> > > > I'm not sure what use case Luigi has in mind, but among Russian l10n
> > > > team we often use WebSVN to refer to specific SVN revisions, for
> > > > example: https://websvn.kde.org/?view=revision=1555342
> > > >
> > > > --
> > > > Alexander Potashev
> > >
> > > Regards,
> > > Ben
> > >
> >
> >
> >
> >
> 

D25015: Update breeze theme shadows

[Noah Davis]

ndavis added a comment.


  In D25015#560516 , @cblack wrote:
  
  > In D25015#560515 , @ndavis wrote:
  >
  > > One thing we might need to do in order to finally stop changing the 
shadows is come up with a math based system for deciding how shadows should 
look based on the elevation we want certain UI elements to have. We could copy 
Material Design shadows, but I don't think we should. MD's shadows get darker 
the larger they are, but that's not how real shadows work. Real shadows get 
darker the smaller they are because light bounces around.
  >
  >
  > Material shadows get more voluminous, not darker.
  
  
  Well, they look darker, which still isn't realistic: 
https://material.io/design/environment/light-shadows.html#shadows

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D25015

To: niccolove, #vdg
Cc: cblack, ndavis, manueljlin, ngraham, filipf, kde-frameworks-devel, 
LeGast00n, GB_2, michaelh, bruns

19.12 releases branches created [*]

[Albert Astals Cid]

The branch naming has changed to try to accommodate for the stopping of the 
"KDE Applications" brand, it's now called
   release/19.12

Make sure you commit anything you want to end up in the 19.12 releases to them

We're already past the dependency freeze.

The Freeze and Beta is this Thursday 14 of November.

More interesting dates
 November 28, 2019: KDE Applications 19.12 RC (19.11.90) Tagging and Release
 December 5, 2019: KDE Applications 19.12 Tagging
 December 12, 2019: KDE Applications 19.12 Release

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

Cheers,
  Albert

P.S: Yes, this release unfortunately falls in the middle of the debranding of 
"KDE Applications" and there's still a few things called "KDE Applications" 
here and there

[*] There's a small issue with kwave we're working on figuring it out

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Ben Cooksley]

On Sun, Nov 10, 2019 at 11:47 AM Friedrich W. H. Kossebau
 wrote:
>
> Am Samstag, 9. November 2019, 21:22:16 CET schrieb Ben Cooksley:
> > On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid  wrote:
> > > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va
> escriure:
> > > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev
>  wrote:
> > > > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > > > > This would include the shutdown of WebSVN in particular, which when
> > > > > > coupled with the shutdown of our two CGit instances would also allow
> > > > > > for us to eliminate an entire virtual machine from our systems.
> > > > >
> > > > > Will there be any web interface for SVN after shutdown of WebSVN?
> > > > >
> > > > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > > > available during the next 10 years?
> > > >
> > > > Phabricator's browser will be retired as part of the shutdown of
> > > > Phabricator, which will take place once Gitlab has assumed
> > > > responsibility for code hosting and review, and the tasks have been
> > > > migrated from Phabricator.
> > > >
> > > > Should WebSVN be shutdown as well, then there would be no web
> > > > interface to our SVN repository.
> > >
> > > That's not acceptable.
> >
> > Mind explaining why?
>
> FWIW, everytime I had to deal with translations as developer (like checking
> pot files as well as .po files contents) I found having the web interface and
> its browsing feature very valuable to quickly find what I was looking for,
> over having to locally mess around with svn commands and juggling between
> commandline & file viewers. Including url bookmarks for quick access to
> browsing certain sets of files.
>
> Incidents which I remember right now included:
> * finding out whether extraction scripts were working as intended
> * comparing translations seen by users over what they should see
>
> Are there any other KDE clients of the svn repos still around, besides
> translation system?

The only other clients I am aware of are a small number of websites,
which can be found at /trunk/www/ in SVN.
The list of ones we serve can be found at
https://invent.kde.org/sysadmin/binary-factory-tooling/blob/master/staticweb/standard-jobs.yaml#L69

> Perhaps the "full clone" needed for WebSVN could be reduced to the translation
> subtrees, would that improve situation to a degree if possible? (well, you
> surely thought of this yourself, just in case)

Unfortunately WebSVN needs a full copy of the underlying repository to
be able to work.

>
> For me as developer contributor to projects in KDE spheres, losing the web
> browsing interface for raw translation files would be a regression in
> developer experience.
>
> Cheers
> Friedrich
>
>

Regards,
Ben

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Ben Cooksley]

On Sun, Nov 10, 2019 at 11:19 AM Albert Astals Cid  wrote:
>
> El dissabte, 9 de novembre de 2019, a les 21:22:16 CET, Ben Cooksley va 
> escriure:
> > On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid  wrote:
> > >
> > > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va 
> > > escriure:
> > > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev 
> > > >  wrote:
> > > > >
> > > > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > > > > This would include the shutdown of WebSVN in particular, which when
> > > > > > coupled with the shutdown of our two CGit instances would also allow
> > > > > > for us to eliminate an entire virtual machine from our systems.
> > > > >
> > > > > Will there be any web interface for SVN after shutdown of WebSVN?
> > > > >
> > > > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > > > available during the next 10 years?
> > > > >
> > > >
> > > > Phabricator's browser will be retired as part of the shutdown of
> > > > Phabricator, which will take place once Gitlab has assumed
> > > > responsibility for code hosting and review, and the tasks have been
> > > > migrated from Phabricator.
> > > >
> > > > Should WebSVN be shutdown as well, then there would be no web
> > > > interface to our SVN repository.
> > >
> > > That's not acceptable.
> >
> > Mind explaining why?
>
> Because we use it in l10n.kde.org to link to po files.

Mind detailing what those links are used for?

>
> > Bear in mind that there is a cost both in terms of infrastructure, and
> > people time to maintain a service such as WebSVN.
>
> We have money, we don't have to shut down things we use because there is a 
> cost.

I wasn't referring to monetary cost there, I was referring to the flow
on effects (such as having to maintain the necessary components on the
master server to allow for the Subversion repository to be mirrored).

Note also the "people time" component there.

>
> Cheers,
>   Albert

Thanks,
Ben

>
> > This includes having to maintain a mirror of the repository on the
> > machine that runs WebSVN, along with the associated infrastructure for
> > allowing that mirroring to happen on the master server.
> >
> > >
> > > Cheers,
> > >   Albert
> >
> > Regards,
> > Ben
> >
> > >
> > > >
> > > > >
> > > > > I'm not sure what use case Luigi has in mind, but among Russian l10n
> > > > > team we often use WebSVN to refer to specific SVN revisions, for
> > > > > example: https://websvn.kde.org/?view=revision=1555342
> > > > >
> > > > > --
> > > > > Alexander Potashev
> > > >
> > > > Regards,
> > > > Ben
> > > >
> > >
> > >
> > >
> > >
> >
>
>
>
>

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Alexander Potashev]

вс, 10 нояб. 2019 г. в 04:10, Ben Cooksley :
>
> On Sun, Nov 10, 2019 at 11:19 AM Albert Astals Cid  wrote:
> >
> > El dissabte, 9 de novembre de 2019, a les 21:22:16 CET, Ben Cooksley va 
> > escriure:
> > > On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid  wrote:
> > > >
> > > > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va 
> > > > escriure:
> > > > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev 
> > > > >  wrote:
> > > > > >
> > > > > > сб, 9 нояб. 2019 г. в 03:20, Ben Cooksley :
> > > > > > > This would include the shutdown of WebSVN in particular, which 
> > > > > > > when
> > > > > > > coupled with the shutdown of our two CGit instances would also 
> > > > > > > allow
> > > > > > > for us to eliminate an entire virtual machine from our systems.
> > > > > >
> > > > > > Will there be any web interface for SVN after shutdown of WebSVN?
> > > > > >
> > > > > > Can we assume https://phabricator.kde.org/source/svn/ remains
> > > > > > available during the next 10 years?
> > > > > >
> > > > >
> > > > > Phabricator's browser will be retired as part of the shutdown of
> > > > > Phabricator, which will take place once Gitlab has assumed
> > > > > responsibility for code hosting and review, and the tasks have been
> > > > > migrated from Phabricator.
> > > > >
> > > > > Should WebSVN be shutdown as well, then there would be no web
> > > > > interface to our SVN repository.
> > > >
> > > > That's not acceptable.
> > >
> > > Mind explaining why?
> >
> > Because we use it in l10n.kde.org to link to po files.
>
> Mind detailing what those links are used for?

A common workflow suggested for translators without SVN account
(and/or those who find it hard to use SVN) is as folllows:

 1. Go to https://l10n.kde.org/stats/gui/trunk-kf5/team/ru/ ("ru" for
Russian) and pick a .po translation file that needs update - e.g.
incomplete translation or one containing mistakes.

 2. Click on the .po file at l10n.kde.org to downloaded. WebSVN is
used for this.

 3. Edit the downloaded .po file, send for review, etc.


WebSVN is even mentioned in KDE's primary translation how-to:
https://l10n.kde.org/docs/translation-howto/gui-translation.html

-- 
Alexander Potashev

KDE Frameworks 5.64.0 released

[David Faure]

10th November 2019. KDE today announces the release of KDE Frameworks 5.64.0.

KDE Frameworks are 81 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https://kde.org/products/frameworks/


Attica

  Add some std::move in setter functions

Baloo

  Make it compile against qt5.15
  Use propertymap to store properties in Baloo::Result
  Add standalone conversion functions for PropertyMap to Json and vice versa
  [Database] Rework handling environment flags
  Replace recursion in FilteredDirIterator with loop iteration

Breeze Icons

  Center-align the non-square 64px audio mimetype icons (bug 393550)
  Delete remnants of nepomuk icon
  Move colorful 32px help-about icon into actions (bug 396626)
  Improve draw icons (bug 399665)
  Delete nepomuk icon
  Fill middle mouse button area
  Add folder-recent, extend hand of clock in folder-temp
  Use a more correct and appropriate visual metaphor for "get hot new stuff" 
icon (bug 400500)
  Update elisa icon
  Use css instead of scss as output format
  Fix incorrect rendering of 22px edit-opacity icon
  Add edit-opacity icons (bug 408283)
  Icons for windy weather (bug 412718)
  Fix incorrect margins in 16/22px media icons
  Use the text rather than highlight color for rating/star emblem
  Add draw-arrow icons (bug 408283)
  Add draw-highlight action icons (bug 408283)
  Add PATH/LD_LIBRARY_PATH to qrcAlias invocation
  Add applications-network icon for renaming Internet category to Network
  Add edit-line-width icons (bug 408283)

Extra CMake Modules

  Don't set C/C++ standards if already set
  Use modern way to set the C/CXX standad
  Raise CMake requirements to 3.5
  ECMAddQch: support PREDEFINED_MACROS/BLANK_MACROS with blanks & quotes

Framework Integration

  Add standard icons to support to all entries in QDialogButtonBox (bug 398973)
  ensure winId() not called on non-native widgets (bug 412675)

KActivitiesStats

  tests: fix macos build failure
  Windows MSVC compile fix
  Add a utility accessor to get a QUrl from a ResultSet::Result

KArchive

  Fix memory leak in KXzFilter::init
  Fix null pointer reference when extraction fails
  decodeBCJ2: Fix assert with broken files
  KXzFilter::Private: remove unused props
  K7Zip: Fix memory use in readAndDecodePackedStreams

KCalendarCore #

  Add libical version too
  Explicitly define the Journal copy ctor

KCMUtils

  Conditionally show navigation buttons in the header for multi-page KCMs
  don't use a custom header height (bug 404396)
  add extra include
  Fix memory leak of KQuickAddons::ConfigModule objects (bug 412998)
  [KCModuleLoader] Show error when QML fails to load

KConfig

  kconfig_compiler: Move the KSharedConfig::Ptr when using them
  Make it compile against qt5.15 without deprecated method
  Expose isImmutable to introspection (e.g. QML)
  Add convenience for defaults/dirty states to KCoreConfigSkeleton
  Make kconfig_compiler generate ctors with the optional parent arg
  Make preferences() a public function

KConfigWidgets

  Avoid overloading KCModule::changed

KContacts

  Install translations

KCoreAddons

  KProcessInfoList -- add proclist backend for FreeBSD

KDeclarative

  Use compile time checked connect
  Make the settingChanged() slot protected
  Get KQuickAddons::ConfigModule to expose if we're in the defaults state
  Grab the keyboard when KeySequenceItem is recording
  Add ManagedConfigModule
  Remove outdated comment about [$e] expansion
  [ConfigModule] Expose mainUi component status and error string

KDELibs 4 Support

  KLocale api docs: make it easier to find how to port code away from it

KDocTools

  man: use  instead of 

KFileMetaData

  Fix crash in writer collection and cleanup

KHTML

  Extend KHtmlView::print() to use a predefined QPrinter instance (bug 405011)

KI18n

  Add KLocalizedString::untranslatedText
  Replace all qWarning and related calls with categorised logging

KIconThemes

  Fix usage of the new deprecation macros for assignIconsToContextMenu
  Deprecate KIconTheme::assignIconsToContextMenu

KIO

  Const & signature of new introduced SlaveBase::configValue
  Port to the QSslError variant of KSslInfoDialog
  Port KSSLD internals from KSslError to QSslError
  Make non-ignorable SSL errors explicit
  auto-enable KIO_ASSERT_SLAVE_STATES also for from-git builds
  Port (most of) KSslInfoDialog from KSslError to QSslError
  kio_http: avoid double Content-Type and Depth when used by KDAV
  Port the KSSLD D-Bus interface from KSslError to QSslError
  Replace usage of SlaveBase::config()->readEntry by SlaveBase::configValue
  Remove two unused member variables using KSslError
  Avoid sending KDirNotify::emitFilesAdded when the emptytrashjob finishes
  Deprecate the KTcpSocket-based variant of SslUi::askIgnoreSslErrors
  Treat "application/x-ms-dos-executable" as executable on all platforms (bug 
412694)
  Replace usage of 

KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.12 - Build # 79 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.12/79/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 01:37:44 +
 Build duration:
26 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5Wayland-5.64.0.xmllogs/KF5Wayland/5.64.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 46 test(s), Skipped: 0 test(s), Total: 46 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report63%
(5/8)90%
(240/268)90%
(240/268)85%
(27190/32074)53%
(10951/20609)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.client100%
(43/43)100%
(43/43)99%
(12499/12573)50%
(6589/13095)autotests.server100%
(5/5)100%
(5/5)99%
(373/376)49%
(177/360)src.client96%
(73/76)96%
(73/76)85%
(6344/7481)64%
(1829/2836)src.compat100%
(2/2)100%
(2/2)100%
(81/81)100%
(0/0)src.server95%
(117/123)95%
(117/123)84%
(7893/9364)64%
(2356/3687)src.tools0%
(0/2)0%
(0/2)0%
(0/785)0%
(0/302)src.tools.testserver0%
(0/3)0%
(0/3)0%
(0/119)0%
(0/14)tests0%
(0/14)0%
(0/14)0%
(0/1295)0%
(0/315)

KDE CI: Frameworks » kdesu » kf5-qt5 FreeBSDQt5.13 - Build # 20 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdesu/job/kf5-qt5%20FreeBSDQt5.13/20/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:30:26 +
 Build duration:
33 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 0 test(s), Skipped: 0 test(s), Total: 1 test(s)Failed: projectroot.autotests.kdesutest

KDE CI: Frameworks » kdelibs4support » kf5-qt5 FreeBSDQt5.13 - Build # 40 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdelibs4support/job/kf5-qt5%20FreeBSDQt5.13/40/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:30:06 +
 Build duration:
34 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 39 test(s)Failed: projectroot.autotests.kmimetypetestFailed: projectroot.autotests.kstandarddirstest

KDE CI: Frameworks » kimageformats » kf5-qt5 FreeBSDQt5.13 - Build # 20 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kimageformats/job/kf5-qt5%20FreeBSDQt5.13/20/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:32:52 +
 Build duration:
39 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 13 test(s), Skipped: 0 test(s), Total: 14 test(s)Failed: projectroot.autotests.kimageformats_read_hdr

KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.13 - Build # 32 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.13/32/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:37:44 +
 Build duration:
58 min and counting
   JUnit Tests
  Name: projectroot.autotests Failed: 15 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 42 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testRemoteAccessFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.client.kwayland_testWindowmanagementFailed: projectroot.autotests.client.kwayland_testXdgShellStableFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay

Re: Notice of intention to remove tests from KCrash and KNotifications

[Ben Cooksley]

On Thu, Nov 7, 2019 at 1:18 AM Harald Sitter  wrote:
>
> On Wed, Nov 6, 2019 at 8:07 AM Ben Cooksley  wrote:
> >
> > On Tue, Nov 5, 2019 at 11:50 PM Harald Sitter  wrote:
> > >
> > > I get where you are coming from, but honestly, none of this makes
> > > pushing unreviewed commits that disable the entire test collection of
> > > an entire framework any more correct. If it had only affected the one
> > > test I wouldn't mind so much, but since it hasn't it only goes to
> > > proof that we have reviews for a reason. In particular for repos that
> > > are part of frameworks where we rely on tests to tell us if the
> > > frameworks are good for the monthly release.
> >
> > Unfortunately reviews require responsive developers.
> >
> > In this instance, both Frameworks have been found to have developers
> > which are not responsive (because my previous requests have been
> > ignored), so sending a patch for review would have been pointless -
> > because there would have been nobody to review it.
> >
> > Therefore bypassing review and taking any necessary action against the
> > offending code (even if that does happen to be all of the tests) to
> > correct the situation is the only viable option forward.
>
> This is really not true.
> We got the workaround for KCrash landed in not even half a business
> day - including review.
>

Unfortunately it is certainly my perception - which is based off of my
emails on the subject not receiving any response.
This experience is one that hasn't only happened with Frameworks - it
has also happened (several times) with PIM.

Taking direct action against a project is pretty much guaranteed to
trigger a fairly rapid response (which is exactly what happened in
this case).

It should be noted that saying i'm going to take action usually
results in either no response, or a response along the lines of "no,
you can't do that" rather than the issue actually being addressed
(which once again, is what happened in this case too)


> > > There are many shades of grey between sending a "someone please fix"
> > > mail to a mailing list and the nuclear option you implemented. The
> > > most notable one being that you can ask someone who worked on the
> > > repo, or tests recently "Hey, X, can you please disable the test on
> > > windows because its impairing CI?" to which the answer is probably yes
> > > because you'd not only address a very specific person but also the
> > > task is doable in less than 5 minutes.
> > > I understand that there's an element of cat herding in this, but
> > > quality must matter for our products, and the quality of frameworks is
> > > very tightly linked to autotesting and reviews because of how we
> > > release them.
> >
> > This would require spending more time on the issue, which is something
> > i'd very much rather avoid.
> >
> > It is expensive enough having to login to the CI builders to clear out
> > these jobs when they get stuck (looking at anything that uses Akonadi
> > especially here, along with these two Frameworks) and then asking the
> > project lists to please fix their faulty code (which is then ignored,
> > indicating that the concept of community maintained does not really
> > work).
> >
> > Having to then lookup someone and then forward it on to them requires
> > yet more time, with no guarantee that it will work - especially
> > because some contributors are still hostile to any platform that is
> > not FOSS and outright refuse to do anything to help those platforms.
> >
> > In the event that it does not work - then what would I do? Pick on the
> > next person in the list (requiring yet more time)?
> >
> > Sorry, but that is simply too expensive, and if that is the policy
> > you'd like to run with, then i'll stick to stripping projects of their
> > test execution privileges outright across all platforms in the event
> > they cause issues like this (which if ECM is anything to go by, is
> > something people won't even notice even if the commit that puts that
> > in effect is CC'ed to the project mailing list, which means that
> > nobody will notice when the tests break because the CI system won't be
> > running them)
>
> I did not express myself well enough.
> What I'd like you to do is talk to someone, not anyone, a very
> specific someone of your choosing, to take care of the issue for you.
> IOW: The sysadmins should delegate to a developer if the sysadmins
> find themselves unable to accurately deal with a code problem (such as
> a failing test that needs deactivating). If you tell an actually
> relevant developer that's obviously better, if you don't have time to
> look at the git log then that's fine too.
>
> There are two different work items to differentiate here:
>
> 1. fixing something
> 2. disabling something because a fix was not made in an acceptable time frame
>
> 1 likely requires domain-knowledge of the specific framework and
> probably quit a bit of time.
> 2 would generally only require understanding of cmake and a fairly

KDE CI: Frameworks » kguiaddons » kf5-qt5 FreeBSDQt5.13 - Build # 22 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/kguiaddons/job/kf5-qt5%20FreeBSDQt5.13/22/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:11:42 +
 Build duration:
1 hr 10 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)
   CONSOLE OUTPUT
  [...truncated 504 lines...][2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/KDateValidator[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/KWordWrap[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/kdatevalidator.h[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/kwordwrap.h[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/KFontUtils[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/kfontutils.h[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/KIconUtils[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/KImageCache[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/KModifierKeyInfo[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/kiconutils.h[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/kimagecache.h[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/include/KF5/KGuiAddons/kmodifierkeyinfo.h[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/share/doc/qch/KF5GuiAddons.qch[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/share/doc/qch/KF5GuiAddons.tags[2019-11-10T03:22:07.521Z] -- Installing: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/install-divert/home/jenkins/install-prefix/mkspecs/modules/qt_KGuiAddons.pri[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Running Tests)[Pipeline] sh[2019-11-10T03:22:08.528Z] + python3 -u ci-tooling/helpers/run-tests.py --product Frameworks --project kguiaddons --branchGroup kf5-qt5 --platform FreeBSDQt5.13 --usingInstall /home/jenkins/install-prefix/[2019-11-10T03:22:08.787Z] No matching processes belonging to you were found[2019-11-10T03:22:15.338Z] /bin/sh: kdeinit5: not found[2019-11-10T03:22:19.509Z] Cannot find file: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/build/DartConfiguration.tcl[2019-11-10T03:22:19.509Z]Site: [2019-11-10T03:22:19.509Z]Build name: (empty)[2019-11-10T03:22:19.509Z] Create new tag: 20191109-1051 - Experimental[2019-11-10T03:22:19.509Z] Cannot find file: /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/build/DartConfiguration.tcl[2019-11-10T03:22:19.509Z] Test project /usr/home/jenkins/workspace/Frameworks/kguiaddons/kf5-qt5 FreeBSDQt5.13/build[2019-11-10T03:22:19.509Z] Start 1: kwordwraptest[2019-11-10T03:22:19.509Z] 1/3 Test #1: kwordwraptest    Passed0.05 sec[2019-11-10T03:22:19.509Z] Start 2: kcolorutilstest[2019-11-10T03:22:19.765Z] 2/3 Test #2: kcolorutilstest ..   Passed0.36 sec[2019-11-10T03:22:19.765Z] Start 3: kiconutilstest[2019-11-10T03:22:19.765Z] 3/3 Test #3: kiconutilstest ...   Passed0.04 sec[2019-11-10T03:22:19.765Z] [2019-11-10T03:22:19.765Z] 100% tests passed, 0 tests failed out of 3[2019-11-10T03:22:19.765Z] [2019-11-10T03:22:19.765Z] Total Test time (real) =   0.44 sec[2019-11-10T03:22:19.765Z] XIO:  fatal IO error 4 (Interrupted

KDE CI: Frameworks » threadweaver » kf5-qt5 SUSEQt5.12 - Build # 47 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/threadweaver/job/kf5-qt5%20SUSEQt5.12/47/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 02:19:53 +
 Build duration:
1 hr 2 min and counting
   CONSOLE OUTPUT
  [...truncated 80 lines...][2019-11-10T03:22:04.731Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:04.791Z]  > git config remote.origin.url https://anongit.kde.org/kde-build-metadata # timeout=10[2019-11-10T03:22:04.812Z] Fetching upstream changes from https://anongit.kde.org/kde-build-metadata[2019-11-10T03:22:04.812Z]  > git fetch --tags --force --progress -- https://anongit.kde.org/kde-build-metadata +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:04.972Z]  > git rev-parse origin/master^{commit} # timeout=10[2019-11-10T03:22:04.990Z]  > git config core.sparsecheckout # timeout=10[2019-11-10T03:22:05.007Z]  > git checkout -f ea1bcfbb32bb0a7a7aa9a70c5d31c34b7d9fbd11 # timeout=10[Pipeline] checkout[2019-11-10T03:22:05.383Z] No credentials specified[2019-11-10T03:22:05.386Z] Cloning the remote Git repository[2019-11-10T03:22:06.301Z] Checking out Revision f73dbc2057cf62155fd499ce3a79ec06849e33f2 (origin/master)[2019-11-10T03:22:06.325Z] Commit message: "GIT_SILENT Upgrade KF5 version to 5.65.0."[2019-11-10T03:22:05.388Z] Cloning repository https://anongit.kde.org/kapidox[2019-11-10T03:22:05.388Z]  > git init /home/jenkins/workspace/Frameworks/threadweaver/kf5-qt5 SUSEQt5.12/ci-tooling/kapidox # timeout=10[2019-11-10T03:22:05.470Z] Fetching upstream changes from https://anongit.kde.org/kapidox[2019-11-10T03:22:05.471Z]  > git --version # timeout=10[2019-11-10T03:22:05.503Z]  > git fetch --tags --force --progress -- https://anongit.kde.org/kapidox +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:06.111Z]  > git config remote.origin.url https://anongit.kde.org/kapidox # timeout=10[2019-11-10T03:22:06.113Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:06.119Z]  > git config remote.origin.url https://anongit.kde.org/kapidox # timeout=10[2019-11-10T03:22:06.124Z] Fetching upstream changes from https://anongit.kde.org/kapidox[2019-11-10T03:22:06.124Z]  > git fetch --tags --force --progress -- https://anongit.kde.org/kapidox +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:06.297Z]  > git rev-parse origin/master^{commit} # timeout=10[2019-11-10T03:22:06.302Z]  > git config core.sparsecheckout # timeout=10[2019-11-10T03:22:06.304Z]  > git checkout -f f73dbc2057cf62155fd499ce3a79ec06849e33f2 # timeout=10[Pipeline] checkout[2019-11-10T03:22:07.148Z] No credentials specified[2019-11-10T03:22:07.150Z] Cloning the remote Git repository[2019-11-10T03:22:07.151Z] Cloning repository https://anongit.kde.org/kde-dev-scripts[2019-11-10T03:22:07.151Z]  > git init /home/jenkins/workspace/Frameworks/threadweaver/kf5-qt5 SUSEQt5.12/ci-tooling/kde-dev-scripts # timeout=10[2019-11-10T03:22:07.154Z] Fetching upstream changes from https://anongit.kde.org/kde-dev-scripts[2019-11-10T03:22:07.154Z]  > git --version # timeout=10[2019-11-10T03:22:07.157Z]  > git fetch --tags --force --progress -- https://anongit.kde.org/kde-dev-scripts +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:08.517Z] Checking out Revision 7db3c74d0335682a78bbcb741325004b36a68a90 (origin/master)[2019-11-10T03:22:08.548Z] Commit message: "Merge remote-tracking branch 'origin/Applications/19.08'"[Pipeline] }[Pipeline] // stage[2019-11-10T03:22:08.315Z]  > git config remote.origin.url https://anongit.kde.org/kde-dev-scripts # timeout=10[2019-11-10T03:22:08.316Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:08.321Z]  > git config remote.origin.url https://anongit.kde.org/kde-dev-scripts # timeout=10[2019-11-10T03:22:08.325Z] Fetching upstream changes from https://anongit.kde.org/kde-dev-scripts[2019-11-10T03:22:08.326Z]  > git fetch --tags --force --progress -- https://anongit.kde.org/kde-dev-scripts +refs/heads/*:refs/remotes/origin/* # timeout=10[2019-11-10T03:22:08.512Z]  > git rev-parse origin/master^{commit} # timeout=10[2019-11-10T03:22:08.518Z]  > git config core.sparsecheckout # timeout=10[2019-11-10T03:22:08.521Z]  > git checkout -f 7db3c74d0335682a78bbcb741325004b36a68a90 # timeout=10[Pipeline] stage[Pipeline] { (Setup Dependencies)[Pipeline] sh[2019-11-10T03:22:10.082Z] + python3 -u ci-tooling/helpers/prepare-dependencies.py --product Frameworks --project threadweaver --branchGroup kf5-qt5 --environment production --platform SUSEQt5.12 --installTo /home/jenkins//install-prefix/[2019-11-10T03:22:11.974Z] Traceback (most recent call last):[2019-11-10T03:22:11.974Z]   File "/usr/lib64/python3.7/urllib/request.py", line 1317, in do_open[2019-11-10T03:22:11.974Z] 

KDE CI: Frameworks » networkmanager-qt » kf5-qt5 SUSEQt5.12 - Build # 61 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/networkmanager-qt/job/kf5-qt5%20SUSEQt5.12/61/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 02:18:08 +
 Build duration:
1 hr 3 min and counting
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)
   CONSOLE OUTPUT
  [...truncated 1262 lines...][2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/tundevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/utils.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/vethdevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/vlandevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/vpnconnection.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/vpnplugin.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/wimaxdevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/wimaxnsp.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/wireddevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/wirelessdevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/wirelessnetwork.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/wireguarddevice.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/adslsetting.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/bluetoothsetting.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/bondsetting.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/bridgesetting.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/bridgeportsetting.h[2019-11-10T03:22:03.183Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/cdmasetting.h[2019-11-10T03:22:03.184Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/connectionsettings.h[2019-11-10T03:22:03.184Z] -- Installing: /home/jenkins/workspace/Frameworks/networkmanager-qt/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/include/KF5/NetworkManagerQt/networkmanagerqt/gsmsetting.h[2019-11-10T03:22:03.184Z] -- 

KDE CI: Frameworks » purpose » kf5-qt5 SUSEQt5.12 - Build # 143 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/purpose/job/kf5-qt5%20SUSEQt5.12/143/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 02:18:53 +
 Build duration:
1 hr 3 min and counting
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)
   CONSOLE OUTPUT
  [...truncated 741 lines...][2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/plugins/kf5/purpose/reviewboardplugin.so[2019-11-10T03:21:38.190Z] -- Set runtime path of "/home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert//home/jenkins/install-prefix/lib64/plugins/kf5/purpose/reviewboardplugin.so" to "/home/jenkins/install-prefix/lib64"[2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/share/purpose/reviewboardplugin_config.qml[2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/libReviewboardHelpers.so.5.65.0[2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/libReviewboardHelpers.so.5[2019-11-10T03:21:38.190Z] -- Set runtime path of "/home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert//home/jenkins/install-prefix/lib64/libReviewboardHelpers.so.5.65.0" to "/home/jenkins/install-prefix/lib64"[2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/qml/org/kde/purpose/reviewboard/librbpurposequickplugin.so[2019-11-10T03:21:38.190Z] -- Set runtime path of "/home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert//home/jenkins/install-prefix/lib64/qml/org/kde/purpose/reviewboard/librbpurposequickplugin.so" to "/home/jenkins/install-prefix/lib64"[2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/qml/org/kde/purpose/reviewboard/qmldir[2019-11-10T03:21:38.190Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/share/icons/hicolor/16x16/apps/reviewboard-purpose.png[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/share/icons/hicolor/128x128/apps/reviewboard-purpose.png[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/plugins/kf5/purpose/phabricatorplugin.so[2019-11-10T03:21:38.269Z] -- Set runtime path of "/home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert//home/jenkins/install-prefix/lib64/plugins/kf5/purpose/phabricatorplugin.so" to "/home/jenkins/install-prefix/lib64"[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/share/purpose/phabricatorplugin_config.qml[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/libPhabricatorHelpers.so.5.65.0[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/libPhabricatorHelpers.so.5[2019-11-10T03:21:38.269Z] -- Set runtime path of "/home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert//home/jenkins/install-prefix/lib64/libPhabricatorHelpers.so.5.65.0" to "/home/jenkins/install-prefix/lib64"[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/qml/org/kde/purpose/phabricator/libphabricatorquickplugin.so[2019-11-10T03:21:38.269Z] -- Set runtime path of "/home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert//home/jenkins/install-prefix/lib64/qml/org/kde/purpose/phabricator/libphabricatorquickplugin.so" to "/home/jenkins/install-prefix/lib64"[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/lib64/qml/org/kde/purpose/phabricator/qmldir[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 SUSEQt5.12/install-divert/home/jenkins/install-prefix/share/icons/hicolor/16x16/apps/phabricator-purpose.png[2019-11-10T03:21:38.269Z] -- Installing: /home/jenkins/workspace/Frameworks/purpose/kf5-qt5 

KDE CI: Frameworks » kpty » kf5-qt5 FreeBSDQt5.13 - Build # 20 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kpty/job/kf5-qt5%20FreeBSDQt5.13/20/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:20:40 +
 Build duration:
1 hr 33 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 0 test(s), Skipped: 0 test(s), Total: 1 test(s)Failed: projectroot.autotests.kptyprocesstest

KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.13 - Build # 37 - Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.13/37/
 Project:
kf5-qt5 SUSEQt5.13
 Date of build:
Sun, 10 Nov 2019 03:48:28 +
 Build duration:
1 hr 14 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5Wayland-5.65.0.xmllogs/KF5Wayland/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.autotests Failed: 2 test(s), Passed: 44 test(s), Skipped: 0 test(s), Total: 46 test(s)Failed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testWaylandSeat
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report63%
(5/8)90%
(240/268)90%
(240/268)84%
(27005/32072)53%
(10823/20609)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.client100%
(43/43)100%
(43/43)98%
(12350/12574)50%
(6483/13095)autotests.server100%
(5/5)100%
(5/5)99%
(373/376)49%
(177/360)src.client96%
(73/76)96%
(73/76)85%
(6336/7480)64%
(1827/2836)src.compat100%
(2/2)100%
(2/2)100%
(81/81)100%
(0/0)src.server95%
(117/123)95%
(117/123)84%
(7865/9362)63%
(2336/3687)src.tools0%
(0/2)0%
(0/2)0%
(0/785)0%
(0/302)src.tools.testserver0%
(0/3)0%
(0/3)0%
(0/119)0%
(0/14)tests0%
(0/14)0%
(0/14)0%
(0/1295)0%
(0/315)

Re: kde-devel mailing list archive

[Albert Astals Cid]

El dissabte, 9 de novembre de 2019, a les 23:45:30 CET, Alexander Potashev va 
escriure:
> Hi,
> 
> How do I access kde-devel mailing list archive?

https://marc.info/?l=kde-devel=1=2

Cheers,
  Albert

> 
> The archive linked at https://mail.kde.org/mailman/listinfo/kde-devel
> appears empty.
> 
> 

Re: Sysadmin Load Reduction: Subversion Infrastructure

[Nicolás Alvarez]

El sáb., 9 de nov. de 2019 a la(s) 19:48, Friedrich W. H. Kossebau
(kosse...@kde.org) escribió:
> FWIW, everytime I had to deal with translations as developer (like checking
> pot files as well as .po files contents) I found having the web interface and
> its browsing feature very valuable to quickly find what I was looking for,
> over having to locally mess around with svn commands and juggling between
> commandline & file viewers. Including url bookmarks for quick access to
> browsing certain sets of files.
>
> Incidents which I remember right now included:
> * finding out whether extraction scripts were working as intended
> * comparing translations seen by users over what they should see
>
> Are there any other KDE clients of the svn repos still around, besides
> translation system?
> Perhaps the "full clone" needed for WebSVN could be reduced to the translation
> subtrees, would that improve situation to a degree if possible? (well, you
> surely thought of this yourself, just in case)

This is unfortunately not possible. WebSVN needs a full copy of the
repository with its history, not a svn checkout, and that can't be
trimmed to a subtree. Or maybe you *can* extract a subtree, but then
you can't keep that in sync with new changes that appear in the master
repository. Even in git that's a giant pain.

-- 
Nicolás

Re: 19.12 releases branches created [*]

[Albert Astals Cid]

El diumenge, 10 de novembre de 2019, a les 1:28:30 CET, Albert Astals Cid va 
escriure:
> The branch naming has changed to try to accommodate for the stopping of the 
> "KDE Applications" brand, it's now called
>release/19.12
> 
> Make sure you commit anything you want to end up in the 19.12 releases to them
> 
> We're already past the dependency freeze.
> 
> The Freeze and Beta is this Thursday 14 of November.
> 
> More interesting dates
>  November 28, 2019: KDE Applications 19.12 RC (19.11.90) Tagging and Release
>  December 5, 2019: KDE Applications 19.12 Tagging
>  December 12, 2019: KDE Applications 19.12 Release
> 
> https://community.kde.org/Schedules/Applications/19.08_Release_Schedule

https://community.kde.org/Schedules/Applications/19.12_Release_Schedule 
obviously ^_^

Cheers,
  Albert

> 
> Cheers,
>   Albert
> 
> P.S: Yes, this release unfortunately falls in the middle of the debranding of 
> "KDE Applications" and there's still a few things called "KDE Applications" 
> here and there
> 
> [*] There's a small issue with kwave we're working on figuring it out
> 
> 
> 

Re: Sysadmin Load Reduction: Code Related Services

[Ben Cooksley]

On Sun, Nov 10, 2019 at 1:24 PM Albert Astals Cid  wrote:
>
> El diumenge, 10 de novembre de 2019, a les 1:04:04 CET, Ben Cooksley va 
> escriure:
> > On Sun, Nov 10, 2019 at 11:22 AM Albert Astals Cid  wrote:
> > >
> > > El dissabte, 9 de novembre de 2019, a les 21:52:13 CET, Ben Cooksley va 
> > > escriure:
> > > > On Sun, Nov 10, 2019 at 8:43 AM Albert Astals Cid  wrote:
> > > > >
> > > > > El dissabte, 9 de novembre de 2019, a les 18:47:57 CET, Ben Cooksley 
> > > > > va escriure:
> > > > > > On Sun, Nov 10, 2019 at 12:29 AM Luigi Toscano 
> > > > > >  wrote:
> > > > > > >
> > > > > > > Ben Cooksley ha scritto:
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > In the category of code related services, Sysadmin currently 
> > > > > > > > supports
> > > > > > > > a wide-ranging number of services (which makes sense given the 
> > > > > > > > nature
> > > > > > > > of the community). Some of these however may no longer be in 
> > > > > > > > use or
> > > > > > > > will be duplicative of other services following the transition 
> > > > > > > > to
> > > > > > > > Gitlab.
> > > > > > > >
> > > > > > > > In the category of duplicative, we have our two CGit instances 
> > > > > > > > at
> > > > > > > > cgit.kde.org and packaging.neon.kde.org. Prior to Gitlab, these 
> > > > > > > > were
> > > > > > > > justifiable as there was no other way of browsing scratch/clone
> > > > > > > > repositories over the web.
> > > > > > > >
> > > > > > > > With the migration to Gitlab however all repositories will 
> > > > > > > > become
> > > > > > > > browsable through it, meaning it no longer makes sense to offer 
> > > > > > > > two
> > > > > > > > browsers that provide the exact same information (with Gitlab 
> > > > > > > > having
> > > > > > > > greater capabilities). I'd therefore like to shut both of these 
> > > > > > > > down
> > > > > > > > once Code Hosting has transitioned to Gitlab.
> > > > > > >
> > > > > > > Luckily we tried to use commits.kde.org as generic redirect. Will 
> > > > > > > the generic
> > > > > > > redirect commits.kde.org be updated to point to the proper 
> > > > > > > repository? It may
> > > > > > > be complicated if the new structure contains the namespaces for 
> > > > > > > each
> > > > > > > repository, but we need to keep it working.
> > > > > >
> > > > > > The commits.kde.org redirector is intended to provide permanent 
> > > > > > links,
> > > > > > so yes it will be updated to redirect people to Gitlab instead once
> > > > > > the switch to Gitlab is completed.
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > In the category of no longer in use, we have the compatibility
> > > > > > > > generator for the kde_projects.xml file. This was introduced 
> > > > > > > > when we
> > > > > > > > shutdown Redmine/Chiliproject and migrated to Phabricator, as a 
> > > > > > > > way of
> > > > > > > > keeping services that needed to discover a list of KDE Projects
> > > > > > > > functional.
> > > > > > > >
> > > > > > > > As we've since migrated to using YAML files within the
> > > > > > > > sysadmin/repo-metadata repository for both the CI System and
> > > > > > > > kdesrc-build (and with LXR using kdesrc-build to do it's code
> > > > > > > > checkouts) there shouldn't to my knowledge be anything still 
> > > > > > > > relying
> > > > > > > > on this (aside from perhaps scripty).>
> > > > > > > > I'd therefore like to shut this generator down as well, along 
> > > > > > > > with the
> > > > > > > > compaibility redirector running at projects.kde.org (given that 
> > > > > > > > it has
> > > > > > > > been some time since we were using that site, and many projects 
> > > > > > > > have
> > > > > > > > moved around in the virtual structure since then, making the 
> > > > > > > > redirects
> > > > > > > > it is able to offer useless)
> > > > > > >
> > > > > > > Two points:
> > > > > > > - scripty still uses the XML file and we may need some time to 
> > > > > > > migrate.
> > > > > >
> > > > > > I feared this may have been the case. What sort of timeline are we
> > > > > > looking at in terms of switching scripty over?
> > > > >
> > > > > Over to what?
> > > >
> > > > To using the YAML files within sysadmin/repo-metadata, which is what
> > > > the legacy kde_projects.xml file is generated from currently.
> > >
> > > Well, someone has to change the code that parses the xml to code that 
> > > gets stuff from git and parses yaml, it's not hard, but has to be done.
> >
> > *nod*
> >
> > I do recall that at one point in our conversations that scripty only
> > used the kde_projects.xml file as a check against it's own internal
> > data.
>
> Yes and no, we have our i18n branch data hardcoded, but we don't have a list 
> of repos, so we need the list of repos from somewhere (and we use the branch 
> data from kde_projects.xml to compare it to our hardcoded one to see if 
> there's some mismatch).
>

Thanks for confirming how that is used.

> Cheers,
>   Albert
>

Cheers,
Ben

> > Has that 

KDE CI: Frameworks » kcoreaddons » kf5-qt5 FreeBSDQt5.13 - Build # 57 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.13/57/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:29:13 +
 Build duration:
31 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 26 test(s), Skipped: 0 test(s), Total: 27 test(s)Failed: projectroot.autotests.kdirwatch_inotify_unittest

KDE CI: Frameworks » kpackage » kf5-qt5 FreeBSDQt5.13 - Build # 27 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kpackage/job/kf5-qt5%20FreeBSDQt5.13/27/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 01:35:25 +
 Build duration:
42 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_packagestructuretest

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.13 - Build # 25 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.13/25/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:08:01 +
 Build duration:
58 min and counting
   JUnit Tests
  Name: projectroot Failed: 457 test(s), Passed: 35 test(s), Skipped: 0 test(s), Total: 492 test(s)Failed: projectroot.autotests.Compat_libical3_AppleICal_1.5.icsFailed: projectroot.autotests.Compat_libical3_Evolution_2.8.2_timezone_test.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.1.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.1a.icsFailed: projectroot.autotests.Compat_libical3_KOrganizer_3.2.icsFailed: projectroot.autotests.Compat_libical3_MSExchange.icsFailed: projectroot.autotests.Compat_libical3_Mozilla_1.0.icsFailed: projectroot.autotests.Compat_libical3_Todos.icsFailed: projectroot.autotests.Compat_libical3_eGroupware.icsFailed: projectroot.autotests.RecurNext_ConnectDaily1.icsFailed: projectroot.autotests.RecurNext_ConnectDaily10.icsFailed: projectroot.autotests.RecurNext_ConnectDaily11.icsFailed: projectroot.autotests.RecurNext_ConnectDaily1a.icsFailed: projectroot.autotests.RecurNext_ConnectDaily2.icsFailed: projectroot.autotests.RecurNext_ConnectDaily3.icsFailed: projectroot.autotests.RecurNext_ConnectDaily4.icsFailed: projectroot.autotests.RecurNext_ConnectDaily5.icsFailed: projectroot.autotests.RecurNext_ConnectDaily6.icsFailed: projectroot.autotests.RecurNext_ConnectDaily7.icsFailed: projectroot.autotests.RecurNext_ConnectDaily8.icsFailed: projectroot.autotests.RecurNext_ConnectDaily9.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase01.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase02.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase03.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase04.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase05.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase06.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase07.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase08.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase09.icsFailed: projectroot.autotests.RecurNext_KAlarm_TestCase10.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test01.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test02.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test03.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test04.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test05.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test06.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test07.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test08.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test09.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test10.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test11.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test12.icsFailed: projectroot.autotests.RecurNext_KOrganizer_Test13.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase01.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase02.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase03.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase04.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase05.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase06.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase07.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase08.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase09.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase10.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase11.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase12.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase15.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase16.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase17.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase18.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase19.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase20.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase21.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase23.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase24.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase25.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase26.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase27.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase28.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase29.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase30.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase31.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase32.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase33.icsFailed: projectroot.autotests.RecurNext_LibICal_TestCase34.icsFailed: 

KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.12 - Build # 80 - Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.12/80/
 Project:
kf5-qt5 SUSEQt5.12
 Date of build:
Sun, 10 Nov 2019 02:17:13 +
 Build duration:
57 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5Wayland-5.65.0.xmlcompat_reports/KF5Wayland_compat_report.htmllogs/KF5Wayland/5.65.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.autotests Failed: 1 test(s), Passed: 45 test(s), Skipped: 0 test(s), Total: 46 test(s)Failed: projectroot.autotests.client.kwayland_testRemoteAccess
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report63%
(5/8)90%
(240/268)90%
(240/268)85%
(27174/32076)53%
(10932/20609)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.client100%
(43/43)100%
(43/43)99%
(12474/12573)50%
(6566/13095)autotests.server100%
(5/5)100%
(5/5)99%
(373/376)49%
(177/360)src.client96%
(73/76)96%
(73/76)85%
(6352/7483)65%
(1832/2836)src.compat100%
(2/2)100%
(2/2)100%
(81/81)100%
(0/0)src.server95%
(117/123)95%
(117/123)84%
(7894/9364)64%
(2357/3687)src.tools0%
(0/2)0%
(0/2)0%
(0/785)0%
(0/302)src.tools.testserver0%
(0/3)0%
(0/3)0%
(0/119)0%
(0/14)tests0%
(0/14)0%
(0/14)0%
(0/1295)0%
(0/315)

KDE CI: Frameworks » kdesu » kf5-qt5 FreeBSDQt5.13 - Build # 21 - Still Unstable!

[CI System]

BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kdesu/job/kf5-qt5%20FreeBSDQt5.13/21/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 02:10:30 +
 Build duration:
1 hr 5 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 0 test(s), Skipped: 0 test(s), Total: 1 test(s)Failed: projectroot.autotests.kdesutest

KDE CI: Frameworks » kguiaddons » kf5-qt5 FreeBSDQt5.13 - Build # 23 - Fixed!

[CI System]

BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kguiaddons/job/kf5-qt5%20FreeBSDQt5.13/23/
 Project:
kf5-qt5 FreeBSDQt5.13
 Date of build:
Sun, 10 Nov 2019 03:45:03 +
 Build duration:
34 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)

KDE CI: Frameworks » kitemmodels » kf5-qt5 WindowsMSVCQt5.13 - Build # 21 - Failure!

[CI System]

BUILD FAILURE
 Build URL
https://build.kde.org/job/Frameworks/job/kitemmodels/job/kf5-qt5%20WindowsMSVCQt5.13/21/
 Project:
kf5-qt5 WindowsMSVCQt5.13
 Date of build:
Sun, 10 Nov 2019 01:33:42 +
 Build duration:
4 hr 32 min and counting
   CONSOLE OUTPUT
  [...truncated 367 lines...][2019-11-10T06:05:46.936Z] Scanning dependencies of target kselectionproxymodeltest_autogen[2019-11-10T06:05:46.936Z] Scanning dependencies of target proxymodeltestapp_autogen[2019-11-10T06:05:46.936Z] Scanning dependencies of target kselectionproxymodel_smoketest_autogen[2019-11-10T06:05:46.936Z] [ 44%] Automatic MOC for target kdescendantsproxymodeltest[2019-11-10T06:05:49.704Z] [ 41%] Automatic MOC for target kdescendantsproxymodel_smoketest[2019-11-10T06:05:50.199Z] [ 44%] Built target kdescendantsproxymodel_smoketest_autogen[2019-11-10T06:05:50.199Z] [ 44%] Automatic MOC for target klinkitemselectionmodeltest[2019-11-10T06:05:50.199Z] [ 44%] Automatic MOC for target kmodelindexproxymappertest[2019-11-10T06:05:50.766Z] [ 44%] Automatic MOC for target krecursivefilterproxymodeltest[2019-11-10T06:05:50.766Z] [ 44%] Built target klinkitemselectionmodeltest_autogen[2019-11-10T06:05:50.766Z] [ 44%] Built target kmodelindexproxymappertest_autogen[2019-11-10T06:05:50.766Z] [ 44%] Built target krecursivefilterproxymodeltest_autogen[2019-11-10T06:05:50.766Z] [ 44%] Built target kdescendantsproxymodeltest_autogen[2019-11-10T06:05:50.766Z] [ 44%] Automatic MOC for target proxymodeltestapp[2019-11-10T06:05:50.766Z] [ 44%] Automatic MOC for target kselectionproxymodel_smoketest[2019-11-10T06:05:50.767Z] [ 43%] Automatic MOC for target kconcatenaterowsproxymodeltest[2019-11-10T06:05:50.767Z] [ 44%] Automatic MOC for target krearrangecolumnsproxymodeltest[2019-11-10T06:05:50.767Z] [ 44%] Automatic MOC for target kselectionproxymodeltest[2019-11-10T06:05:50.767Z] [ 44%] Automatic MOC for target kextracolumnsproxymodeltest[2019-11-10T06:05:51.270Z] [ 44%] Built target kselectionproxymodeltest_autogen[2019-11-10T06:05:51.270Z] [ 44%] Built target krearrangecolumnsproxymodeltest_autogen[2019-11-10T06:05:51.270Z] [ 44%] Built target kconcatenaterowsproxymodeltest_autogen[2019-11-10T06:05:51.270Z] [ 44%] Built target kextracolumnsproxymodeltest_autogen[2019-11-10T06:05:51.270Z] [ 44%] Built target kselectionproxymodel_smoketest_autogen[2019-11-10T06:05:52.018Z] Scanning dependencies of target kdescendantsproxymodel_smoketest[2019-11-10T06:05:52.018Z] Scanning dependencies of target kmodelindexproxymappertest[2019-11-10T06:05:52.018Z] Scanning dependencies of target klinkitemselectionmodeltest[2019-11-10T06:05:52.018Z] Scanning dependencies of target krecursivefilterproxymodeltest[2019-11-10T06:05:52.740Z] Scanning dependencies of target kdescendantsproxymodeltest[2019-11-10T06:05:52.740Z] [ 49%] Building CXX object autotests/CMakeFiles/kdescendantsproxymodel_smoketest.dir/kdescendantsproxymodel_smoketest.cpp.obj[2019-11-10T06:05:52.740Z] kdescendantsproxymodel_smoketest.cpp[2019-11-10T06:05:52.740Z] Scanning dependencies of target kselectionproxymodeltest[2019-11-10T06:05:52.740Z] [ 49%] Building CXX object autotests/CMakeFiles/kmodelindexproxymappertest.dir/kmodelindexproxymappertest.cpp.obj[2019-11-10T06:05:52.740Z] kmodelindexproxymappertest.cpp[2019-11-10T06:05:52.740Z] Scanning dependencies of target krearrangecolumnsproxymodeltest[2019-11-10T06:05:52.740Z] [ 50%] Building CXX object autotests/CMakeFiles/klinkitemselectionmodeltest.dir/klinkitemselectionmodeltest.cpp.obj[2019-11-10T06:05:52.740Z] Scanning dependencies of target kconcatenaterowsproxymodeltest[2019-11-10T06:05:52.740Z] klinkitemselectionmodeltest.cpp[2019-11-10T06:05:53.324Z] Scanning dependencies of target kextracolumnsproxymodeltest[2019-11-10T06:05:53.324Z] [ 50%] Building CXX object autotests/CMakeFiles/krecursivefilterproxymodeltest.dir/krecursivefilterproxymodeltest.cpp.obj[2019-11-10T06:05:53.324Z] [ 50%] Building CXX object autotests/CMakeFiles/kdescendantsproxymodel_smoketest.dir/kdescendantsproxymodel_smoketest_autogen/mocs_compilation.cpp.obj[2019-11-10T06:05:53.325Z] krecursivefilterproxymodeltest.cpp[2019-11-10T06:05:53.325Z] Scanning dependencies of target kselectionproxymodel_smoketest[2019-11-10T06:05:53.325Z] [ 51%] Building CXX object autotests/CMakeFiles/kdescendantsproxymodeltest.dir/kdescendantsproxymodeltest.cpp.obj[2019-11-10T06:05:53.325Z] kdescendantsproxymodeltest.cpp[2019-11-10T06:05:53.325Z] [ 54%] Building CXX object autotests/CMakeFiles/kselectionproxymodeltest.dir/kselectionproxymodeltest.cpp.obj[2019-11-10T06:05:53.583Z] kselectionproxymodeltest.cpp[2019-11-10T06:05:53.583Z] [ 55%] Building CXX object autotests/CMakeFiles/krearrangecolumnsproxymodeltest.dir/krearrangecolumnsproxymodeltest.cpp.obj[2019-11-10T06:05:53.583Z] krearrangecolumnsproxymodeltest.cpp[2019-11-10T06:05:53.583Z] [ 55%] Building CXX object