Bugzilla – Bug 230726
do not touch old repos while updating
Last modified: 2007-08-02 13:30:31 UTC
10.0 -> update -> 10.2 While updating the installer complained about old repos (for 10.0) they are not accessible. Ok, maybe they are not in fact, but: a) what is the point using old repos for new version b) it is pretty hard to connect over the internet when the network is the next point on the list of the installer itself
Can you please attach y2logs. If you are in doubt please follow: http://en.opensuse.org/YaST. Thanks!
Saving server space :-) https://bugzilla.novell.com/attachment.cgi?id=111074&action=view please note I deleted old repos now.
I did the very same thing at home only yesterday. The old repos were disabled properly. There were no complaints. It also turned out that keeping the old repos (albeit disabled) is a good thing. You can then later simply change the URLs - most servers have a similar directory structure for newer releases, so in most cases you can simply change .../some/where/10.0/... to .../some/where/10.2/... -- I did that yesterday. It saved a lot of time.
I think there already was such bug which was fixed by same later libzypp update. Lukas, don't you know of something?
There was a feature request for 10.2 to disable (but not delete) all old sources when updating. First, I wanted to implement it in yast2-update (installation), then I've realized that it already worked (done by ZYPP). I've tested it and it worked well. Maybe the problem is when updating from version that, in fact, doesn't have any ZYPP (like 10.0). y2log-4: SourceManager.cc(restore):417 Found sources: 0 SourceManager.cc(restore):503 SourceManager restore done. SourceManager.cc(restore):504 SourceManager: ========================= SourceManager.cc(restore):504 known Sources 0 SourceManager.cc(restore):504 deleted Sources 0 SourceManager.cc(restore):504 ======================================== clients/inst_kickoff.ycp:356 Pkg Builtin called: TargetDisableSources Disabling all sources in store at /mnt Disabling source SUSE-Linux-10.1-Add-on-10.1-0-20060701-141352 Disabling source --20060701-222849 Disabling source --20060701-213142 Disabling source 20060701-223758 Disabling source SUSE-Linux-10.1-CD-download-x86-10.1-0-20060701-141213 Disabling source contributions_by_Robert_Schiele-200606011252-20060701-222120 Disabling source 20060701-200226 Disabling source --20060701-223511 Disabling source GNOME-supplementary-2.12-0-20060701-214031 y2log-3: SourceManager.cc(restore):417 Found sources: 10 known Sources 1 - Source[1|YaST|SUSE-Linux-10.1-Add-on-10.1-0-20060701-141352]{dvd:///(/); cache /var/lib/zypp/cache/Source.eibFzu; autorefresh: 0; enabled: 1} Maybe this source hasn't been disabled for some reason? Because it's installed Add-On product? But this is 10.1 and not 10.0 source. yast2-3: Curl error for: ftp://ftp.gwdg.de/pub/linux/usr-local-bin/10.1/media.1/directory.yast: Error code: Connection failed Error message: Couldn't resolve host 'ftp.gwdg.de' Anyway, this seems to be deeper in ZYPP, reassigning to lslezak to evaluate
One note, 10.1 --> I reported this problem, my 10.2 is recognized as a 10.1.
Where it is recognized as 10.1, in which yast module? Please, comment it.
Here it is my report: https://bugzilla.novell.com/show_bug.cgi?id=230913 I semi solved the problem manually editing repo for patches.
There is a new dialog for handling repositories during update. *** This bug has been marked as a duplicate of bug 221197 ***