Develop repositories out of date.

[zapotah]

Describe the bug Develop repositories are out of date. Last release is 4.7.11 from mid december.

To Reproduce Steps to reproduce the behavior:

1. Use the repository

Expected behavior Expect to see ie. 4.11.6 at the time of writing in repo

System:

• Any Debian Linux

Ombi Version:

• 4.7.11

[github-actions[bot]]

Hi!
Thanks for the issue report. Before a real human comes by, please make sure you used our bug report format.
Have you looked at the wiki yet? https://docs.ombi.app/
Before posting make sure you also read our FAQ.
Make the title describe your issue. Having 'not working' or 'I get this bug' for 100 issues, isn't really helpful.
If we need more information or there is some progress we tag the issue or update the tag and keep you updated.
Thanks!
Ombi Bot.

[tidusjar]

What repository are you using?

[zapotah]

Both of the https://apt.ombi.app/develop and https://packagecloud.io/Ombi-app/Ombi-Dev/debian/ only have up to 4.7.11

[BastionNtB]

Just adding my two cents here, using the repo from the documentation.

echo "deb [arch=amd64 signed-by=/usr/share/keyrings/ombi-archive-keyring.gpg] https://packagecloud.io/Ombi-app/Ombi/debian/ jessie main" | sudo tee /etc/apt/sources.list.d/ombi.list echo "deb-src [arch=amd64 signed-by=/usr/share/keyrings/ombi-archive-keyring.gpg] https://packagecloud.io/Ombi-app/Ombi/debian/ jessie main" | sudo tee -a /etc/apt/sources.list.d/ombi.list

[Xarano-GIT]

Is any any news on this?

I've changed over to the stable repo for now which at least gives me 4.10.2 instead of 4.7.11, but I would love to be able to test out all the new versions again.

[fbayerx]

Can confirm the behaviour, develop is stuck on 4.7.11; switching to https://apt.ombi.app/master allowed updating to 4.10.2

Edit: This issue is problematic as neither 4.7.11 nor 4.10.2 contain a fix for #4502

[jayfromm]

I presume that https://github.com/Ombi-app/Ombi/issues/4560 was closed for being a duplicate. Fine by me but what's the resolution?

[BastionNtB]

I presume that #4560 was closed for being a duplicate. Fine by me but what's the resolution?

#4504 is still open because there isn't a resolution, and seeing this open since Feb... looks like whoever managed the repositories has left the building, and maybe they don't know how to update them or got locked out of the cloud repo? Just spit balling.

I might swap over to just pulling from git if that's the case though...

[tidusjar]

So basically, the apt repo, I have no idea how to maintain it and update it. It’s way over my head and I just don’t have the time to work it out.

The Ombi.Apt repo has a GitHub action that triggers the apt build and then publishes it. But that’s exceeded the storage for the repo, so stuff needed to be deleted out.

The plan was to move over to package cloud, but again, I’m in over my head with it.

[dotsam]

I opened https://github.com/Ombi-app/Ombi.Apt/issues/6 for this, as it looks like the current issue is to do with the way that the repo was cleared out leaving reference to files that were removed.

In the meantime, I've just cloned the Ombi.Apt repo and am manually building a .deb for myself with the gen_pack.py script.

[joshbgosh10592]

Glad to see I'm not the only one stuck in the past. I strongly prefer to use apt rather than manually installing packages because I always manage to screw something up.

[pax0707]

Same here.

[cyberjock]

Problem identified here as well. Someone asked me to look at his Ombi installation, and I found it still on the Dec 2021 (I think) version (4.7.11). He wanted me to upgrade him to the MySQL setup, but I'm going to have to wait due to this. I'd prefer to be on newer code than 2021 before proceeding further.

I suspect a significant number of installations of Ombi in the world are still on 4.7.11 because of this bug. Hopefully this gets fixed soon.

[tidusjar]

The package cloud repo has later code

On Sun, 5 Jun 2022 at 8:34 am, cyberjock @.***> wrote:

Problem identified here as well. Someone asked me to look at his Ombi installation, and I found it still on the Dec 2021 (I think) version (4.7.11). He wanted me to upgrade him to the MySQL setup, but I'm going to have to wait due to this. I'd prefer to be on newer code than 2021 before proceeding further.

I suspect a significant number of installations of Ombi in the world are still on 4.7.11 because of this bug. Hopefully this gets fixed soon.

— Reply to this email directly, view it on GitHub https://github.com/Ombi-app/Ombi/issues/4505#issuecomment-1146756948, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSVULCZA4KQJ2O3LUTC25LVNRKAZANCNFSM5OGSYASA . You are receiving this because you commented.Message ID: @.***>

[zapotah]

If this requires manual work for now, could someone again in the interim push packages manually?

[pax0707]

Any update on this?

[cyberjock]

I'm not related to the development team or anything, but I don't think so. I simply added the cloudpackage repo and was able to upgrade from there.

I may be nai've to the situation, but it seems like the best path forward is for the Ombi team to shutdown the apt repos and use the cloudpackage exclusively. Then at least you'd get an error that the repo doesn't exist, and all the people that think the apt repo is being maintained would have an obvious sign that it is not. At least, that is assuming that the Ombi team is not wanting to manage the apt repo (which it seems like they don't).

Again, I'm probably nai've to the situation as I don't know what the benefits (or drawbacks) to using apt vs cloudpackage would be. I only figured it out 6 months later because I was being very detailed about everything and made the realization. Otherwise I'd still be on the old version from last year.

[krisklosterman]

Just used PackageCloud repo and it installed version 4.20.1 Current repo version is 4.27.1

[cyberjock]

Hah. I just checked mine. I'm using https://packagecloud.io/Ombi-app/Ombi/debian jessie InRelease and I'm on 4.16.11 from April. Which repo are you using? Are you on the developer repo?

[krisklosterman]

The package cloud development one from the docs is at 4.20. The 4.27.1 I meant was the git code download version.

[cyberjock]

So yeah... I'm just more confused now.

I happened to notice that Ombi was out of date back in June, not having an update since I installed it in Dec 2021.

After switching to the packagecloud.io option, I got an upgrade to 4.16.11. This was June, but the update was from April. It was the "Stable" version, so I don't necessarily expect it to be "the most up to date". However, it's October, and not a single update has been pushed to packagecloud.io's stable. Now I'm hearing the development branch is at 4.20, but git is at 4.27.1. I really do not understand anything with this.

I'm gonna just throw my hands in the air and say 'I have no idea what the latest stable is' as the docs are really not helping (they STILL list the apt repo, despite it basically being abandoned per this thread). I'm gonna hope that someday someone will get around to actually making it clear what version each of the repos should have, and what the heck the latest "stable" release is. I'm feeling like all the repos including the development repo is "abandoned".

Well, I'll just leave it as it is and hope my version never had problems. LOL

[jslattery26]

Any updates? Im stuck on 4.7.11.

[Groodles]

I've switched from the PackageCloud Stable to the Dev branch and then received 4.20.1 in the next upgrade.

However, the about page is still telling me that 4.22.5 is the latest and this is also confirmed by the "latest" tag on Github.

While I can download 4.22.5 manually, I dont know what to do with that file....

[fdebijl]

I've switched from the PackageCloud Stable to the Dev branch and then received 4.20.1 in the next upgrade.

However, the about page is still telling me that 4.22.5 is the latest and this is also confirmed by the "latest" tag on Github.

While I can download 4.22.5 manually, I dont know what to do with that file....

@Groodles @jslattery26 same issue here, I ended up just pulling the linux-x64.tar.gz from the releases page and writing that into the Ombi directory - just make to sure to backup your DB's (usually in /etc/Ombi) before you update:

cd ~
# Get latest release
wget https://github.com/Ombi-app/Ombi/releases/download/v4.33.1/linux-x64.tar.gz
# Create directory for the tarball contents and extract it to that dir
mkdir -p ./Ombi
tar -xf linux-x64.tar.gz -C ./Ombi
# Stop the Ombi service, copy over all the files and restart the service
sudo service ombi stop
sudo cp -R ./Ombi/* /opt/Ombi
sudo service ombi start

This shouldn't have any side effects and be just as stable as any other approach to updating, but let me know if this doesn't work out for you - it's been stable for me so far.

[Groodles]

@fdebijl Many thanks for the help and instructions. I have since updated to 4.33.1 without issue.

:)

[oOStroudyOo]

I ended up using the Linuxserver.io image which gets me to version 4.38.1 which matches the latest pre-release on GitHub today.

I run mine on a Proxmox Linux Container (Debian) with Docker and Docker-Compose installed.

Create a directory if it doesn't exist: mkdir -p ~/dockers/ombi

Create and edit nano ~/dockers/ombi/docker-compose.yml I used the following code (Yours may be different) (Use ombi:development for latest pre-release, or ombi:latest for stable): --- version: "2.1" services: ombi: image: lscr.io/linuxserver/ombi:development container_name: ombi environment: - PUID=1000 - PGID=1000 - TZ=Europe/London - BASE_URL=/ombi #optional volumes: - ./config:/config ports: - 3579:3579 restart: unless-stopped

Then run: cd ~/dockers/ombi && docker pull lscr.io/linuxserver/ombi:development && docker compose up -d This will install the app.

Then for updates I've created a batch file on the top level directory (cd && nano ombiupdate.sh) with this code inside: cd ~/dockers/ombi && docker stop ombi && docker rm ombi && docker pull lscr.io/linuxserver/ombi:development && docker compose up -d Then I just need to run bash ombiupdate.sh from the top level directory to update the application. or cd && bash ombiupdate.sh from any other level of directory.

Seems to work flawless for me and I've never had any issues updating to latest pre-release (Linuxserver.io tends to get the latest pre-release around a day or 2 after Github).

Further information can be found here: https://docs.linuxserver.io/images/docker-ombi