https://bugzilla.novell.com/show_bug.cgi?id=801469
https://bugzilla.novell.com/show_bug.cgi?id=801469#c5
Lee Duncan changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
InfoProvider|stefan.muenkner@mx.uni-saar |
|land.de |
--- Comment #5 from Lee Duncan 2013-04-24 11:05:13 PDT ---
Test results so far:
* upgrading from 12.1 iscsitarget to 12.2 iscsitarget, with /etc/ietd.conf
modified
- orig /etc/ietd.conf config file copied to /etc/iet/ietd.conf, as expected
- new empty ietd.conf renamed to /etc/iet/ietd.conf.installed, as expected
- symlink created in /etc pointing to /etc/iet/ietd.conf, as expected
- BUT symlink is called /etc/ietd.conf.rpmsave <== ERROR
As I think about it, this makes sense. One of the last actions taken by the
post-install script is to create the symlink /etc/ietd.conf pointing to
/etc/iet/ietd.conf.
But the RPM packaging is still in progress. I can only assume that when the
post-install script completes that the packaging software says "I see there is
a /etc/ietd.conf present, and that is part of MY package, and it is being
removed, so I must rename it rather than remove it. It evidently doesn't know
that the post-install script just set it up as a symlink.
I'm not sure how to get around this. One option might be to list /etc/ietd.conf
as a symlink in the RPM "files" section, but I suspect this will break upgrade,
i.e. the packaging software will refuse to upgrade a configuration file to a
symlink.
--
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.