Debian Wheezy - No Idea Which Repo I'm On / Am I Testing?

gauntface · 01-20-2013, 11:11 AM

Hi All,

This may seem like a stupid thread title, but please bear with me.

I installed Debian Wheezy from the Debian site, aware that I was on a testing build of Debian. The reason for this is because I wanted to get off of Ubuntu Unity and back on to a clean version of Gnome Shell.

Now I'm trying to install xbmc and having some issues.

Quote:

matt@debian:~$ sudo apt-get install libcdio10
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcdio10 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libcdio10' has no installation candidate
matt@debian:~$ sudo apt-get install xbmc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
xbmc : Depends: xbmc-bin (>= 3:11.0-0.squeeze1) but it is not going to be installed
Depends: xbmc-data (>= 3:11.0-0.squeeze1)
Depends: xbmc-skin or
xbmc-skin-confluence
E: Unable to correct problems, you have held broken packages.

I dug a little deeper and found that if I try to install xbmc-bin it has some of it's own dependency issues:

Quote:

matt@debian:~$ sudo apt-get install xbmc-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
xbmc-bin : Depends: libcdio10 but it is not installable
Depends: libglew1.5 (>= 1.5.4) but it is not installable
Depends: libmicrohttpd5 but it is not installable
Depends: libmysqlclient16 (>= 5.1.21-1) but it is not installable
Depends: libshairport1 but it is not going to be installed
Depends: libssl0.9.8 (>= 0.9.8m-1) but it is not installable
Depends: libyajl1 (>= 1.0.8) but it is not installable
E: Unable to correct problems, you have held broken packages.

Then I tried installing libcdio10 and it's not found:

Quote:

matt@debian:~$ sudo apt-get install libcdio10
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcdio10 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libcdio10' has no installation candidate

I did some googling to see how to install xbmc on Debian Wheezy thinking that perhaps on the test build it wasn't an easy apt-get install process but blog posts suggest otherwise.

So the only thing I can't think of is that my repo list is wrong. I performs an apt-get update && apt-get dist-upgrade and now my sources.list looks like this, but I still have the same issue with xbmc:

Code:

# 

# deb cdrom:[Debian GNU/Linux wheezy-DI-b3 _Wheezy_ - Official Snapshot i386 NETINST Binary-1 20121011-11:55]/ wheezy main

# deb cdrom:[Debian GNU/Linux wheezy-DI-b3 _Wheezy_ - Official Snapshot i386 NETINST Binary-1 20121011-11:55]/ wheezy main

deb http://ftp.uk.debian.org/debian/ wheezy main non-free contrib
deb-src http://ftp.uk.debian.org/debian/ wheezy main non-free contrib

deb http://security.debian.org/ wheezy/updates main non-free contrib
deb-src http://security.debian.org/ wheezy/updates main non-free contrib

deb http://www.deb-multimedia.org squeeze main non-free
deb-src http://www.deb-multimedia.org squeeze main non-free
deb http://www.deb-multimedia.org squeeze-backports main
deb-src http://www.deb-multimedia.org squeeze-backports main

That's where I am at the moment. Does anyone have the missing link to fix this problem? I'm at a bit of a loss.

Thanks,
Matt

TobiSGD · 01-20-2013, 11:47 AM

You have added the wrong repository for the multimedia part. Your main distribution is Wheezy/Testing, but you have added Squeeze/Stable to the sources.list. As far as I know there is also no backports repository on deb-multimedia.org.
To fix that remove the last three lines from the sources.list file and replace the remaining line from de-multimedia.org with

Code:

 deb http://www.deb-multimedia.org wheezy main non-free

Then run

Code:

apt-get update
apt-get dist-upgrade

to update the package database and replace anything that is possibly already installed from the multimedia repository with the version for your branch of Debian.
After that the installation of xbmc and other programs should work.

widget · 01-20-2013, 03:12 PM

As Wheezy is currently Debian testing there are no backport repos at all for Wheezy.

Backported packages for Debian Stable come from Debian Testing.

On thing you should know about, as one ex Ubuntu user to another, is this thread;
http://www.linuxquestions.org/questi...e-list-330913/

The Debian repo system is actually simpler than the Ubuntu system. It is, however, a bit tough to understand at first.

If you install Debian Stable, right now, the repo will be listed as "squeeze" in your sources.list.

If you install Debian Testing, right now, the repo will be listed as "wheezy" in your sources.list.

This will keep you in those repos when Wheezy becomes the new stable.

If, however, your sources.list reads "stable" in a Squeeze install there will be a big change when Wheezy becomes the new stable. Your system will then upgrade to Wheezy.

If you, like me, have "testing" in your Wheezy sources.list the system will, on the day Wheezy becomes the new stable, upgrade to Jessie (the new "testing" version code name).

I do not use xbmc but running this;

Code:

root@debian:/home/sam# apt-cache search "xbmc"
libnfo1 - an NFO file parser/writer library
minidlna - lightweight DLNA/UPnP-AV server targeted at embedded systems
texlive-latex-extra - TeX Live: LaTeX supplementary packages
xbmc-eventclients-xbmc-send - XBMC Media Center (Event Client XBMC-SEND package)
xbmc - XBMC Media Center (full metapackage)
xbmc-addon-xvdr - XVDR addon for XBMC.
xbmc-bin - XBMC Media Center (binary data package)
xbmc-data - XBMC Media Center (arch-independent data package)
xbmc-eventclients-common - XBMC Media Center (Event Client Common package)
xbmc-eventclients-dev - XBMC Media Center (Event Client Dev package)
xbmc-eventclients-j2me - XBMC Media Center (Event Client J2ME package)
xbmc-eventclients-ps3 - XBMC Media Center (Event Client PS3 package)
xbmc-eventclients-wiiremote - XBMC Media Center (Event Client WII Remote support package)
xbmc-skin-confluence - XBMC Media Center (Confluence HD skin)
xbmc-skin-focus - XBMC skin
xbmc-skin-rapier - XBMC skin - Rapier.
xbmc-skin-xeebo - Boxee style skin for XBMC.
xbmc-standalone - XBMC Media Center (standalone program)

Makes me think you want either;

Code:

xbmc - XBMC Media Center (full metapackage)

or

Code:

xbmc-standalone - XBMC Media Center (standalone program)

The package "xbmc" should pull in every thing you want easily. Not sure what the "xbmc-standalone" package is but you very well may.

Have Fun.

I think you will find Debian to be very nice.

Phiebie · 01-23-2013, 11:19 AM

Quote:

Originally Posted by widget

Code:

root@debian:/home/sam# apt-cache search "xbmc"

I think you will find Debian to be very nice.

Of course:-)
But you could/should also have stated, that Deb recommends to use "aptitude" for the handling of packages. This program not only resolves dependencies when installing, but also prevents you from uninstalling - in your eyes (un-) - necessary packages, that are needed for other packages.
I lively remember when I once did an "apt-get install xxx" and then followed the advice to "autoremove" quite a bunch of other progs. Well, my disk was then almost empty and I had to reinstall from scratch my whole system!

TobiSGD · 01-23-2013, 02:08 PM

Quote:

Originally Posted by Phiebie

Of course:-)
But you could/should also have stated, that Deb recommends to use "aptitude" for the handling of packages. This program not only resolves dependencies when installing, but also prevents you from uninstalling - in your eyes (un-) - necessary packages, that are needed for other packages.
I lively remember when I once did an "apt-get install xxx" and then followed the advice to "autoremove" quite a bunch of other progs. Well, my disk was then almost empty and I had to reinstall from scratch my whole system!

The autoremove option is inherently dangerous, every Debian user should be aware of that. It is of course highly recommended to actually read what apt-get or aptitude will recommend, especially when they recommend to remove a large number of packages. Nonetheless, aptitude will not prevent you from destroying your system with automatically removed packages, since aptitude will automatically launch the autoremove function every time a package is (de-)installed, it just indicates it directly when (de-)installing about that. So if you are careless aptitude is as dangerous as apt-get.

widget · 01-23-2013, 09:00 PM

I think you will find that they recommend apt-get now. Changed to apt-get for version upgrades with the release of Squeeze.

I certainly prefer aptitude for installing from Debian experimental.

lazylogic · 01-24-2013, 04:06 AM

For what it's worth, I've just installed a laptop with Debian Wheezy with the following repositories:

Quote:

deb http://ftp.riken.jp/Linux/debian/debian/ wheezy main non-free contrib
deb http://security.debian.org/ wheezy/updates main non-free contrib
deb http://www.deb-multimedia.org testing main non-free

Using aptitude to simulate an installation, no problem is reported

Quote:

aptitude -s install xbmc
The following NEW packages will be installed:
libcec2{a} libglew1.7{a} liblockdev1{a} libmicrohttpd10{a} libpcrecpp0{a} libtinyxml2.6.2{a} libva-glx1{a} mesa-utils{a} xbmc xbmc-bin{a}
xbmc-data{a} xbmc-skin-confluence{a}
0 packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.7 MB of archives. After unpacking 66.0 MB will be used.

So if you follow what TobiSGD had advise above in #2, you should be fine.

Enjoy!

TobiSGD · 01-24-2013, 05:12 AM

You should either use testing or wheezy over the complete file, not both. Otherwise you will run into troubles when Wheezy becomes the new Stable, from this point one you are mixing a Stable and a Testing repository.
So, if you want to go with the Testing branch and stay there replace all occurrences of wheezy with testing, if you want to go with Wheezy (even after it becomes Stable) replace testing with wheezy.

widget · 01-24-2013, 11:09 AM

Quote:

Originally Posted by TobiSGD

You should either use testing or wheezy over the complete file, not both. Otherwise you will run into troubles when Wheezy becomes the new Stable, from this point one you are mixing a Stable and a Testing repository.
So, if you want to go with the Testing branch and stay there replace all occurrences of wheezy with testing, if you want to go with Wheezy (even after it becomes Stable) replace testing with wheezy.

Excelent point.

Hasn't mattered much up to now but anyone with "dirty" sources.lists better be cleaning them up.