Updating recipe-repositories, magit and forge

[haji-ali]

In the current version of radian, we are one straight-pull-recipe-repositories away from things breaking because it seems that the git-commit package is no longer available in these repositories which is required by the version of magit that is in radian. Thus, updating the repositories requires updates to forge and magit for things to work again.

Is updating these packages on the agenda?

PS: I've done it in my local setup, but thought others might be running into similar issues.

[raxod502]

At present I don't have a timeline for when I upgrade packages in Radian, but given that the recipe repositories are in the lockfile as well, all this means is that when I or a contributor updates the versions, everything needs to be updated at the same time. This is always the case, though, as new versions of packages may require new versions of their dependencies, etc.

If you upgraded packages to new versions and find that they are working, I am always happy to merge updates.

[haji-ali]

Oh, I wasn't brave enough to update all packages, just the ones that broke after recipe repositories updates.

I can look into updating all packages and see if that breaks anything, but it will take me some time to report back.

[raxod502]

Partial upgrades are fine too, what matters is that functionality works.

[haji-ali]

I am trying to do this, but when I run straight-freeze-versions, I get errors in *straight-process* of the form (this is not the only repo).

$ cd ~/Documents/Projects/dotfiles/emacs/dot-config/emacs/.elocal/straight/repos/el-patch/
$ git merge-base --is-ancestor main origin/main

fatal: Not a valid object name origin/main

[Return code: 128]

$ cd ~/Documents/Projects/dotfiles/emacs/dot-config/emacs/.elocal/straight/repos/el-patch/
$ git --no-pager log --format\=\%h\ \%s origin/main..main

fatal: ambiguous argument 'origin/main..main': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

[Return code: 128]

any ideas why this might be happening?

[raxod502]

Not offhand, can you check the straight.el issue tracker and report there if it's not logged?

As a workaround, you can of course fix up the Git state manually or with a script in affected repositories.