Package Details: makemkv 1.17.9-1

Git Clone URL: https://aur.archlinux.org/makemkv.git (read-only, click to copy)
Package Base: makemkv
Description: DVD and Blu-ray to MKV converter
Upstream URL: https://www.makemkv.com
Licenses: LGPL-2.1-or-later, LicenseRef-GuinpinSoft-inc-EULA
Submitter: hydro
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 329
Popularity: 2.14
First Submitted: 2010-01-26 15:31 (UTC)
Last Updated: 2025-02-01 21:02 (UTC)

Dependencies (4)

Sources (4)

Pinned Comments

FabioLolix commented on 2024-07-20 16:33 (UTC)

This now depends on libavcodec.so so when it needs to be rebuilded against new ffmpeg version you are forced to uninstall first otherwise the update will be blocked

fosskers commented on 2023-06-11 13:56 (UTC)

I can confirm that a manual sudo modprobe sg was necessary to get makepkg to detect my DVD drive.

FabioLolix commented on 2023-03-16 21:41 (UTC)

Beta key:

Latest Comments

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

lpga commented on 2020-12-15 16:06 (UTC) (edited on 2020-12-15 16:24 (UTC) by lpga)

To be more clear, in "${srcdir}" i found two directories:

makemkv-bin-1.15.4 # as expected

makemkv-oss-1.15.3 # here is the problem

I usually use pikaur, but I have the same problem using yay, and yes I cleared the package cache. I solved the problem modifying the PKGBUILD as follows:

pkgname=makemkv
pkgver=1.15.4
pkgrel=1
........
sha256sums=('45eba7e61a7b467b1fe8de722fa890d556e19f3fc02a7b7f8d846ac8e2badb9a'
            '42bbaaf5828068d175a43b4e869b4ff7952314bd8d03812e44e478bfa5d91c4c' # *makemkv-oss-1.15.4.tar.gz*
            '5573b2e4bade10d8cd258a7c235eb46f66ef8c8c97e5d5eb090c38fa0f94389b'
            'f12c0facf2f0071a9f728b138986f0a4c2b4ff6ace2dfb2e96364e215e9fda6f'
            '2a6237d3d5ce073734c658c7ec5d2141ecd0047e6d3c45d1bd594135c928878f')
........
build() {
  cd "${srcdir}/${pkgname}-oss-1.15.3" # *here is the fix to the problem*
  CFLAGS="$CFLAGS -std=c++11" CC=gcc CXX=g++ ./configure --prefix=/usr
  make
}

package() {
  cd "${srcdir}/${pkgname}-oss-1.15.3" # *here is the fix to the problem*

I just found the same fix in the PKGBUILD of makemkv-cli. :-)

blackhole commented on 2020-12-15 10:55 (UTC)

Ok, I was using yay, so I removed cache with

yay -Scc

Now installation is fine!

Marcel_K commented on 2020-12-15 10:51 (UTC)

You really get some (cached?) different file one way or another, because every time I delete makemkv-oss-1.15.4.tar.gz and redownload it again (from either the http source or the https source, doesn't matter), I get the correct file, with the checksum in the PKGBUILD and the correct directory name in the tarball. Is there anyone that also gets the correct file?

I really don't know what is happening here.

lpga commented on 2020-12-15 08:11 (UTC)

@Marcel_K if you extract the contents of makemkv-oss-1.15.4.tar.gz, you can see the real directory name: makemkv-oss-1.15.3 exactly what @blackhole wrote in his comment

blackhole commented on 2020-12-15 05:37 (UTC)

Ok, changed to https:

makemkv-oss-1.15.4.tar.gz ... FAILED

Ok, changed the sha256sum, new error:

/src/makemkv-oss-1.15.4: No such file or directory

It seems that the file is makemkv-oss-1.15.4.tar.gz but the directory name in /src is makemkv-oss-1.15.3

chungy commented on 2020-12-15 05:11 (UTC)

Update the URL to "https://www.makemkv.com" (note https instead of http), the plain-http view of the file is of the previous version, and that's what is causing checksum errors.

Marcel_K commented on 2020-12-14 23:11 (UTC)

@lpga: what do you mean? Here the archive name and the directory name are the same.

lpga commented on 2020-12-14 21:44 (UTC) (edited on 2020-12-14 21:46 (UTC) by lpga)

1) archive named makemkv-oss-1.15.4

2) in the archive the name's directory is makemkv-oss-1.15.3

it isn't only a checksum error...

Marcel_K commented on 2020-12-14 20:58 (UTC)

Or a download error. Indeed delete the file and try to run makepkg again.

patrickh commented on 2020-12-14 20:29 (UTC)

@albuntu It looks like the makemkv-oss-1.15.4.tar.gz source file you might have got, could be the 1.15.3 instead (happened to me as well). Try to delete it/clean build it.