[Bug 212048] New: Temporarily unavailable installation sources are completely dropped while refreshing
https://bugzilla.novell.com/show_bug.cgi?id=212048 Summary: Temporarily unavailable installation sources are completely dropped while refreshing Product: openSUSE 10.2 Version: Alpha 5 Platform: x86 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andreas.hanke@gmx-topmail.de QAContact: jsrain@novell.com I just tried to manually refresh the Factory installation source, which is set to "Refresh: Off", in "yast2 inst_source" via the "Source Settings -> Refresh Now" button. It said Can't provide /suse/setup/descr/32bit-10.2-49.x86_64.pat from http://ftp-1.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source because the tree is currently broken, and asked "Retry/Abort". I selected "Abort", which should just abort the refresh. Then it asked: Abort the catalog configuration? All changes will be lost. I selected "Yes", which just said it would not change anything, but it deleted the installation source entirely. I verified by looking at /var/lib/zypp/db/sources that the installation source is indeed entirely gone. zmd does not show this behaviour. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 ------- Comment #1 from andreas.hanke@gmx-topmail.de 2006-10-12 13:03 MST ------- Created an attachment (id=101357) --> (https://bugzilla.novell.com/attachment.cgi?id=101357&action=view) YaST2 logfiles -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |dmacvicar@novell.com |screening@forge.provo.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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 ------- Comment #2 from andreas.hanke@gmx-topmail.de 2006-10-30 19:31 MST ------- This bug is _really_ annoying. I just lost my Factory installation source again - because of one (1) pattern file that was not accessible on the server because of synchronization issues. I wonder what will happen if people lose their security update sources later because of this. Especially if zmd is really going to be removed from the default installation. Currently zmd "saves" you because it adds the lost source back while refreshing services. Without a running zmd, the sources won't come back. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 marcio.ferreira@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcio.ferreira@gmail.com Severity|Critical |Blocker ------- Comment #3 from marcio.ferreira@gmail.com 2006-10-31 06:06 MST ------- Andreas, Ive just did the test you told me (to run yast inst_source offline) and indeed the source was de-registered from yast (the cache data was there, but it downloaded all again, as the source wasnt listed in /var/lib/zypp/db/sources, of course). Seems very critical to me (and of course very annoying), thats why I've changed the priority of this bug to blocker. This way we wont need zmd to rescue the system. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 marcio.ferreira@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |215649 nThis| | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 mvidner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com ------- Comment #4 from mvidner@novell.com 2006-11-01 07:04 MST ------- This is a duplicate of non-public bug 210514 which I am fixing but it probably cannot be made open so I'll copy the relevant details here soon. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=212048 mvidner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #6 from mvidner@novell.com 2006-11-02 06:21 MST ------- from bug 210514: The source was not accessible at that time (probably because the proxy was not set up) and Pkg::SourceCleanupBroken was called. yast2-pkg-bindings-2.13.67 has "delete broken sources if they cannot be restored ( bug 157100)" It seems that we went too far by removing the sources like this. The message given is just "There were errors when restoring the source configuration. Not all sources are available for configuration." There is no warning that the source will be deleted permanently if one exits either via Finish or Abort! To work around it, one has to terminate the process while the popup is still being shown. We plan to fix it by better informing the user so that he can decide whether to remove the source because it is broken or whether to keep it because the failure is transient. Performing the registration again should re-add the source to YaST. .. Fixed in yast2-packager-2.14.1 for 10.2 Beta2. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com