Package Details: losslesscut-bin 3.30.0-2

Git Clone URL: https://aur.archlinux.org/losslesscut-bin.git (read-only, click to copy)
Package Base: losslesscut-bin
Description: Crossplatform GUI tool for lossless trimming/cutting of video/audio files
Upstream URL: https://github.com/mifi/lossless-cut
Licenses: MIT
Submitter: dmp1ce
Maintainer: dmp1ce
Last Packager: dmp1ce
Votes: 16
Popularity: 1.38
First Submitted: 2020-11-10 13:10
Last Updated: 2020-12-20 13:28

Latest Comments

1 2 3 4 Next › Last »

dmp1ce commented on 2020-11-10 13:14

Thanks @smrqdt.

I created losslesscut-bin and made the merge request on both packages.

smrqdt commented on 2020-11-10 04:02

As this package uses prebuilt binaries it should contain a "-bin" suffix in its name (https://wiki.archlinux.org/index.php/AUR_submission_guidelines), please consider renaming. Afaik the process for that is cloning and submitting a merge request (using "Submit Request" in the Package Actions box).

dmp1ce commented on 2020-07-13 14:33

@jogai, what problem are you having? I see the svg here: https://raw.githubusercontent.com/mifi/lossless-cut/master/src/icon.svg

jogai commented on 2020-07-13 06:31

The icon svg is not on github anymore.

dmp1ce commented on 2020-07-10 13:25

3.23.8 is a tag, not a release currently.

https://github.com/mifi/lossless-cut/releases

dmp1ce commented on 2020-04-10 19:38

3.19.0 is a "pre-release". Please flag again when it is a "release".

https://github.com/mifi/lossless-cut/releases

dmp1ce commented on 2020-04-02 00:36

cultleader: Thanks! Should be fixed now.

cultleader commented on 2020-04-01 22:59

@dmp1ce I had to change the ln line in the pkgbuild from ln -s /usr/share/losslesscut/lossless-cut "$pkgdir"/usr/bin/losslesscut to ln -s /usr/share/losslesscut/losslesscut "$pkgdir"/usr/bin/losslesscut It's strange because on the losslesscut github, they use lossless-cut in their examples as well.

JupY commented on 2020-03-12 20:24

@dmp1ce, Reinstalling did the trick for me. Thanks for your help!

dmp1ce commented on 2020-03-12 00:56

@JupY, Perhaps try removing the package and reinstalling. I'm going to try and prevent the issue in the next release.