search

QubesOS / qubes-issues

The Qubes OS Project issue tracker
https://www.qubes-os.org/doc/issue-tracking/
535 stars 47 forks source link

Make it easier to find documentation for Qubes infrastructure #9473

Open runephilosof opened 2 weeks ago

runephilosof commented 2 weeks ago

New issue description

See comment https://github.com/QubesOS/qubes-issues/issues/9473#issuecomment-2379027806

I could not find a description in the qubes documentation of the package build flow, maybe a link to https://github.com/QubesOS/qubes-infrastructure should be somewhere in the docs.

Original issue description

Brief summary

I assume it is the repro warnings here https://gitlab.com/QubesOS/qubes-core-qubesdb/-/pipelines/1305030410/ that are keeping the succeeding debian repro from publishing to the package repositories

I noticed this because I need the new version of qubesdb to be published to the debian repositories to be able to update the kali-core template (python dependency version upgrade).

Steps to reproduce

Have a failing reproduction build for fedora while the reproduction build succeeds on debian

Expected behavior

Debian publishes. Fedora does not (actually I am in doubt about what is expected for the failing ones, since they are configured to allow failures)

Actual behavior

None of them go on to the next stages (tests and publish)

marmarek commented 2 weeks ago

are keeping the succeeding debian repro from publishing to the package repositories

Nope. Those are set with allow_failure: true (and that's why it's just a warning, not error) and are not blocking anything.

None of them go on to the next stages (tests and publish)

None of that applies to this package (we don't use gitlab for pushing to official repositories). It's relevant for few components that have extra tests.

I noticed this because I need the new version of qubesdb to be published to the debian repositories to be able to update the kali-core template (python dependency version upgrade).

Which specifically? The most recent version is 4.2.6 and it is in stable repositories already: https://github.com/QubesOS/updates-status/issues/4977

runephilosof commented 1 week ago

None of that applies to this package

Right, I see now.

https://github.com/QubesOS/updates-status/issues/4977

Thanks for the link. By searching for mentions of the qubesos-bot I found https://github.com/QubesOS/qubes-infrastructure, which explains how the package build flow works. I could not find a description in the qubes documentation of the package build flow, maybe a link to https://github.com/QubesOS/qubes-infrastructure should be somewhere in the docs.

runephilosof commented 1 week ago

I noticed this because I need the new version of qubesdb to be published to the debian repositories to be able to update the kali-core template (python dependency version upgrade).

Which specifically? The most recent version is 4.2.6 and it is in stable repositories already

I see now. I was confused by archlinux update to python <3.13, which is mentioned in the debian changelog. The kali-core template uninstalls python3-qubesdb, when you do apt full-upgrade, because 4.2.6 in Debian depends on python3 (<< 3.12). I guess python3-qubesdb needs to depend on 3.11 for stable Debian and 3.12 for Debian testing/unstable. Not sure how to do that.

marmarek commented 1 week ago

I guess python3-qubesdb needs to depend on 3.11 for stable Debian and 3.12 for Debian testing/unstable. Not sure how to do that.

That dependency is generated automatically during package build. I guess the package just needs a rebuild.

runephilosof commented 1 week ago

It would need to be built in a trixie (Debian testing) build environment in addition to bookworm (Debian stable)

marmarek commented 1 week ago

It would need to be built in a trixie (Debian testing) build environment in addition to bookworm (Debian stable)

Actually, are you sure your kali template uses qubes repo for trixie (check /etc/apt/sources.list.d/qubes-r4.list)? We do build packages for trixie already...