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

Plex Media Server Desktops & Laptops
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