Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[danhardison]

Hello,

This is more of a linux question, but I am getting a missing dependency error for libgnutls26 when I try to makepkg jriver-media-center 20.0.129-1 package.

When I try to install the missing dependency, I end up with a missing dependency for libgcrypt11, and then a missing file: libgcrypt11_1.5.0-5+deb7u3_amd64.deb

I'm not sure how many crimes against linux I've committed along the way, but just hoping that someone might have been down this road and can spot what I have to do??

Dan

[mwillems]

Could you post the PKGBUILD you're using?  I'm not sure the current AMD64 version of MC20 (which is .131 BTW) actually has a dependency on libgnutls26 or libcrypt anymore? 

Two choices: try installing the 32-bit version (it will have a few more multilib deps, but it runs identically to the 64 bit version and that's what the PKGBUILD was designed for), or try removing those packages from the deps list in the PKGBUILD and see what happens.  Worst case, MC will segfault, but my recollection is that those are no longer deps of the 64-bit build.

[danhardison]

I got it from here..

https://aur.archlinux.org/packages/jriver-media-center/

I pasted the PKGBUILD from the "latest comments" where it said New Version 20.0.129

pkgname=jriver-media-center
_debpkgver=20.0.129
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' 'libgnutls26')
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/v20/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"
}

Have I gone to the wrong place?

Thanks. Any advice appreciated.

Dan

[mwillems]

Try removing the libgnutls26 dependency and running it again.  I'm pretty sure the current version doesn't actually have that dependency.

[danhardison]

OK. Will do. Cheers!

[danhardison]

Try removing the libgnutls26 dependency and running it again.  I'm pretty sure the current version doesn't actually have that dependency.

That appears to have worked. At least, it built and installed without error. I did it remotely using putty, so I can't run the GUI and get the full experience. I'll try that at home tonight. Thanks for the advice.

But I realise my Topic/Subject is probably wrong.. because are we saying this is actually MC20, not 21? I take it 21 is not available for Arch yet? And you mentioned build .131. Where do I get that from?

Cheers,
Dan

[mwillems]

That appears to have worked. At least, it built and installed without error. I did it remotely using putty, so I can't run the GUI and get the full experience. I'll try that at home tonight. Thanks for the advice.

But I realise my Topic/Subject is probably wrong.. because are we saying this is actually MC20, not 21? I take it 21 is not available for Arch yet? And you mentioned build .131. Where do I get that from?

Cheers,
Dan

You might want to take some time and familiarize yourself with the Arch build system, e.g. https://wiki.archlinux.org/index.php/PKGBUILD.  It's really pretty easy to update PKGBUILDs on your own once you get the knack.  For example, if you change the version number on the second line of the PKGBUILD you posted, you can download and install build .131 instead. 

The change to get it to download version .21 requires one additional step, but it's also trivial.  If you can't spot it I'll post my homemade v21 PKGBUILD.   

[danhardison]

OK, thanks. I can definitely do that; i.e. update the PKGBUILD file, but how did you know .131 was available? Is there somewhere else besides the AUR page I'm looking at where I can find this out? Sorry if this is a dumb question. I might be missing something obvious.

Dan

[Awesome Donkey]

For Media Center 20 for Linux, you can see the topics announcing the latest builds in this forum section: http://yabb.jriver.com/interact/index.php?board=35.0

However since development of Media Center 21 is underway, development of Media Center 20 will (and likely already has) ceased.

[danhardison]

OK. I think I get it now.

Combination of linux inexperience and coming up to speed with the forum/product release structure etc.

Thank you all for your patience.

[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]

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

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]

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

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

[mwillems]

How are you interacting with your linux computer?  Do you have a GUI?  If so, which one?  In most GUIs there's a windows style "start" button or a dock that MC should now show up in.

If you're interacting with it solely through CLI, the way to run the program is by typing "mediacenter21" at the command line.  If you have no GUI installed though, it will probably crash because MC requires a GUI/Xserver in order to run successfully.  If you're in that situation, I can offer some specific advice, just let me know

[danhardison]

Ahh the old case-sensitivity. I typed MediaCenter21 and got "invalid command" (or whatever)..

I did ls -l and can't see mediacenter21 in the folder.. Where does it put it? Anyway, that works. I can see the program!

In answer to your question, I'm using the Audiophile Linux shell. It only has a limited pre-prepared list of programs available in its custom right-click start menu.

I am not sure how long I'll persist with ap-linux. I get the feeling now from lots of linux forum reading that it's not anything special. But as you told me earlier, dabbling in arch linux is good for learning!

Thanks a lot. Hopefully you won't hear from me for a while  ;-)

Dan

[mwillems]

I did ls -l and can't see mediacenter21 in the folder.. Where does it put it? Anyway, that works. I can see the program!

Traditionally the linux filesystem put system-wide commands in the /bin directory, and anything in that directory can normally be executed from anywhere.  Many modern linux distros (including Arch) put all commands in /usr/bin (where user installed commands were traditionally placed), and I think that's where mediacenter21 is.  But it's in one of those two places as I recall.

But it's not super relevant where it actually is though. If it helps to think of it this way, the reason you can execute mediacenter21 is the same reason you can execute ls or other shell commands; they're all together somewhere. The strict technical answer is that you can execute all commands in a directory that's included in your users PATH environment variable. That's useful to know if you ever want to write scripts to be executed by cron or the root user as they don't necessarily have the same PATH as you do.  If you want to see what directories are in your PATH, type

Code: [Select]

echo $PATH


In answer to your question, I'm using the Audiophile Linux shell. It only has a limited pre-prepared list of programs available in its custom right-click start menu.

Ah that makes sense; it's probably a modified version of openbox; if so you could probably easily edit the right-click menu (it's just in a human readable .xml file somewhere).

I am not sure how long I'll persist with ap-linux. I get the feeling now from lots of linux forum reading that it's not anything special. But as you told me earlier, dabbling in arch linux is good for learning!

My advice if you're starting over is to start from scratch with Vanilla Arch and complete the learning odyssey!

Thanks a lot. Hopefully you won't hear from me for a while  ;-)

Glad to help, and I hope you'll be back, we need more linux enthusaists around here