I have reported problems installing the new Fedora 35 templates late last week [1] - and - also reported in the thread, that the ‘in-place upgrade’ of my system from 4.0 to 4.1 was only two weeks ago.
One additional thing that I noticed today, is that a dom0 update does not install any new packages - but - for the second(?) time only deletes 14 (?) packages.
Yesterday I was not able to collect the precise info from the Update VM, but today I succeeded. - Here’s the output:
[vr@dom0 ~]$
[vr@dom0 ~]$ sudo qubes-dom0-update --clean --console --show-output
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time…
warning: Converting database from bdb_ro to sqlite backend
25 files removed
Fedora 32 - x86_64 5.2 MB/s | 70 MB 00:13
Fedora 32 - x86_64 - Updates 4.1 MB/s | 30 MB 00:07
Qubes Dom0 Repository (updates) 2.0 MB/s | 3.8 MB 00:01
Last metadata expiration check: 0:00:02 ago on Tue May 31 07:48:22 2022.
Dependencies resolved.
> > > I've performed the same task today - and - the same 14 packages were
> > > removed again ...
> > >
> > > So it's clear now that something went wrong with my 'in-place upgrade'
> !
> > >
> > > Anything that I could try, beside a completely fresh installation of
> Qubes
> > > OS R4.1 ?
> >
> > I've had similar issues:
> > After 4.1 upgrade, dom0 doesn't update · Issue #7503 · QubesOS/qubes-issues · GitHub
> >
> > Maybe try some of the ideas suggested there?
>
> The Python 2 packages should be safe to remove, unless I have missed
> something.
>
It's unclear to me, why I should ...
If I would manually delete those packages, would they not get re-installed
the next day?
In dom0, this is leftover cruft from R4.0. It serves no purpose in
R4.1. My R4.1 dom0 does not even have a Python 2 interpreter.
Or asked differently:
If they are not needed in R4.1 / Fedora 32 for dom0, why have they been
included in the first place?
Not sure.
- --
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab