Steps to reproduce with opam 2.5.1 (narrowed down to a smaller commit range):
This works:
git clone https://github.com/ocaml/opam-repository && cd opam-repository
git checkout 142525538e5694742be38a5edaf7d3d6051acaf8
opam repo remove testbug --all
opam repo add testbug .
git checkout d9cabb4c55
opam update testbug
This fails:
git clone https://github.com/ocaml/opam-repository && cd opam-repository
git checkout '142525538e5694742be38a5edaf7d3d6051acaf8^'
opam repo remove testbug --all
opam repo add testbug .
git checkout d9cabb4c55
opam update testbug
Interestingly running opam update testbug again works then (but this doesn't help with the original issue I had).
Although updating directly from 142525538e5694742be38a5edaf7d3d6051acaf8^ to 142525538e5694742be38a5edaf7d3d6051acaf8 works too.
FWIW updating the default https remote works, it is just using a git remote that fails.
$ opam --version
2.5.1
$ git --version
git version 2.54.0
$ patch --version
GNU patch 2.8
Although it looks like opam processes the patch using an OCaml implementation of patch, so the bug might be there.
Steps to reproduce with opam 2.5.1 (narrowed down to a smaller commit range):
This works:
This fails:
Interestingly running
opam update testbugagain works then (but this doesn't help with the original issue I had).Although updating directly from 142525538e5694742be38a5edaf7d3d6051acaf8^ to 142525538e5694742be38a5edaf7d3d6051acaf8 works too.
FWIW updating the default https remote works, it is just using a git remote that fails.
Although it looks like opam processes the patch using an OCaml implementation of patch, so the bug might be there.