Pin Clipboard History by PK ID to dodge a name collision #71

Merged

TheDarkWizard merged 1 commit from pin-clipboard-history into main

2026-07-15 05:11:34 +00:00

TheDarkWizard commented

2026-07-15 05:10:58 +00:00

Owner

GNOME and GNOME NVIDIA builds have failed since last night with:

ERROR: Multiple compatible Gnome extensions with the same name are found, which this module cannot select

Cause is upstream: a brand-new, unrelated extension named exactly 'Clipboard History' (clipboard-history@Diyar1877, PK 10400, 39 downloads) was approved on extensions.gnome.org yesterday and also targets Shell 50, so the gnome-extensions module's name search now returns two compatible hits and bails. Every re-run of the merge build fails the same way, which fails the bluebuild matrix and blocks the release job behind it.

Fix per the module docs: install ours by PK ID, 4839, which is clipboard-history@alexsaveau.dev and matches the UUID already enabled in zzz-monolith.gschema.override. Only the GNOME recipe entry changes; gnome-nvidia inherits it.

GNOME and GNOME NVIDIA builds have failed since last night with: ERROR: Multiple compatible Gnome extensions with the same name are found, which this module cannot select Cause is upstream: a brand-new, unrelated extension named exactly 'Clipboard History' (clipboard-history@Diyar1877, PK 10400, 39 downloads) was approved on extensions.gnome.org yesterday and also targets Shell 50, so the gnome-extensions module's name search now returns two compatible hits and bails. Every re-run of the merge build fails the same way, which fails the bluebuild matrix and blocks the release job behind it. Fix per the module docs: install ours by PK ID, 4839, which is clipboard-history@alexsaveau.dev and matches the UUID already enabled in zzz-monolith.gschema.override. Only the GNOME recipe entry changes; gnome-nvidia inherits it.

TheDarkWizard added 1 commit

2026-07-15 05:10:58 +00:00

Pin Clipboard History by PK ID to dodge a name collision

bluebuild / Check if a rebuild is needed (pull_request) Successful in 4s

Details

PR Rebase Hint / Post rebase command (pull_request) Successful in 4s

Details

bluebuild / Release (pull_request) Has been cancelled

Details

bluebuild / Generate Release (pull_request) Has been cancelled

Details

bluebuild / Build GNOME (GNOME, recipe-gnome.yml) (pull_request) Has been cancelled

Details

bluebuild / Build GNOME NVIDIA (GNOME NVIDIA, recipe-gnome-nvidia.yml) (pull_request) Has been cancelled

Details

0c08398082

A brand-new unrelated extension named exactly 'Clipboard History'
(clipboard-history@Diyar1877, PK 10400) got approved on
extensions.gnome.org yesterday and also targets Shell 50, so the
gnome-extensions module's name search now finds two compatible matches
and refuses to pick one. That kills every GNOME and GNOME NVIDIA build,
which fails the bluebuild matrix and blocks the release job with it.

Install ours (clipboard-history@alexsaveau.dev, matching the UUID in
zzz-monolith.gschema.override) by its PK ID 4839, which the module
accepts for exactly this case.

forgejo-actions commented

2026-07-15 05:11:01 +00:00

🧪 Test this PR on a real install

Once the build checks on this PR pass, a signed test image is published for each edition this PR builds. Pick the one matching your hardware and, from an existing Monolith install (which already has the signing policy), rebase onto it:

gnome

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome:pr-71-44
systemctl reboot

gnome-nvidia

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-71-44
systemctl reboot

The tags are rebuilt on every new commit here, so rpm-ostree upgrade pulls the latest build. When you're done testing, return to your edition's released image (:latest).

The commands cover the editions this PR affected when it was opened; commits that touch more editions publish their tags too, just without a refreshed comment. The test tags stop updating once this PR is merged or closed.

### 🧪 Test this PR on a real install **Once the build checks on this PR pass**, a signed test image is published for each edition this PR builds. Pick the one matching your hardware and, from an existing Monolith install (which already has the signing policy), rebase onto it: **`gnome`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome:pr-71-44 systemctl reboot ``` **`gnome-nvidia`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-71-44 systemctl reboot ``` The tags are rebuilt on every new commit here, so `rpm-ostree upgrade` pulls the latest build. When you're done testing, return to your edition's released image (`:latest`). _The commands cover the editions this PR affected when it was opened; commits that touch more editions publish their tags too, just without a refreshed comment. The test tags stop updating once this PR is merged or closed._

TheDarkWizard merged commit df96e44f59 into main

2026-07-15 05:11:34 +00:00

TheDarkWizard referenced this pull request from a commit

2026-07-15 05:11:35 +00:00

Merge pull request 'Pin Clipboard History by PK ID to dodge a name collision' (#71) from pin-clipboard-history into main