Move Herdr to the herdr-git package - #7520
Draft
omarchybot wants to merge 1 commit into
Draft
Conversation
The herdr package was built from an Omarchy fork of Herdr whose only divergence was three commits replaying an agent's CLI options when a session resumed. Upstream declined that work twice — from a contributor in herdrdev/herdr#2036 and from us in herdrdev/herdr#2614, closed in favour of an agent resume manifest meant to supersede it — so the fork bought one feature at the price of rebasing it onto upstream forever. omacom-io/omarchy-pkgs#170 drops the fork and builds from upstream master instead, which renames the package to herdr-git. Renaming means the package list has to name the new package, and existing installs need a nudge: herdr-git declares replaces, but pacman honours that only during a full sysupgrade, which leaves anyone who updates another way holding the old name. The migration installs herdr-git in one transaction rather than dropping herdr and adding it back, because the session is usually running inside herdr and an install that failed between the two would leave the machine with no terminal. That needs --ask 4, since --noconfirm answers "no" to the conflict herdr-git raises against the installed herdr — the same reason omarchy-upgrade-to-quattro passes it. It ends by asserting the package is really there, because pacman does not always exit non-zero when an install fails and a migration that marked itself done would leave the machine on the fork for good. Nothing here can merge before herdr-git is published to the package mirrors: until then the migration fails, stays pending and retries, which is safe but noisy. 🤖 Generated by Opus 5 in Claude Code. Reviewed by Codex XHigh. Co-Authored-By: Codex XHigh <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
herdrpackage was built from an Omarchy fork of Herdr whose only divergence was three commits replaying an agent's CLI options when a session resumed. Upstream declined that work twice — from a contributor in herdrdev/herdr#2036, and from us in herdrdev/herdr#2614, closed in favour of an agent resume manifest meant to supersede it — so the fork bought one feature at the price of rebasing it onto upstream forever. omacom-io/omarchy-pkgs#170 drops the fork and builds from upstream master instead, which renames the package toherdr-git.Packaging upstream's v0.8.0 release rather than master was the other way out, and it regresses more than the fork gained: configurable outer pane borders, direct pane resize keybindings, move tab keybind actions, centered tab labels and outer terminal window title sync all merged upstream after that tag, so the release predates five features Omarchy contributed.
The rename means the package list has to name the new package, and existing installs need a nudge.
herdr-gitdeclaresreplaces, but pacman honours that only during a full sysupgrade, so anyone who updates another way keeps the old name.The migration installs
herdr-gitin one transaction rather than droppingherdrand adding it back, because the session is usually running inside Herdr and an install that failed between the two would leave the machine with no terminal. That needs--ask 4:--noconfirmanswers "no" to the conflictherdr-gitraises against the installedherdr, which is the same reasonomarchy-upgrade-to-quattropasses it. It ends by asserting the package is really present, because pacman does not always exit non-zero when an install fails, and a migration that marked itself done would leave the machine on the fork for good.Draft on purpose: nothing here can merge before
herdr-gitis published to the package mirrors. Until then the migration fails, stays pending and retries — safe, but noisy. Two steps outside this repo have to land first: publishherdr-gitfor every architecture, thenrepo-removethe oldherdrfrom each mirror's database, which deleting its PKGBUILD does not do on its own.omarchy-herdris still published today for exactly that reason, orphaned by the previous rename.🤖 Generated by Opus 5 in Claude Code. Reviewed by Codex XHigh.