More > JRiver Media Center 21 for Linux

Installing MC 21 on Arch linux

<< < (3/4) > >>

danhardison:
I have taken the lead alluded to by mwillems and created the following PKGBUILD file:

pkgname=jriver-media-center
_debpkgver=21.0.3
pkgver=$_debpkgver
pkgrel=1
pkgdesc="The Most Comprehensive Media Software"
arch=('x86_64')
url="http://www.jriver.com/"
license=('custom')
depends=('alsa-lib' 'gcc-libs' 'libx11' 'libxext' 'libxcb' 'libxau' 'libxdmcp' 'util-linux' 'libxext' 'gtk2' 'p11-kit' 'libtasn1')
optdepends=('mesa-libgl: nouveau video support' 'nvidia-libgl: nvidia video support' 'xorg-fonts-75dpi:' 'xorg-fonts-100dpi:' 'vorbis-tools:' 'lame:' 'musepack-tools:')
source=("http://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-$pkgver-amd64.deb" 'License.txt')
sha256sums=('4b15a34b24992e3c28f05321eddba7fdfd900951628d2669a275072eeeeb2391' 'ee00f430918df6be37777a61e12812875b5583379c78daaa969bae7383a41fbd')

package() {
cd "$srcdir"
bsdtar xf data.tar.xz -C "$pkgdir"
install -Dm644 "License.txt" \
"$pkgdir/usr/share/licenses/$pkgname/COPYING"
}

But, it fails to pass the sha256 validity checksum (makes sense I guess)

What should I do about this?

Dan

mwillems:

--- Quote from: danhardison on August 13, 2015, 02:17:34 am ---I have taken the lead alluded to by mwillems and created the following PKGBUILD file:

pkgname=jriver-media-center
_debpkgver=21.0.3
pkgver=$_debpkgver
pkgrel=1
pkgdesc="The Most Comprehensive Media Software"
arch=('x86_64')
url="http://www.jriver.com/"
license=('custom')
depends=('alsa-lib' 'gcc-libs' 'libx11' 'libxext' 'libxcb' 'libxau' 'libxdmcp' 'util-linux' 'libxext' 'gtk2' 'p11-kit' 'libtasn1')
optdepends=('mesa-libgl: nouveau video support' 'nvidia-libgl: nvidia video support' 'xorg-fonts-75dpi:' 'xorg-fonts-100dpi:' 'vorbis-tools:' 'lame:' 'musepack-tools:')
source=("http://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-$pkgver-amd64.deb" 'License.txt')
sha256sums=('4b15a34b24992e3c28f05321eddba7fdfd900951628d2669a275072eeeeb2391' 'ee00f430918df6be37777a61e12812875b5583379c78daaa969bae7383a41fbd')

package() {
cd "$srcdir"
bsdtar xf data.tar.xz -C "$pkgdir"
install -Dm644 "License.txt" \
"$pkgdir/usr/share/licenses/$pkgname/COPYING"
}

But, it fails to pass the sha256 validity checksum (makes sense I guess)

What should I do about this?

Dan


--- End quote ---

Three possible solutions:

1) The "right" way: Download the .deb package manually to your build directory, and take a new shasum, and put it in the PKGBUILD.  Makepkg will then run correctly.  This doesn't really provide any additional layers of security as you're only testing your own download, but is the technically correct way to do it.
2) The "wrong" way: pass the "--skipinteg" flag to makepkg and it will ignore the shasums, which normally presents some security risks, but given that it's proprietary pre-compiled software hosted on a private server, the chance of it being maliciously modified by third parties is comparatively low (in my non-professional estimation).  (This is what I do when the Aur PKGBUILD is out of date, which is usually). 
3) The "long view" way: Nag Bob to start posting Shasums in the build threads  ;)

Mark_NL:

--- Quote from: mwillems on August 13, 2015, 07:34:53 am ---1) The "right" way: Download the .deb package manually to your build directory, and take a new shasum, and put it in the PKGBUILD.  Makepkg will then run correctly.  This doesn't really provide any additional layers of security as you're only testing your own download, but is the technically correct way to do it.
2) The "wrong" way: pass the "--skipinteg" flag to makepkg and it will ignore the shasums, which normally presents some security risks, but given that it's proprietary pre-compiled software hosted on a private server, the chance of it being maliciously modified by third parties is comparatively low (in my non-professional estimation).  (This is what I do when the Aur PKGBUILD is out of date, which is usually).  
3) The "long view" way: Nag Bob to start posting Shasums in the build threads

--- End quote ---

what I usually do is in between 1) and 2):

Download the .deb package manually to your build directory (can be done by running makepkg and after the error), run the updpkgsums (script) in your build directory. This will generate new checksums and update the PKGBUILD with those.

https://wiki.archlinux.org/index.php/Makepkg
(look into Tips and Tricks)

+1 for 3)

danhardison:
Thanks for both your answers. This sounds do-able!

Cheers
Dan

danhardison:
I did the updpkgsums and it worked! Then did pacman -U etc and all seems rosey.

My next question will make you laugh. How do you run it? I am used to the Windows world where you double-click an exe.

Dan

Navigation

[0] Message Index

[#] Next page

[*] Previous page