Re: Bug#1134655: ITP: forge -- Go library and CLI for working with git forges. Supports GitHub, GitLab, Gitea/Forgejo, and Bitbucket Cloud through a single interface.

Simon Josefsson <[email protected]> Tue, 28 Apr 2026 11:26:01 +0200

Newsgroups	gmane.linux.debian.devel.general
Message-ID	<[email protected]>

> > I'm not sure how important the /usr/bin/forge tool from the 'snap'
> > package is, and if it is possible to rename that, and asked
> > upstream
> > about it:
> > 
> > https://github.com/KorfLab/SNAP/issues/24
> > 
> > Solving that wouldn't really solve the problem with the git-pkg-
> > forge
> > package using a generic name, but it may improve things anyway. 
> > The
> > same arguments about /usr/bin/forge appears to be true for the
> > existing
> > 'snap' package too, unless I'm missing something.
> 
> snap doesn't actually install /usr/bin/forge, right?  It can just be
> used to install a snap which occupies /usr/bin/forge?

No, I'm talking about the 'snap' source package:

https://tracker.debian.org/pkg/snap

It builds a binary package 'snap' that provides /usr/bin/forge:

https://packages.debian.org/sid/amd64/snap/filelist

/Simon

> 
> In that case it's not clear that Policy cleanly applies but I would
> be
> in favour of interpreting Policy broadly here.

signature.asc (application/pgp-signature, 1.2 KB)