Package Details: popcorntime 0.5.1-1

Git Clone URL: https://aur.archlinux.org/popcorntime.git (read-only, click to copy)
Package Base: popcorntime
Description: Stream movies from torrents. Skip the downloads. Launch, click, watch.
Upstream URL: https://popcorn-time.site/
Licenses: GPL3
Submitter: ItachiSan
Maintainer: ItachiSan
Last Packager: ItachiSan
Votes: 57
Popularity: 0.83
First Submitted: 2016-03-01 20:36 (UTC)
Last Updated: 2024-05-05 13:11 (UTC)

Dependencies (8)

Required by (0)

Sources (4)

Pinned Comments

ItachiSan commented on 2018-07-24 21:01 (UTC) (edited on 2021-06-14 09:35 (UTC) by ItachiSan)

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.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 17 Next › Last »

ItachiSan commented on 2018-09-03 10:10 (UTC)

@everyone the issue is caused from my local environment as it is shared between Windows and Linux, so whenever the issue is spotted I need to fix it (AKA dos2unix).

nanners commented on 2018-09-03 09:02 (UTC)

Out of curiosity, how would I find the correct sha512 sum for a bad file in the future? I figure maintainer here will update ASAP, but if I could locate or generate the right one based on an upstream file, I'll know in the future.

kouros17 commented on 2018-09-02 21:20 (UTC)

ERROR: One or more files did not pass the validity check!

G4Zz0L1 commented on 2018-09-02 17:52 (UTC)

The sha512sum for popcorntime.desktop is wrong

servimo commented on 2018-09-02 15:59 (UTC)

Same here: "popcorntime.desktop sha256sums check fail"

gerardo-junior commented on 2018-09-02 12:56 (UTC)

popcorntime.desktop sha256sums check fail

ItachiSan commented on 2018-07-30 13:05 (UTC)

@servimo I suppose you launch the application through your application bar of KDE (I suppose it is your DE). Because of that, the app is started from kdeinit thus getting all the information present in your desktop session, thus also SSH. It's a guess, but I believe to be correct,

servimo commented on 2018-07-29 16:51 (UTC)

https://forum.manjaro.org/t/popcorn-time-and-proc-self-exe/53697

ItachiSan commented on 2018-07-24 21:01 (UTC) (edited on 2021-06-14 09:35 (UTC) by ItachiSan)

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.

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 17 Next › Last »