äische
> Normalzeit
> > > >>>
> > > >>> Albert
> > > >>>
> > > >>>>> Astals Cid wrote:
> > > >>>>>> neochat - NEW
> > > >>>>>>
> > > >>>>>> *
been thinking that having a separate file that would be used
> >
> > instead
> >
> > > of .flatpak-manifest.yml if present when doing a build on a stable
> > > branch
> > > would be a good solution.
> > > Under this you would have a .flatpak-manif
On Thu, Jan 23, 2025 at 5:49 AM Volker Krause
> >
> > wrote:
> > >>>>> On Dienstag, 21. Januar 2025 23:11:56 Mitteleuropäische Normalzeit
> > >>>
> > >>> Albert
> > >>>
> > >>>>> Astals Cid wrote:
> >
On Sat, Jan 25, 2025 at 10:46 AM Ingo Klöcker wrote:
> On Freitag, 24. Januar 2025 18:57:43 Mitteleuropäische Normalzeit Ben
> Cooksley
> wrote:
> > I had been thinking that having a separate file that would be used
> instead
> > of .flatpak-manifest.yml if present when d
On Freitag, 24. Januar 2025 18:57:43 Mitteleuropäische Normalzeit Ben Cooksley
wrote:
> I had been thinking that having a separate file that would be used instead
> of .flatpak-manifest.yml if present when doing a build on a stable branch
> would be a good solution.
> Under this you
> >>> Albert
> >>>
> >>>>> Astals Cid wrote:
> >>>>>> neochat - NEW
> >>>>>>
> >>>>>> * https://invent.kde.org/network/neochat/-/pipelines/869365
> >>>>>>
> >>>>>
5:49 AM Volker Krause wrote:
On Dienstag, 21. Januar 2025 23:11:56 Mitteleuropäische Normalzeit
Albert
Astals Cid wrote:
neochat - NEW
* https://invent.kde.org/network/neochat/-/pipelines/869365
* flatpak build fails
Same as https://invent.kde.org/network/neochat/-/merge_requests
is very important that CI is
> > > > > > > passing
> > > > > > > for
> > > > > > > multiple reasons.
> > > > > > >
> > > > > > > Bad news: We have 2 new repositories failing :/
> > > > > > >
>
gt; > Please work on fixing them, otherwise i will remove the failing CI
> > > > > > jobs on their 4th failing week, it is very important that CI is
> > > > > > passing
> > > > > > for
> > > > > > multiple reasons.
> >
very important that CI is
> > > > > passing
> > > > > for
> > > > > multiple reasons.
> > > > >
> > > > > Bad news: We have 2 new repositories failing :/
> > > > >
> > > > > = FLATPAK FAILING =
09-19 21:35, Albert Astals Cid wrote:
> > > > Please work on fixing them, otherwise i will remove the failing CI
> > > > jobs on their 4th failing week, it is very important that CI is
> > > > passing
> > > > for
> > > > multiple reasons.
&
ling CI
> > > jobs on their 4th failing week, it is very important that CI is passing
> > > for
> > > multiple reasons.
> > >
> > > Bad news: We have 2 new repositories failing :/
> > >
> > > = FLATPAK FAILING =
> > >
>
passing
> > for
> > multiple reasons.
> >
> > Bad news: We have 2 new repositories failing :/
> >
> > = FLATPAK FAILING =
> >
> > kate:
> > * https://invent.kde.org/utilities/kate/-/pipelines/484147
> >
> > * This highlights
On Freitag, 19. Mai 2023 02:26:37 CEST Justin Zobel wrote:
> Hey Everyone,
>
> As Binary Factory is to be shut down soon we are moving the Flatpak
> manifests to their individual GitLab repositories.
>
> Most of this is fairly simple, however, some GitLab repositories ha
Le ven. 19 mai 2023 à 02:27, Justin Zobel a écrit :
> Hey Everyone,
>
> As Binary Factory is to be shut down soon we are moving the Flatpak
> manifests to their individual GitLab repositories.
>
> Most of this is fairly simple, however, some GitLab repositories have
>
Hey Everyone,
As Binary Factory is to be shut down soon we are moving the Flatpak
manifests to their individual GitLab repositories.
Most of this is fairly simple, however, some GitLab repositories have
enabled reuse linting (which is great). The Flatpak manifests I have
come across so far
On Sat, Sep 10, 2022 at 11:14 AM TheEvilSkeleton
wrote:
>
> Hi,
>
> At the moment, as an outsider, it's quite difficult to check what
> dependencies the KDE runtime provides. We have to check through the manifest,
> which in my opinion is quite unintuitive.
>
> To address that, I suggest a centr
Hi,
At the moment, as an outsider, it's quite difficult to check what
dependencies the KDE runtime provides. We have to check through the
manifest, which in my opinion is quite unintuitive.
To address that, I suggest a centralized page that lists these
dependencies. My current idea is to lis
On Thu, Dec 5, 2019 at 1:25 PM Aleix Pol wrote:
>
> On Wed, Dec 4, 2019 at 9:00 AM Ben Cooksley wrote:
> >
> > On Wed, Dec 4, 2019 at 3:12 AM Boudewijn Rempt wrote:
> > >
> > > Krita's flatpak nightly and nightly stable builds are broken, and I don
On Wed, Dec 4, 2019 at 9:00 AM Ben Cooksley wrote:
>
> On Wed, Dec 4, 2019 at 3:12 AM Boudewijn Rempt wrote:
> >
> > Krita's flatpak nightly and nightly stable builds are broken, and I don't
> > know why. It's almost as if flatpak-builder tries to parse th
On woensdag 4 december 2019 09:00:21 CET Ben Cooksley wrote:
> November 16 would roughly line up with when we changed the way the
> builders work, so it's possible that the version of flatpak-builder in
> use was changed at that time.
>
> Looking in that folder, I do see a
On Wed, Dec 4, 2019 at 3:12 AM Boudewijn Rempt wrote:
>
> Krita's flatpak nightly and nightly stable builds are broken, and I don't
> know why. It's almost as if flatpak-builder tries to parse the yaml file as
> json:
>
> [2019-12-02T22:37:51.554Z] + flatpak-
Krita's flatpak nightly and nightly stable builds are broken, and I don't know
why. It's almost as if flatpak-builder tries to parse the yaml file as json:
[2019-12-02T22:37:51.554Z] + flatpak-builder --force-clean --delete-build-dirs
--arch=x86_64 --ccache --sandbox --user --in
El dilluns, 26 d’agost de 2019, a les 16:58:34 CEST, Aleix Pol va escriure:
> On Mon, Aug 26, 2019 at 6:58 AM Jan Grulich wrote:
> >
> > Hi,
> >
> > do we want to do another Flatpak/Snap/Appimage BoF at Akademy this year?
> > From
> > my side it definitely
On Mon, Aug 26, 2019 at 6:58 AM Jan Grulich wrote:
>
> Hi,
>
> do we want to do another Flatpak/Snap/Appimage BoF at Akademy this year? From
> my side it definitely can be useful and we can also have new people around
> this time and help them to package their applications if an
to do another Flatpak/Snap/Appimage BoF at Akademy this year?
> From
> my side it definitely can be useful and we can also have new people around
> this time and help them to package their applications if anyone is
> interested.
>
> Which day would you prefer? There is AGM on Mon
Hi,
do we want to do another Flatpak/Snap/Appimage BoF at Akademy this year? From
my side it definitely can be useful and we can also have new people around
this time and help them to package their applications if anyone is interested.
Which day would you prefer? There is AGM on Monday and a
Thank you for all of your answers and explanations!
Yesterday, I managed to compile the flatpak successfully by adding polkit,
PolkitQt and KAuth to the manifest. I haven't had the time to test the
resulting package, but at the moment I'm confident that it will work, since the
GNO
On Mon, Jun 3, 2019 at 2:13 AM Stefan Brüns
wrote:
> SMB4K is a quite lowlevel system tool. There are tools which are too lowlevel
> to package as flatpak/snap/appimage/whatever in a useful way
That is not true. Certainly not for appimage and snap anyway, both
offer operation without/l
t;> helper
> >> included? Or is it impossible to install a KAuth helper into a flatpak?
> >> Help is much appreciated.
> >
> > I think that's the main question, does a KAuth helper make sense in a
> > flatpak app?
> >
> > Given that flatpak
On 6/2/19 4:37 AM, Albert Astals Cid wrote:
El divendres, 31 de maig de 2019, a les 13:05:04 CEST, Alexander Reinholdt va
escriure:
Has anyone on this list successfully packaged a program with a KAuth helper
included? Or is it impossible to install a KAuth helper into a flatpak? Help
is
El divendres, 31 de maig de 2019, a les 13:05:04 CEST, Alexander Reinholdt va
escriure:
> Has anyone on this list successfully packaged a program with a KAuth helper
> included? Or is it impossible to install a KAuth helper into a flatpak? Help
> is much appreciated.
I think that&#
Hello everyone,
I am currently trying to produce a flatpak for Smb4K. However, the build
process always fails when the KAuth helper binary is to be installed into the
flatpak folder. The following error message is displayed:
[...]
CMake Error at helpers/cmake_install.cmake:55 (file):
file
I'd like to be there too!
Nate
On 06/28/2018 06:18 AM, Aleix Pol wrote:
On Thu, Jun 28, 2018 at 7:54 AM Jan Grulich wrote:
Hi,
I would like to organize a BoF for Flatpak and Snap related stuff, to discuss
our support of sandboxing, plans for future and so on. I would like to know
wh
On Thu, Jun 28, 2018 at 7:54 AM Jan Grulich wrote:
>
> Hi,
>
> I would like to organize a BoF for Flatpak and Snap related stuff, to discuss
> our support of sandboxing, plans for future and so on. I would like to know
> whether there is an interest before booking a room for th
Tuesday works for me.
On Thu, Jun 28, 2018 at 7:54 AM Jan Grulich wrote:
>
> Hi,
>
> I would like to organize a BoF for Flatpak and Snap related stuff, to discuss
> our support of sandboxing, plans for future and so on. I would like to know
> whether there is an interest before
Hi,
I would like to organize a BoF for Flatpak and Snap related stuff, to discuss
our support of sandboxing, plans for future and so on. I would like to know
whether there is an interest before booking a room for this.
Some stuff I can think of right now we can discuss:
* Flatpak and Snap
Hello,
On lundi 16 avril 2018 11:45:50 CEST you wrote:
> On dimanche 15 avril 2018 01:52:41 CEST Aleix Pol wrote:
> > On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien
> >
> > wrote:
> > > Hello,
> > >
> > > I really appreciate the work th
On Sun, Apr 15, 2018 at 9:56 AM, Ben Cooksley wrote:
> On Sun, Apr 15, 2018 at 11:52 AM, Aleix Pol wrote:
>> On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien
>> wrote:
>>> Hello,
>>>
>>> I really appreciate the work that has gone into flatpak and t
On dimanche 15 avril 2018 01:52:41 CEST Aleix Pol wrote:
> On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien
>
> wrote:
> > Hello,
> >
> > I really appreciate the work that has gone into flatpak and the excellent
> > support for it in KDE and the KDE infrastr
On neděle 15. dubna 2018 9:56:40 CEST Ben Cooksley wrote:
> On Sun, Apr 15, 2018 at 11:52 AM, Aleix Pol wrote:
> > On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien
> >
> > wrote:
> >> Hello,
> >>
> >> I really appreciate the work that has gone
On Sun, Apr 15, 2018 at 11:52 AM, Aleix Pol wrote:
> On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien
> wrote:
>> Hello,
>>
>> I really appreciate the work that has gone into flatpak and the excellent
>> support for it in KDE and the KDE infrastructure for
On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien
wrote:
> Hello,
>
> I really appreciate the work that has gone into flatpak and the excellent
> support for it in KDE and the KDE infrastructure for it.
>
> I have an hard time understanding what is the best way to distribute
I would strongly encourage it. Flathub is quickly becoming the de facto source
for Flatpak apps, and all of GNOME’s apps are already there. It would be great
to get some more KDE representation there too.
Nate
> On Apr 14, 2018, at 3:20 PM, Matthieu Gallien
> wrote:
>
> Hello,
&
Hello,
I really appreciate the work that has gone into flatpak and the excellent
support for it in KDE and the KDE infrastructure for it.
I have an hard time understanding what is the best way to distribute a stable
release through flatpak.
I am not sure if the KDE flatpak repositories are
t :
>>
>> Hi,
>> Recently flathub started building our runtime into their systems. I
>> recommend using the runtimes there. I updated the wiki to reflect the
>> change:
>> https://community.kde.org/Guidelines_and_HOWTOs/Flatpak
>>
>> You will possibly
mend using the runtimes there. I updated the wiki to reflect the
> change:
> https://community.kde.org/Guidelines_and_HOWTOs/Flatpak
>
> You will possibly have to remove and add again the runtime, but other
> than that everything should work as usual.
>
> Aleix
>
> Can I
i to reflect the
> change:
> https://community.kde.org/Guidelines_and_HOWTOs/Flatpak
>
> You will possibly have to remove and add again the runtime, but other
> than that everything should work as usual.
>
> Aleix
>
> Can I point possible users wanting to test the Elisa music playe
Hello
Le 19 sept. 2017 17:00, "Aleix Pol" a écrit :
Hi,
Recently flathub started building our runtime into their systems. I
recommend using the runtimes there. I updated the wiki to reflect the
change:
https://community.kde.org/Guidelines_and_HOWTOs/Flatpak
You will possibly have
Hi,
Recently flathub started building our runtime into their systems. I
recommend using the runtimes there. I updated the wiki to reflect the
change:
https://community.kde.org/Guidelines_and_HOWTOs/Flatpak
You will possibly have to remove and add again the runtime, but other
than that everything
On giovedì 10 agosto 2017 18:04:47 CEST, Aleix Pol wrote:
On Thu, Aug 10, 2017 at 5:56 PM, Elvis Angelaccio
wrote:
On giovedì 10 agosto 2017 17:19:12 CEST, Aleix Pol wrote: ...
Yes
I've done it for ark. Let's see if it works :D
>>
>>
>> Here's an example:
>>
>> https://cgit.kde.org/flatpak-kde-applications.git/tree/org.kde.portal-test-kde.remoteapp
>>
>> We could also have it point to a branch.
>>
>> Ideally in a world where this vision is fully implemented we coul
On giovedì 10 agosto 2017 17:19:12 CEST, Aleix Pol wrote:
On Tue, Aug 8, 2017 at 7:17 PM, Elvis Angelaccio
wrote:
On martedì 8 agosto 2017 18:10:31 CEST, Aleix Pol wrote: ...
Here's an example:
https://cgit.kde.org/flatpak-kde-applications.git/tree/org.kde.portal-test-kde.remoteapp
We
, so that
>> application maintainers maintain it, rather than me with a weird
>> packager hat. I could set up a sample one for one of the apps I
>> maintain if there's interest.
>
>
> Yes please, that would be good.
>
>> - There are some technical issues we still h
d be good.
- There are some technical issues we still have before Qt/KDE
applications can shine under Flatpak. Anyone feel free to have a peek
and fix them all: https://phabricator.kde.org/project/view/124/
Aleix
Cheers,
Elvis
train on the server
>> and will be more useful to developers who are trying to make sure that
>> their application works.
>>
>> Logs can be found here:
>> https://distribute.kde.org/flatpak-apps-testing/log-flatpak-kde-applications
>> .text
>
> Does Flatp
ying to make sure that
> their application works.
>
> Logs can be found here:
> https://distribute.kde.org/flatpak-apps-testing/log-flatpak-kde-applications
> .text
Does Flatpak support the concept of stable/unstable builds? Could we actually
get the builds from the stable branch
stem is
>>>> meant for) - I assume it'll be finished by approximately 10am? (which
>>>> is when LXR starts it's KF5 update)
>>>>
>>>>>
>>>>> Logs can be found here:
>>>>> https://distribute.kde.org/flat
ir application works.
>>>
>>> I can confirm that the time the cronjob is set to run is 3am.
>>> That's fine from my perspective (it's basically what the system is
>>> meant for) - I assume it'll be finished by approximately 10am? (which
>>> is
>> That's fine from my perspective (it's basically what the system is
>> meant for) - I assume it'll be finished by approximately 10am? (which
>> is when LXR starts it's KF5 update)
>>
>>>
>>> Logs can be found here:
>>> https:
) - I assume it'll be finished by approximately 10am? (which
> is when LXR starts it's KF5 update)
>
>>
>> Logs can be found here:
>> https://distribute.kde.org/flatpak-apps-testing/log-flatpak-kde-applications.text
>>
>> Cheers!
>> Aleix
>
> Cheers,
> Ben
Yes, it should be done in 7h.
Aleix
update)
>
> Logs can be found here:
> https://distribute.kde.org/flatpak-apps-testing/log-flatpak-kde-applications.text
>
> Cheers!
> Aleix
Cheers,
Ben
Hey,
Just configured to have the server issue a new daily build (at 3am
UTC, if I cron'ed correctly). Shouldn't be a big strain on the server
and will be more useful to developers who are trying to make sure that
their application works.
Logs can be found here:
https://distribute.kde.o
On Thu, Nov 17, 2016 at 11:45 AM, Matthias Kuhn wrote:
> On 11/16/2016 04:02 PM, Aleix Pol wrote:
>> On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
>>> Hi,
>>>
>>> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
>&g
On 11/16/2016 04:02 PM, Aleix Pol wrote:
> On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
>> Hi,
>>
>> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
>> very happy to see the work on a KDE flatpak repository which already
>>
On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
> Hi,
>
> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
> very happy to see the work on a KDE flatpak repository which already
> packages Qt [2].
>
> I have recently been looking
if we see that
> we're getting so much projects that need PyQt that it makes sense,
> then by all means it should go in.
>
> Having different run-times for applications that use KDE Frameworks
> and applications that don't feels like shooting ourselves in the foot,
&g
Kuhn wrote:
>>> Hi,
>>>
>>> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
>>> very happy to see the work on a KDE flatpak repository which already
>>> packages Qt [2].
>>>
>>> I have recently been look
use of Qt libraries. I was
>> very happy to see the work on a KDE flatpak repository which already
>> packages Qt [2].
>>
>> I have recently been looking into a couple of different approaches to
>> ship app bundles and flatpak sounds like a very interesting one.
>
Hi Matthias,
Really happy to see there's interest!
On Mon, Nov 14, 2016 at 12:44 PM, Matthias Kuhn wrote:
> Hi,
>
> I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
> very happy to see the work on a KDE flatpak repository which already
> pa
27;m open for all kind of clever ideas.
All the best
Matthias
On 11/14/2016 12:57 PM, Jan Grulich wrote:
> Hi,
>
> if you add your additional dependencies which are not in KDE's flatpak
> runtime
> currently, then I guess it won't have any difference for your users. They
>
27;m open for all kind of clever ideas.
All the best
Matthias
On 11/14/2016 12:57 PM, Jan Grulich wrote:
> Hi,
>
> if you add your additional dependencies which are not in KDE's flatpak
> runtime
> currently, then I guess it won't have any difference for your users. They
>
Hi,
if you add your additional dependencies which are not in KDE's flatpak runtime
currently, then I guess it won't have any difference for your users. They will
either have to download a runtime requiring more space or an app bundle/repo
requiring extra space due to QtLocation, QCA
Hi,
I'm a developer of QGIS [1] which makes heavy use of Qt libraries. I was
very happy to see the work on a KDE flatpak repository which already
packages Qt [2].
I have recently been looking into a couple of different approaches to
ship app bundles and flatpak sounds like a very interestin
That won't work alone, see https://github.com/flatpak/flatpak/issues/61
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fflatpak%2Fflatpak%2Fissues%2F61&sa=D&sntz=1&usg=AFQjCNH5YVQFWeOpPkZx-vP920-rLuEI0Q>
David
On Wed, Jun 1, 2016 at 7:22 AM, Khad wrote:
> Hello,
>
> I try to install flatpak runtime from https://community.kde.org/Flatpak
>
> flatpak install kde org.kde.Platform
>
> but got this error:
>
> error: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling f
Hello,
I try to install flatpak runtime from https://community.kde.org/Flatpak
flatpak install kde org.kde.Platform
but got this error:
error: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from
repo: Can't pull from untrusted non-gpg verified remote
Do you have gpg fo
77 matches
Mail list logo
