|
Bugzilla – Full Text Bug Listing |
| Summary: | During system updating, SuSEconfig.fonts will be call when updating each font package, wasting lots of time. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Zhe Su <zsu> |
| Component: | Installation | Assignee: | Ruediger Oertel <ro> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <nld10-bugs-qa> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, andreas.hanke, coolo, kukuk, ro |
| Version: | Alpha 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Zhe Su
2006-03-10 08:22:54 UTC
It seems like a general problem of updating, script SuSEconfig.fonts might be called only once at the end of the update. This is problem of the particular packages - they should check the "YAST_IS_RUNNING" variable and if it is set, then not run SuSEconfig at all (it will be run by YaST after packages are installed/upgraded). Please, reassign to maintainer of affected font packages (don't know whether really all of them are affected, or only some and which) Mike, please help look at this bug. All font packages are already using the macro '%run_suseconfig_fonts'
in the %post and %postun scripts.
As you can see in /usr/lib/rpm/suse_macros, this macro just calls
the macro %run_suseconfig with some options.
And in the same file you can see that %run_suseconfig is defined as:
%run_suseconfig(m:) \
%{!-m:echo -e "\\nERROR: missing parameter for macro run_suseconfig\\n" ; exit 1 ; } \
if test "$YAST_IS_RUNNING" != "instsys" ; then \
if test -x /sbin/SuSEconfig -a -f /sbin/conf.d/SuSEconfig.%{-m*} ; then \
/sbin/SuSEconfig --module %{-m*} \
else \
echo -e "\\nERROR: SuSEconfig or requested SuSEconfig module not present!\\n" ; exit 1 \
fi \
fi \
%nil
i.e. this macro already checks the whether the YAST_IS_RUNNING is set to "instsys"
and if yes it does nothing.
So the problem on update is probably that YAST_IS_RUNNING is not set to "instsys".
Why not? Should it be set to "instsys"? Are there other values for
this variable beside "instsys"? Which ones? Maybe the %run_suseconfig
macro should be changed so that it does not do anything if
YAST_IS_RUNNING is set to *any* value?
reassign to ro@suse.de. I discussed with Stefan Hundhammer <sh@suse.de> and we found that YaST2 sets YAST_IS_RUNNING=yes after the initial reboot. YAST_IS_RUNNING=instsys is set only before the initial reboot. Therefore, the %run_suseconfig macro should most likely do nothing if YAST_IS_RUNNING is set to any value and only execute SuSEconfig modules if YAST_IS_RUNNING is not set. to keep the changes minimal at this point, I'd propose to only change %run_suseconfig_fonts and not %run_suseconfig in general. I think that's OK. I guess the possible impact may be worse than the problem we try to fix. can we move this forward to 10.2 ? I think yes. In that case we can probably do it right and change %run_suseconfig instead of only changing %run_suseconfig_fonts. Will you fix this issue in SLE 10? No, I will not accept such a change now for SLE10. Rudi, can you fix this? ok,%run_suseconfig_fonts will now skip anything if YAST_IS_RUNNING is set |