Hi Colin,

Am Thu, Mar 07, 2024 at 05:06:48PM +0000 schrieb Colin Watson:

https://freexian-team.pages.debian.net/debusine/

https://meetings-archive.debian.net/pub/debian-meetings/2023/MiniDebConf-Cambridge/debusine.webm

Looks good.

https://debusine.debian.net/

Jut created a token and run the first task (creating a chroot).

While for the moment Debusine may seem like a less polished version of
Salsa CI, it has very different goals,

Speaking about Salsa CI: I would like to do what Enrico mentioned to
somehow re-run building some Salsa commit using sbuild and (optionally)
the autopkgtest on the result.

https://freexian-team.pages.debian.net/debusine/tutorials/getting-started-with-debusine.html

This doc brought me just to creating the chroot.

Please give us feedback, positive and negative; we want to make this a
tool that Debian contributors use efficiently and pleasantly.

I'd love to but seems I need some kickstart help.

Thanks a lot to all who worked on this
Andreas.

--
http://fam-tille.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Mar 08, 2024 at 10:21:30AM +0100, Andreas Tille wrote:

Am Thu, Mar 07, 2024 at 05:06:48PM +0000 schrieb Colin Watson:

While for the moment Debusine may seem like a less polished version of Salsa CI, it has very different goals,

Speaking about Salsa CI: I would like to do what Enrico mentioned to
somehow re-run building some Salsa commit using sbuild and (optionally)
the autopkgtest on the result.

We don't have direct support for building from git yet. Ian asked about
that in Cambridge, and it's certainly a good idea though not currently
in the funded plan - Raphaël gave a more detailed response starting from around 30:27 in the mini-DebConf video.

However, you can always build a source package from the commit in
question, upload it to debusine, then start creating work requests from
there.

(This will become more interesting once we have collections and
workflows properly in place; that will allow doing things like running autopkgtests of all the reverse-dependencies of a change you're
experimenting with.)

https://freexian-team.pages.debian.net/debusine/tutorials/getting-started-with-debusine.html

This doc brought me just to creating the chroot.

It goes on to describe "debusine import-debian-artifact", which you can
use to upload packages to debusine, and "debusine create-work-request
sbuild" based on a chroot you've created.

We're definitely still at the stage where you have to poke around quite
a bit to figure out exactly how to submit jobs, though.

Thanks,

--
Colin Watson (he/him) [cjwatson@debian.org]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Colin,

thank you for this project, it looks very interesting. Would you also
support running ratt there? For some packages ratt often fails on my
local machines due to RAM constraints.

Best regards,
Martin

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE/VqS9CCBN6S2aAs9UqV8/OE9ZX0FAmXsS3cACgkQUqV8/OE9 ZX31kA/+L5TAKYEZ6iXD7KDuzvHokxNK3HSeyEaRWIIBKVAWne9Wh/uC/AV25qSV 1WdCRLQa5d8IhThXGb2Wxy9eBzJcWHiitorkVszgvPu2NgtbPWMyIQ1KERoWpUh7 8y/JZuw5/RHzbF1E1xw3MWIIUVYz4y2evUu6tY5SlSWpXkHgr3qmygR7kB8KuYnB FIzZB3BsFHxm8nx7RQ6F2j0yWw/8H9vLjlqF0Uc/cwBR/uEkZiZMVkAP/ATYxl9k vX9Ll0I3QMVRUw/1roQaCiDyCa6CrAi+EvFj/TR2ZmjXZJGPAJGfvOEleyvuNtzP 5uma9FumdZbY3N6YWuxmURqeSR32hbgUS25AW4lfSzd6+o6fz/Dapdqw56n177yz CDk9Uxk4I9Fv2xQTanE7l2nRP+ujKOqDSblI/cWHHz+hBnW13yXMHmaQ4pagcoyS 0r06HLPuvpkfUhpD8hmiUIC3sPqqOKYX+a8qZhT/mUf3G5FaavidHeMex0ziQ5Pd MNArIqh6di5AN9hIcrhuTKgkH1dzJ2kdeqfYfKrEgLtJTx+wvkqtFva8bDqEoyGp 6EfrdfGF3n8/bA0EzEONy+Jmnds33zAtvNAgKyrsrMdTybEytfWb8gnHxI0dzcpM kVAE5o/fxjBIK5GvxczPtiz7Z9EiKMhbYIE/JrCy5iMHCAq54og=
=d0QN
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Martin (2024.03.09_11:43:54_+0000)

thank you for this project, it looks very interesting. Would you also
support running ratt there? For some packages ratt often fails on my local machines due to RAM constraints.

We are building out the pieces that will lead to being able to
reimplement ratt within Debusine.

Running ratt as a single debusine job wouldn't make as much sense as
running a single build for each changed reverse dependency.

We just landed support for sbuild's --extra-package= argument [0], which
is the building block needed for ratt-style builds. I intend to script something to schedule all the builds for a new reverse dependency, soon.
I have reverse-dependencies I want to test.

[0]: https://salsa.debian.org/freexian-team/debusine/-/issues/320

Stefano

--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Mar 09, 2024 at 01:43:18PM +0000, Stefano Rivera wrote:

Hi Martin (2024.03.09_11:43:54_+0000)

thank you for this project, it looks very interesting. Would you also support running ratt there? For some packages ratt often fails on my local machines due to RAM constraints.

We are building out the pieces that will lead to being able to
reimplement ratt within Debusine.

Running ratt as a single debusine job wouldn't make as much sense as
running a single build for each changed reverse dependency.

Indeed. The high-level goal for our second STF milestone is to add
generic support for this sort of automatic orchestration of QA tasks
across many packages, and we're currently working on the essential
building blocks for this. https://salsa.debian.org/freexian-team/debusine/-/milestones/9 has
details, especially anything to do with "collections" or "workflows".

ratt as such isn't explicitly one of the funded developers' goals, and
we'll probably probably start with automating runs of lintian and
autopkgtest. However, I expect in a couple of months we'll have enough
pieces to make it possible for Debian developers to build something like
ratt using debusine - probably in a "some assembly required" kind of way
at first.

--
Colin Watson (he/him) [cjwatson@debian.org]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Colin,

Am Fri, Mar 08, 2024 at 11:41:27AM +0000 schrieb Colin Watson:

Speaking about Salsa CI: I would like to do what Enrico mentioned to somehow re-run building some Salsa commit using sbuild and (optionally)
the autopkgtest on the result.

We don't have direct support for building from git yet. Ian asked about
that in Cambridge, and it's certainly a good idea though not currently
in the funded plan - Raphaël gave a more detailed response starting from around 30:27 in the mini-DebConf video.

Well, I've heard that question (would have had the same when watching
the talk). I was hoping that the time between the talk and the
annoucement here would have brought something new. ;-)

However, you can always build a source package from the commit in
question, upload it to debusine, then start creating work requests from there.

(This will become more interesting once we have collections and
workflows properly in place; that will allow doing things like running autopkgtests of all the reverse-dependencies of a change you're
experimenting with.)

This kind of stuff - something like "`rott` but not on my local machine"
would be the most interesting thing for me to use debusine.

https://freexian-team.pages.debian.net/debusine/tutorials/getting-started-with-debusine.html

This doc brought me just to creating the chroot.

It goes on to describe "debusine import-debian-artifact", which you can
use to upload packages to debusine, and "debusine create-work-request
sbuild" based on a chroot you've created.

We're definitely still at the stage where you have to poke around quite
a bit to figure out exactly how to submit jobs, though.

Thank you for your patient explanation
Andreas.

--
http://fam-tille.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Mar 11, 2024 at 09:28:06PM +0530, Praveen Arimbrathodiyil wrote:

cat > work-request-ruby-semver-dialects.debusine << END
build_components:
- any
- all
host_architecture: amd64
input:
source_artifact_id: 788
environment_id: 154
END

debusine create-work-request sbuild < work-request-ruby-semver-dialects.debusine
result: success
message: Work request registered on https://debusine.debian.net/api with id 155.
work_request_id: 155

log
https://debusine.debian.net/artifact/789/configure_for_execution.log

Your environment_id apparently refers to a debian:binary-packages
artifact, not a debian:system-tarball artifact. I think this is because
you gave it the work request ID of your mmdebstrap job rather than the
ID of the artifact it produced. Looking at https://debusine.debian.net/work-request/154/, you should try
"environment_id: 786" instead.

This sort of mistake is pretty easy to make right now with the low-level interface that we currently have. It'll be easier once we've done a bit
more work on collections, at which point debusine will have its own idea
of reasonable base tarballs to use for (e.g.) unstable amd64 builds and
won't need to be told manually.

--
Colin Watson (he/him) [cjwatson@debian.org]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)