Re: [opensuse] Re: zypper refuses to update some software
- From: Marcus Meissner <meissner@xxxxxxx>
- Date: Fri, 5 Aug 2011 13:33:05 +0200
On Fri, Aug 05, 2011 at 01:26:45PM +0200, Joachim Schrod wrote:
Marcus Meissner wrote:
On Thu, Aug 04, 2011 at 09:46:32PM -0400, j.e.perry@xxxxxxx wrote:[more packages discarded]
I switched from zypper dup to sypper up a few months ago, and lately
I've been getting a long list of packages that won't be updated. Some
of them have been in this message for weeks (I update a couple of times
a week), and look pretty important to me. THe update I just did, for
instance:
The following package updates will NOT be installed:
NetworkManager-kde4-libs NetworkManager-kde4-libs-lang
NetworkManager-openvpn-kde4 NetworkManager-pptp-kde4
The following packages are going to be upgraded:
libzypp python-satsolver satsolver-tools zypper
Am I missing something? Is my database corrupt? Is everything ok? There
is a long list of kde modules, for instance, that has been in the "no
update" list forever.
Do I need to fix something? What?
It looks like it wants to install the update stack patch first.
After you have done it, the rest will also be installable.
zypper patch // first run will install update stack update (new zypper/libzypp)
zypper patch // second run will install the rest updates
Markus, are you sure?
I have such a really long list during zypper update as well. I
checked almost every packet in that "will NOT be installed" list;
these are all packages from other OBS repositories or packman where
I deliberately did not switch to them, but use the original package
from 11.4 resp. 11.4 update repository.
E.g., I use the repository openSUSE:/Tools/openSUSE_11.4/ to get
OBS. It has a more current apache2 than the one in the 11.4 update
repository. So, with each zypper up I get told that a whole bunch
of apache2 packages will not get installed. Well, I know that:
After all I decided that I won't switch wholeheartedly to
openSUSE-Tools, but use that repo just for obs and not for apache2
and haveged. Packman is similar; I want it only for audio/video and
not for the rest of packages that they provide.
What I would really like to have: A zypper or zypp.conf option
"don't list non-updateable packages caused by irrelevant vendor
changes" in the "will NOT be installed" list at zypper update.
Irrelevant here means: The package would change vendor and all its
dependencies could be installed. Then the admin probably didn't
install it by choice. As a further example, a relevant change that
should be still listed: A package cannot be updated because one of
its dependencies would have to change vendor to do the update.
That's of interest, since here admin actions are probably needed.
Currently, I have to do the dependency analysis to distinguish
these two cases myself, and also haven't yet found good tools in
the zypper framework that tells me concisely "why could something
not be installed".
You can always check with a direct zypper in why zypper thinks
it would be a bad idea to install them:
zypper in NetworkManager-kde4-libs
which will likely print the reason of why not.
But yes, if they are not instalable they might not need to be displayed.
Ciao, marcus
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- Follow-Ups:
- Re: [opensuse] Re: zypper refuses to update some software
- From: Joachim Schrod
- Re: [opensuse] Re: zypper refuses to update some software
- References:
- [opensuse] zypper refuses to update some software
- From: j . e . perry
- [opensuse] Re: zypper refuses to update some software
- From: Joachim Schrod
- [opensuse] zypper refuses to update some software
- Prev by Date: Re: [opensuse] AD domain password change
- Next by Date: Re: [opensuse] KDE 4.7 , opensuse 11.4 64bit.
- Previous by thread: [opensuse] Re: zypper refuses to update some software
- Next by thread: Re: [opensuse] Re: zypper refuses to update some software
- Index(es):
Relevant Pages
|
