DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My "problem" is that I cannot install the MATE desktop. I had previously successfully installed it on Ububtu 12.04 and Debian 7.4.somethng-or-other. These gave me problems in other areas, though 7.4.Whatever-it-was did give me most of what I wanted. Now I've installed debian 7.5. Everything else is fine, but I get an error in Synaptic when I try to install MATE:
Quote:
E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies
I've looked at a number of different posts in this and other forums, however, they all seem to be about mixing "test" and "stable" repositories. That is definitely not what I'm doing. Here are the contents of my /etc/apt/sources.list:
Quote:
# deb cdrom:[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37]/ wheezy contrib main
deb cdrom:[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37]/ wheezy contrib main
# Line commented out by installer because it failed to verify:
deb http://security.debian.org/ wheezy/updates main contrib
# Line commented out by installer because it failed to verify:
# deb-src http://security.debian.org/ wheezy/updates main contrib
# wheezy-updates, previously known as 'volatile'
# A network mirror was not selected during install. The following entries
# are provided as examples, but you should amend them as appropriate
# for your mirror of choice.
Using Synaptic to try to fix the problem gave me the error quoted above. So how can I fix this? One post that I read suggested "dpkg -l" to find the package that was "held" but the output was... well... daunting to say the least. In the masses of information produced, the following line drew my attention:
Quote:
ii mate-archive-keyring 1.6.0 all GnuPG key of the MATE repository
Can I just remove that package and start again? After all the fiddling about, I am reluctant to just "try" something and hope that it works. Is this package really required for the MATE desktop? I'm thinking maybe I should do without it.
Any thoughts or hints would be welcome.
Cheers
Achim
P.S. Yes, I have tried "apt-get update" followed by "apt-get install -f" (suggested in a number of other posts). It achieved precisely nothing, nichts, nada.
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
Rep:
Please post all the output you can so we can see exactly what is going on.
Just as an aside MATE is now in Debian's official repository for Sid and Jessie and is being backported into Wheezy. In the next couple of months you will be able to run MATE natively (meaning no 3rd party repository) in Wheezy.
Your sources.list is a little messy. Instead of this
Code:
# deb cdrom:[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37]/ wheezy contrib main
deb cdrom:[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37]/ wheezy contrib main
# Line commented out by installer because it failed to verify:
deb http://security.debian.org/ wheezy/updates main contrib
# Line commented out by installer because it failed to verify:
# deb-src http://security.debian.org/ wheezy/updates main contrib
# wheezy-updates, previously known as 'volatile'
# A network mirror was not selected during install. The following entries
# are provided as examples, but you should amend them as appropriate
# for your mirror of choice.
deb http://ftp.debian.org/debian/ wheezy-updates main contrib
# deb-src http://ftp.debian.org/debian/ wheezy-updates main contrib
# MATE desktop
# deb http://repo.mate-desktop.org/debian wheezy main
deb http://packages.mate-desktop.org/repo/debian wheezy main
I would have this
Code:
deb http://http.debian.net/debian wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib
deb http://ftp.debian.org/debian/ wheezy-updates main contrib
# MATE desktop
deb http://repo.mate-desktop.org/debian wheezy main
Last edited by k3lt01; 05-22-2014 at 06:48 PM.
Reason: sources.list suggestion
The only other output I can supply is that which I get from the combination "apt-get update" and "apt-get install -f".
Quote:
achim@ascomtux:~$ sudo apt-get update
[sudo] password for achim:
Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37] wheezy Release.gpg
Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37] wheezy Release
Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37] wheezy/contrib amd64 Packages/DiffIndex
Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37] wheezy/main amd64 Packages/DiffIndex
Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37] wheezy/contrib Translation-en_AU
Ign cdrom://[Debian GNU/Linux 7.5.0 _Wheezy_ - Official amd64 DVD Binary-1 20140426-13:37] wheezy/main Translation-en_AU
Hit http://packages.mate-desktop.org wheezy Release.gpg
Hit http://packages.mate-desktop.org wheezy Release
Get:1 http://ftp.debian.org wheezy-updates Release.gpg [836 B]
Hit http://packages.mate-desktop.org wheezy/main amd64 Packages
Hit http://security.debian.org wheezy/updates Release.gpg
Get:2 http://ftp.debian.org wheezy-updates Release [124 kB]
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://ftp.debian.org wheezy-updates/main amd64 Packages/DiffIndex
Get:3 http://ftp.debian.org wheezy-updates/contrib amd64 Packages [14 B]
Get:4 http://ftp.debian.org wheezy-updates/contrib Translation-en [14 B]
Ign http://packages.mate-desktop.org wheezy/main Translation-en_AU
Hit http://ftp.debian.org wheezy-updates/main Translation-en/DiffIndex
Ign http://packages.mate-desktop.org wheezy/main Translation-en
Fetched 125 kB in 3s (38.8 kB/s)
Reading package lists... Done
achim@ascomtux:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
achim@ascomtux:~$
I confess I am not that skilled in the use of aptitude. Until recently I only used Synaptic to manage packages. I guess it's time to learn, eh?
As for the state of my sources.list, well, I tend to leave 'em how I find 'em. The three lines at the bottom are my doing. The rest was that way from the start. :-)
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
Rep:
Quote:
Originally Posted by achim_59
The only other output I can supply is that which I get from the combination "apt-get update" and "apt-get install -f".
Please post it all.
Quote:
Originally Posted by achim_59
I confess I am not that skilled in the use of aptitude. Until recently I only used Synaptic to manage packages. I guess it's time to learn, eh?
if you are talking about the command line it is a good idea to learn it but it is not a necessity.
Quote:
Originally Posted by achim_59
As for the state of my sources.list, well, I tend to leave 'em how I find 'em. The three lines at the bottom are my doing. The rest was that way from the start. :-)
The big problem with your sources.list is you must always have the install cd/dvd available. If you don't you may find you have problems like the one you are having now. I would suggest you tidy it up and run apt-get update after you tidy it up and let us know what happens. My guess is MATE requires a package from Debian that Debian can't supply because your sources.list is pointing to 1 cd/dvd and not the full main section of the repository and that is why it can't resolve dependencies.
I will work my way through the suggestions in the next day or so and post again after that.
My problem... one of my problems is that I have 1 or 2 hours in the evenings (at best) to work on this stuff. To add to the difficulties, except on weekends, I only have the mobile connection through my UMTS modem. I have just gone over my limit for this month and have now been throttled down to speeds comparable with a 56K modem, if that. Downloading is really slow at the moment.
Incidentally, I have "tidied up" the sources.list, so that it no longer points to the CD. I really had'nt noticed it before... only goes to show that you can look without seeing! Sadly this tidying up has had no appreciable effect.
However, I will look closely at all the sugesstions people have given and try a few things out.
Thanks again to all who have contributed. I'll keep you posted, as it were.
Fix your broken system before adding 3rd party repos.
Edit your sources as follows:
Code:
deb http://ftp2.de.debian.org/debian wheezy main contrib
#deb-src http://ftp2.de.debian.org/debian wheezy main contrib
deb http://security.debian.org/ wheezy/updates main contrib
#deb-src http://security.debian.org/ wheezy/updates main contrib
# wheezy-updates, previously known as 'volatile'
deb http://ftp2.de.debian.org/debian/ wheezy-updates main contrib
#deb-src http://ftp2.de.debian.org/debian/ wheezy-updates main contrib
It's public holiday over here. As a result I have a bit more time than usual to try to sort this stuff out.
OK, first some replies:
EDDY1: I hadn't added the line "deb http://http.debian.net/debian wheezy main contrib non-free" but I have now.
k3lt01: Thanks for the advice in the first place and my apologies for not taking better note of what you suggested.
cynwulf: Your suggestion has been noted. It would mean taking a few steps back, but maybe that's the best way to go. If nothing else works I'll give the upgrade a go.
What I have done to date is:
1. Contrary to the advice given so far, I added yet another repository for Shrew Soft VPN Client. Yeah... bad boy and all that, but the VPN client works fine and doesn't cause problems. Besides, I need it for my work.
2. I did a kernel upgrade to 3.12 and tried again to fix the broken packages. I'm wondering what held packages actually are? Why are they being held? What is holding them and why can't they be fixed or replaced? Out of scope for this forum, I know, but it's something I'll have to look into if I'm gonna understand this stuff.
3. Having been spoiled by Ubuntu for the past 7 years, I hadn't done an update (Ubuntu prompts you... sometimes too often). So I did an update using the system tool which updated forty-something packages, removed some more, and listed a number of "blocked updates" at the end. Something else to look into. One thing I noted with interest is that I now have a 3.14 kernel as well. Guess I'll try booting into that next time I restart. I'll hang on to the old ones, though incase I have problems down the track.
The blocked packages included GNU flashplayer packages, Network mapper, and some Samba packages.
In each case the details showed the following message:
Quote:
This update is blocked.
The developer logs will be shown as no description is available for this update:
I'm not sure how significant this is and I really don't want to be distracted from the task at hand. I'll get back to this stuff, later.
Next steps:
1. Make a backup of the applications stuff I'm working on, as well as the intalled software (Java, JBoss, etc).
2. Restart & hold breath.
3. Try to fix broken packages... I will use the suggestions made above.
4. If the preceding steps don't achieve the desired result, then I'll the upgrade cynwulf has suggested (with appropriate sources.list.
I will post detailed results when I've done all that.
2. I did a kernel upgrade to 3.12 and tried again to fix the broken packages. I'm wondering what held packages actually are? Why are they being held? What is holding them and why can't they be fixed or replaced? Out of scope for this forum, I know, but it's something I'll have to look into if I'm gonna understand this stuff.
Packages can be held for many reasons. The user (you) can do it (not the case here), or the package manager will hold a package because it believes that the package will break your system, make it unstable, conflicts with another installed package, etc.
Quote:
3. Having been spoiled by Ubuntu for the past 7 years, I hadn't done an update (Ubuntu prompts you... sometimes too often). So I did an update using the system tool which updated forty-something packages, removed some more, and listed a number of "blocked updates" at the end. Something else to look into. One thing I noted with interest is that I now have a 3.14 kernel as well. Guess I'll try booting into that next time I restart. I'll hang on to the old ones, though incase I have problems down the track.
Debian will do this as well if the repositories are set up properly.
It's always a good idea to make sure a new kernel works before removing the old, you'll be ok there.
Quote:
4. If the preceding steps don't achieve the desired result, then I'll the upgrade cynwulf has suggested (with appropriate sources.list.
The reason cynwulf told you to dist-upgrade is that a normal upgrade will not install or remove additional packages, just upgrade what you have installed. Therefore, by running apt-get dist-upgrade, any packages that may need to be installed to satisfy dependencies will be. In fact, some of your packages that are being held back are likely being held back because of missing dependencies.
From the apt-get man page:
Code:
upgrade
upgrade is used to install the newest versions of all packages
currently installed on the system from the sources enumerated in
/etc/apt/sources.list. Packages currently installed with new
versions available are retrieved and upgraded; under no
circumstances are currently installed packages removed, or packages
not already installed retrieved and installed. New versions of
currently installed packages that cannot be upgraded without
changing the install status of another package will be left at
their current version. An update must be performed first so that
apt-get knows that new versions of packages are available.
dist-upgrade
dist-upgrade in addition to performing the function of upgrade,
also intelligently handles changing dependencies with new versions
of packages; apt-get has a "smart" conflict resolution system, and
it will attempt to upgrade the most important packages at the
expense of less important ones if necessary. The dist-upgrade
command may therefore remove some packages. The
/etc/apt/sources.list file contains a list of locations from which
to retrieve desired package files. See also apt_preferences(5) for
a mechanism for overriding the general settings for individual
packages.
Seems I clicked a tick too soon. I had prepared a detailed report of what I did with all the outputs and everything. I intended to post that before logging out and back in. Well, I finished typing it all, checked a couple of settings, and then clicked "log out". The dumb part is that I didn't submit the post first! What an idiot!
Short version: Broken packages problem solved.
OK here's a summary of what I did. Firstly, a listing of what my /etc/apt/sources.list looks like:
Code:
deb http://http.debian.net/debian wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib
deb http://ftp.debian.org/debian/ wheezy-updates main contrib
# MATE desktop
# deb http://repo.mate-desktop.org/debian wheezy main
deb http://packages.mate-desktop.org/repo/debian wheezy main
# Shrew Soft VPN for debian
deb http://ftp.de.debian.org/debian wheezy-backports main
Steps taken:
Backup. Only the personal & work stuff, of course.
Entered "apt-get update". No untoward messages.
Entered "apt-get install -f". This gave a message suggesting there was nothing to be done. However, it also listed a vast array of "automatically installed" packages which were "no longer required". It also suggested the next command.
Entered "apt-get autoremove" (I think). I may have the command syntax wrong, but it was something like that. The previously listed packages were removed with no really drastic side effects.
Used synaptic to successfully install MATE desktop. No errors, just a message stating "All packages successfully installed."
It's a real pain, that I've lost all those listings. It showed some interesing stuff, like the fact that Libre Office was amongst the packages which were autoremoved. I'm now faced with a difficult decision: do I re-install Libre Office or do I replace it with Open Office? I use Open Office at a customer site under Windows and I'm pretty happy with it (beats the pants off MS Office for usability). Die Qual der Wahl!! If only all my problems were like that.
Yep. I do still have a few areas of concern. The WLAN/Blue tooth device (Intel Dual AC7260) doesn't seem to be recognised, so I'm not able to use WLAN, which is important for my work. External monitors are also not being identified. I have an HDMI port for attaching an external monitor, but I end up with the same picture on the monitor and on the laptop. When I check System -> Control Center -> Monitors, I'm shown one "unknown" Full HD Monitor and clicking Detect Monitors doesn't achieve anything. I'm assuming that it's the laptop Monitor that's being shown, since that's the desciption I got from ubuntu 12.04 when I checked the Monitor (ubuntu correctly identified the external monitor as a Fujitsu). My reasons for changing from 12.04 to debian? Complicated and ultimately very necessary but I won't bore you with the details.
I will trawl the internet for solutions to my other problems, but essentially I can work with what I've got if I have to. I'll post new threads if I need help. This one I am going to mark as solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
debian held broken package
Updates installed
