https://bugzilla.novell.com/show_bug.cgi?id=448183
User jdsn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=448183#c13
J. Daniel Schmidt
When I add the update repo by "community repositories" option in the repository manager, I get the update repo with a localized alias which does not match your check.
Who do you mean with "your check"? A localized alias for the update repo should not be used, as the registration only compares alias Names but not the repo-URL. This is another bug.
Why does "yast2 online_update" not need to compare the alias string to work?
I don't think that "yast2 online_update" checks the repos at all. Comparing alias strings is only possible if you have two strings to compare. The first amount of alias strings comes from the list of all repos. The string to compare these strings with can not be read from anywhere currently - we just don't know it (see as well [4]). There is no place where it is defined. As this seems to become a bigger issue I'll summarize here the current status, as a documentation and as a help for us what we are talking about. ------------------ There are currently four applications dealing with the update repo. I just collected the information how and what they do: 1) yast2-online_update_configuration 2) kupdateapplet 3) suseRegister 4) yast2-(inst_source|repositories) ------ 1) Would be able to check for an active update repo and add the default update repo (if missing), if there would be this information in the products file. This is not the case and will not be fixed for 11.1, see bug #449842. As the update information in the products file (_if_ it would be included) only consists of a URL only and does not provide alias name, this module only checks for the URL - it compares all URLs of all repos with this default one (only protocol, hostname and path (ignores parameters and trailing slashes)). 2) With the packagekit backend the updaterapplet fetches a list of all repos and checks if one of these match this pattern: /update/i With the zypp backend the updaterapplet asks zypper which in turn looks into the system and counts if there are patches, and if yes, assumes that there is an update repo. (So if there is an update repo which is empty zypper will not recognize it.) 3) suseRegister gets its information from the NCC server. This data contains the alias name of the default update repo (as it is added by [4]). It now checks if there is a repo installed with this alias name. No URL checking is happening here. 4) With the software repositories module you can add the deault update repo with the alias that is also known by the NCC server. But this module does not know that it adds an update repo, its just one of many repos that are available. It can not tell which one of these is the default update repo. So as you can see, we have four applications that have five different ways to work with the update repo. That is why we can not fix it now. We know about all that. Thats why I wrote that this is a CANTFIX bug. The best solution would be to have one place in the system where this information is stored with all needed additional parameters and can and must be read from there by every application dealing with updates in any way. Thus adding Klaus for architect input and Duncan and Coolo for comments. I will now move the target to 11.2 as we should find a proper solution for that after 11.1 is released. -- 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.