Bug 448183

Bug No. 1 of this bug report is a duplicate of bug #447043 and alredy fixed.
Bug No. 2 is applet related -> tgoettlicher

Bug No. 2 has been fixed in kupdateapplet 0.8.23.

I have installed RC1 with kde4-kupdateapplet-0.8.27-1.1 and 
Bug #2 is not fixed. I have baseurl=http://download.opensuse.org/update/11.1/
in my repos. 
Btw, what does the "Set default" button intend to do? 

(In reply to comment #3 from Thomas Schmidt)
> Btw, what does the "Set default" button intend to do? 

It should set the default update repository, in case you deleted it or it was missing due to some error or for whatever reason.

This button will now be disabled (as a result of the fix of bug #444301) if the module can find an active update repository. Finding the active update repo is still not working though, see bug #449844.

It will as well be disabled if no default update repository can be found. Unfortunately this information is still missing in the products definition, see bug #449842.

But you should be able to get a valid update repository via
  "Advanced" -> "Register for Support and get update repository"

Please retry with yast2-registration 2.17.16 from:
   ~jdsn/Export/y2rpms/yast2-registration/

I installed 2.17.16. Still have the blue question mark in the tray. Right click -> "check now" opens a KDE popup on the top border of the screen (easy to miss) which says "Please configure an update repository" and a link "more". 
Clicking on "more" does not do anything... :-(

Ah, sorry it does open a new window in the background that allows me to open the YaST2 Online Update Configuration. 
"Set default" is inactive. 
Using "Edit software repositories", I see my active update repo. 
Using "Register..." does works, and adds http://download.opensuse.org/update/11.1/ to my repos. 

So now I have 
http://download.opensuse.org/update/11.1/
and 
http://download.opensuse.org/update/11.1

configured. Maybe the missing ending / makes it not detect the update repo?

[tschmidt@bessel:/space/workspace/swamp-suse]diff /etc/zypp/repos.d/openSUSE-11.1-Updates.repo /etc/zypp/repos.d/repo_4.repo
1,2c1,2
< [openSUSE-11.1-Updates]
< name=openSUSE-11.1-Updates
---
> [repo_4]
> name=Hauptaktualisierungs-Repository
5c5,6
< baseurl=http://download.opensuse.org/update/11.1
---
> baseurl=http://download.opensuse.org/update/11.1/
> path=/

openSUSE-11.1-Updates.repo is recognized by the update applet, repo_4.repo not.

Michael, how does suseRegister compare the existing URLs?
The update URL was added while it was already existing.
Only the trailing slash differes.

It do not compare the URLs. It compare the aliasses. You can write an URL in so many different ways, that it is almost impossible to unify them to do a string compare. So I use the alias. If you add the update URL in behind the back of suse_register, you should use the same alias. It is "openSUSE-11.1-Updates" for 11.1 .

Ok, so this issue is expected behaviour. 
But it would be nice to check for "http://download.opensuse.org/update/11.1" 
in addition to the alias. 
Please close if you like. 

(In reply to comment #10 from Thomas Schmidt)
> But it would be nice to check for "http://download.opensuse.org/update/11.1" 

The problem is, that we do not have this string to compare anything with it. We currently don't have a place where the "default update URL" is defined.
Yes it is included in the extra-URLs of the YaST control file, but there are several others as well, and there is no secure way to identify which one is the URL for updates (no, pattern matching for /update/ is not an option).

For the detailled discussion see bug #449842. I think this will be fixed for 11.2.

Closing as WONTFIX - but meaning CANTFIX.

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. 

Why does "yast2 online_update" not need to compare the alias string to work?

(In reply to comment #12 from Thomas 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.

A proper fix for bug #449842 (as summatized in comment #21 ) would solve this issue as well. Thus closing as duplicate.

*** This bug has been marked as a duplicate of bug 449842 ***