Morning Everyone!
As you know every now and again you get update suggestions.
Now my question is how do you choose which to take and which to leave?
Security updates makes sense, but sometimes there are stuff for touchpads or twitter apps, that I do not have.
And often stuff that I do not understand at all!
Thanks!
J
11.3 +KDE 4.4
PS The Updater Applet has been on 0% now for about 5-10 minutes
Hi,
I generally get all the updates that are proposed unless I have a specific reason not to…
I too have the problem of the “hanging” updater applet. It seems to be caused by “packagekit” whatever that may be.
To get around this, you can kill packagekit and go to yast->software-online update…
HTH
Lenwolf
When you get a security or recommended update offered by the applet (or by using YaST > Software > Online update), they are from the Update repos. When you say that it is an update for software you do not have, I think you are wrong. Mabe you did not use it, but those updates are definitely for packages you have.
When you get a security or recommended update offered by the applet (or by using YaST > Software > Online update), they are from the Update repos.
More precise: from the update repo (http://download.opensuse.org/update/). By default the applet only notifies about this repo.
toI used repos as a singular. May be I should py more attention where shortcuts fall 
I’m puzzled, too, as my update applet suggests one set of packages that are available, then “zypper lu” tells me some other (larger) selection, which, as I understand now, is because zypper also scans through repos other than the ‘update’). If I now call “zypper up” I get the following:
zypper up
Loading repository data...
Reading installed packages...
The following package updates will NOT be installed:
ant batik bea-stax-api digikam fop gstreamer-0_10-plugin-gnomevfs gstreamer-0_10-plugin-hal gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-extra gstreamer-0_10-plugins-good-lang
jakarta-commons-logging jing jline jna jpackage-utils junit k3b k3b-lang kaffeine kipi-plugins kipi-plugins-acquireimage konversation ksshaskpass ktorrent libgstbasevideo-0_10-0 libgstphotography-0_10-0 libgstsignalprocessor-0_10-0
libkdcraw8 libkexiv2-8 libkipi7 libvpx0 libxine1 libxine1-codecs libxine1-gnome-vfs libxine1-pulse mkvtoolnix regexp rhino saxon servletapi4 skanlite smplayer sox swing-layout taglib trang update-alternatives vamp-plugin-sdk xalan-j2
xerces-j2 xerces-j2-xml-apis xerces-j2-xml-resolver xmlbeans yakuake
The following NEW package is going to be installed:
libx264-107
The following packages are going to be upgraded:
MPlayer cclive dvdauthor ffmpeg google-chrome-beta gpac gstreamer-0_10 gstreamer-0_10-devel gstreamer-0_10-lang gstreamer-0_10-plugins-base gstreamer-0_10-plugins-base-lang gstreamer-0_10-utils gstreamer-utils lame liba52-0
libavcodec52 libavcore0 libavdevice52 libavfilter1 libavformat52 libavutil50 libdca0 libfaac0 libfaad2 libgpac0 libgstapp-0_10-0 libgstinterfaces-0_10-0 libgstreamer-0_10-0 libmp3lame0 libpostproc51 libquvi0 libswscale0 libtwolame0
libx264-98 mjpegtools perl-Config-Tiny wxWidgets
37 packages to upgrade, 1 new.
Overall download size: 54.2 MiB. After the operation, additional 955.0 KiB will be used.
Continue? [y/n/?] (y):
what surprises me are the packages which are “NOT” to be installed. Checking with yast, I saw them originating from repos which have higher priorities than the standard default ones, and cause no dependency problems. Still, even if I select in Yast “All packages->Update if newer versions available” they are not updated! I have to go through them one by one and select the higher version from the corresponsing repository. Very strange… Anyone has a clue ?
(P.S. In general I find this multi-level redirections quite annoying, that zypper and yast both call packagekit, which calls aria2c, which calls rpm, which calls cpio … are we sure there’s no simpler and cleaner scheme that would do the job properly? )
I have not studied your case thouroughly, but did you take into account that YaST will never install a newer version of a package when it must change the Vendor (the repo) to be able to do so. Unless you explicitly tell it to change Vendor. It seems logical to me that when you decided you want a certain package from Packman, that that is not automaticaly changed when another repo has a newer version without you agreeing to that.
In fact (not) changing Vendor is more important then the priority mechanism to influence what you want. I have all on the same priority.
Well, unless it’s in the “update” repo as a special case, apparently… hmm, what you say makes sense indeed. So if I manually update a package and allow the vendor change, it won’t get updated if the other repo comes up with a newer version next day? Got to check that out. Thanks for the hint!
On 2010-10-26 16:06, dich wrote:
>
> I’m puzzled, too, as my update applet suggests one set of packages that
> are available, then “zypper lu” tells me some other (larger) selection,
> which, as I understand now, is because zypper also scans through repos
> other than the ‘update’). If I now call “zypper up” I get the
> following:
You have to compare with “zypper patch”, not “up”.
> (P.S. In general I find this multi-level redirections quite annoying,
> that zypper and yast both call packagekit, which calls aria2c, which
> calls rpm, which calls cpio … are we sure there’s no simpler and
> cleaner scheme that would do the job properly? )
One program do it all? No, thanks. This is the Linux way: several small programs each doing its own
part well.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
It is not only the Unix/Linux way, it is the way programming goes in general. You use the building blocks that are availble and do not invent the wheel again. These programs you mentioned use extensively libraries that are used by many. And so on. One does not program the sin() function again and again, that was allready done in the sixties.
Also, when using these building blocks, it is often easy to replace one with another hen need arises.
You performed a “Switch system packages …” on the Packman repo. Thus “newer” versions from any other repo will not be considered an update. The way you’re doing it now, means manually undoing things you need to do, f.e. to get full multimedia support in your install. If you do a “zypper up” it shows all available updates incl. the ones you for packages that you told it to get from another repo. What it’s doing is telling you they’re available too, but will not be installed, which is OK.
Same can happen on packages from KDE: repos.
I’d like to partly disagree with your statement. The things that nowadays the bottleneck has become the number of dependencies which various building blocks carry with them. “re-using” stuff that is already created by someone else should be done in a very carefull way, and linux generally suffers from undisciplined development (which is indeed part of its phylosophy). A small example - in suse 11.0 the KDE updated applet would show you the progress of the update if you wish to. That functionality is gone, since the applet is now completely rewritten, and uses parts of other libraries that do not provide that feature anymore. There are many other such examples, which you know very well by yourself - you keep running 11.2 and not upgrade to 11.3 for a good reason I suppose, as many new applications suffer from unwanted “development” which results in loss of functionality and stability.
Concerning the statement that one task would be performed by several small pieces, each of which does it’s job well - I may support the ideology, but not the reality. “curl” which is (or maybe was) used to download the update packages caused a lot of problems if the network wasn’t 100% stable, which didn’t cause any trouble earlier.
Anyway, thanks for resolving the issue with update package publisher!