Bug 218705

at least the missing 10.1 -> 10.2 translation is worth "critical"

Created attachment 104095 [details]
bug218705.tar.bz2

Lslezak, please, check why these sources are contacted -- they should be "disabled" after the update, so why disabled entry contacts the source?

Olaf: are they disabled or enabled after the update?
I've checked it with the previous beta that there were disabled, anyway this might have changed.

I have no idea. During the 10.1 install, I changed nothing.
How can I check this? system is apple.suse.de, if you want to poke around yourself.

Status│Refresh│Name│URL
Off   │Off    │YaST│cd:///?devices=/dev/hde
Off   │On     │YUM │http://ftp.hosteurop...use/update/10.1
Off   │On     │YUM │http://ftp.hosteurop...use/update/10.1
On    │On     │YaST│iso:///?iso=openSUSE-10.2-...install/openSUSE-10.2-Bet...
On    │On     │YUM │http://ftp.tu-chemnit...use/update/10.1.42

Yes, it is turned off, but "Refresh" is turned on. I'm afraid this is wrong.
Thanks Olaf (see: `yast2 inst_sources`)

At the first stage of the update the sources at target have been successfully deactivated, but at the second stage the sources are initialized and then disabled. I think this is wrong.

Duncan, according to the log even the disabled sources are initialized:

2006-11-07 10:05:47 <1> apple(3986) [zypp::SourceManager] SourceManager.cc(sourceTableAdd):107 SourceManager add Source[1|YaST|SUSE-Linux-10.1-CD-download-ppc-
10.1-0-20061103-181123]{cd:///?devices=/dev/hde(/); cache /var/lib/zypp/cache/Source.POlJlI; autorefresh: 0; enabled: 1}                                       
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(sourceTableAdd):110 SourceManager: =========================                        
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(sourceTableAdd):110   known Sources 1                                               
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(sourceTableAdd):110     - Source[1|YaST|SUSE-Linux-10.1-CD-download-ppc-10.1-0-20061
103-181123]{cd:///?devices=/dev/hde(/); cache /var/lib/zypp/cache/Source.POlJlI; autorefresh: 0; enabled: 1}                                                   
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(sourceTableAdd):110   deleted Sources 0                                             
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(sourceTableAdd):110 ========================================                        
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(restore):482 Added source as id 1                                                   
2006-11-07 10:05:47 <0> apple(3986) [zypp::SourceManager] SourceManager.cc(restore):493 disable source                                                         
2006-11-07 10:05:47 <1> apple(3986) [zypp::SourceManager] SourceManager.cc(restore):434 Restoring source: url:[http://ftp.hosteurope.de/mirror/ftp.suse.com/pub
/suse/update/10.1] product_dir:[] alias:[http://ftp.hosteurope.de/mirror/ftp.suse.com/pub/suse/update/10.1] cache_dir:[/var/lib/zypp/cache/Source.Sc8wdP] auto_
refresh:[ 1]                                                                                                                                                   
...

Why does it happen? Is it caused by enabled autorefresh status?

*** Bug 215341 has been marked as a duplicate of this bug. ***

Yes.

inst_source is broken enough to get the source list from source manager and not from the storage directly. That means, if we disable nitializng disabled sources, inst source edtor will not see disabled sources when launched.

I will see if we can make the refresh() on construction for disabled sources do nothing. That will break on the first code that calls resolvables() in a disabled source, probably.

*** Bug 220056 has been marked as a duplicate of this bug. ***

BTW I have implemented a workaround in pkg-bindings - TargetDisableSources()
binding not only disables the old sources but disables autorefreh as well. So
this situation should not happen anymore. Do we need to do anything else?

not for now. I will close the bug.

We can really fix it when inst_source stops using source manager.

Good to know that "outdated" installation sources are no longer auto-refreshed. However, this was a bit OOB (out of bug ;-)

(In reply to comment #1)
> at least the missing 10.1 -> 10.2 translation is worth "critical"

According to the comments above, this is not fixed yet. At least nobody wrote about it ;-)

*** Bug 222222 has been marked as a duplicate of this bug. ***

Results after update 10.1 final -> 10.2 final (i586):
- the 10.1 update sources are disabled (and refreshing is disabled also)
- the disabled 10.1 sources are still hanging around there and waste useful
  space in the installation sources dialog ;-)
- after successful registration, a 10.2 update source is added
  [guessed: without registration, no 10.2 update source would be there]

IMHO the severity of this bug can be lowered - please decide yourself.

lowering severity. SHould be fixed in 10.3

mass reopening all 10.2 LATER+REMIND bugs.

close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it.