Bug 307378

Summary:	Writing disabled Remote administration initializes package manager
Product:	[openSUSE] openSUSE 10.3	Reporter:	Stanislav Visnovsky <visnov>
Component:	Installation	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	coolo, locilka, sbrabec, stefan.wiese
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Stanislav Visnovsky 2007-09-04 13:56:15 UTC

From the user POV, it looks like the remote administration module tries to initialize complete package management, even if disabled.

However, it looks like there are 2 bugs:

1) remote administration write progress does not move to 100%
2) inst_fam installation client initializes a complete sw stack.

Comment 1 Jiri Srain 2007-09-04 14:44:05 UTC

inst_fam really does initialize the complete stack, because

- it optionally enables netdaemon (can be removed, since it is obsolete)

- defines a sysconfig variable FAM_LOCAL_ONLY also depending on installed packages (KDE/GNOME)

I talkt to Stanislav Brabec, and according to his explanation, if I understand it correctly, it makes sense to have different value in desktop and server products, but not depending on which desktop is used. Removing this option from the control file (keeping only "always" and "never" and removing "kde" and "gnome" - even GNOME has diffrerent mechanism now, so these options do nto make sense any more) allows to get rid of the package management start.

Comment 2 Stanislav Brabec 2007-09-04 16:22:56 UTC

FAM setup in YaST should be removed. GNOME does not need it any more and request for remote FAM notification configurator for NFS server/client in YaST was rejected. For more see FATE #300348.

Comment 3 Jiri Srain 2007-09-05 11:35:24 UTC

Removed, fixed control files just submitted to STABLE, the setup client itself removed from SVN.

Comment 4 Lukas Ocilka 2007-09-27 09:00:38 UTC

*** Bug 326380 has been marked as a duplicate of this bug. ***