On Sat, Mar 28, 2020 at 12:44 PM Kevin Kofler wrote:
>
> Ben Cooksley wrote:
> > I'm unhappy with them due to how they handled the complete disaster
> > that was a significant version update to a core system library (libc I
> > think) which they did in a stable, released distribution.
>
> I cannot
First up: I would like to apologize for submitting and landing
https://phabricator.kde.org/D28076 and
https://phabricator.kde.org/D28086 without properly checking that
everything was behaving as it should.
For the initial breakage of https://phabricator.kde.org/D28076, I
failed to check that it bu
On Sat, Mar 21, 2020, 10:27 AM Johan Ouwerkerk
wrote:
> On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
> >
> > Comments welcome. Please note that simply fixing the dependency
> > breakage in this case is not enough to resolve this - there are
> > underlying issues which need to be addressed
Ben Cooksley wrote:
> I'm unhappy with them due to how they handled the complete disaster
> that was a significant version update to a core system library (libc I
> think) which they did in a stable, released distribution.
I cannot really speak for that part, but for the following part:
> It was
On Tue, Mar 24, 2020 at 12:55 AM Thomas Baumgart wrote:
>
> On Montag, 23. März 2020 09:32:26 CET Ben Cooksley wrote:
>
> > On Mon, Mar 23, 2020 at 6:53 AM Albert Astals Cid wrote:
>
> [...]
>
> > > But If you're volunteering to do a Windows gitlab CI for QCA I'll take it
> > > :)
> >
> > Not at
On Montag, 23. März 2020 09:32:26 CET Ben Cooksley wrote:
> On Mon, Mar 23, 2020 at 6:53 AM Albert Astals Cid wrote:
[...]
> > But If you're volunteering to do a Windows gitlab CI for QCA I'll take it :)
>
> Not at this stage - aside from you mentioning it here, and Krita
> needing to use Ming
On Mon, Mar 23, 2020 at 6:53 AM Albert Astals Cid wrote:
>
> El diumenge, 22 de març de 2020, a les 16:12:04 CET, Ben Cooksley va escriure:
> > On Mon, Mar 23, 2020 at 12:49 AM Albert Astals Cid wrote:
> > >
> > > El diumenge, 22 de març de 2020, a les 3:19:57 CET, Ben Cooksley va
> > > escriure
El diumenge, 22 de març de 2020, a les 16:12:04 CET, Ben Cooksley va escriure:
> On Mon, Mar 23, 2020 at 12:49 AM Albert Astals Cid wrote:
> >
> > El diumenge, 22 de març de 2020, a les 3:19:57 CET, Ben Cooksley va
> > escriure:
> > > Note however that images based upon Fedora or anything that sh
On Mon, Mar 23, 2020 at 12:41 AM Johan Ouwerkerk wrote:
>
> On Sun, Mar 22, 2020 at 3:20 AM Ben Cooksley wrote:
> >
> > We already do have a repository of artifacts :)
> > You can find the public view of this at
> > https://build-artifacts.kde.org/production/
> >
>
> >
> > We already use Virtual
On Mon, Mar 23, 2020 at 12:49 AM Albert Astals Cid wrote:
>
> El diumenge, 22 de març de 2020, a les 3:19:57 CET, Ben Cooksley va escriure:
> > Note however that images based upon Fedora or anything that shares
> > it's lineage (including CentOS and it's derivates) is strictly
> > prohibited and w
El diumenge, 22 de març de 2020, a les 3:19:57 CET, Ben Cooksley va escriure:
> Note however that images based upon Fedora or anything that shares
> it's lineage (including CentOS and it's derivates) is strictly
> prohibited and won't be accepted for inclusion.
I still find this highly annoying si
On Sun, Mar 22, 2020 at 3:20 AM Ben Cooksley wrote:
>
> We already do have a repository of artifacts :)
> You can find the public view of this at
> https://build-artifacts.kde.org/production/
>
>
> We already use Virtual Machines for both FreeBSD and Windows.
>
> The main problem here is that the
On Sun, Mar 22, 2020 at 12:00 PM Johan Ouwerkerk wrote:
>
> On Sat, Mar 21, 2020 at 10:27 PM Ben Cooksley wrote:
> >
> > On Sun, Mar 22, 2020 at 3:27 AM Johan Ouwerkerk
> > wrote:
> > >
> > > On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
> > > >
> > > > Comments welcome. Please note that
El sáb., 21 de mar. de 2020 a la(s) 20:00, Johan Ouwerkerk
(jm.ouwerk...@gmail.com) escribió:
> Out of interest, apart from the amount of work it might take what
> would be the main blocker for using VMs and things like Vagrant boxes
> for FreeBSD as the next best thing to containers? I'd ask the s
On Sat, Mar 21, 2020 at 10:27 PM Ben Cooksley wrote:
>
> On Sun, Mar 22, 2020 at 3:27 AM Johan Ouwerkerk
> wrote:
> >
> > On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
> > >
> > > Comments welcome. Please note that simply fixing the dependency
> > > breakage in this case is not enough to
On Sun, Mar 22, 2020 at 3:27 AM Johan Ouwerkerk wrote:
>
> On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
> >
> > Comments welcome. Please note that simply fixing the dependency
> > breakage in this case is not enough to resolve this - there are
> > underlying issues which need to be address
On Sun, Mar 22, 2020 at 3:08 AM David Edmundson
wrote:
>
> You're absolutely right that mistakes were made and have reason to be
> frustrated.
>
> kde-gtk-config is now maintained by new developers.
> Plasma has a new influx of new people which is good to see and
> something we need to foster care
On Sat, Mar 21, 2020 at 1:32 AM Ben Cooksley wrote:
>
> Comments welcome. Please note that simply fixing the dependency
> breakage in this case is not enough to resolve this - there are
> underlying issues which need to be addressed here.
>
> Regards,
> Ben Cooksley
> KDE Sysadmin
I cannot commen
You're absolutely right that mistakes were made and have reason to be
frustrated.
kde-gtk-config is now maintained by new developers.
Plasma has a new influx of new people which is good to see and
something we need to foster carefully.
Overall these new devs are doing a super job and we want to e
In data sabato 21 marzo 2020 01:31:40 CET, Ben Cooksley ha scritto:
> Plasma community in general until I raised the matter by commenting on
> the original review - several days after the fact.
I take the opportunity to ask reviewers who review changes to watch for the
impact of such changes on
Hi all,
In recent days the repository `kde-gtk-config` has had a string of
issues with the CI system which raises serious questions concerning
the development practices of this project.
The first violation was a compilation failure introduced following the
commit of changes in https://phabricator
21 matches
Mail list logo
