Re: Request for sponsorship my debian-packages on mentors
Hi Otto and Andrew,
I've uploaded the following 3 packages to go-team, created branches
and tags, and made a MR for merging into debian/sid:
https://salsa.debian.org/go-team/packages/golang-github-marusama-semaphore/-/merge_requests/1
https://salsa.debian.org/go-team/packages/golang-github-bitfinexcom-bitfinex-api-go/-/merge_requests/1
https://salsa.debian.org/go-team/packages/golang-github-bradleyfalzon-ghinstallation/-/merge_requests/1
P.S. For golang-github-marusama-semaphore, I couldn't rename the main
branch to upstream and make it protected, and make the debian/sid
branch the default, because I first moved the repository out of my
space and then started working on its branches.
ср, 11 мар. 2026 г. в 19:58, Otto Kekäläinen <otto@debian.org>:
>
> Hi Mikhail and Andrew,
>
> ...
> > > Should I ultimately use flight-deck or upload repositories from my
> > > space to go-team? I tried creating repositories through the
> > > flight-deck website, but I got the error "Failed to create merge
> > > request: failed to create branch: GitLab API error (403 Forbidden):
> > > 403 Forbidden." Even though I created a personal access token and set
> > > the scopes read_user, read_repository, read_registry, read_api,
> > > write_repository, api, self_rotate, and write_registry.
> >
> > ^ Otto, any idea?
>
> Arthur fixed this today.
>
> > > So far, I've been able to upload the golang-github-marusama-semaphore
> > > package from my space to go-team.
> > > Was this the right decision?
> >
> > Now I can see your package on
> > https://salsa.debian.org/go-team/packages/golang-github-marusama-semaphore
> >
> > Please set default branch correctly.
> > Please update the branch layout according to DEP14.
> >
> > If would be nice if you can send merge request after initial
> > commit(from dh-make-golang) and request for review.
>
> Mikhail: For reference, you can see at
> https://salsa.debian.org/go-team/packages/golang-github-kataras-pio/-/merge_requests/1
> or https://salsa.debian.org/go-team/packages/billy/-/merge_requests/1
> how Leonardo submitted a MR with the initial packaging and we have
> been able to conduct a review there using the GitLab Merge Request
> facilities that track each comment, new version, CI status etc
Reply to: