[solved] Broken packages?

rzrscm · 2011-12-30 06:57:30

Is there a way to fix this or an alternative way to get the packages? I've never had any problems with installing SDL libraries on any past versions of #!...

rzrscm@SVII:~$ sudo apt-get install -f libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-de
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libsdl-ttf2.0-dev' for regex 'libsdl-ttf2.0-de'
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:
libsdl1.2-dev : Depends: libasound2-dev but it is not going to be installed
Depends: libartsc0-dev but it is not going to be installed
Depends: libesd0-dev but it is not going to be installed
Depends: libpulse-dev but it is not going to be installed
E: Broken packages

Also, here's my sources file...It was default until I started having this problem and uncommented the commented lines to see if it'd help.

## CRUNCHBANG
## Compatible with Debian Squeeze, but use at your own risk.
deb http://packages.crunchbang.org/statler statler main
deb-src http://packages.crunchbang.org/statler statler main

## CRUNCHBANG MULTIMEDIA
## Debian Multimedia Mirror
deb http://packages.crunchbang.org/statler-mm squeeze main non-free
deb-src http://packages.crunchbang.org/statler-mm squeeze main non-free

## CRUNCHBANG MOZILLA
## Debian Mozilla Mirror
deb http://packages.crunchbang.org/statler-mozilla squeeze-backports iceweasel-release
deb-src http://packages.crunchbang.org/statler-mozilla squeeze-backports iceweasel-release

## DEBIAN
deb http://ftp.debian.org/debian/ squeeze main contrib non-free
deb-src http://ftp.debian.org/debian/ squeeze main contrib non-free

## DEBIAN SECURITY
deb http://security.debian.org/ squeeze/updates main
deb-src http://security.debian.org/ squeeze/updates main

## DEBIAN BACKPORTS
deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free
deb-src http://backports.debian.org/debian-backports squeeze-backports main contrib non-fr$

When I try to install the packages that it says it depends on but aren't going to be installed...I get this...

rzrscm@SVII:/etc/apt$ sudo apt-get install -f libasound2-dev libartsc0-dev libesd0-dev libpulse-dev
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:
libartsc0-dev : Depends: libglib2.0-dev but it is not going to be installed
libasound2-dev : Depends: libasound2 (= 1.0.23-2.1)
libesd0-dev : Depends: pkg-config but it is not going to be installed
libpulse-dev : Depends: libpulse0 (= 0.9.21-3+squeeze1) but 1.1-2 is to be installed
Depends: libpulse-mainloop-glib0 (= 0.9.21-3+squeeze1) but it is not going to be installed
Depends: libpulse-browse0 (= 0.9.21-3+squeeze1) but it is not going to be installed
Depends: libglib2.0-dev but it is not going to be installed
Depends: libavahi-client-dev but it is not going to be installed
E: Broken packages

Last edited by rzrscm (2012-01-01 10:04:36)

rzrscm · 2011-12-30 22:43:33

I just figured out that this and many other problems I've been having have been due to the backports being enabled by default. I disabled the backports sources and it seems to have solved every problem I've been having with packages.

pvsage · 2011-12-30 23:00:27

Try changing the pinning for Squeeze to 500 and see if the problem is still fixed. Then mark the thread as [solved]. wink

rzrscm · 2011-12-31 00:46:51

pvsage wrote:

Try changing the pinning for Squeeze to 500 and see if the problem is still fixed. Then mark the thread as [solved].

How do I do that?

pvsage · 2011-12-31 00:52:01

Edit the first post in the thread & append [solved] to the subject line.

rzrscm · 2011-12-31 00:54:04

pvsage wrote:

Edit the first post in the thread & append [solved] to the subject line.

I mean how do I change the pinning for Squeeze to 500?

rzrscm · 2011-12-31 01:07:10

Alright...The problem doesn't seem to be fixed after all. I still can't install SDL packages or Nvidia drivers.

rzrscm · 2011-12-31 01:09:35

Here's my current sources.list...

## CRUNCHBANG
## Compatible with Debian Squeeze, but use at your own risk.
deb http://packages.crunchbang.org/statler statler main
#deb-src http://packages.crunchbang.org/statler statler main

## CRUNCHBANG MULTIMEDIA
## Debian Multimedia Mirror
deb http://packages.crunchbang.org/statler-mm squeeze main non-free
#deb-src http://packages.crunchbang.org/statler-mm squeeze main non-free

## CRUNCHBANG MOZILLA
## Debian Mozilla Mirror
#deb http://packages.crunchbang.org/statler-mozilla squeeze-backports iceweasel-release
#deb-src http://packages.crunchbang.org/statler-mozilla squeeze-backports iceweasel-release

## DEBIAN
deb http://ftp.debian.org/debian/ squeeze main contrib non-free
#deb-src http://ftp.debian.org/debian/ squeeze main contrib non-free

## DEBIAN SECURITY
deb http://security.debian.org/ squeeze/updates main
#deb-src http://security.debian.org/ squeeze/updates main

## DEBIAN BACKPORTS
#deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free
#deb-src http://backports.debian.org/debian-backports squeeze-backports main contrib non-free

And preferences...

Package: *
Pin: release n=statler
Pin-Priority: 1001

Package: *
Pin: release n=squeeze
Pin-Priority: 500

dubois · 2011-12-31 01:19:49

I'm a late-comer to the thread but if it was me I wouldn't have both Crunchbang and Squeeze repositories open at the same time as they may, might, will conflict with each other. Which do you want to be your main repo right now? Comment out the other, try to make your updates, see how it goes. The theory holds now as it did previously with the backports.

rzrscm · 2011-12-31 01:40:50

dubois wrote:

I'm a late-comer to the thread but if it was me I wouldn't have both Crunchbang and Squeeze repositories open at the same time as they may, might, will conflict with each other. Which do you want to be your main repo right now? Comment out the other, try to make your updates, see how it goes. The theory holds now as it did previously with the backports.

Which one would you suggest me to use if I'm trying to get Nvidia drivers and SDL dev libraries installed?

dubois · 2011-12-31 01:43:40

I don't know. I don't have those drivers in either of my netbooks but I'd bet on Debian having them though.

el_koraco · 2011-12-31 01:44:06

Ahm, of course you want both #! and Squeeze repos, 99% of the system is Debian. Let's see the output of

apt-cache policy libasound2-dev libartsc0-dev libesd0-dev libpulse-dev

rzrscm · 2011-12-31 01:46:30

el_koraco wrote:

Ahm, of course you want both #! and Squeeze repos, 99% of the system is Debian. Let's see the output of
apt-cache policy libasound2-dev libartsc0-dev libesd0-dev libpulse-dev

rzrscm@SVII:~/code/cpp/allegro$ apt-cache policy libasound2-dev libartsc0-dev libesd0-dev libpulse-dev
libasound2-dev:
Installed: (none)
Candidate: 1.0.23-2.1
Version table:
1.0.23-2.1 0
500 http://ftp.debian.org/debian/ squeeze/main i386 Packages
libartsc0-dev:
Installed: (none)
Candidate: 1.5.9-3+b2
Version table:
1.5.9-3+b2 0
500 http://ftp.debian.org/debian/ squeeze/main i386 Packages
libesd0-dev:
Installed: (none)
Candidate: 0.2.41-8
Version table:
0.2.41-8 0
500 http://ftp.debian.org/debian/ squeeze/main i386 Packages
libpulse-dev:
Installed: (none)
Candidate: 0.9.21-3+squeeze1
Version table:
0.9.21-3+squeeze1 0
500 http://ftp.debian.org/debian/ squeeze/main i386 Packages

Also, when I try to install those packages...

The following packages have unmet dependencies:
libartsc0-dev : Depends: libglib2.0-dev but it is not going to be installed
libasound2-dev : Depends: libasound2 (= 1.0.23-2.1)
libesd0-dev : Depends: pkg-config but it is not going to be installed
libpulse-dev : Depends: libglib2.0-dev but it is not going to be installed
Depends: libavahi-client-dev but it is not going to be installed
E: Broken packages

Last edited by rzrscm (2011-12-31 01:50:35)

el_koraco · 2011-12-31 01:48:16

It's very late here, I'll look into this tomorrow. Maybe someone else can take a crack at it in the meantime.

dubois · 2011-12-31 01:51:20

I'll let you do this el_k, but previously I was speaking from experience with Statler 10 and found that keeping both repos open at the same time altered my system over time -- the longer the time from S 10's release date the greater the change because Statler was static while Debian Squeeze wasn't. I mean, it was stable but not static. It continued to get updates and soon Statler was no longer Statler as envisioned by corenominal but something else.

rzrscm · 2011-12-31 01:58:09

dubois wrote:

I'll let you do this el_k, but previously I was speaking from experience with Statler 10 and found that keeping both repos open at the same time altered my system over time -- the longer the time from S 10's release date the greater the change because Statler was static while Debian Squeeze wasn't. I mean, it was stable but not static. It continued to get updates and soon Statler was no longer Statler as envisioned by corenominal but something else.

Well, I just tried disabling Debian repos and keeping the #!, and I get this...

rzrscm@SVII:~/code/cpp/allegro$ sudo apt-get install libasound2-dev libartsc0-dev libesd0-dev libpulse-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libasound2-dev
E: Unable to locate package libartsc0-dev
E: Unable to locate package libesd0-dev
E: Unable to locate package libpulse-dev

When I disable #! and enable Debian and run upgrade...I get this...I canceled it because I don't know if this is something I want to do.

rzrscm@SVII:~/code/cpp/allegro$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
grub-common grub-pc
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,801 kB of archives.
After this operation, 41.0 kB of additional disk space will be used.

Last edited by rzrscm (2011-12-31 02:02:16)

dubois · 2011-12-31 02:01:30

I'm a GUI kind of guy and would use synaptic but if you or someone else knows how to do it via terminal OK, but those broken packages need to be dealt with first, I'm sure.

rzrscm · 2011-12-31 02:08:06

dubois wrote:

I'm a GUI kind of guy and would use synaptic but if you or someone else knows how to do it via terminal OK, but those broken packages need to be dealt with first, I'm sure.

Does Synaptic have any features that would help me deal with the broken packages? I do almost everything in the terminal...But I'm willing to try any idea right now.

dubois · 2011-12-31 02:26:09

Edit > Fix Broken Packages

But I only ever had to do it one about a year or so ago and that's all I remember about it. If you're more comfortable with the CLI then use that even if you have to search through here or elsewhere for details. There'll be a batch of users coming on soon -- may be some help there. wink

dubois · 2011-12-31 02:40:39

In Synaptic:
Choose Edit > Fix Broken Packages from the menu.
Choose Apply Marked Changes from the Edit menu or press Ctrl + P.
Confirm the summary of changes and click Apply.
In a terminal:
sudo dpkg --configure -a
sudo apt-get install -f

SOURCE -- http://crunchbanglinux.org/forums/post/128167/#p128167

rzrscm · 2011-12-31 03:19:02

dubois wrote:

In Synaptic:
Choose Edit > Fix Broken Packages from the menu.
Choose Apply Marked Changes from the Edit menu or press Ctrl + P.
Confirm the summary of changes and click Apply.
In a terminal:
sudo dpkg --configure -a
sudo apt-get install -f

SOURCE -- http://crunchbanglinux.org/forums/post/128167/#p128167

Nothing...Still broken.

pvsage · 2011-12-31 06:01:20

dubois wrote:

I'm a late-comer to the thread but if it was me I wouldn't have both Crunchbang and Squeeze repositories open at the same time as they may, might, will conflict with each other. Which do you want to be your main repo right now? Comment out the other, try to make your updates, see how it goes. The theory holds now as it did previously with the backports.

I think you may be thinking of CrunchBang + Wheezy/Testing or CrunchBang + Sid/Unstable. Default for Statler is to have Statler + Squeeze repos active; that way you get security updates from Debian.

@rzrscm: I wish I could help you with nVidia drivers, but I don't have any hardware that requires them; no experience with SDL either. Perhaps if you bait the subject line with a more descriptive title (e.g. add nVidia and SDL to the subject) you might hook people who have more knowledge on these.

el_koraco · 2011-12-31 09:51:12

Let's try this:

sudo apt-get install -t squeeze libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev

FYI, I get pretty much the same results on pure Squeeze as you, so it's nothing to do with Statler. Debian patch hell is in the works.

Last edited by el_koraco (2011-12-31 09:54:05)

rzrscm · 2012-01-01 10:11:03

el_koraco wrote:

Let's try this:
sudo apt-get install -t squeeze libsdl1.2-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev
FYI, I get pretty much the same results on pure Squeeze as you, so it's nothing to do with Statler. Debian patch hell is in the works.

I finally solved the problem and everything works. What I did was disable all of the backports packages, then I changed the pinning around so Squeeze's priority was 1001 and Statler's was 100...Then I ran a dist-upgrade and it downgraded just about everything. After that, I redid the pin priority to what it was before and did another upgrade...Now I have the Nvidia drivers and SDL libraries installed and everything else I was having problems with are working. My only gripe with this is that it downgraded Iceweasel to an earlier version that doesn't support Adblock, and the only way to get the newer version would be enabling the backports and letting it upgrade some stuff from there, which would obviously put me in the same position I was in before...At least I have NoScript.

Last edited by rzrscm (2012-01-01 10:14:19)

el_koraco · 2012-01-01 10:14:17

http://mozilla.debian.net/

CrunchBang Linux

SEARCH

#1 2011-12-30 06:57:30

[solved] Broken packages?

#2 2011-12-30 22:43:33

Re: [solved] Broken packages?

#3 2011-12-30 23:00:27

Re: [solved] Broken packages?

#4 2011-12-31 00:46:51

Re: [solved] Broken packages?

#5 2011-12-31 00:52:01

Re: [solved] Broken packages?

#6 2011-12-31 00:54:04

Re: [solved] Broken packages?

#7 2011-12-31 01:07:10

Re: [solved] Broken packages?

#8 2011-12-31 01:09:35

Re: [solved] Broken packages?

#9 2011-12-31 01:19:49

Re: [solved] Broken packages?

#10 2011-12-31 01:40:50

Re: [solved] Broken packages?

#11 2011-12-31 01:43:40

Re: [solved] Broken packages?

#12 2011-12-31 01:44:06

Re: [solved] Broken packages?

#13 2011-12-31 01:46:30

Re: [solved] Broken packages?

#14 2011-12-31 01:48:16

Re: [solved] Broken packages?

#15 2011-12-31 01:51:20

Re: [solved] Broken packages?

#16 2011-12-31 01:58:09

Re: [solved] Broken packages?

#17 2011-12-31 02:01:30

Re: [solved] Broken packages?

#18 2011-12-31 02:08:06

Re: [solved] Broken packages?

#19 2011-12-31 02:26:09

Re: [solved] Broken packages?

#20 2011-12-31 02:40:39

Re: [solved] Broken packages?

#21 2011-12-31 03:19:02

Re: [solved] Broken packages?

#22 2011-12-31 06:01:20

Re: [solved] Broken packages?

#23 2011-12-31 09:51:12

Re: [solved] Broken packages?

#24 2012-01-01 10:11:03

Re: [solved] Broken packages?

#25 2012-01-01 10:14:17

Re: [solved] Broken packages?

Board footer