Looks like you need to read the announcements.
That announcement doesnât say auto-updates have been restored so the previous status still stands.
Please read carefully.
- We are finalizing the repositories.
- We are testing the repositories
- The Plex/Web notification of updates versus the Repository will be out of sync because the repositories you see are not being updated. The new ones are.
- As has been the case for 18+ months now, the âWarningâ is only a warning. It is the result of Debian/Ubuntu now expecting the âCodeNameâ variable to be set in the repository. Our old repository does not set it. Our new repository does. PMS installs and runs correctly because this is only a warning is it NOT an error.
Should anyone not understand , please refer them to this post.
Future inquires / posts / complaints about this warning will go unanswered.
Thank you for your undertstanding.
6 Likes
I think a lot of people get the idea of a warning and understand. You are just getting unfortunate added trouble by the fact that people are getting a warning AND finding themselves unable to apt-get the update that the web ui is encouraging them to apply. They then search the warning text since they are seeing it in direct conjunction with a failure to upgrade (even though they are unrelated) and Google dumps them here in this thread, so they donât see the other forum notices about apt-get not being available, etc. unless they parse it from the conversation, which I think has only ârecentlyâ really laid out the two sides of this since all the notices that only say that its a warning, not an error, doesnât address the very real, but completely unrelated âproblemâ people think they are having with getting updates through apt-get.
Yes I am. I am the âmessenger who gets shotâ and hereâs why I am becoming overtly frustratedâŠ
- Search the forums âLinux Repo Warningâ â the answers are there⊠right at the top
- Search google âubuntu linux repo expectedâ and it again takes you to Plex where itâs answered.
- My job here is to help people use Plex on Linux. My job is not to teach people how to admin their systems and solve admin 101 problems.
- My job is not to teach folks how to search the forums and internet and give them the 'Step by step" for every single answer. Linux is a SELF-HELP OS. Those who cannot accept this fundamental premise should return to the Mac / WIndows worlds.
This is why, after all this time of explaining it, I am more than âannoyedâ.
I would venture to guess Iâve got 20+ years in age on the average user here so how come I am better with searching the internet than they, those who grew up with it, are ?
Oddly, these are the same ones quick to judge and tell me Iâm doing it wrong.
See the conundrum ?
(Can you tell I had a long week and weekend? hehehe)
2 Likes
Ive seem this message of yours in several threads so when you are done, Iâm wondering which thread you will post in so I know which one to watch? Or will you make a new post all together or in the new server versions announcement thread?
I will make a new post for all.
Listen, Iâm not trying to give you a hard time, Iâm just saying this so you can see the user side and maybe in so doing it you can alleviate some stress through understanding.
Iâd say its party because you know its not the problem and you have a deeper knowledge of linux than they do, since thats the job. I mean can you really tell me that if you were trying to do something(whose inner workings you didnât know like the back of your hand), you got a warning, and then the thing you were trying to do proceeded to not work for no other discernable reason, you wouldnât Google that warning?
I absolutely acknowledge youâve answered the question many times. But depending on the thread sometimes its more buried than others. For instance this thread, I think its a little buried. Another thread I found, you answered and covered both sides of the issue almost immediately, and the thread ended up super short because of it.
My sincere advice as someone who works in IT support and has to answer the same âstupidâ questions over and over again to users, since you are getting a lot of frustration etc. For issues like this that keep coming up, over and over and drive you nuts, make and save canned response(s) that covers both sides, in this instance; acknowledge the warning and note that itâs just a warning and not stopping anything, and then explain that their real problem is with the release delay.
Whenever the topic comes up, copy, paste, go on with your day. It saves a ton of time and stress for you and makes you appear to always be cool and on top of things. If you end up with a lot, Iâd setup a phrase expander, we use PhraseExpress at my work. But then you donât even need to search through a word dock or what have you, just type a related codeword like âconflictdistâ and the expander will replace that with paragraphs of pre-written text.
Copying my post from earlier in this thread (2018 post)
1 Like
Right, and that is great for so far as the warning itself is concerned, but from what Iâve read, it seems most if not all of the people who were persisting did so because they got the warning AND werenât getting the update advertised by the UI, which I recognize is an issue unrelated to the warning, but people see them happen together and when they arenât addressed together you get longer/confused threads. Or so it seems in my opinion at least. Thatâs what I was getting at. Iâve beaten this horse to death though, so you do you. I really have just been trying the help.
Maybe this will be more easily quotable.
The Warning message printed, which can be easily overridden, is just a warning because of the missing codename. This is the ONLY flaw with the repository. The binaries are fine. PMS installs and runs fine.
The fact that the plex-pass versions are not available from the repository is not a flaw as the repository is only used for production ready code and the plex-pass versions are considered beta, not early access now.
Is that accurate?
That is 100% correct.
Repositories are public-access, non-plex pass.
PlexPass downloads are âpreview / betaâ releases.
Out of curiosity, when you setup the new repos could you add another âchannelâ (like instead of just âpublic mainâ, have like âpass betaâ) where it downloads the Plex pass beta version too. But then on initial setup make it only work if server admin has pass. Or even if they switch âchannelsâ (I donât know the terminology) after setup finished, just donât let the server fully start up/work if the server admin doesnât have pass?
It has been discussed many times but thereâs no way to link your PlexPass acount to it and perform proper validation (X-Plex-Token).
Hi Chuck, hope uâve been wellies. Yes Iâve been curious to what happened with the upgrade situation here.
-wbm
I lost count of which version of the Repo builder weâre on. 
We are trying to move forward so different repositories can be hosted, not only Linux.
We have all the NAS boxen as well weâd love to bring into it.
1 Like
Sorry to be add on, but I updated from xenial to ubuntu last week, and am also seeing the error. While itâs stated all over the place that this is in fact a WARNING, the fact is that apt doesnât recognize the content of the repo, so wonât update.
This was run this morning:
plexmediaserver:
Installed: 1.14.1.5488-cc260c476
Candidate: 1.14.1.5488-cc260c476
yet the front end complained that 1.15 was available. So I downloaded that.
wget -N https://downloads.plex.tv/plex-media-server-new/1.15.2.793-782228f99/debian/plexmediaserver_1.15.2.793-782228f99_amd64.deb
and installed it, and voila it works.
Sooo⊠what the dealio?
2 Likes
Not ready yet.
The Warning is harmless. (hence Warning and not Error)
Kindly ignore.
Couple of things, adding them here since itâs related to this thread.
- Please pass our complaints onto management for their silly policy. As a lifetime Plex Pass user, I disagree with their judgement on who gets the deb automatically. Put the authentication in tying the server to my plex account (for Pass features), not the software download itself. There doesnât appear to be a method for even using tokens for restricting access on APT, so I donât think we should expect it. Best bet is you do something like gemfury and fake it with user accounts on linux based on the API tokens, but thatâs⊠hardly maintainable.
- Your customer-facing attitude is appalling. You shouldnât expect customers to read an entire public support thread, nor should you expect appreciation for your work. If you maintain these two attitudes, customer support isnât for you. Expect to repeat yourself and receive no thanks. Câest la vie of a support rep.
- Maybe look to dropping the âConflicting distributionâ warning all-together. That seems like a misconfig, and while it helped us find the root cause (plexpass releases weâre told to update to in-browser arenât automatically update-able) you canât expect people to understand that
W:means Warning.
I mean no disrespect, and I hope this helps.
2 Likes
