Upgrade from Buster to Bullseye broken

[bishoptf]

What is the problem?

I have an older instance that for whatever reason today was offline, and I decided to upgrade from buster to bullseye and that broke Octoprint. I should have fully upgraded Octoprint before upgrading the OS and even make a backup but here I am. This is a raspbian image with Octoprint installed.

What did you already try to solve it?

I upgraded Octoprint from the command line and that completed but starting the service returns the following error:
"OctoPrint/venv/bin/octoprint", line 5, in
Dec 08 13:14:25 3dpi octoprint[474]: from octoprint import main
Dec 08 13:14:25 3dpi octoprint[474]: ModuleNotFoundError: No module named 'octoprint'

Have you tried running in safe mode?

Can't get that far, service not starting

Did running in safe mode solve the problem?

See above

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

WRITE HERE

Additional information about your setup

I have a directory in my home .octoprint that has all of my data just not sure how to migrate that old instance to a new one or continue using the old instance...

WRITE HERE

[bishoptf]

I have figured a few things out, this was installed on top of raspbian and it has been a few years ago. I have it running but need to figure out how to correct how it is installed and not sure how to correct. Looks like the octoprint binary is installed in .local and it works and I have a .octoprint directory that has printer profiles etc. Not sure best way to remove it from .local and have it installed in what I believe would be the normal directory....still poking and trying to figure this out.

[jneilliii]

see upgrade options section, step 2 is what you did?

OctoPrint tells me my Python environment is outdated and will soon no longer be supported, how do I upgrade?

See Python | endoflife.date I try my best to support Python versions for at least a year longer than their official EOL, or even more if the latest OctoPi requires that, but longer than that it's really not going to work anymore as the dependencies these days also stop supporting EOL versions faster than they used to, and that means that keeping things supported on a Python version that doesn't even get security fixes anymore means a TON of support overhead that simply doesn't work anymore if y…

[bishoptf]

There was a lot going on, not sure how I originally installed this many years ago. Raspbian install with Octoprint installed on top, still not sure exactly how it was working etc. I installed a new standalone version and updated python and I believe I finally have everything working again. At some point I need to just re-install from scratch which if I have had a backup would have probably taking me less time to get things working again, but I kept poking at it and working through each issue and I think I just have got it working like it was before. Probably should have just left it and saved it for another day, OS upgrade went fine but it was just Octoprint that I had an issue and I think most of that was how I upgraded the instance.

Thanks for the reply...