Updates fail: "The repository does no longer have a Release file"

jackster · May 3rd 2021

Since last night I have been getting these emails from my OMV installation (4.1.36-1) and I get the same errors in the webGUI Update Management:

Code

E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch Release' does no longer have a Release file.
E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis-plex stretch Release' does no longer have a Release file.
E: The repository 'https://dl.bintray.com/openmediavault-plugin-developers/arrakis-docker stretch Release' does no longer have a Release file.

Now the issue obviously is that the repo no longer has the requested Release files. Is there another repo I can use to fix this and which file(s) do I need to update? Thank you in advance

ryecoaaron · May 3rd 2021

omv-extras repos moving to github

I never update the omv 4.x version of omv-extras to point to the new github repos because I think everyone should upgrade to a supported version.

jackster · May 3rd 2021

So there is nothing else I can do except upgrade to OMV5?

ryecoaaron · May 3rd 2021

Quote from jackster

So there is nothing else I can do except upgrade to OMV5?

Did you read the other post? You can manually update your repos and add the new signing key if you insist on staying on OMV 4.x. Why do you need to stay on the unsupported version?

There are upgrade scripts - Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5)

jackster · May 3rd 2021

Quote from ryecoaaron

Did you read the other post? You can manually update your repos and add the new signing key if you insist on staying on OMV 4.x. Why do you need to stay on the unsupported version?

There are upgrade scripts - Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5)

Thanks, I did read the post but I didn't find/understand the necessary information needed to update my repos. I followed the link at https://wiki.omv-extras.org/ to OMV-Extras.org Plugin and tried the steps mentioned there but it did not work, and I saw nowhere what I should update my repos to or how to actually do it.

In any case I agree it's best to the upgrade route. I have been putting it off because installing OMV4 was quite a lot of work with a lot of issues and I'm afraid I'll have the same problems again. Oh well, I guess I'll just have to bite the bullet and try the script

stickynickel · May 3rd 2021

Quote from ryecoaaron

Why do you need to stay on the unsupported version?

I can't speak for anyone other than myself, but I've been working 15 hour days for the last year plus and just don't have the time to run through the upgrade process (using the scripts) and work through fixing whatever fails or doesn't complete successfully. My server has been 100% critical for the other 4 members of my household since they can't get out .

ryecoaaron · May 3rd 2021

Quote from jackster

how to actually do it.

It isn't documented anywhere. My goal was to get people to update. If I documented it, I might as well update the 4.x plugin. The remove the omv-extras repos since there won't be any updates. sudo rm /etc/apt/sources.list.d/omv-extras-org.list

Quote from stickynickel

I can't speak for anyone other than myself, but I've been working 15 hour days for the last year plus and just don't have the time to run through the upgrade process (using the scripts) and work through fixing whatever fails or doesn't complete successfully. My server has been 100% critical for the other 4 members of my household since they can't get out .

This doesn't break your server. Just remove the file above.

ryecoaaron · May 3rd 2021

And no matter what, I can't put anything in the bintray repos (since they no longer exist - not my fault) to make an easy update.

bash0r · Jul 8th 2021

Has anyone managed to get OMV4 to work with the new omv-extras github repo?

Is it enough to use the omvextras.list from OMV5? I am not sure what „adding the signing key“ actually means

I hope someone else has already succeeded.

//EDIT:

pcon has obviously answered my question in this thread:

omv-update: failed to fetch ...

ryecoaaron · Jul 8th 2021

Quote from bash0r

Has anyone managed to get OMV4 to work with the new omv-extras github repo?

Uh, yes. I upgraded an OMV 4 box last night.

Quote from bash0r

Is it enough to use the omvextras.list from OMV5?

Nope.

Quote from bash0r

adding the signing key“ actually means

Every repo needs a signing key. I changed it when I moved the repos to github.

Quote from bash0r

pcon has obviously answered my question in this thread:

Which he got from the pinned thread in this same forum that you posted on.

Participate now!