Popcorn time arch linux

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.

Источник

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.

Latest Comments

mrbrklyn commented on 2023-06-05 01:08 (UTC) (edited on 2023-06-05 01:13 (UTC) by mrbrklyn)

it errors on build because it is not creating the correct directories — replacing . with —

==> Entering fakeroot environment. ==> Starting package(). /home/ruben/popcorn/popcorntime/PKGBUILD: line 94: cd: /home/ruben/popcorn/popcorntime/src/popcorn-desktop/build/Popcorn-Time/linux64: No such file or directory flatbush:[ruben]:~/popcorn/popcorntime$ ls -al /home/ruben/popcorn/popcorntime/src/ total 4 drwxr-xr-x 4 ruben ruben 97 Jun 4 21:03 . drwxr-xr-x 5 ruben ruben 179 Jun 4 21:03 .. lrwxrwxrwx 1 ruben ruben 48 Jun 4 21:03 gulp-fixes.patch -> /home/ruben/popcorn/popcorntime/gulp-fixes.patch drwxr-xr-x 3 ruben ruben 16 Jun 4 21:00 npm_cache drwxr-xr-x 12 ruben ruben 4096 Jun 4 21:03 popcorn-desktop lrwxrwxrwx 1 ruben ruben 51 Jun 4 21:03 popcorntime.desktop -> /home/ruben/popcorn/popcorntime/popcorntime.desktop 

je-vv commented on 2022-09-05 06:29 (UTC)

korimitsu commented on 2022-07-18 19:33 (UTC)

0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@8.14.0 2 info using node@v18.6.0 3 timing npm:load:whichnode Completed in 0ms 4 timing config:load:defaults Completed in 1ms 5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 2ms 6 timing config:load:builtin Completed in 2ms 7 warn config production Use `--omit=dev` instead. 8 timing config:load:cli Completed in 4ms 9 timing config:load:env Completed in 2ms 10 timing config:load:file:/var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/.npmrc Completed in 0ms 11 timing config:load:project Completed in 4ms 12 timing config:load:file:/home/user/.npmrc Completed in 0ms 13 timing config:load:user Completed in 0ms 14 timing config:load:file:/usr/etc/npmrc Completed in 0ms 15 timing config:load:global Completed in 0ms 16 timing config:load:validate Completed in 2ms 17 timing config:load:credentials Completed in 1ms 18 timing config:load:setEnvs Completed in 0ms 19 timing config:load Completed in 16ms 20 timing npm:load:configload Completed in 16ms 21 timing npm:load:mkdirpcache Completed in 1ms 22 timing npm:load:mkdirplogs Completed in 1ms 23 verbose title npm ls 24 verbose argv "ls" "--all" "true" "--production" "true" "--parseable" "true" 25 timing npm:load:setTitle Completed in 1ms 26 timing config:load:flatten Completed in 3ms 27 timing npm:load:display Completed in 6ms 28 verbose logfile logs-max:10 dir:/home/user/.npm/_logs 29 verbose logfile /home/user/.npm/_logs/2022-07-18T19_29_01_646Z-debug-0.log 30 timing npm:load:logFile Completed in 6ms 31 timing npm:load:timers Completed in 0ms 32 timing npm:load:configScope Completed in 0ms 33 timing npm:load Completed in 32ms 34 timing arborist:ctor Completed in 1ms 35 silly logfile start cleaning logs, removing 1 files 36 silly logfile done cleaning log files 37 timing command:ls Completed in 1708ms 38 verbose stack Error: invalid: backbone@1.4.0 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/backbone 38 verbose stack invalid: underscore@1.13.1 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/underscore 38 verbose stack invalid: http-node@1.2.0 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/http-node 38 verbose stack invalid: vtt.js@0.12.1 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/vtt.js 38 verbose stack at LS.exec (/usr/lib/node_modules/npm/lib/commands/ls.js:205:9) 38 verbose stack at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 38 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli.js:78:5) 39 verbose cwd /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop 40 verbose Linux 5.18.11-1-MANJARO 41 verbose node v18.6.0 42 verbose npm v8.14.0 43 error code ELSPROBLEMS 44 error invalid: backbone@1.4.0 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/backbone 44 error invalid: underscore@1.13.1 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/underscore 44 error invalid: http-node@1.2.0 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/http-node 44 error invalid: vtt.js@0.12.1 /var/tmp/pamac-build-user/popcorntime/src/popcorn-desktop/node_modules/vtt.js 45 verbose exit 1 46 timing npm Completed in 1892ms 47 verbose code 1 48 error A complete log of this run can be found in: 48 error /home/user/.npm/_logs/2022-07-18T19_29_01_646Z-debug-0.log 

je-vv commented on 2022-03-03 07:06 (UTC)

@ItachiSan, 0.4.7 already released:

It includes auto API update, so it seems pretty useful

ItachiSan commented on 2021-07-30 14:13 (UTC)

@je-vv yes, the error is safe to ignore.

It is a gulp build step where they report missing dependencies, that are however solved from NW.JS builder. 🙂

je-vv commented on 2021-07-29 20:58 (UTC)

Thanks a lot @ItachiSan, it seems to be working back.

BTW, I see some npm error, but I’m guessing they are don’t care, since I remember seen errors before, and popcorntime still working:

Error: Command failed: npm ls --all=true --production=true --parseable=true npm ERR! code ELSPROBLEMS npm ERR! invalid: backbone@1.4.0 /home/general/.pkgs/src/laur/popcorntime/src/popcorn-desktop/node_modules/backbone npm ERR! invalid: underscore@1.12.1 /home/general/.pkgs/src/laur/popcorntime/src/popcorn-desktop/node_modules/underscore npm ERR! invalid: webtorrent@0.118.0 /home/general/.pkgs/src/laur/popcorntime/src/popcorn-desktop/node_modules/webtorrent npm ERR! invalid: bittorrent-protocol@3.3.1 /home/general/.pkgs/src/laur/popcorntime/src/popcorn-desktop/node_modules/bittorrent-protocol npm ERR! invalid: http-node@1.2.0 /home/general/.pkgs/src/laur/popcorntime/src/popcorn-desktop/node_modules/http-node npm ERR! invalid: vtt.js@0.12.1 /home/general/.pkgs/src/laur/popcorntime/src/popcorn-desktop/node_modules/vtt.js npm ERR! A complete log of this run can be found in: npm ERR! /home/general/.npm/_logs/2021-07-29T20_47_08_980Z-debug.log at ChildProcess.exithandler (node:child_process:397:12) at ChildProcess.emit (node:events:394:28) at ChildProcess.emit (node:domain:532:15) at maybeClose (node:internal/child_process:1067:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) at Process.callbackTrampoline (node:internal/async_hooks:130:17)

These are to be ignored, right?

ItachiSan commented on 2021-07-29 16:50 (UTC)

I am currently on holiday, so I have some but little time to work on side projects (the seaside calls :P)

I’ve verified and confirmed all the issues & solutions. You are correct, I used 0.4.5 plus a few extra commits which however made PopcornTime unusable.

I’ve now changed the PKGBUILD in order to build from the tag. 🙂

je-vv commented on 2021-07-24 01:58 (UTC)

One thing I noticed though, is that the AUR popcorntime package is using commit:

Whereas the 0.4.5 release is using commit:

The one used by the package, on master, is around 35 commits ahead of the one for release 0.4.5. Could it be @ItachiSan that you got an unstable commit?

Is it possible to use the released tarball instead of git commits? And if in need grab specific commits/patches for specific fixes, then do so? Like, for 0.4.5, use instead of a git commit:

And additional commits as patches as needed? At this point, the current commit used by the AUR package is not the one for 0.4.5, neither top of master. There might be some fixes ahead of it for its current behavior.

je-vv commented on 2021-07-24 01:39 (UTC)

It seems the issue from popcorntime is actually not being able to read at leas some of the configurations, such as the custo APIs. I installed popcorntime-bin, and the issue doesn’t show up with popcorntime-bin, which means the configs seem fine, but I pretty much prefer using Arch/Artix built packages than *-bin ones. I have no clue why the built popcorntime can’t read the configurations/preferences.

je-vv commented on 2021-07-13 05:53 (UTC) (edited on 2021-07-13 05:54 (UTC) by je-vv)

@ItachiSan, it seems whenever starting popcorntime after the last upgrade (to 0.4.5-1), the license agreement is always shown. Also the custom API settings (required to specify *-ru.tk) are always lost, so popcorntime can’t be used (the change to the custom apis require popcorn to be restarted), since on start, the prior settings are lost. Any ways to fix or work this around? Thanks !

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник