This is great! Good job.

>         Aside from the GitLab-side, we also need a .gitlab-ci.yml file
>         in the repository itself. I can bulk-commit these, along with
>         adding them to Files-Excluded in debian/copyright so that
>         upstream copies are discarded.

Please do. (it looks like the d/copyright thing won't be needed if you
can change the path to debian/gitlab-ci)

>     I suggest setting this path to “debian/gitlab-ci.yml” for our
>     repositories, so that we don’t need to mangle upstream’s
>     .gitlab-ci.yml and have all relevant files within the debian/


On 2018-01-28 09:35 AM, Michael Stapelberg wrote:
>     On Sat, Jan 27, 2018 at 11:21 PM, Michael Stapelberg
>     < <>> wrote:
>         With this feature place, the next step I’d like to implement is
>         a speculative package auto-updater: upon noticing the Debian and
>         upstream version have diverged, we could import the new version,
>         send a Merge Request, have the CI check for breakages and
>         (manually) merge and upload if no breakages are introduced.

That would be great.

Did you see the recent devscripts commit? #811565[1] was marked as pending.

We will be ale to use uscan to watch for new upstream versions. The tool
you are building could make use of this.

Maybe you want to contribute to this script:

It protects branches and create webhooks on all repositories in the
"packages" subgroup on salsa. We should add the debian/gitlab-ci.yml
config too so that we can just run the script and have all salsa
projects configured uniformly.

By the way, don't forget to update dh-make-golang too, so that new
repositories have the setting.



Alexandre Viau

Attachment: signature.asc
Description: OpenPGP digital signature

Pkg-go-maintainers mailing list

Reply via email to