Error upgrading zorin 16 to 17 (stable-jammy Release' does not have a Release file)

Im unable to update to Zorin 16 using the upgrade Zorin application.
it seems to be unable to find a Ubuntu stable release.
Do I just have to upgrade some packages?
Any ideas what could cause this?
This is my error log:

[CHECKING] Started
[CHECKING:Validating Upgrade Attempt] Started
[CHECKING:Validating Upgrade Attempt] Completed
[CHECKING:Checking Filesystem] Started
[CHECKING:Checking Filesystem] Completed
[CHECKING:Restarting Apt] Started
[CHECKING:Restarting Apt] Completed
[CHECKING:Simulating Flatpak Transaction] Started
[CHECKING:Simulating Flatpak Transaction] Completed
[CHECKING:Processing Apt Repos] Started
[CHECKING:Processing Apt Repos] Completed
[CHECKING:Updating Apt Repos] Started
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Fatal Error: { error-repo-download-failed: E:The repository 'https://download.mono-project.com/repo/ubuntu stable-jammy Release' does not have a Release file. }
[CHECKING:Updating Apt Repos] Failed
[CHECKING] Failed
[CHECKING:Restoring System] Started
[CHECKING:Restoring System] Completed

Yes, I have the same issue, this is the error output after the "retrying" lines:

[CHECKING:Updating Apt Repos] Fatal Error: { error-repo-download-failed: W:Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386', E:The repository 'Index of /repo/ubuntu stable-jammy Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target Packages (main/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target Translations (main/i18n/Translation-en_GB) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target DEP-11-icons-small (main/dep11/icons-48x48.tar) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target DEP-11-icons (main/dep11/icons-64x64.tar) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target DEP-11-icons-hidpi (main/dep11/icons-64x64@2.tar) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13, W:Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/zorin-upgrader-simulate.list:1 and /etc/apt/sources.list.d/zorin.list:13 }
[CHECKING:Updating Apt Repos] Failed

..Are these packages that could be "ring-fenced", or could they be removed manually to allow the upgrade? Don't press me on this.. I have no idea what I'm taking about... :smiley:

I think the whole Repo is the Problem:

This is the Name of the Repo. I don't know if You need this but You could delete it, make a sudo apt update && sudo apt upgrade and then try the Zorin 17 Upgrade again.

1 Like

..Noticing that I had the Mono repository myself, I followed your suggestion, which seems to have cleared out the error-log quite a bit, but a fail -

[CHECKING] Started
[CHECKING:Validating Upgrade Attempt] Started
[CHECKING:Validating Upgrade Attempt] Completed
[CHECKING:Checking Filesystem] Started
[CHECKING:Checking Filesystem] Completed
[CHECKING:Creating Necessary Files] Started
[CHECKING:Creating Necessary Files] Completed
[CHECKING:Adding GPG Keys] Started
[CHECKING:Adding GPG Keys] Completed
[CHECKING:Restarting Apt] Started
[CHECKING:Restarting Apt] Completed
[CHECKING:Simulating Flatpak Transaction] Started
[CHECKING:Simulating Flatpak Transaction] Completed
[CHECKING:Processing Apt Repos] Started
[CHECKING:Processing Apt Repos] Completed
[CHECKING:Updating Apt Repos] Started
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Fatal Error: { error-repo-download-failed: }
[CHECKING:Updating Apt Repos] Failed
[CHECKING] Failed
[CHECKING:Restoring System] Started
[CHECKING:Restoring System] Error: { error-repo-download-failed: }
[CHECKING:Restoring System] Completed

..Just putting this out for general consumption; any info regarding which repo might be buggering things up would be gratefully received...

Yes, that is for Mono. If a user added the Mono repository and the maintainer for Mono has not created a Jammy release file, this can be seen.

This is the same as if a user of Zorin OS 17 added the Mono repo, then ran sudo apt update when that repo lacks a Jammy release file.

Have you completely purged Mono and removed any repositories for Mono?

1 Like

Did you only unmark the Repo in the List or did you complete delete the Repo? And when You delete the Repo: How did You delete it?

Thanks for your input.. Yeah, I initially only removed the repo (D'uh!), but them removed mono using " sudo apt remove mono-devel", however still no joy on the upgrade front -

[CHECKING] Started
[CHECKING:Validating Upgrade Attempt] Started
[CHECKING:Validating Upgrade Attempt] Completed
[CHECKING:Checking Filesystem] Started
[CHECKING:Checking Filesystem] Completed
[CHECKING:Creating Necessary Files] Started
[CHECKING:Creating Necessary Files] Completed
[CHECKING:Adding GPG Keys] Started
[CHECKING:Adding GPG Keys] Completed
[CHECKING:Restarting Apt] Started
[CHECKING:Restarting Apt] Completed
[CHECKING:Simulating Flatpak Transaction] Started
[CHECKING:Simulating Flatpak Transaction] Completed
[CHECKING:Processing Apt Repos] Started
[CHECKING:Processing Apt Repos] Completed
[CHECKING:Updating Apt Repos] Started
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Retrying
[CHECKING:Updating Apt Repos] Fatal Error: { error-repo-download-failed: }
[CHECKING:Updating Apt Repos] Failed
[CHECKING] Failed
[CHECKING:Restoring System] Started
[CHECKING:Restoring System] Error: { error-repo-download-failed: }
[CHECKING:Restoring System] Completed

..So not sure wot's missing now; I've send this in as an error report, so hopefully it will assist the dev team...

Take a Look in the sorces.list.d Folder if there are Files from this Mono Repo and delete them. BUT BE CAREFUL: Look 2 or 3 times before You delete something. When you delete the wrong Stuff you could have even more Trouble. Then You should look in the keyrings Folder and the trusted.gpg.d Folder too if there are Files form this Repo. Here is the same: BE CAREFUL!

When You did that open the Terminal and type sudo apt update to update the Sources. And then You could try it again.

Another Solution would be: Save Your Data on an external Drive and make a fresh Install of Zorin 17.

Thanks, I'll proceed.. cautiously. I wanted to avoid the "fresh install" malarky as I have a quite a number of packages I use that I'd have to re-install. One thing that occurred to me is that I have both back-ups and "Timeshift" back-ups, the latter I took as I believe it allows packages to be re-instated, however, would I be able to do this if the Timeshift image was taken with the previous OS verson? Anywho, I'll have a rummage as you suggest and see what happens...

UPDATE: I've looked in sources.list.d and trusted.gpg.d and there's no entries/mention of anything with "mono" in it. However in Synaptic, I see all these:


...plus a load of "libmono..." entries. Should I remove these, also? This Mono stuff sticks like a bogey to a blanket, doesn't it? :smiley:

1 Like

To be honest I don't know. I would think that a Z16 Back Up would not work with Z17 because there are different Systems. But that are only my Thoughts. I don't know it.

If these Mono Stuff belongs to the Mono Thing what do You had installed I would say Yes. The libmono ... A little bit difficult. When You uninstall it You should look if it deletes something with it what could be important for the Zorin System. Because when You uninstall the wrong Stuff ... that could be bad.

Thanks again... I have the following listed in Synaptic as "broken dependencies":


..when I try to fix them (so I can "start again"), I get the following messages:
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
..looks like a full re-install might be on the cards, but it's a bit disappointing, I'd waited for the upgrader to become live, and clicked it with great enthusiasm, but heigh-ho... I think the most annoying thing is that I believe Mono was installed to support running something under Wine, but that never worked either..

Thanks again for your suggestions..

1 Like

Have you tried

sudo apt --fix-broken install

2 Likes

Sorry that I wasn't a great Help. You can try the Command from @Aravisian. Maybe that helps. And if not ... See it like this: When You make a fresh Install You are lose old File-Ballast and have then a clean System.

No indeed, thanks for taking the time to reply - all info gratefully received, and you highlight alternatives to try...

1 Like

Thanks for that.. I ran this, then the suggested follow on "sudo apt autoremove" and all the Mono packages and twiddly-bits were expunged. Mmm.. expunged.. Where was I? Oh yeah, then I tried the upgrader again, but I still get this at the bottom of the logfile:

[CHECKING:Updating Apt Repos] Fatal Error: { error-repo-download-failed: }
[CHECKING:Updating Apt Repos] Failed
[CHECKING] Failed
[CHECKING:Restoring System] Started
[CHECKING:Restoring System] Error: { error-repo-download-failed: }
[CHECKING:Restoring System] Completed

So I dunno what it can't download. Maybe I'm just looking at a reinstall... Heigh-ho..

Did you made after the autoremove a sudo apt update && sudo apt upgrade for refreshing the Sources and look if there some Updates?

God! It's just "amateur night" with me.. Shoulda thought of that.. Anywho, I dunnit and same error on the upgrader. Time for me to stop bugging people and just do a full reinstall, methinks, altho' I'm intrigued as to why it won't work through the upgrader, and mebbe all this will help refine the tool...

1 Like

We may need to check your sources.list and sources.list.d and see which repo is giving you trouble.

ls /etc/apt/sources.list.d

cat /etc/apt/sources.list

This what I got -
sources.list.d:
audio-recorder-ubuntu-ppa-focal.list
audio-recorder-ubuntu-ppa-focal.list.save
berglh-ubuntu-pulseaudio-a2dp-focal.list
berglh-ubuntu-pulseaudio-a2dp-focal.list.save
brave-browser-release.list
brave-browser-release.list.save
gencfsm-ubuntu-ppa-focal.list
gencfsm-ubuntu-ppa-focal.list.save
google-chrome.list
google-chrome.list.save
mozillacorp-ubuntu-mozillavpn-focal.list
mozillacorp-ubuntu-mozillavpn-focal.list.save
zorin.list
zorin.list.save
zorinos-ubuntu-apps-focal.list
zorinos-ubuntu-apps-focal.list.save
zorinos-ubuntu-drivers-focal.list
zorinos-ubuntu-drivers-focal.list.save
zorinos-ubuntu-patches-focal.list
zorinos-ubuntu-patches-focal.list.save
zorinos-ubuntu-stable-focal.list
zorinos-ubuntu-stable-focal.list.save

sources.list content:

These may be causing the issue, since their addition is done by adding the key and the repo rather than by using apt-add-repository