Server Version#:plexmediaserver-1.25.6.5577-c8bd13540.x86_64
Player Version#:N/A
Is there some reason that I don’t see the current public PMS version as available in https://downloads.plex.tv/repo/rpm/$basearch/ ? (basearch = x86_64. PlexWeb is telling me that 1.25.9.5721 is available.
release to the repos is always a few days/a week delayed just in case a nasty bug is found.
My web interface has been telling me for a few weeks that updates are available. The backend repo doesn’t appear to be getting updated timely, somebody’s automation looks to be broken.
If you’re using Centos 7, the actual fault is with Centos.
They’ve shutdown all respository updating when they shutdown their repositories.
openSuSE Leap 15.3
As soon as BlueBeanie announced the shift of Centos to being upstream of RHEL, I’ve dropped it like a hot potato.
I’m setting up Leap 15.2 (the ISO I had on hand) in a VM now.
Given what it’s downloading, I might be ready by Christmas 
LOL
I just confirmed something’s not right.
I installed 15.3 (twice before I got it right).
Installed 1.22.3 and then asked yast to update.
It told me it was up to date.
I’ve reached out to the build team to find out if they are missing something or I am.
I just completed installation and setup of a fresh Fedora 35 VM.
I repeated the same steps as performed on openSUSE.
Fedora works (as did Centos) where Suse does not.
I think it appropriate to go find out why.
I’d concur. Let me know if my system logs might help.
I think this is one for you to take to the openSUSE forum.
By reviewing what our repo has, I am confident we’re doing it correctly
so that makes me ask “what happened with Leap?”
Do you concur ?
Interesting thought, that. Lessee… gonna ask those good folks to take a quick look at a 3rd part repository where it works properly with an RHEL style distro, but openSuSE Leap doesn’t seem to pick the latest available RPM. Or… how to create a multi-distribution capable repository.
That’s really only being a bit snarky. Repositories… hrrrrm… hey… unless you ask me not to, think I’m gonna try & pull down the complete repository. I do have a CentOS host here I can fire up temporarily (Katello test host,) and see if I can play some games with repodata.
Pretty sure, if I understand the build team correctly, the most you would pull are the package files if you had absolute paths.
On their side, there is software which receives the repo query and then generates the responses so attempting to download the whole repo won’t work.
The build team did respond to me early this morning and they get the same results with Leap 15.3. The conclusion is that something in zypper is suddenly different than all the other RPM repo handlers.
As for building a multi-distro repository, by definition either RPM or DEB packaging spec (which is what we have).
Maybe, zypper vs yum/dnf is different somehow.
apt for all the debian-based distros is fine.
I think you & I are reaching the same conclusions.
I was thinking that I’d list the PMS repository link over in the openSuSE forums, but based on the security measures referenced above, I’m not sure that’s going to do any good.
Getting back to your build team… no argument that zypper is doing something different. Is there any possibility that the software that generates the repo responses is NOT generating the proper values for zypper vs. yum/dnf? You’d have to be able to snoop logs or HTTPS traffic to figure that out.
Caveat: I have not posted this over in the openSuSE forums yet.
At the moment, zypper says that no new version of the plexmediaserver RPM is available:
> sudo zypper up plexmediaserver
Loading repository data...
Reading installed packages...
No update candidate for 'plexmediaserver-1.26.2.5797-5bd057d2b.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
I’m putting together a Foreman/Katello implementation for my own openSuSE provisioning, and just for grins, tossed the Plex download URL into a repository configuration. It downloaded plexmediaserver-1.27.0.5897-3940636f2.x86_64, which is the latest published version.
Conclusion: Obviously, Katello and openSuSE are making different requests to your yum repository, and getting different returns. Does Plex really have a front end filter on the download HTTP server?
Hrrrm… now that I have 2 separate RPM files… I can stuff those into a local apache server here, and run createrepo.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
