https://bugzilla.novell.com/show_bug.cgi?id=779400 https://bugzilla.novell.com/show_bug.cgi?id=779400#c14 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bluedzins@wp.pl --- Comment #14 from Jiří Suchomel <jsuchome@suse.com> 2012-10-02 08:20:03 UTC --- (In reply to comment #13)
So you edited the URL during upgrade, but the repo still got deleted?
In order to keep repo, you have to disable it, otherwise it won't survive upgrade.
(On my second upgrade, I exactly did it -- they survived).
Good! Now you see there is a way. During upgrade, YaST just does not add the repositories that are not accessible, and I think this is reasonable behavior. And YaST also deletes old repositories by default (which is reasonable), while offering you the list of them with a possibility to change the status. Still, I find this reasonable, it would not make a sense to stack planty of unused and obsoleted repos in your new system. Your situation, without working network drivers is special, so you have to take care of network repositories.
I can see that this bug report is about suspend/resume
Yes, indeed. But I think if you want to focus solely on this report and only this you are limited only to notifying user that the working driver is deleted, and she/he should install the deleted driver again to gain full capabilities.
I do not see a way how to inform user that some "working" drivers have been deleted and "not working" are being installed. The installer could not know which drivers (or kernel itself) fits your hardware best. You know it and you have the option to _not_ upgrade selected packages. Or to upgrade them with working alternatives, just like suggested in this bug report. So, I can see 3 mentioned problems here: - about network drivers, that is another bug report, as you say - about repositories during upgrade, there is a way to keep them even when you don't have network access - about proprietary HW drivers, you have to take care -- 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.