[opensuse] zypper up question

24 May 2010

      All,

Intentional top post / new thread because the main question seems to
have been lost in the clutter.

Is there a way, via zypper, I can easily see which repo yast2-mail is
currently using, and which one has the updated version?

ie. It seems a vendor change is needed and zypper up is therefore
simply telling me it is skipping that package.  Now I want to dig into
that a little more.

fyi: I assume I could launch yast and look at the versions tab, but
I'd like to handle this via zypper since it seems to be getting better
and better.

Greg

On Fri, May 21, 2010 at 4:49 PM, Greg Freemyer  wrote:
...
On Fri, May 21, 2010 at 4:33 PM, Marcus Meissner  wrote:
...
On Fri, May 21, 2010 at 05:28:43PM -0300, Marco Calistri wrote:
...
Greg Freemyer ha scritto:
...
All,
I just ran zypper up and it gave me the normal list of things it was
going to upgrade, but also a list it was not going to upgrade.  What
is the list of not upgraded about?  It seems surprisingly long.  See
below.
I particularly interested in the kernel packages its not upgrading.
===
sudo zypper up
root's password:
Retrieving repository 'KDE:KDE4:Factory:Desktop' metadata [done]
Building repository 'KDE:KDE4:Factory:Desktop' cache [done]
Retrieving repository 'YaST:Web' metadata [done]
Building repository 'YaST:Web' cache [done]
Loading repository data...
Reading installed packages...
The following package updates will NOT be installed:
  autoconf automake bash bash-doc desktop-file-utils
evolution-data-server faad2 ffmpeg gnome-keyring gnome-keyring-32bit
gnome-keyring-lang gstreamer-0_10-plugins-base
  gstreamer-0_10-plugins-base-lang gstreamer-0_10-plugins-good
kernel-debug kernel-debug-devel kernel-default kernel-default-devel
kernel-desktop-devel kernel-docs kernel-source
  kernel-syms kernel-trace kernel-trace-devel kernel-xen
kernel-xen-devel kupdateapplet kupdateapplet-packagekit libavcodec52
libavdevice52 libavformat52 libavutil50 libfaad2
  libgpod4 libgpod-tools libkdecore4-32bit libphonon4-32bit
libpostproc51 libreadline6 libreadline6-32bit libschroedinger-1_0-0
libswscale0 libv4l lighttpd lighttpd-mod_magnet
  PackageKit readline-devel readline-doc rubygem-actionmailer-2_3
rubygem-actionpack-2_3 rubygem-activerecord-2_3
rubygem-activeresource-2_3 rubygem-activesupport-2_3 rubygem-rack
  rubygem-rails-2_3 rubygem-rake rubygems rubygem-sqlite3 sysvinit
Vuze-libswt3-gtk2 webyast-base-ui xdg-utils xkeyboard-config
yast2-mail yast2-registration
  yast2-registration-branding-openSUSE
.
.
.
.
===
Thanks
Greg
That's an interesting question; me too am seeing it from awhile.
We could try to compare the installed pkg against the repository updates
with "zypper info <pkg-name>" to see if the installed version is the
latest available.
Other aspect IMHO is worth to mention is the slight difference of
packageKit's behaviour, with the one of zypper: sometimes they reports a
different scenario about update availability.
To see what the problem with those updates are , try:
e.g.
zypper in yast2-mail
it will show the conflicts you need to resolve.
Ciao, Marcus
Marcus,
I tried exactly that and it looks like a yast2-mail is a repo / vendor
change.  I don't recall getting yast2-mail as an example from a
non-standard repo.  (I do have several repo's in my list, see below).
Is there a way I can easily see which repo yast2-mail is currently
using, and which one has the updated version?
==
sudo zypper in yast2-mail
root's password:
Loading repository data...
Reading installed packages...
'yast2-mail' is already installed.
There is an update candidate for 'yast2-mail', but it is from
different vendor. Use 'zypper install yast2-mail-2.18.5-2.1.noarch' to
install this candidate.
Resolving package dependencies...
Nothing to do.
==
==
...
sudo zypper lr
#  | Alias                           | Name
| Enabled | Refresh
---+---------------------------------+---------------------------------+---------+--------
1  | KDE:KDE4:Factory:Desktop        | KDE:KDE4:Factory:Desktop
| Yes     | Yes
2  | Kernel:HEAD                     | Kernel:HEAD
| Yes     | Yes
3  | X11:lxde                        | X11:lxde
| Yes     | Yes
4  | YaST:Web                        | YaST:Web
| Yes     | Yes
5  | devel:languages:ruby:extensions | devel:languages:ruby:extensions
| Yes     | Yes
6  | devel:tools:building            | devel:tools:building
| Yes     | Yes
7  | download.opensuse.org-oss       | Main Repository (DEBUG)
| Yes     | Yes
8  | download.opensuse.org-standard  | Main Repository (Contrib)
| Yes     | Yes
9  | download.videolan.org-SuSE      | VideoLan Repository
| Yes     | Yes
10 | ftp.skynet.be-suse              | Packman Repository
| Yes     | Yes
11 | home:poletti_marco              | home:poletti_marco
| Yes     | Yes
12 | openSUSE:Tools                  | openSUSE:Tools
| Yes     | Yes
13 | openSUSE_11.2_Non-OSS           | openSUSE 11.2 Non-OSS
| Yes     | Yes
14 | openSUSE_11.2_Oss               | openSUSE 11.2 Oss
| Yes     | Yes
15 | openSUSE_11.2_Updates           | openSUSE 11.2 Updates
| Yes     | Yes
==
Thanks
Greg
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
CNN/TruTV Aired Forensic Imaging Demo -
  http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retriev...

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com

--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
CNN/TruTV Aired Forensic Imaging Demo -
  http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retriev...

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse+help@opensuse.org

Greg Freemyer

Ken Schneider - openSUSE

Jeffrey L. Taylor

Greg Freemyer

Jano Kupec

Greg Freemyer

tags

participants (4)