Sometimes some custom repositories are not available.
Then YaST2 Software manager is reading */repodata/repomd.xml for long time and
fails, and ask user what to do; if user selects to Skip this repository, YaST2
still will try to access this repository (at stage of creating/updating catch
for accesible repositories)! And YaST2 will again ask in same dialog what to
do! I suppose, that YaST2 must remember, that used skipped repository, and not
to try access it again.

Tested and reproducible in openSUSE 13.2 and Leap 42.1