https://bugzilla.novell.com/show_bug.cgi?id=245074 Summary: new gconf installation scriptlets not failsafe Product: openSUSE 10.3 Version: Alpha 1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: andreas.hanke@gmx-topmail.de QAContact: qa@suse.de There are a bunch of possible cases that the new gconf installation scriptlets do not handle. So far I found: (1) In %pre, it creates a hardlink, but the target file can already exist if a previous scriptlet failed for an unpredictable reason. If the hardlink already existed, this is wrong and overwriting it is OK, so it can be handled by using "ln -f" instead of "ln". (2) In %preun, it tries to call usr/bin/gconftool-2 without checking whether it exists. It should check whether usr/bin/gconftool-2 exists because rpm does not implement package ordering on removal reliably, and not being able to remove schemas should not be fatal. This can happen if GNOME moves again or gconftool-2 goes away, but uninstalling old packages should still be possible. (3) Also in %preun, it tests whether schemas/outdated/*.schemas exists, and if not, it tries to uninstall schemas/*.schemas without checking if it exists. It should check because the user might have deleted the *.schemas file manually and otherwise the same rationale as for (2) applies. (4) In %posttrans, it calls usr/bin/gconftool-2 without checking for anything. This is the only place where this is the correct thing to do because if this fails, which is nearly impossible anyway, the package will not work correctly. Therefore, in this place, similar checks should _not_ be added because we _want_ the installation to fail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.