From elan.ruusamae at gmail.com  Thu Dec 19 13:16:42 2024
From: elan.ruusamae at gmail.com (=?utf-8?Q?Elan_Ruusam=C3=A4e?=)
Date: Thu, 19 Dec 2024 14:16:42 +0200
Subject: Docker builds plugin  (try 2)
Message-ID: <86870BA9-75A2-423E-B309-21E55189A152@gmail.com>

[- somewhy my previous email did not end up in public archive: https://lists.pld-linux.org/mailman/pipermail/pld-devel-en/ -]

ERROR: BuildKit is enabled but the buildx component is missing or broken.
       Install the buildx component to build images with BuildKit:
       https://docs.docker.com/go/buildx/

is buildx plugin packaged somewhere?

https://github.com/docker/buildx#linux-packages- https://github.com/docker/buildx#linux-packages


couldn?t find it from github package search:
- https://github.com/search?q=org%3Apld-linux+buildx&type=repositories

From atler at pld-linux.org  Thu Dec 19 14:28:32 2024
From: atler at pld-linux.org (Jan Palus)
Date: Thu, 19 Dec 2024 14:28:32 +0100
Subject: Docker builds plugin  (try 2)
In-Reply-To: <86870BA9-75A2-423E-B309-21E55189A152@gmail.com>
References: <86870BA9-75A2-423E-B309-21E55189A152@gmail.com>
Message-ID: <ruirslcx3sfd34i622pjtzg3ul65gnt3dqqgi3gxaemy7um75p@iyemgetsu4xh>

On 19.12.2024 14:16, Elan Ruusam?e wrote:
> [- somewhy my previous email did not end up in public archive: https://lists.pld-linux.org/mailman/pipermail/pld-devel-en/ -]
> 
> ERROR: BuildKit is enabled but the buildx component is missing or broken.
>        Install the buildx component to build images with BuildKit:
>        https://docs.docker.com/go/buildx/
> 
> is buildx plugin packaged somewhere?
> 
> https://github.com/docker/buildx#linux-packages- https://github.com/docker/buildx#linux-packages
> 
> 
> couldn?t find it from github package search:
> - https://github.com/search?q=org%3Apld-linux+buildx&type=repositories

Available now in docker-buildx.


From baggins at pld-linux.org  Fri Dec 20 19:20:40 2024
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Fri, 20 Dec 2024 19:20:40 +0100
Subject: Please cleanup gnome packaging mess
Message-ID: <Z2W1eBMMt8K_YXxv@starbug.lan>

For start:

Fri Dec 20 19:03:37 CET 2024
error: [gnome-photos.spec] gnome-photos-44.0-2.x86_64: req /usr/share/tracker3-miners/domain-ontologies not found
error: [nautilus3.spec] nautilus3-42.6-4.x86_64: req /usr/share/tracker3 not found
error: [nautilus3.spec] nautilus3-42.6-4.x86_64: req tracker3-miners >= 3.0 not found

There are many GNOME packages in $pkg and $pkg3 versions, where one with
the '3' seems to be some old, obsolete stuff.

Can we have a clarity on this, and, preferably a _single_ incarnation of
each package? If something needs to be removed, please let me know what.

As it is now, I'm very much inclined to just remove all the $pkg3 stuff
from th.

Cheers
-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From qboosh at pld-linux.org  Sun Dec 22 09:37:59 2024
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Sun, 22 Dec 2024 09:37:59 +0100
Subject: Please cleanup gnome packaging mess
In-Reply-To: <Z2W1eBMMt8K_YXxv@starbug.lan>
References: <Z2W1eBMMt8K_YXxv@starbug.lan>
Message-ID: <20241222083759.GA27393@mail>

On Fri, Dec 20, 2024 at 07:20:40PM +0100, Jan R?korajski wrote:
> For start:
> 
> Fri Dec 20 19:03:37 CET 2024
> error: [gnome-photos.spec] gnome-photos-44.0-2.x86_64: req /usr/share/tracker3-miners/domain-ontologies not found
> error: [nautilus3.spec] nautilus3-42.6-4.x86_64: req /usr/share/tracker3 not found
> error: [nautilus3.spec] nautilus3-42.6-4.x86_64: req tracker3-miners >= 3.0 not found

I reconfigured gnome-photos not to use tracker and adjusted nautilus3
for tinysparql+localsearch.

> There are many GNOME packages in $pkg and $pkg3 versions, where one with
> the '3' seems to be some old, obsolete stuff.
> 
> Can we have a clarity on this, and, preferably a _single_ incarnation of
> each package? If something needs to be removed, please let me know what.
> 
> As it is now, I'm very much inclined to just remove all the $pkg3 stuff
> from th.

tracker3* packages are obsoleted by tinysparql+localsearch.

I kept nautilus3 because most external plugins have not been ported yet
to nautilus 4 API (43+), including still maintained evince (to be
replaced by papers soon) and brasero (I am now aware of any newer GNOME
replacement for it).


-- 
Jakub Bogusz    http://qboosh.pl/


From baggins at pld-linux.org  Sun Dec 22 11:05:06 2024
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 22 Dec 2024 11:05:06 +0100
Subject: Please cleanup gnome packaging mess
In-Reply-To: <20241222083759.GA27393@mail>
References: <Z2W1eBMMt8K_YXxv@starbug.lan>
 <20241222083759.GA27393@mail>
Message-ID: <Z2fkUjnS3kXGQl-Y@starbug.lan>

On Sun, 22 Dec 2024, Jakub Bogusz wrote:

> On Fri, Dec 20, 2024 at 07:20:40PM +0100, Jan R?korajski wrote:
> > For start:
> > 
> > Fri Dec 20 19:03:37 CET 2024
> > error: [gnome-photos.spec] gnome-photos-44.0-2.x86_64: req /usr/share/tracker3-miners/domain-ontologies not found
> > error: [nautilus3.spec] nautilus3-42.6-4.x86_64: req /usr/share/tracker3 not found
> > error: [nautilus3.spec] nautilus3-42.6-4.x86_64: req tracker3-miners >= 3.0 not found
> 
> I reconfigured gnome-photos not to use tracker and adjusted nautilus3
> for tinysparql+localsearch.
> 
> > There are many GNOME packages in $pkg and $pkg3 versions, where one with
> > the '3' seems to be some old, obsolete stuff.
> > 
> > Can we have a clarity on this, and, preferably a _single_ incarnation of
> > each package? If something needs to be removed, please let me know what.
> > 
> > As it is now, I'm very much inclined to just remove all the $pkg3 stuff
> > from th.
> 
> tracker3* packages are obsoleted by tinysparql+localsearch.
> 
> I kept nautilus3 because most external plugins have not been ported yet
> to nautilus 4 API (43+), including still maintained evince (to be
> replaced by papers soon) and brasero (I am now aware of any newer GNOME
> replacement for it).

Thank you.

Please do let me know in the future if any package (not only
GNOME) should be removed because it's obsoleted by something.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/