Re: automated CI on salsa to prepare MR for new upstream version
Hi Yaroslav,
On Wed, Jan 25, 2023 at 10:05:03AM -0500, Yaroslav Halchenko wrote:
> I just wanted to say Thank you for all the pointers! Overall, janitor
> looks great and the most advanced and seems already covering various
> aspects but might be a bit "too big to tune for our own use-case", so we
> might indeed pick up on ideas/implementations... we will see.
The janitor runs the "deb-new-upstream" command under the hood to make the
actual changes. You should be able to run that from e.g. CI. It tries to
do the right thing as much as possible without flags, but I'm happy to
add flags to allow tweaking its behaviour.
Alternatively, if the package is in Debian you could simply merge
the changes the Janitor has already published at a predictable
location (https://janitor.debian.net/git/<source-pkg> -b fresh-releases)
Cheers,
Jelmer
>
> On Sat, 21 Jan 2023, Andrej Shadura wrote:
>
> > Hi,
>
> > On Fri, 20 Jan 2023, at 17:01, Yaroslav Halchenko wrote:
> > > Dear Debian gurus,
>
> > > Lazy me would love to get automation going akin to the one in
> > > conda-forge (see e.g. [1]) -- whenever a new upstream is released
> > > (as could be detected with a run of uscan) the CI would
>
> > <...>
>
> > > Is there any package/tool which already does something like that on CI?
> > > Or may be you see some issues with such a procedure?
>
> > Not quite the same, but we have machinery to update packages from Debian in Apertis:
> > https://gitlab.apertis.org/infrastructure/ci-package-builder/
>
> > Related scripts live here:
> > https://gitlab.apertis.org/infrastructure/apertis-docker-images/-/tree/apertis/v2024dev1/package-source-builder/overlay/usr/bin
> > https://gitlab.apertis.org/pkg/apertis-dev-tools/-/tree/apertis/v2024dev1/tools
> --
> Yaroslav O. Halchenko
> Center for Open Neuroscience http://centerforopenneuroscience.org
> Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
> WWW: http://www.linkedin.com/in/yarik
>
Reply to: