Libzypp/Issues

From openSUSE

Performance

zmd meta data parsing is not fast enough for realworld requirements

With a typical SUSE Linux user inst-source setup parsing the metadata takes up to 10 minutes. This is with variations depending on download speed and the amount of installation sources. This also manifests in suse_register (which is using zmd) and general i/o during normal operation when zmd wakes up and starts parsing.

Bug: #176301

Operation

inst-source syncing between yast inst_source and zmd is not robust

If you add sources to yast they're automatically added to zen/rug - but this doesn't work the other way around. This can also lead to a de-synced inst-source setup where the YaST inst_source frontend can't delete a channel in zmd's database because its not there anymore.

To add sources via ZMD/rug/zen-updater that are merged to YaST use the type "ZYPP". This type can be used for suse packages and YUM repositories.

  rug service-add --type=ZYPP url name

plain cache sources dont work anymore

libzypp just has no support for plain cache inst-sources so you cant add a directory that only contains RPMs and no metadata as installation source. This leads to several fall-out bugs like Konqueror fails when trying to "install package with Yast".

Bug: #168358

NB! Seems to be resolved in openSUSE 10.2. --Lenborje 09:55, 29 December 2006 (UTC)

Multiple packagemanagement instances at one

You can't have more instances of packagemanagement running at once.

Delta and patch rpms can't be handled

Delta and patch rpms are currently ignored.

All repository sources are updated initially

This isn't necessary and leads to long wait times in downloading all those updates when you may only intend to make one quick update. They should remain un-updated until the user initiates an update with a button or command etc.

Inconsistent Name Usage

Are they "Software Catalogs", "Repositories", "Services", "Channels"...? Pick one term and only use that.

ZMD looses repositories when a reboot/shutdown is initiated while ZMD sleeps

ZMD - and consequently also zen-updater - 'forget' about some or all installation/update sources when the system is shutdown or rebooted during ZMD's sleep. This is especially tricky because the user probably won't realize that his/her repositories are gone and will live happily without ever receiving security-updates and bugfixes.

Bug: #231256 --eet 2007-03-27

Usage

No visible feedback during download/parsing

YaST gives no information when it's downloading or refreshing repodata making inexperienced users think it's frozen.

Bug: #159803

Unsigned Warning

Keeps poping up despite clicking "dont ever show me this message again"

Bug: #175845

Is fixed by only showing it once per yast run with first libzypp update.

Unsubscribing from a catalog

Unsubscribing from a catalog with rug does not have the same meaning as disabling a inst-source in YaST. This is confusing.

Bug: #171623

Naming of repos

When adding repos to YaST installation source module they're added to ZMD with numbers for a name (a timestamp I think) - making it hard to keep track of the repos once you have a few added. Would be nice to be able to name the repos manually when adding them with YaST. Or at least be able to rename the repo service later.

Dependencies are automatically installed

If select to install a package in YaST software management which depends on one or more other packages, these are automatically installed without prior warning to the user.

This is not really a bug I guess. -Msmeissn

Conflicts need to be handled one at a time

If somehow you do something that causes conflicts, YaST will make you solve these conflicts one at a time - even though there might be 20 or more conflicts that all have the reason.

I cannot reproduce this. You can handle all of them at once in the conflicts dialog. Please bugreport if not. -Msmeissn

I believe this was fixed in an update. I don't remember which one or when. Openjim 16:35, 11 October 2006 (UTC)

Asynchronous Refresh of Repositories

An option to automatically refresh contents from all online repositories every night would be very helpful. Currently the refresh happens when the user access the software management tool from YaST, and will 5-6 repos the process takes over a minute (sometimes several minutes when the repo servers a busy). This is extremely annoying to the user, specially when the user simply wants to quickly check what RPMs are installed on the system. A nightly cron job for the purpose of refresh would be just perfect.