[SOLVED] Problem with bash update

MartenH · 11-17-2014, 01:11 PM

I attempt to perform an update using

Code:

sudo apt-get -y install bash

But instead of an update I get the following result:

Code:

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:
 bash : PreDepends: libc6 (>= 2.15) but 2.13-38+deb7u6 is to be installed
E: Unable to correct problems, you have held broken packages.

What can I do to resolve this?

rtmistler · 11-17-2014, 02:33 PM

Not sure if running

Code:

sudo apt-get update

may help here. I'm also guessing that you already did do that, but for me that's a common error because I'm so fast to get the install, I forget to update the repository first. There are also force options for apt, however if you do that and don't have compatible libraries, then that's bad. I'd look at what it's saying it doesn't have as a dependency and try to install that. The other question I'd try to resolve is whether or not I have bash in the first place.

MartenH · 11-17-2014, 03:36 PM

Yeah, I tried that already. Makes no difference sadly.

widget · 11-17-2014, 04:30 PM

First off, what version are you using? I just checked in my Squeeze install and it is using libc6_2.11.3-2.

How long since the last package upgrade?

A look at your sources.list would be helpful.

Code:

cat /etc/apt/sources.list

MartenH · 12-02-2014, 04:15 PM

I'm not sure how I check which version i have?

Here is the requested output:

Code:

$ sudo cat /etc/apt/sources.list
#

# deb cdrom:[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot i386 LIVE/INSTALL Binary 20130505-15:44]/ wheezy main

#deb cdrom:[Debian GNU/Linux 7.0.0 _Wheezy_ - Official Snapshot i386 LIVE/INSTALL Binary 20130505-15:44]/ wheezy main

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

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

# wheezy-updates, previously known as 'volatile'
deb http://ftp.se.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.se.debian.org/debian/ wheezy-updates main

deb http://download.webmin.com/download/repository sarge contrib
deb http://webmin.mirror.somersettechsolutions.co.uk/repository sarge contrib

#For firefox download
deb http://packages.linuxmint.com debian import

widget · 12-02-2014, 08:39 PM

Code:

Debian GNU/Linux 7.0.0 _Wheezy

Is a pretty good indication that you are running Debian 7 (Wheezy).

A better indication of the version is from;
[code]
cat /etc/debian_version
[code]
which for a currently up to date Wheezy should give you the output;

Code:

7.7

Your sources.list looks good so that shouldn't be the problem. If the output from the debian_version file is not 7.7 you need to, as root;

Code:

apt-get update && apt-get upgrade && apt-get dist-upgrade

apt-get dist-upgrade is skipped by many people for fear that it does a version upgrade. This is not the case. What it does is upgrade packages that may need new packages installed or some old package removed to work properly.

If you run into problems with the complete upgrade due to not keeping up as you should then you should first try, as root;

Code:

dpkg --configure -a

and then, if that doesn't do the trick and you keep getting the message about broken packages use, again as root;

Code:

apt-get -f install

which will attempt to fix the broken package problem.

A really good idea is to quit using the -y option with any command you use. That is handy for people that know exactly what the problems may be and that are sure they will not have them. As you are having them it would be a really good idea to have all the output available to you for any command you give.

MartenH · 12-03-2014, 03:50 PM

Thanks for the good replies.

I thought you meant the libc version.
You are correct that I am running Wheezy and cat /etc/debian_version gives me 7.7 as expected.

running

Code:

sudo apt-get update && apt-get upgrade && apt-get dist-upgrade

gives me

Code:

... repository updates...
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

running each command individually gives me successful update, but both upgrade and dist-upgrade end as

Code:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  bash
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

I get no output at all with

Code:

sudo dpkg --configure -a

And I get the same result as for upgrade and dist-upgrade when running

Code:

sudo apt-get -f install

widget · 12-03-2014, 07:31 PM

So bash must be up to date.

If you tried to install it you should be notified that it is already at the latest version.

When you use your terminal, unless you are using a non default shell, bash is your shell so it must be installed.

Code:

apt-cache policy bash

can be run at the user prompt ($).

Should show bash as installed.

Code:

sam@lounge:~$ apt-cache policy bash
bash:
  Installed: 4.3-11+b1
  Candidate: 4.3-11+b1
  Version table:
 *** 4.3-11+b1 0
        500 http://ftp.us.debian.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status

Your version number and the repo should be the only differences.

If your concern is the bash security upgrades then don't worry about it, you have the latest patches from Debian.

dmlinton · 11-20-2015, 09:49 PM

I know that this thread is somewhat old but the solution is to comment, or remove, the linux mint repository from the apt sources.

MartenH · 11-28-2015, 06:43 PM

Quote:

Originally Posted by dmlinton

I know that this thread is somewhat old but the solution is to comment, or remove, the linux mint repository from the apt sources.

You are correct. I solved this about a year later by figuring out that was the problem. I added the line for firefox download and it messed things up.
Forgot to update this thread for anyone else with the same issue.