ate some new KF API just added in
> cooperation
> with that very repo wanting to use it, I cannot do so when someone had
> added a
> flatpak job on CI to that repo.
>
> Because with such flatpak jobs it seems they are limiting the available KF
> version not to the current latest
ate some new KF API just added in
> cooperation
> with that very repo wanting to use it, I cannot do so when someone had
> added a
> flatpak job on CI to that repo.
>
> Because with such flatpak jobs it seems they are limiting the available KF
> version not to the current latest
someone had added a
flatpak job on CI to that repo.
Because with such flatpak jobs it seems they are limiting the available KF
version not to the current latest one, as expected for continuous integration,
but some older (anywhere documented?) snapshot:
"runtime-version": "
Hello,
On vendredi 14 avril 2017 07:54:25 CEST Matthieu Gallien wrote:
> Hello,
>
> On jeudi 13 avril 2017 19:31:37 CEST Kevin Funk wrote:
> > On Thursday, 13 April 2017 18:25:19 CEST Matthieu Gallien wrote:
> > > Hello,
> > >
> > > I am trying to use KFileMetaData on Windows with mingw-5.3 32 b
Hello,
On jeudi 13 avril 2017 19:31:37 CEST Kevin Funk wrote:
> On Thursday, 13 April 2017 18:25:19 CEST Matthieu Gallien wrote:
> > Hello,
> >
> > I am trying to use KFileMetaData on Windows with mingw-5.3 32 bits. I am
> > getting compilation errors in the automatic tests and have an hard time
>
On Thursday, 13 April 2017 18:25:19 CEST Matthieu Gallien wrote:
> Hello,
>
> I am trying to use KFileMetaData on Windows with mingw-5.3 32 bits. I am
> getting compilation errors in the automatic tests and have an hard time
> getting it to works nominally.
Paste the errors please, maybe we can f
Hello,
I am trying to use KFileMetaData on Windows with mingw-5.3 32 bits. I am
getting compilation errors in the automatic tests and have an hard time
getting it to works nominally.
Is there public servers currently testing KDE Frameworks 5 including
KFileMetaData ?
Should I switch to Micros
Thanks David and Harald,
I had already found some months ago that you have to go through
"default" but had forgotten about it.
Have a nice day
Best regards
2017-03-15 13:57 GMT+01:00 Harald Sitter :
> you need to drill down into the 'default' configuration
> http://i.imgur.com/D4Asuaa.png
>
> O
you need to drill down into the 'default' configuration
http://i.imgur.com/D4Asuaa.png
On Wed, Mar 15, 2017 at 10:10 AM, Matthieu Gallien
wrote:
> Hello,
>
> I am a bit lost when looking at both KFileMetaData projects under
> build.kde.org. I am not able to get any coverage, cppcheck or
> automat
On mercredi 15 mars 2017 10:10:25 CET Matthieu Gallien wrote:
> Hello,
>
> I am a bit lost when looking at both KFileMetaData projects under
> build.kde.org. I am not able to get any coverage, cppcheck or
> automatic tests results.
>
> Am I looking at the wrong place ?
>
> Is it expected ?
Dunn
Hello,
I am a bit lost when looking at both KFileMetaData projects under
build.kde.org. I am not able to get any coverage, cppcheck or
automatic tests results.
Am I looking at the wrong place ?
Is it expected ?
Thanks in advance for any help
Best regards
--
Matthieu Gallien
Hi folks,
As you've probably observed, the CI system sent a large number of
mails to this list over the past few hours.
This was fallout from an extremely binary incompatible change
affecting virtually all frameworks.
I would suggest that maintainers please check the build logs for each
of the f
12 matches
Mail list logo
