Bug 220056

Summary:	YaST attempts to check for updates before network is brought up
Product:	[openSUSE] openSUSE 10.2	Reporter:	Forgotten User DVG0Sx8gYR <forgotten_DVG0Sx8gYR>
Component:	Installation	Assignee:	Duncan Mac-Vicar <dmacvicar>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	jsuchome, lslezak
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 install logs

Description Forgotten User DVG0Sx8gYR 2006-11-10 20:20:24 UTC

This problem was found when performing an update from beta1 to beta2. After the packages are installed and after the initial reboot, YaST attempts to refresh already configured update sources before actually bringing up the network.

I've created an attachment containing the install log. The relevant line can be found at line: 3342 which starts with the text: "2006-11-10 20:04:01 <0> linux-dgwq(3145) [media] MediaCurl.cc(attachTo):568"

Comment 1 Forgotten User DVG0Sx8gYR 2006-11-10 20:22:34 UTC

Created attachment 104743 [details]
YaST2 install logs

Comment 2 Lukas Ocilka 2006-11-13 11:34:08 UTC

sh: online update is maintained by jsuchome

anyway, 'source refresh' error is probably in packager, pkg-bindings -> lslezak

Comment 4 Ladislav Slezák 2006-11-13 12:18:27 UTC

The problem is in initialization of libzypp - even disabled sources are refreshed.
I don't know whether it's a feature or a bug. Duncan?

Another solution is to disable autorefresh for all sources in pkg-bindings (in TargetDisableSources() binding which is called during update to disable all sources at target).

Comment 5 Ladislav Slezák 2006-11-13 13:53:06 UTC

I have applied the workaround in yast2-pkg-bindings-2.14.0 (in TargetDisableSources()) => decreasing the severity

Comment 6 Ladislav Slezák 2006-11-16 13:20:19 UTC


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