https://bugzilla.novell.com/show_bug.cgi?id=391745 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |tgoettlicher@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=391745 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=391745#c2 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |christian.esken-services@arcor.de --- Comment #2 from Ján Kupec 2008-05-20 05:44:26 MST --- Probably nothing. Seems like it was not refreshed before checking for updates, is that possible? If not, it can be a problem with the repository at last, if the metadata are not in sync with the rpms it contains. But if that's the case it should be only temporary. Christian please try to re-run the updater now. If it fails with this error again, attach zypper.log. Then try to run 'zypper refresh' as root in the console before applying updates with the updater as a possible workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=391745 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=391745#c4 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tgoettlicher@novell.com --- Comment #4 from Ján Kupec 2008-05-21 05:12:15 MST --- Auto-refresh means zypper will try to refresh the repo before operations like install, update, search and other without explicitly requesting the refresh. But the updater (AFAIK) explicitly does the refresh. It's an update notification tool, after all :O) So if you'd only use zypper or yast for package management, your approach would work (but be aware, that unless you refresh a repo, you can end up with an error like the one you reported: zypper thinks some rpm should be there, but the repo has newer version now and removed (some of) the old one). But if you also use the updater, it refreshes all your repos from time to time. Thomas, correct me if i'm wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=391745 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=391745#c6 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #6 from Ján Kupec 2008-05-22 05:46:04 MST --- (In reply to comment #3 from Christian Esken)

Anyhow. This night the updater ran 8aut refresh still deactivated), found more updates and installed everything (see below). So my problem is solved. Do you still want to investigate?

No need for it.

If not, I don't mind if you close this bug report.

Thanx for the report, at least we see that we might eventually improve the handling of this 'repository-being-updated-so-temporarily-inconsistent' case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.