-
Notifications
You must be signed in to change notification settings - Fork 0
Builder logic should pin upstream dependencies #14
Comments
Documenting a few research notes from discussion with @emkll. Would expect a patch like this to resolve (but it doesn't):
There are relevant vars such as |
I can reproduce the error, the dependency came via QubesOS/qubes-linux-utils@99d87c2 . @marmarek suggested to wait until QubesOS/qubes-linux-utils@99d87c2 lands into qubes-utils 4.0.29 and there is one dependency issue to be fixed. |
The problematic version (1.2.9) is only in testing repository, do you have |
Thank you both, that's very helpful guidance.
@marmarek No, we don't! However, I'm definitely getting the 1.2.9 version in the local chroot when building. If copy the contents of
And that 1.2.9 version is pulled in via
But in a Debian10-based AppVM elsewhere on my machine, clearly that package is not in the stable repos, so clearly the build process is using test-only dependencies, despite lack of testing repos being enabled. Even after applying this patch:
and re-running |
Ok, by not working |
On the latest master branch, the
make template
operation fails:Inspecting that log file, we see:
It looks like newer upstream changes have broken our template build logic, so let's investigate. There may be overrides that we can place in
securedrop-workstation.conf
, or perhaps we should pin a submodule of the qubes-builder repo.Steps to reproduce
make template
./qubes-builder/build-logs/template-buster.log
, observe errorThe text was updated successfully, but these errors were encountered: