Hi Chris,
On 3/22/25 18:43, Christopher Obbard wrote:
Upstream has changed the location from github to their own domain.
I believe the code is still hosted on github; just with a different
CNAME for al.essio.dev to point to their github pages location.
This means that all go source which originally imported
"github.com/alessio/shellescape" are now changing to
"al.essio.dev/pkg/shellescape" and thus do not build with this
package since the path has changed.
I wonder what the best way forward here is? Perhaps we should keep
the source package the same name (since its still hosted in the same
place on github) and provide symlinks in a separate binary package
named golang-al-essio-dev-shellescape ?
For now, in debos I have simply added a patch to modify the source
code to use the original import path.
I am happy to do the work here, just need some guidance on the right
way forward.
This case is referenced in the Debian Go Packaging policy [1] with an
example. The policy suggests to rename both the binary and source
packages and to install a symbolic link for compatibility.
Since the freeze for Trixie has started, maybe we can just keep the old
packages names for now, and add a symlink and the Provides for
compatibility for the new location, at least until after the release of
Trixie. What do you think?
Best regards,
Dylan
[1] https://go-team.pages.debian.net/packaging.html#_upstream_package_moves
