On Fri, Apr 14, 2023 at 04:10:29PM +0200, qubes-li...@riseup.net wrote:
> Hi uman,
> thanks for your reply.
> 'unman' via qubes-users:
> > Exactly this issue arose on GitHub - it is, as you say, because you did
> > not update the qubes repository definition in timely way.
> > You can read the issue 
> > [here](https://github.com/qubesos/qubes-issues/issues/7865)
> > The resolution is to follow the steps in the upgrade script - courtesy
> > of Marek:
> > ```
> > The source of the problem is that in R4.1 we actually stopped shipping own 
> > duplicated xen packages, and are relying on those from official Debian 
> > repositories. But the upgrade path requires manual step because of that.
> > The in-place R4.0 -> R4.1 upgrade tool handle that automatically, but in 
> > case of manual upgrade, see this part:
> > https://github.com/QubesOS/qubes-dist-upgrade/blob/release4.0/scripts/upgrade-template-standalone.sh#L37-L72
> > ```
> Yes I know about this github ticket, I mentioned in my last email, but
> I have the impression that these step can not be used _after_
> running 'apt update; apt upgrade; apt dist-upgrade' anymore - which is the 
> situation I'm in.
> Is there also a way to recover a system after the 'apt upgrade' step happened 
> already?

I'd probably be rolling back most of your recent changes, and starting
again, after making sure that I have a decent backup of the qube in its
current state.
You need to roll back those packages, and -f should work for the
install. I have some old templates hanging about - if you can wait until
tomorrow I'll pull one and work through the process in the morning.

You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to