Arch Linux User Repository

You are free to report issues regarding the packaging here! Please read all the info of this message as they include quite some information.

Be aware that sometimes the package will fail to build because of outdated upstream and updated dependency, which will require me some time to test and solve the problem.

I do also have life stuff, packaging is a free-time activity.

I believe I have an issue that is Arch-related and not upstream related

I too found out only recently this way to debug the app (as of: 2021-06-13), which helps immensely.

Whenever reporting here or on the Github issues, please provide the output of the command:

popcorntime --enable-logging=stderr

In case you are forwarding the log to a file, as the log entries will end in stderr, remember to redirect stderr to stdout

popcorntime --enable-logging=stderr 2>&1 > my_output.log

Info regarding the package

1. The package uses the sources available at: https://github.com/popcorn-official/popcorn-desktop. I am aware of the different clones and branches; I do still believe that this code is acceptable (not affected itself from malware).

2. This package uses a custom NW.js build provided from the PopcornTime team; essentially, a custom compiled browser. While this won't affect you as it should be used only within the app, you are here informed that I have no power over this component.

3. The above point stands as the official NW.js Chromium source lacks multiple modern codecs, such as AC3 and HEVC (H.265).

4. Earlier this package used the official nw.js toolchain provided available at https://dl.nwjs.io/ and the prebuilt FFmpeg library with additional codecs available at https://github.com/iteufel/nwjs-ffmpeg-prebuilt/ . This was because the nw.js toolchain provided by the PopcornTime team can not be proven as non-malware easily. However, due to point 3, this approach was reverted. You are free to use an older PKGBUILD with the appropriate variable updates to re-enable this, however you will miss support for recent codecs.

5. In addition, the PKGBUILD won't point to the Git release reference but will also include important commits, for e.g. security reasons or providers changes.

Unable to build the package, full build log: https://pastebin.com/cn9iUN41

I can't install 0.3.10-8 because:

Validating source files with sha256sums... popcorn-desktop ... Skipped gulp-fixes.patch ... FAILED popcorntime.desktop ... Passed ==> ERROR: One or more files did not pass the validity check!

Got when upgrading 0.3.10-7 -> 0.3.10-8:

==> Validating source files with sha256sums... popcorn-desktop ... Skipped gulp-fixes.patch ... FAILED popcorntime.desktop ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: build: failure on package popcorntime

Seems like the new gulp-fixes.patch has different sha256sum hash:

212a60c2c9f5cf5aa0e16a5c8baa511d5d63a2fd25945efa0c9056d97ab31d24

But it still fails in the end, even by fixing the checksum:

added 29 packages from 30 contributors in 24.728s patching file gulpfile.js Hunk #1 FAILED at 64 (different line endings). Hunk #2 FAILED at 83 (different line endings). 2 out of 2 hunks FAILED -- saving rejects to file gulpfile.js.rej ==> ERROR: A failure occurred in prepare(). Aborting... ==> ERROR: build: failure on package popcorntime

The indie (vodo) tab does not display anything, then the app freezes.

Thanks for the update but its not working for me. The loading screen shows up briefly and then I get an empty black screen.

@Eschwartz thanks for the tip, didn't know of it. Will change the PKGBUILD accordingly. I won't do a version bump though, as there is no release change (it would just build the same).

Please don't set the npm cache like that, you have no guarantee you'll have a chance to reset it later on.

See npm help 7 config under "Environment Variables" and use

export npm_config_cache="$srcdir/npm_cache"

this time it's working, thanks for the update!

Hi guys, Not sure where my message has gone (I am pretty sure I posted here something yesterday but nothing is here), anyways I have a working version.

Before was fully broken, now I can get through the menu, up to breaking other stuff (nicely done software), I am testing another commit to see if a fresher version doesn't break all the UI.

Anyways, there are many issues building; the current version of npm has a nasty bug, you can find it here: https://github.com/npm/npm/issues/19989

The "fix" is that I install locally (within node_modules) a working npm version and use it for the build. I also have, some times, the same error while installing the non-broken npm!!! The only """tested""" way for me that """works""" is in my home directory (mine is a ext4 filesystem). I can't help with that. Consider that, if you survive to the first NPM install, you are good to go. Other options is to use an older npm available in the AUR (I recall there are npm4 and npm53).

Stay tuned!

Same issue here. Previous version (0.3.10-3) still works perfectly. Something messed up in 0.3.10-4. Fortunately version 0.3.10-3 is still available as package popcorntime-bin.