Skip to content

Point package metadata URLs at omacom/omarchy - #429

Open
CRinATL wants to merge 1 commit into
omacom:masterfrom
CRinATL:point-package-urls-at-omacom
Open

CRinATL wants to merge 1 commit into
omacom:masterfrom
CRinATL:point-package-urls-at-omacom

Conversation

@CRinATL

@CRinATL CRinATL commented Sep 13, 2026

Copy link
Copy Markdown

Summary

url= and BUG_REPORT_URL in the Omarchy packages still point at github.com/basecamp/omarchy. GitHub redirects, so nothing is broken — this just points the metadata at the canonical location.

BUG_REPORT_URL is the user-visible one. It reaches /etc/os-release through etc-overrides/os-release on install and upgrade, so installed systems currently advertise the old URL:

$ grep BUG_REPORT_URL /etc/os-release        # omarchy-settings 4.0.3-1
BUG_REPORT_URL="https://github.com/basecamp/omarchy/issues"

7 lines across 5 packages: omarchy, omarchy-settings, omarchy-dev, omarchy-settings-dev, and macbook8-spi-pxa2xx-nodma-dkms (whose url= is the project homepage — its sources are local).

Deliberately not touched

  • source= git URLs in all four omarchy packages. They fetch fine through the redirect, and retargeting a package's fetch URL seemed like a packager's call rather than a drive-by. Nothing reads url=, and helpers/package-metadata.sh derives its git URL from source=, so the two are independent.
  • bin/omarchy-release, bin/omarchy-pkgs, README.md, which also carry the old name.
  • Genuine Basecamp references: helpers/basecamp-notifier.sh, pkgbuilds/basecamp-cli/, pkgbuilds/once-bin/, the README chatbot URL.
  • No pkgver/pkgrel bump, matching how content-only commits are handled here; the pinned pair picks this up at the next release cut.

Known related staleness

The omacom-io org was renamed to omacom as well (omacom-io/omarchy-pkgs now redirects to omacom/omarchy-pkgs), so url= in dell-xps-touchpad-haptics, dell-xps13-sidecar-amps, omacalc, omacut, omarchy-audio-tuner, omarchy-fish, omarchy-zsh, omawrite and ttfx is stale the same way. Left out to keep this to one rename — happy to fold it in or send a follow-up, whichever you prefer.

Tests

  • makepkg --printsrcinfo before/after for all five packages: the only differing line is url =.
  • bash -n on all five PKGBUILDs.
  • The four self-tests CI runs (sync-upstream, sync-rebuilds, omarchy-pkgs, omarchy-release) pass. tests/build-isolation.sh uses synthetic fixtures and exercises bin/build/helpers/, none of which are touched here.

🤖 Generated with Claude Code

https://claude.ai/code/session_012ksH6owbThaY5cXqmyNzXg

The repo moved from basecamp/omarchy to omacom/omarchy. Clones and browser
traffic follow the redirect, so nothing is broken — this just points the
metadata at the canonical location.

BUG_REPORT_URL is the user-visible one: it is written into the os-release
shipped to /etc on install and upgrade (except on Apple Silicon, where the
.install keeps the Arch Linux ARM configuration).

Only url= and BUG_REPORT_URL are touched. The source= git URLs are left alone
deliberately — they fetch correctly through the redirect, and retargeting a
package's fetch URL felt like a packager's call rather than a drive-by. Nothing
in bin/ or helpers/ reads url=, and helpers/package-metadata.sh derives its git
URL from source=, so the two are independent.

bin/omarchy-release, bin/omarchy-pkgs and README.md also still carry the old
name; happy to follow up there if wanted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ksH6owbThaY5cXqmyNzXg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant