Config file behavior change in rpm 4.0.4?

[Matthias Saou]

Hi,

I think I've been seeing something that quite bothers me ever since
upgrading to rpm 4.0.4 : It looks like the config files are now *always*
handled as if they had been changed (for the old behavior).
- When upgrading a package with files tagged as %config(noreplace), the new
files are always created as .rpmnew.
- When upgrading a package with files tagged as %config, the old files are
always kept as .rpmsave.

Am I right on this? I had been seeing it recently when updating systems
using Rawhide, but now that rpm 4.0.4 has made it into the Enigma updates
and also into Skipjack, I've been experiencing this on all my systems...

I guess I could simply ask Jeff, "is this me or...?", because if this
change was intentional, I really don't understand why it was made.

Matthias

--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.2 (Enigma) running Linux kernel 2.4.18-0.3-pi8k
Load : 0.02 0.09 0.06, AC on-line, battery charging: 100% (11:22)

_______________________________________________
Rpm-list mailing list
Rpm-...@redhat.com
https://listman.redhat.com/mailman/listinfo/rpm-list

[Peter Bowen]

On Thu, 2002-04-18 at 07:09, Matthias Saou wrote:
> Hi,
>
> I think I've been seeing something that quite bothers me ever since
> upgrading to rpm 4.0.4 : It looks like the config files are now *always*
> handled as if they had been changed (for the old behavior).
> - When upgrading a package with files tagged as %config(noreplace), the new
> files are always created as .rpmnew.
> - When upgrading a package with files tagged as %config, the old files are
> always kept as .rpmsave.
>
> Am I right on this? I had been seeing it recently when updating systems
> using Rawhide, but now that rpm 4.0.4 has made it into the Enigma updates
> and also into Skipjack, I've been experiencing this on all my systems...
>
> I guess I could simply ask Jeff, "is this me or...?", because if this
> change was intentional, I really don't understand why it was made.

No this is not just you, and no the change was not intentional. Grab
rpm-4.0.4-7x.16 from RawHide to fix this issue. I'm hoping that Red Hat
will release an updated errata fairly soon, as this is a very annoying
bug.

Thanks.
Peter

[Rob Evensen]

I have a simple question. What are the options that can be used with the
%config tag? I have not seen the (noreplace) option in either the Maximum
RPM or any other documentation that I have been able to find. Is there any
other source that I could peruse for further information? Again thanks for
being patient with yet another beginner.

Rob Evensen

[Jeff Johnson]

On Thu, Apr 18, 2002 at 01:09:27PM +0200, Matthias Saou wrote:
> Hi,
>
> I think I've been seeing something that quite bothers me ever since
> upgrading to rpm 4.0.4 : It looks like the config files are now *always*
> handled as if they had been changed (for the old behavior).
> - When upgrading a package with files tagged as %config(noreplace), the new
> files are always created as .rpmnew.
> - When upgrading a package with files tagged as %config, the old files are
> always kept as .rpmsave.
>
> Am I right on this? I had been seeing it recently when updating systems
> using Rawhide, but now that rpm 4.0.4 has made it into the Enigma updates
> and also into Skipjack, I've been experiencing this on all my systems...
>
> I guess I could simply ask Jeff, "is this me or...?", because if this
> change was intentional, I really don't understand why it was made.
>

Nope, I compared a binary md5 sum witha an ascii string.

All fixed in rpm-4.0.4-7x.16, which may be available in Raw Hide.

73 de Jeff

--
Jeff Johnson ARS N3NPQ
j...@redhat.com (j...@jbj.org)
Chapel Hill, NC

[Matthias Saou]

Once upon a time, Jeff wrote :

> On Thu, Apr 18, 2002 at 01:09:27PM +0200, Matthias Saou wrote:
> >
> > I guess I could simply ask Jeff, "is this me or...?", because if this
> > change was intentional, I really don't understand why it was made.
> >
>
> Nope, I compared a binary md5 sum witha an ascii string.
>
> All fixed in rpm-4.0.4-7x.16, which may be available in Raw Hide.

Alright. And it seems that my skipjack machine that I just updated got that
4.0.4-7x.16 package too.
Well, I now have 41 .rpmnew and .rpmsave files on that box, which is quite
a lot since I didn't edit a single configuration file yet ;-)

Too much coffee Jeff, too much coffee... :-)

Matthias

--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.2 (Enigma) running Linux kernel 2.4.18-0.3-pi8k

Load : 0.39 0.39 0.23, AC on-line, battery charging: 100% (11:34)

[Jeff Johnson]

On Thu, Apr 18, 2002 at 09:02:22AM -0500, Rob Evensen wrote:
> I have a simple question. What are the options that can be used with the
> %config tag? I have not seen the (noreplace) option in either the Maximum
> RPM or any other documentation that I have been able to find. Is there any
> other source that I could peruse for further information? Again thanks for
> being patient with yet another beginner.

There are only two %config qualifiers
%config(noreplace)
Don't wipe out user modifications, install with a .rpmnew
extension instead.
Note carefully that %config(noreplace) file *will* be
upgraded/replaced if not locally modified.

%config(missingok)
Don't wine if the file (e.g. /etc/rc.d/rcN.d/ symlinks)
is not present because of user configuration.

73 de Jeff

--
Jeff Johnson ARS N3NPQ
j...@redhat.com (j...@jbj.org)
Chapel Hill, NC

_______________________________________________

[Matthias Saou]

Once upon a time, Jeff wrote :

> There are only two %config qualifiers
[...]

>
> %config(missingok)
> Don't wine if the file (e.g. /etc/rc.d/rcN.d/ symlinks)
> is not present because of user configuration.

Just a quick note on that last explanation for the "missingok" qualifier. I
think that nowadays it's much better to not include any of the /etc/rcN.d/
symlinks in the spec's %files section and to only include the main
/etc/init.d/ script, chkconfig-aware by default and use "chkconfig --add
servicename" in the %post scriplet and "chkconfig --del servicename" in the
%preun one (after having stopped the service itself, and only if it's not
an upgrade but a removal... better).

For sure, nothing new for most of you, but probably worth mentioning ;-)

Matthias

--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Red Hat Linux release 7.2 (Enigma) running Linux kernel 2.4.18-0.3-pi8k

Load : 0.26 0.23 0.25, AC on-line, battery charging: 100% (11:34)