Package Details: losslesscut-git 3.64.0.r95.g25022044-1

Git Clone URL: https://aur.archlinux.org/losslesscut-git.git (read-only, click to copy)
Package Base: losslesscut-git
Description: The swiss army knife of lossless video/audio editing.Using system-wide ffmpeg.(Use system-wide electron)
Upstream URL: https://github.com/mifi/lossless-cut
Keywords: codec cut editor ffmpeg lossless player video video-editor video-files
Licenses: GPL-2.0-only
Conflicts: losslesscut
Provides: losslesscut
Submitter: zxp19821005
Maintainer: zxp19821005
Last Packager: zxp19821005
Votes: 3
Popularity: 0.62
First Submitted: 2023-12-07 04:20 (UTC)
Last Updated: 2025-02-25 01:46 (UTC)

Pinned Comments

zxp19821005 commented on 2024-01-08 10:19 (UTC)

When you first used it,you will got errors like 'Cann't find ffmpeg'.Then please switch to advanced settings and manually set the ffmpeg path to /usr/bin.That will be OK.

Latest Comments

1 2 3 Next › Last »

zxp19821005 commented on 2025-02-25 01:48 (UTC)

@eomanis Thank you for the feedback. I tried uninstalling the system's yarn and calling it using node and npx, but it seems that .yarnrc.xml is not working. I have updated the dependencies and added yarn.

eomanis commented on 2025-02-25 00:55 (UTC) (edited on 2025-02-25 00:58 (UTC) by eomanis)

@zxp19821005 Thank you, it has built successfully now, but it still requires the arch-packaged yarn to be installed because of PKGBUILD line 80:

yarn config set --home enableTelemetry 0

Which causes this build error:

==> Starting prepare()...
(...)
Now using node v20.18.3 (npm v10.8.2)
/home/builduser/.cache/paru/clone/losslesscut-git/PKGBUILD: line 80: yarn: command not found
==> ERROR: A failure occurred in prepare().
    Aborting...

After installing the Arch yarn package the build succeeds. The build does indicate that it uses another yarn after the enableTelemetry step:

==> Starting prepare()...
(...)
Now using node v20.18.3 (npm v10.8.2)
➤ YN0000: Successfully set enableTelemetry to false
➤ YN0000: · Yarn 4.4.0

Maybe the enableTelemetry yarn call needs NODE_ENV=development prepended, too.

zxp19821005 commented on 2025-02-24 04:40 (UTC)

@eomanis This package was built from yarn@4.4.0, which was in the source files, not use the system's yarn (1.22.22). I've fixed the out of memory errors now.

eomanis commented on 2025-02-23 19:25 (UTC)

Missing build-time dependency yarn

But anyway the build, using paru, failed for me with the out of memory error reported by gue5t.

zxp19821005 commented on 2025-02-10 07:20 (UTC)

@dreieck You can see this : https://github.com/mifi/lossless-cut/blob/cfe7620d2e53c69a14351a6c1907dd84a9932c22/package.json#L76 The binary files were built from electron33, and some dependencies were dependent on electron33 too. If using other versions of electron, you may encounter unknown problems. It is recommended that you directly feedback to the upstream.

dreieck commented on 2025-02-09 15:42 (UTC)

Dependency `electron33' is getting old.

Can you check if there is any newer version of electron which works with this, and update the dependency to the newest supported version?

Regards and thanks for the package!

zxp19821005 commented on 2025-01-06 10:07 (UTC)

@gue5t I've not met a problem like you, but I suggest deleting the whole package and installing again.Here are part of my building logs:

✓ built in 9.93s
  • electron-builder  version=24.13.3 os=6.12.7-arch1-1
  • loaded configuration  file=package.json ("build" field)
  • writing effective config  file=dist/builder-effective-config.yaml
  • packaging       platform=linux arch=x64 electron=33.3.0 appOutDir=dist/linux-unpacked
  • copying Electron  source=/usr/lib/electron33 destination=/home/zxp-endeavouros/.cache/paru/clone/losslesscut-git/src/losslesscut.git/dist/linux-unpacked
  • file source doesn't exist  from=/home/zxp-endeavouros/.cache/paru/clone/losslesscut-git/src/losslesscut.git/ffmpeg/linux-x64/lib
==> 正在进入 fakeroot 环境...

gue5t commented on 2025-01-03 23:30 (UTC)

This package fails to install with a Node OOM message after printing the following:

✓ built in 9.04s
  • electron-builder  version=24.13.3 os=6.12.6-arch1-1
  • loaded configuration  file=package.json ("build" field)
  • writing effective config  file=dist/builder-effective-config.yaml
  • packaging       platform=linux arch=x64 electron=33.3.0 appOutDir=dist/linux-unpacked
  • copying Electron  source=/home/user/.cache/yay/losslesscut-git/src/losslesscut.git destination=/home/user/.cache/yay/losslesscut-git/src/losslesscut.git/dist/linux-unpacked

This seems to correspond to the following line from the PKGBUILD:

NODE_ENV=production yarn electron-builder --linux dir -c.electronDist="${electronDist}"

Somehow this creates an infinitely nested series of dist/linux-unpacked/dist/linux-unpacked directories (not symlinks) which takes gigs and gigs of disk space and seems to blow up the memory usage of Node. It seems like the installation/copy being performed is unintentionally recursive, as the listed "source" contains the listed "destination" in the above output.

I don't know how this could be going differently on my system than others; building with simply makepkg fails this way for me.

zxp19821005 commented on 2024-12-12 02:18 (UTC)

@dreieck Thanks for your suggestions, added it.

dreieck commented on 2024-12-11 17:10 (UTC)

Ahoj,

I noticed that yarn wants to collect data and phone home during build:

➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

Since yarn is run in a local environment, a yarn config set --home enableTelemetry 0 to disable as user is not the solution here.

Telemetry needs to be disabled within the actual environment used for this build.

Can you add this, please?

Regards!