326956 – Unable to add update sources

Bug 326956 - Unable to add update sources

Summary: Unable to add update sources

Status:	RESOLVED DUPLICATE of bug 326483

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	Update Problems (show other bugs)
Version:	RC 1
Hardware:	64bit Linux

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	Thomas Göttlicher
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-09-20 21:04 UTC by Fred van Zwieten
Modified:	2007-09-21 08:13 UTC (History)
CC List:	0 users

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Fred van Zwieten 2007-09-20 21:04:08 UTC

This happens on a fresh offline install, because I was not able to do a online install thru wifi. I have a blue questionmark icon in my statusbar saying "Unable to check whether update are available". The only repository in Yast is the install CD. When I choose "Add/Remove update sources" frmo the update applet nothing happens, and I really mean nothing. Where should I check for errors?

Comment 1 Andreas Jaeger 2007-09-21 07:03:44 UTC

That button is a bug which will be fixed in RC2.

To add the official sources, use "yast2 inst_suse_register".

Thomas, currently opensuse-updater calls yast2 repositories - I think the inst_suse_register would be an option as well.

Comment 2 Thomas Göttlicher 2007-09-21 08:13:44 UTC

(In reply to comment #1 from Andreas Jaeger)
> That button is a bug which will be fixed in RC2.
That's right. Bug 326483.

 
> Thomas, currently opensuse-updater calls yast2 repositories - I think the
> inst_suse_register would be an option as well.
The button says "Add/Remove Update Sources" but "yast2 inst_suse_register" is only able to add repositories. Therefore calling "yast2 repositories" might be the better way. 



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