More > JRiver Media Center 21 for Linux
Quick start guide for installing JRiver Mediacenter 21 ARM for Raspberry Pi
mwillems:
--- Quote from: PrinterPrinter on March 03, 2016, 02:08:10 pm ---Hello,
I'm trying to update my pi as usual and get this error messgae:
--- Code: ---W: Failed to fetch http://raspberrypi.collabora.com/dists/wheezy/rpi/binary-armhf/Packages 403 Forbidden
E: Some index files failed to download. They have been ignored, or old ones used instead.
--- End code ---
What am I missing?
Thank you!
--- End quote ---
That's one of the Raspberry Pi foundation's repos; they've changed to a different repo structure since the transition to wheezy, so it may be that they're no longer supporting the old repos? I can't say, it's definitely not JRiver related. If you've updated the Piu to Raspbian Jessie you can remove that repo.
PrinterPrinter:
--- Quote from: mwillems on March 03, 2016, 05:59:04 pm ---That's one of the Raspberry Pi foundation's repos; they've changed to a different repo structure since the transition to wheezy, so it may be that they're no longer supporting the old repos? I can't say, it's definitely not JRiver related. If you've updated the Piu to Raspbian Jessie you can remove that repo.
--- End quote ---
Oh mate, you're speaking Chinese to me... (and I'm not fluent in Chinese ;-).
I didn't change anything since I started using the Pi, I occasionally run the update command:
sudo apt-get update && sudo apt-get dist-upgrade
How do I start to solve this? is there another command or way for me to just update MC? In the new version they added a toggle switch for the buffering that I believe will help me with occasional hiccups.
Thank you!
mwillems:
--- Quote from: PrinterPrinter on March 04, 2016, 03:11:47 am ---Oh mate, you're speaking Chinese to me... (and I'm not fluent in Chinese ;-).
I didn't change anything since I started using the Pi, I occasionally run the update command:
sudo apt-get update && sudo apt-get dist-upgrade
How do I start to solve this? is there another command or way for me to just update MC? In the new version they added a toggle switch for the buffering that I believe will help me with occasional hiccups.
Thank you!
--- End quote ---
I don't have a Pi running the old version of Raspbian right now, so I can't give you a step by step, but it would probably be harmless to remove the collabora repo entirely. If I recall correctly there is a file named collabora.list in the directory /etc/apt/sources.list.d. You can try removing that file.
Alternatively, you can run the two halves of the update command separately and it should work fine (meaning first run sudo apt-get update and then on the next line run sudo apt-get dist-upgrade). The reason the update doesn't happen is that the && operator stops if there was an error in the first half of the command, even if it's not necessarily a "blocking" error. So try running sudo apt-get dist-upgrade on it's own line, which should work fine as a work around.
jmone:
Liking this thread! I've got a couple of Axiom Airs coming, they are a wireless speaker with an embedded Pi2 running Volumio. My cunning plan is to see if I can also run MC on these speakers (in addition to their existing SW). I'm guessing they are a month away from arriving as they are coming of the production line now.
mwillems:
--- Quote from: jmone on March 05, 2016, 03:42:58 am ---Liking this thread! I've got a couple of Axiom Airs coming, they are a wireless speaker with an embedded Pi2 running Volumio. My cunning plan is to see if I can also run MC on these speakers (in addition to their existing SW). I'm guessing they are a month away from arriving as they are coming of the production line now.
--- End quote ---
Be aware that Volumio is an "all-in-one" type affair that runs customized packages, so you may have some challenges allowing them to cohabit in peace. I haven't tried Volumio in six months or so, but last time I tried it it left a lot to be desired, so you may wind up bypassing it entirely. It'll be interesting to see how that works though, and I'm ready to help when the time comes.
Hopefully you can get at the embedded Pi's SD card without having to cut open the cabinet, as physical access will tremendously simplify the process, especially if they've done something unfriendly/sensible (depending on your perspective) like disabling root access for the end user. Not to mention simplifying backing everything up before the tinkering begins ;D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version