Bugzilla – Bug 304200
zypper can't install opera
Last modified: 2007-08-29 15:04:20 UTC
hydros:~ # zypper sl # | Enabled | Refresh | Type | Name | URI --+---------+---------+--------+---------+------------------------------------------------------------------------------- 1 | Yes | Yes | rpm-md | oss | http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/ 2 | Yes | Yes | rpm-md | rbos | http://repos.opensuse.org/home:/rbos/openSUSE_Factory 3 | Yes | Yes | rpm-md | mozilla | http://repos.opensuse.org/mozilla/SUSE_Factory 4 | Yes | Yes | rpm-md | Update | http://download.suse.com/update/10.3 5 | Yes | Yes | yast2 | non-oss | http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-extra 6 | Yes | Yes | rpm-md | Packman | http://packman.iu-bremen.de/suse/10.3 hydros:~ # zypper refresh Repository 'oss' is up to date. Repository 'rbos' is up to date. Repository 'mozilla' is up to date. Repository 'Update' is up to date. Repository 'non-oss' is up to date. Repository 'Packman' is up to date. All repositories have been refreshed. hydros:~ # zypper install opera * Reading repository 'oss' cache * Reading repository 'rbos' cache * Reading repository 'mozilla' cache * Reading repository 'Update' cache * Reading repository 'extra' cache * Reading repository 'Packman' cache * Reading installed packages [100%] The following NEW package is going to be installed: opera Overall download size: 6.3 M. After the operation, additional 18.8 M will be used. Continue? [y/n]: y Downloading package opera-9.23-3.i586, 6.3 M (18.8 M unpacked) Unexpected exception. Can't provide file ./suse/i586/opera-9.23-3.i586.rpm from repository non-oss Please file a bug report about this. See http://en.opensuse.org/Zypper#Troubleshooting for instructions. hydros:~ # rpm -qv libzypp libzypp-3.18.2-4 hydros:~ # rpm -qv zypper zypper-0.8.14-4 hydros:~ # cat /etc/SuSE-release openSUSE 10.3 (i586) Beta2 VERSION = 10.3 hydros:~ # With exactly same repositories configured, apt install it fine.
Please provide /var/log/zypper.log
Created attachment 159666 [details] zypper.log
Looking at the logs. media file changed, but zypp did not refresh because content was the same, or just because it was not in autorefresh -> we should look for media.1/media changing and not content? the changed media file produced a media not desired exception, which for non ejectable medias, just failed. The error chain there can be improved.
media.1/media is now checked.