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?
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?
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
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.
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
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.
Hi Yaroslav,
Am Wed, Jan 25, 2023 at 10:05:03AM -0500 schrieb Yaroslav Halchenko:
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.
May be a bit late, but may be
apt install routine-update
is your friend. It also calls scripts that are used by Janitor.
is your friend. It also calls scripts that are used by Janitor.
Does it call deb-new-upstream as well? That's the one that mainly seems relevant here.
Does it call deb-new-upstream as well? That's the one that mainly seems relevant here.
I just learned about deb-new-upstream. Its parsing uscan manually but its not
very robust and I should probably switch to use deb-new-upstream.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 106:47:30 |
Calls: | 9,684 |
Calls today: | 5 |
Files: | 13,725 |
Messages: | 6,175,491 |
Posted today: | 1 |