Qubes 4 Debian Packages Question

[qube...@go-bailey.com]

Over the last two sets of Qubes specific updates, I've noticed that
while dom0 and the Fedora templates are showing new qubes related
packages, the debian templates aren't (template is one of the newer ones
installed after the apt security changes).

Other debian updates appear to  be getting updated so the issue appears
to be specific to the qubes related packages in the qubes repo.

I'm more of an rpm person so not overly familiar with how debian handles
its update process but looking at the sources list in the template, it
looks like the package list is being pulled from:

https://deb.qubes-os.org/r4.0/vm/dists/stretch/main/binary-amd64/

Looking at the list there, it appears that the list might be older as it
doesn't reflect the packages available at:

https://deb.qubes-os.org/r4.0/vm/pool/main/q/

For example, it appears that the latest package is:

qubes-gui-agent_4.0.22-1+deb9u1_amd64.deb

and previously:

qubes-gui-agent_4.0.21-1+deb9u1_amd64.deb

while the packages list

https://deb.qubes-os.org/r4.0/vm/dists/stretch/main/binary-amd64/Packages

has 4.0.20-1+deb9u1 as the latest listed package which might explain the
lack of debian updates.

Can some take a look to see if that is indeed the case? If so, can the
package list be updated? If not, any suggestions about what to check to
see why the qubes specific packages aren't updating in the debian template?

Thanks in advance.

[Chris Laprise]

On 3/21/19 3:48 PM, qube...@go-bailey.com wrote:
> Over the last two sets of Qubes specific updates, I've noticed that
> while dom0 and the Fedora templates are showing new qubes related
> packages, the debian templates aren't (template is one of the newer ones
> installed after the apt security changes).

I had noticed the relative lack of Debian updates, also. Thanks for
looking into the package status. Hopefully we'll get a simple answer.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

[unman]

The new packages are still in testing - you can confirm this by looking
at the list at:
https://deb.qubes-os.org/r4.0/vm/dists/stretch-testing/main/binary-amd64/Packages
There you'll see the latest versions.

The repository pool contains all available versions, but they are
separately indexed in the different package files.
If you want to test, edit the /etc/apt/sources.list.d/qubes-r4.list file
and enable the testing repo. Then you'll pick those new versions from
the pool. Please report back any issues you encounter.

unman

[qube...@go-bailey.com]

Thanks for the responses.

Perhaps I'm not following correctly but the testing Package list
mentioned at:

https://deb.qubes-os.org/r4.0/vm/dists/stretch-testing/main/binary-amd64/Packages

has the:

qubes-gui-agent_4.0.22-1+deb9u1_amd64.deb

package in it but doesn't appear to have:

qubes-gui-agent_4.0.21-1+deb9u1_amd64.deb

in it.

Since the latest in the other list is:

qubes-gui-agent_4.0.20-1+deb9u1

would that still imply that the current list is not reflecting the most
recent non testing package, in this case, 4.0.21-1? Or does that
indicate that 4.0.21-1 wasn't released for some reason?

Thanks.

[unman]

Quick check on the tags show 4.0.21 on Mar 8th: with a bug fix on Mar11,
and 4.0.22 tagged on 21st.
So 4.0.21 never reached current because a significant bug was identified
in testing, and an updated version built. 22 will pass in to current in due course.

[qube...@go-bailey.com]

Thanks for the explanation!

[qube...@go-bailey.com]

Try running the commands separately:

sudo qubesctl --skip-dom0 --templates state.sls update.qubes-vm

followed by:

sudo qubesctl --skip-dom0 --standalones state.sls update.qubes-vm

That worked on this end when I got the same error.

[Ulrich Windl]

Thanks!

>
>
>