Files fail to pass validity check

[AlienProber]

I have tried to install Emby Theater through Pamac an yay and always end up with the below. I'm running EndeavourOS which is a Arch based distro.

lienprober@TheMotrhership ~]$ yay -S emby-theater
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  emby-theater-bin-3.0.12-2

  1 emby-theater-bin                 (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 4
:: PKGBUILD up to date, Skipping (1/1): emby-theater-bin
  1 emby-theater-bin                 (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 4
:: (1/1) Parsing SRCINFO: emby-theater-bin
==> Making package: emby-theater-bin 3.0.12-2 (Fri 02 Oct 2020 04:55:42 PM PDT)
==> Retrieving sources...
  -> Found emby-theater_3.0.12_amd64.deb
  -> Found emby-theater.install
==> Validating source files with sha512sums...
    emby-theater_3.0.12_amd64.deb ... FAILED
    emby-theater.install ... Passed
==> ERROR: One or more files did not pass the validity check!
error downloading sources: emby-theater-bin
[alienprober@TheMotrhership ~]$ 

[bboehmke]

I think the root cause of this issue is that the binary attached to the release 3.0.12 was simple replaced with another build that was made on 2020-09-17.

Because the PKGBUILD contains a checksum of the expected deb packages to validate if the files was modified/corrupted, this change broke the AUR package.

I would really appreciate if there would be a new tag/release for new builds. If this is not possible them at least at the new binary additional to the existing release with another file name.

[LukePulverenti]

HI, sorry for the disruption. We'll try not to do that. Generally I only do that when there is a packaging fix for a specific platform and I want to avoid updating everyone to a new build, but i can see the problem that it causes. Thanks for the info.

[bboehmke]

@LukePulverenti It seems the emby-theater_3.0.14_amd64.deb of the release 3.0.14 was again modified.

It would be really great if new builds/packages would be added under a new version or at least with another filename (+ keep the old one).
This upgrades are silently breaking the emby-theater-bin AUR package without any possibility for me to notice this.

It would be really cool if such modifications can be avoided in the future.

[LukePulverenti]

Hi, apologies for the disruption. We'll be getting a 3.0.15 update out to resolve this. Thanks.

[bboehmke]

It seems the packages were replaced again without a new version number.
I will now stop maintaining the AUR package because this situation gets a little annoying.

[AlienProber]

@LukePulverenti here we are at a minimum of 11 months later and looks to be the same general issue for your end. I can understand @bboehmke not wanting to maintain the AUR version any longer. Maybe it's time you did a proper checklist before releasing anything.

[LukePulverenti]

Apologies for the delay. Yes in hindsight we should always be updating the version number.

But I have other news for arch linux. You can now switch to the package built by us: https://archlinux.org/packages/community/x86_64/emby-theater/

@bboehmke thank you for maintaining it up to this point !