Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2008-12-11 at 13:15 +0100, Erik Jakobsen wrote:
Here is what I have started with:
dhcppc3:/media/SU1100.001/suse/i586 # zypper verify Reading installed packages... Dependencies of all installed packages are satisfied.
Good!
dhcppc3:/media/SU1100.001/suse/i586 # zypper lr # | Alias | Name | Enabled | Refresh --+-------------------------------+------------------------+---------+--------
1 | Main Update Repository_2_1_16 | Main Update Repository | Yes | Yes 2 | repo-non-oss | openSUSE-11.0-Non-Oss | Yes | No 3 | Hamradio | Hamradio | Yes | Yes 4 | repo-oss | openSUSE-11.0-Oss | Yes | No 5 | FLDIGI | FLDIGI | Yes | Yes
Right, that looks good too.
dhcppc3:/media/SU1100.001/suse/i586 # zypper verify Reading installed packages... Dependencies of all installed packages are satisfied.
Good.
dhcppc3:/media/SU1100.001/suse/i586 # zypper update Reading installed packages...
The following NEW patches are going to be installed: PackageKit zypper libzypp
The following package is going to be REMOVED: zypper
Notice that it is going to install zypper and remove zypper. I understand it simply means it is going to update zypper. Sometimes that program is quite confusing.
After the operation, 2.6 M will be freed. Continue? [YES/no]:
I need the Hamradio and FLDIGI repos. What do you mean about my repos now ?.
They are ok.
As you can see, there is no probs. running zypper verify.
But zypper update wants to remove zypper.
How can I avoid this ?
I believe it is going to update it. You can try again adding verbose and dry run:
zypper --verbose update --dry-run
On dry run mode you can safely accept anything, because it will not do any changes.
Thanks for the commnents Carlos. I have the dry result here: # zypper --verbose update --dry-run Verbosity: 1 Initializing Target Checking whether to refresh metadata for Main Update Repository Downloading: repomd.xml [done] Checking whether to refresh metadata for Hamradio Downloading: repomd.xml [done] Downloading: repomd.xml [done] Downloading: repomd.xml.asc [done] Downloading: repomd.xml.key [done] Downloading: repomd.xml [done] Downloading: primary.xml.gz [done] Downloading repository 'Hamradio' metadata [done] Building repository 'Hamradio' cache [done] Checking whether to refresh metadata for FLDIGI Downloading: repomd.xml [done] Reading installed packages... Force resolution: No Resolving dependencies... Force resolution: No Resolving dependencies... The following NEW patches are going to be installed: PackageKit-139.noarch (Main Update Repository, maint-coord@suse.de) zypper-114.noarch (Main Update Repository, maint-coord@suse.de) yast2-ncurses-pkg-83.noarch (Main Update Repository, maint-coord@suse.de) libzypp-53.noarch (Main Update Repository, maint-coord@suse.de) The following packages are going to be REMOVED: zypper-0.11.6-4.1.i586 (@System, SUSE LINUX Products GmbH, Nuernberg, Germany) yast2-ncurses-pkg-2.16.13-4.1.i586 (@System, SUSE LINUX Products GmbH, Nuernberg, Germany) After the operation, 3.2 M will be freed. Continue? [YES/no]: YES committing (dry run) Removing yast2-ncurses-pkg-2.16.13-4.1 [done] Removing zypper-0.11.6-4.1 [done] committing (dry run) CommitResult 4 (errors 0, remaining 0, srcremaining 0) dhcppc3:/media/SU1100.001/suse/i586 # rpm -q zypper zypper-0.11.6-4.1 And I can tell you, it doens't lie about the removing of zypper, as I tried it before your last reply ;-) Such a culprit. But then the prob. is how to get zypper to run update, and really do it ? -- Med venlig hilsen / Best regards Erik Jakobsen eja@urbakken.dk Registered Linux user #114875 - http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org