Look at my Ubuntu 16 output. It searches for main not InRelease.
There is something different with Ubuntu 17.10, whether bug or design change (believed to be a bug), which does not work with the existing deb repo. Notice it now calls out InRelease instead of main. Whether it translates main to InRelease or is not recognizing main and defaulting to InRelease is unknown. Changing the repo to support InRelease makes it no longer compatible with anything else.
Fyi: sudo apt upgrade works on 17.1, sudo apt update does not (with the above error message)
i doubt plex packages will be upgraded if the plex repo cannot be updated.
seems like we really have to wait for 18.04 release before there maybe is a fix.
If you can’t get apt on 17.1 to fully cooperate, then I suggest you try using Mr. Worf’s plexupdate script until apt is repaired.
@“frederick.grayson” said:
If you can’t get apt on 17.1 to fully cooperate, then I suggest you try using Mr. Worf’s plexupdate script until apt is repaired.
538 lines of code from nowhere instead of a simple wget && dpkg -i line?
Nope.
I’m hitting the same issue. I cleaned the lists
sudo rm /var/lib/apt/lists/*
and then the issue on update. Here output on doing update a second time:
$ sudo apt-get update
Hit:1 https://downloads.plex.tv/repo/deb public InRelease
Hit:2 http://be.archive.ubuntu.com/ubuntu artful InRelease
Hit:3 http://be.archive.ubuntu.com/ubuntu artful-updates InRelease
Hit:4 http://be.archive.ubuntu.com/ubuntu artful-backports InRelease
Ign:5 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 http://security.ubuntu.com/ubuntu artful-security InRelease
Hit:7 http://dl.google.com/linux/chrome/deb stable Release
Reading package lists… Done
W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public but got )
As you see; the google repo is fetched without issue. Google sources.list is
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
yours
deb https://downloads.plex.tv/repo/deb/ ./public main
mcristina did you try anyway to ‘apt install plexmediaserver’ ?
the warning you get from apt is not that critical (it’s a warning, after all :)), and on my system, despite I got the very same warning message, the package has been installed without other issue…
@ChuckPa said:
As additional information, there is noInReleasereference
Hi Chuck,
The InRelease file is something Ubuntu attempts to download from every entry in the apt sources.lists, it’s nothing more than the typical Release file found in every Debian repository, but signed in-line with your repo’s clearsign GPG key, rather than the classic pair of Release and Release.gpg files. You wouldn’t ever expect to see a reference to it in the sources (it’s part of the infrastructure of every repository), just the squawking apt makes when it queries the $ARCHIVE_ROOT/dists/$DISTRIBUTION URL and gets a 404 or other impediment to retrieving the file.
The reference to the ‘main’ component doesn’t tell apt to examine that directory for what package files are available, only where to find them if they’re needed later. Instead, apt just downloads the InRelease file and parses it for references to the ‘main’ component, and records their respective hashes to add to the local package list. Only once an instruction is given to download/install one of those packages will it interact with the $ARCHIVE_ROOT/dists/$DISTRIBUTION/main directory of your repo, asking to download the file it learned about from the InRelease file.
Could you ask the team why they still don’t have such an InRelease file or even the pair of Release files in the https://downloads.plex.tv/repo/deb/public directory? This has gone on much longer than seems reasonable, and every time I think that it’s time to break down and cough up the dough for a Plex Pass, I think about how this simple issue remains unresolved and conclude that the service isn’t mature enough to justify the expense.
Does that warning stop you from using PMS? I’ve never seen apt-get fail because of it. Others have reported it only a warning.
I have Ubuntu 16 in VM and do not see the ‘InRelease’ thing. I don’t see it on any of the Debian repos (the entire Debian 8 suite which is also in VM).
That said, I take small exception to your statement “in every Debian repository”.
Should it be perfect? Yes, that would be nice. I assert the InRelease thing is confined to Ubuntu 17.
Again, does that stop you from using or downloading PMS. No.
I’m not being a stick in the mud here. My time is limited. Last I tried to make it work for Ubuntu 17, I broke everything else
Right now, it works flawlessly for all but Ubuntu 17.
Which is the lesser of evils?
No Chuck, you’re right about the fact that it isn’t an impediment to working with the package. It does however mean that I have to dismiss the error every time one of my package managers updates the package list. I make use of a lot of different pieces of software and must have something like a couple dozen third-party PPAs in my apt sources and somehow Plex’s is the only one that seems unable to react to the evolution of package management rubrics for the Linux distribution with the largest user base.
I can see that your time is limited, and I’m sorry for bothering you about something you don’t regard as a legitimate concern. My money is also limited and I try to distribute it carefully, placing a high premium on those items which don’t exact a nuisance toll in addition to the sticker price. My intent wasn’t to tell you how to prioritize your responsibilities, only to offer some information as to why it struck me as immaterial to use the absence of a mention of the InReference file in someone’s apt.sources.list to address the error message. It isn’t a question that someone with experience in repository management would ask.
Thanks for such a prompt response to my post.
All the best,
RS
Oh, and I can’t seem to find the bloody edit button for my first post. I made an error when I gave the URL I was curious to learn the presence of an InRelease file within. The correct URL is, in fact:
https://downloads.plex.tv/repo/deb/dists/public
Sorry for the oversight; there’s little worse than trying to be helpful only to send someone down a dead end.
Please don’t misunderstand. It’s a legitimate concern and it needs to be done. The problem I have is finding enough time to be away from the forums, setup my own distro sandbox, mod the distro packaging, then test drive it with all the distros I have to support. Each distro / version to test requires a fresh VM, PMS initial install, update through 3 PMS versions without fail before I can mark it as done. At my 25 Mbps download rate, that works out to one distro/version combo per day. The sucky part is if I break something, I have to start over. QA testing is all-or-nothing… Nature of the beast.
While this is on my mind, If you configure for the 17.x repo structure how did you avoid conflicts with other Debian flavors (all of Ubuntu) and versions? I’ve not managed that piece of magic yet.
I am running into the same issue as stated above. I follow the directions to add the package to my machine and when I run apt-get update I get the same issue. How are the others here still able to install the package. When I run apt-get install plexmediaserver I just get the normal response that it is unable to locate the package. I attached a screen shot of my output if I am being confusing.
same issue here - this server worked flawlessly on 17.04 and since upgrading to 17.10 have this (E)rror:
Please forgive my pedantic tone 
hahaha
How can I address Ubuntu 17.xx if it changes from one version to the next? (see ^^ above)
ok, so to make things more clear, or more confusing : it’s not an Ubuntu “problem”, they are just following the standard that is debian package, well documented on the web.
there are things that are designed on the web to be guidelines, rules, and when the original creator of a technology, ie : DEBIAN is saying there is a Release file in the repository :
https://wiki.debian.org/DebianRepository/Format
there should be a inRelease file in the repository (since 2012 when this standard was updated)
adding said release file should have been done from the start and will not be blocking for “old” Ubuntu as it should already be supported (or will be ignored)
"The file “dists/$DIST/InRelease” shall contain meta-information about the distribution and checksums for the indices, possibly signed with a GPG clearsign signature (for example created by “gpg -a -s --clearsign”). For older clients there can also be a “dists/$DIST/Release” file without any signature and the file “dists/$DIST/Release.gpg” with a detached GPG signature of the “Release” file, compatible with the format used by the GPG options “-a -b -s”. "
TL;DR : Newer os need “inrelease” and will refuse old structure, Older OS will ignore the new “inRelease” structure and have no impact.
does that answer your “how to”?
if not, then there is an alternative : do a stupid folder on the server with “/repo/deb/zorglub”, put the inRelease/newer package structure there, then all of us happy user of 17.10 (or higher) will use this repo while you get your old client compatible on the old folder.
but that’s much more complicated than adding a single file in the repo, anyway
Please forgive me if I sound a bit terse? I am not intending to ‘shoot the messenger’.
Yes, it’s annoying but it does work.
No, there’s nothing I can do about it right now.
Please, be patient because pinging me about what I can’t change annoys me and I get cranky when annoyed 
LOL
I didn’t know you were not in charge of this as I wrongly assumed and I didn’t mean to be harsh either, but I got a bit ticked off by the tone this whole thread was getting into.
I know someone is probably already working on the solution and it’s not like there is a new plex version every day, nor that it needs to be upgraded each release, so no badgering from me.
thanks for the hard work
Thank you for all your help too and understanding.
If you look at the beta announcement regarding package building, hopefully now it’s clear why things seemed ‘stuck in the mud’.
I’m sorry I couldn’t disclose what’s happening. There’s only so much “Please hang in there a bit longer” which can be said. Now that it’s public, I can share that the whole mechanism is being overhauled, from the ground up, from compilation. through package build. to deployment, inclusive of all the repos.
@ChuckPA said:
If you look at the beta announcement regarding package building, hopefully now it’s clear why things seemed ‘stuck in the mud’.
https://forums.plex.tv/discussion/305047/much-faster-hopefully-smaller-mostly-and-better-pms-builds-1-11-1-119-f6453dcf1
Thread not available without a Plex Pass.
