Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Upgrade Error
Upgrade Error
Hi,
Was away for a week and a half, so behind on a few updates. Ran update and upgrade, and receive this error message:
Calculating upgrade... Error!
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:
systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+b1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Note that I am running testing, NOT unstable. Any idea how to help? Thanks in advance!
Was away for a week and a half, so behind on a few updates. Ran update and upgrade, and receive this error message:
Calculating upgrade... Error!
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:
systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+b1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Note that I am running testing, NOT unstable. Any idea how to help? Thanks in advance!
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: Upgrade Error
Is the most likely reason,......if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
https://www.debian.org/doc/manuals/debi ... ng.en.html
3.1.6 You are talking about testing being broken. What do you mean by that?
Sometimes, a package might not be installable through package management tools. Sometimes, a package might not be available at all, maybe it was (temporarily) removed due to bugs or unmet dependencies. Sometimes, a package installs but does not behave in the proper way.
When these things happen, the distribution is said to be broken (at least for this package).
"testing" is testing, it is NOT stable, there for it is unstable , unstable and testing,by Bugs318 » Note that I am running testing, NOT unstable.
all though a little different, are in the same "class" so to speak.
From the same , link above:
See also : https://wiki.debian.org/DebianTesting3.1.5 Could you tell me whether to install stable, testing or unstable?
No. This is a rather subjective issue. There is no perfect answer as it depends on your software needs, your willingness to deal with possible breakage, and your experience in system administration. Here are some tips:
Stable is rock solid. It does not break and has full security support. But it not might have support for the latest hardware.
Testing has more up-to-date software than Stable, and it breaks less often than Unstable. But when it breaks, it might take a long time for things to get rectified. Sometimes this could be days and it could be months at times. It also does not have permanent security support.
=====================
The error message is pretty clear, self explanatory, you could wait a week or 2 and see, maybe by then the broken package will be fixed, I suppose,The following packages have unmet dependencies:
systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+b1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Or you could read some documentation, and try to repair sooner:
https://www.debian.org/doc/manuals/debi ... 02.en.html
and ...................
https://www.debian.org/doc/manuals/debi ... le_literal
This is a pretty good "tutorial" also:
https://raphaelhertzog.com/2011/02/21/d ... tall-them/
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
Re: Upgrade Error
Thanks for the tips and reading. Have been following up somewhat. Tried to install later rdnssd manually (as so far, waiting has not resulted in resolution), but got the following message. Surely this rdnssd update must not necessitate removing gnome and all of those network managers? If so, can I be the only experiencing an issue here? Any further suggestions, beyond wait?
According to "dpkg --get-selections | grep hold" I am not holding back packages, so it is strictly on apt policy, as far as I can tell. Output below.
The following packages will be REMOVED:
gnome network-manager network-manager-gnome network-manager-openvpn network-manager-openvpn-gnome
The following packages will be upgraded:
rdnssd
1 upgraded, 0 newly installed, 5 to remove and 433 not upgraded.
Need to get 43.4 kB of archives.
After this operation, 22.7 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
derek@derek-laptop2: 1779: /etc/apt/sources.list.d$upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Error!
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:
systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+b1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
According to "dpkg --get-selections | grep hold" I am not holding back packages, so it is strictly on apt policy, as far as I can tell. Output below.
The following packages will be REMOVED:
gnome network-manager network-manager-gnome network-manager-openvpn network-manager-openvpn-gnome
The following packages will be upgraded:
rdnssd
1 upgraded, 0 newly installed, 5 to remove and 433 not upgraded.
Need to get 43.4 kB of archives.
After this operation, 22.7 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
derek@derek-laptop2: 1779: /etc/apt/sources.list.d$upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Error!
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:
systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+b1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: Upgrade Error
So why do you think you are running testing, and why is your system trying to install the version from stable??
Code: Select all
apt-cache policy systemd rdnssd
AdrianTM wrote:There's no hacker in my grandma...
Re: Upgrade Error
Well, I installed testing and my repos all point to testing, as shown in the output from that (posted below). I have no idea why apt is pointing towards that.
derek@derek-laptop2: 1780: /etc/apt/sources.list.d$apt-cache policy systemd rdnssd
systemd:
Installed: 230-7
Candidate: 231-4
Version table:
231-4 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
*** 230-7 100
100 /var/lib/dpkg/status
rdnssd:
Installed: 1.0.1-1+b1
Candidate: 1.0.1-6
Version table:
1.0.1-6 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
*** 1.0.1-1+b1 100
100 /var/lib/dpkg/status
derek@derek-laptop2: 1780: /etc/apt/sources.list.d$apt-cache policy systemd rdnssd
systemd:
Installed: 230-7
Candidate: 231-4
Version table:
231-4 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
*** 230-7 100
100 /var/lib/dpkg/status
rdnssd:
Installed: 1.0.1-1+b1
Candidate: 1.0.1-6
Version table:
1.0.1-6 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
*** 1.0.1-1+b1 100
100 /var/lib/dpkg/status
Re: Upgrade Error
Bugs318 wrote:1 upgraded, 0 newly installed, 5 to remove and 433 not upgraded
Bugs318 wrote:Was away for a week and a half, so behind on a few updates
Bugs318 wrote:Ran update and upgrade
dist-upgrade?Bugs318 wrote:Note that I am running testing
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: Upgrade Error
Wow, yeah missed the 'not upgraded' count.
@OP Your claims about the origin and state of your system aren't adding up - the package you have installed is from stable and was never in testing.
If you know why but aren't telling us, then good luck, i'm out.
If you don't know why, you should just install stable and be happy ever after.
(edit: or get busy trying to remember or work out how it got there )
@OP Your claims about the origin and state of your system aren't adding up - the package you have installed is from stable and was never in testing.
If you know why but aren't telling us, then good luck, i'm out.
If you don't know why, you should just install stable and be happy ever after.
(edit: or get busy trying to remember or work out how it got there )
AdrianTM wrote:There's no hacker in my grandma...
Re: Upgrade Error
Yep, that was dist-upgrade (it's an alias) and I have a system from zareason. They claim to have installed testing as per my request. The install disc they sent with my install was, indeed, testing. The repos do and always have pointed to testing, so how this got there, I am not certain. That isn't to say I may not have made a change somewhere, somehow and forgotten in getting another package to run, but I cannot find any sign of a package being held nor of any repo that isn't labelled testing.
If you have suggestions of where and how I could check further for such causation, I'll be happy to oblige, but as far as I can recall or see, there is no obvious reason for a package that was never in testing and the system has been updating well for 14-15 months since purchase with all repos pointing to testing.
If you have suggestions of where and how I could check further for such causation, I'll be happy to oblige, but as far as I can recall or see, there is no obvious reason for a package that was never in testing and the system has been updating well for 14-15 months since purchase with all repos pointing to testing.
Re: Upgrade Error
Note: when this problem arose, I was nowhere near 443 packages in need of upgrade, but none will upgrade and without any ideas for resolution, the upgrades grow.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: Upgrade Error
So install the updated rdnssd.
aptitude might help.
aptitude might help.
AdrianTM wrote:There's no hacker in my grandma...
Re: Upgrade Error
If the OP has done a dist-upgrade (or multiple dist-upgrades) with a Stable repo enabled, this is almost certainly not a one-off issue. (And absent reliable reporting, there's just no way to know for sure.)
Re: Upgrade Error
Will try the aptitude install and post back. For the record, though, my /etc/apt/sources.list I have never enabled a stable repo for a dist-upgrade:
# deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official amd64 DVD Binary-1 20150425-12:54]/ jessie contrib main
# deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official amd64 DVD Binary-1 20150425-12:54]/ jessie contrib main
deb http://ftp.us.debian.org/debian/ testing main non-free contrib
deb-src http://ftp.us.debian.org/debian/ testing main
deb http://security.debian.org/ testing/updates main contrib
deb-src http://security.debian.org/ testing/updates main contrib
# jessie-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ testing-updates main contrib
deb-src http://ftp.us.debian.org/debian/ testing-updates main contrib
# deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official amd64 DVD Binary-1 20150425-12:54]/ jessie contrib main
# deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official amd64 DVD Binary-1 20150425-12:54]/ jessie contrib main
deb http://ftp.us.debian.org/debian/ testing main non-free contrib
deb-src http://ftp.us.debian.org/debian/ testing main
deb http://security.debian.org/ testing/updates main contrib
deb-src http://security.debian.org/ testing/updates main contrib
# jessie-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ testing-updates main contrib
deb-src http://ftp.us.debian.org/debian/ testing-updates main contrib
Re: Upgrade Error
Just as with apt-get, aptitude says it will uninstall gnome and all network manager and vpn software.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: Upgrade Error
You have at least one package installed from Stable. It didn't spontaneously install itself, and I don't believe in gremlins. You report routinely performing a repo update followed by a dist-upgrade, and 30 seconds at Google strongly suggests that this issue is indeed unique to you.Bugs318 wrote:For the record... I have never enabled a stable repo for a dist-upgrade:
If aptitude can't come up with a solution, your path seems clear.
Re: Upgrade Error
Regardless of how it got there (is it possible a package downloaded and installed via dpkg installs?) (and though I am certain I never changed repositories, but may have manually downloaded packages in seeking to get others to work - Skype is one that comes to mind that required some effort), are you basically all saying this is not reparable outside of a clean install or a removal of other packages I rely upon?
- Ardouos
- Posts: 1077
- Joined: 2013-11-03 00:30
- Location: Elicoor II
- Has thanked: 1 time
- Been thanked: 4 times
Re: Upgrade Error
Some packages that you install can add external sources in your sources.list.d/Bugs318 wrote:Regardless of how it got there (is it possible a package downloaded and installed via dpkg installs?) (and though I am certain I never changed repositories, but may have manually downloaded packages in seeking to get others to work - Skype is one that comes to mind that required some effort), are you basically all saying this is not reparable outside of a clean install or a removal of other packages I rely upon?
Last edited by Ardouos on 2016-09-08 18:32, edited 1 time in total.
There is only one Debian | Do not break Debian | Stability and Debian | Backports
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
Re: Upgrade Error
Great links, thanks Ardouos. Before I go about the task of a clean install, however, I'd much rather find a way to get this back up to testing if at all possible. Is there any way that can be done?
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: Upgrade Error
Well the answer is very probably, yes, it should be fairly easily "reparable", depending what 'foreign' packages you have installed and what you think you "rely upon".Bugs318 wrote:Regardless of how it got there (is it possible a package downloaded and installed via dpkg installs?) (and though I am certain I never changed repositories, but may have manually downloaded packages in seeking to get others to work - Skype is one that comes to mind that required some effort), are you basically all saying this is not reparable outside of a clean install or a removal of other packages I rely upon?
The bigger picture is that this is a very common type of package management issue in testing/unstable (due to constant, ongoing package changes) which you will need to learn to deal with to continue successfully.
Spend some time getting some basic familiarity with the package management system and tools (IMHO, the aptitude interface is an excellent aid to this).
If you don't have the time or inclination for such system administration, then stable is what you want to be using (although when mixing in other packages you need to be more aware of these things too).
AdrianTM wrote:There's no hacker in my grandma...