W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public ..

Plex Media Server Desktops & Laptops
21

Oh ok. Sorry for being dumb but I’m still learning. Thank you for the quick reply.

Den ons 1 aug. 2018 22:52ChuckPA plex@discoursemail.com skrev:

22

Thanks so much for your efforts ChuckPA.

23

I appreciate the efforts ChuckPA

24

Warning remains - any upcoming efforts to remediate?

25

The entire repo will be remedied at once.
We have an issue with one of the NAS products.

If you want “weird”, One manufacturer of the chip works one way. The other manufacturer of the CPU chip does it differently. We are working producing one binary image which works for both because the logistics of two nearly identical packages would be chaos.

1 Like
26

But what do NAS arch packaging issues have to do with what should be a relatively quick and simple fix for the Debian/Ubuntu amd64 repo? This issue has been languishing for more than a year now. I’d use the PMS snap package to skirt around the broken APT repo, but it hasn’t been updated since it was added to the snaps repo 2 months ago. If you’re spread too thin on package maintenance, I’m sure there’s more than enough community developers who’d gladly help out if you ask.

27

I’ve said this before in several places but will repeat here.

  1. All the packing, including repository updating, are being reworked from the ground up. These new packages are now being forum beta’d here
    Much faster (hopefully), smaller (mostly) and better PMS builds preview (1.14.0.391-7623e9224)

  2. I made all the repository changes and submitted them for rollout while I was conducting the ARMv8 (RealTek) Alpha test.

  3. While conducting the final full regression testing for all packaging (scheduled for rollout 2 months ago), inclusive of the new Synology and QNAP products which utilize the Annapurna ARMv8, we discovered a problem with the binaries (code page alignment in the .so loader) on Annapurna processors. Specifically, it mandates a 64 KB page size. All other processors use the standard 4 KB page size. This was completely unexpected so back to the toolchain we went and started making accommodation for it.

  4. We just figured this out and are, once again, completely regression testing the entire suite because it changed how ELF files are handled.

  5. When this is actually done, rollout can continue. All the NAS and workstation repositories will be updated at once.

  6. The erroneous warning is fixed. You see it because one parameter not defined in the old package header. “Codename” is now checked for by Ubuntu. It’s not required. If it were required, you would see an Error. You see a Warning because the value is undefined and they’ve chosen to Warn about it. The repository generator has it right now. Can it be retrofitted to the old CI? Not worth the effort.

  7. Snaps were done by Engineering independently of CS/QA.

  8. While I’m sure I speak for everyone in the offer to help, the amount of NDA required upfront would not make it worth it. Also, too many cooks in the kitchen will only make it worse because everyone would need access to physical equipment to complete the testing. The coding is done, Turning the physical crank on all PMS functions, on all products, is where it’s at now. That just takes time. How many people can you shove in a big room and run a full product validation suite on before someone gets hurt? hahaha

That’s where it’s at. I hope this helps you understand where We/I are at.

5 Likes
28

It’s six months later, and I’m still having the issue. Will there be a fix?

29

Yes. Yes. and Yes.

We discussed actual deployment yesterday.
Today, I tested the PlexPass builds which are about to go live for QNAP, Synology, and Desktop Fedora.

When they kick to live PUBLIC the repository, which tracks public, will also switch to live.

The warning will no longer exist.

30

and how did you solve it?

31

We replaced the existing custom repository builder with new.
The new recreates the entire repository each time updates are released.

1 Like
32

Just came here after setting up a new server. My sympathies for all the work getting the repositories working and I am very grateful for it.

A lot of user heartache and complaint could be avoided by adding the following sentence to the instructions at: https://support.plex.tv/articles/235974187-enable-repository-updating-for-supported-linux-server-distributions/

You may see a warning like
W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public but got )
from apt when you update it. You can safely ignore this warning; installs and upgrades will still work.

1 Like
33

So what does that mean, the issue should be fixed now ?
Since I still get it on Ubuntu Server 18.04

Regards
S

34

Same also having issues with bionic

# cat /etc/apt/sources.list.d/plexmediaserver.list

deb https://downloads.plex.tv/repo/deb public main

# lsb_release -a

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic

# apt-get update

Reading package lists... Done
W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public but got )
1 Like
35

Closing thread.

This issue is known. Further reports are not necessary. Thank you.

This is also about to be resolved with the new repository.

Stand by for the announcements.

2 Likes