Christian,

Thanks for your reply and sorry for taking so long to follow up.

On Mon, Mar 07, 2005 at 10:55:18AM +0100, Christian Haugan Toldnes wrote:
> 
> (Mar 07 2005 13:19) Alain Fauconnet wrote:
> > Hello list,
> > 
> > I've encountered what looks to me like strange behaviour when
> > upgrading the Apache package under Trustix 2.1. The
> > /home/httpd/html/index.html file, which I had obviously altered from
> > the default installed page, has been renamed to index.html.rpmsave and
> > the newly installed one has been installed as index.html.rpmnew. So after
> > the upgrade, I didn't have any index.html file at all anymore.
> 
> This should not happen.
> 
> The specific case you describe sounds very strange, and more of what one
> might expect after:
> 
> 1: package upgrade (index.html.rpmnew file added index.html still there)
> 2: package removal (index.html backed up to index.html.rpmsave)
> 
> 
> Might I ask what version the package was originally and what it
> became?

As I can tell from the logs, the previous Apache pkg was
apache-2.0.50-2tr. Then, I see what happened during that operation:

Mar  7 13:13:17 proxy03 swup[25941]: Upgraded apache-2.0.52-7tr.i586.rpm.
Mar  7 13:13:17 proxy03 swup[25941]: Installed apache-html-2.0.52-7tr.i586.rpm.

This rings a bell... would the Apache package have been split in two
separate packages, one having the index.html file? In that case, it's
a new install for the latter, not an upgrade. Would that explain this?

Oh, and I see that despite this box being a Trustix 2.1 release, (as
per /etc/trustix-release) it has been configured (not by me!) to
update from the 2.2 tree in /etc/swup/swup.conf. This doesn't seem
quite sane to me, is it? Wouldn't that be the real cause?

Let's see... this has happened on several Squid proxies here. Another
one claims to be 2.2, though:

> cat /etc/trustix-release 
Trustix Secure Linux release 2.2 (Sunchild)

However, I see the same update pattern in swup logs:

Mar  1 13:01:43 proxy01 swup[21143]: Upgraded apache-2.0.52-7tr.i586.rpm.
Mar  1 13:01:43 proxy01 swup[21143]: Installed apache-html-2.0.52-7tr.i586.rpm.

I'm confused. Would you be so kind to shed some light on this? I
suspect that we've messed up, but how? I can get details on how this
last box was upgraded from 2.1 to 2.2 (and probably should).

(...)

> > I'm fairly new to Trustix and the wonderful world of RPM-packaged Unices
> > (my background is more *BSD and do-it-yourself-from-source upgrades).
> > Is this expected behaviour? I'd accept it for binaries, but for
> > modifiable files like index.html I find this a bit intrusive.
> 
> index.html is marked to be a config file, thus it will not be changed
> during upgrade. That's why you get the .rpmnew file, which is 100%
> correct behaviour.
> 
> The .rpmsave file is what you get when the package is removed, but you
> had made changes to the config file when it was available. It is a
> backup of the changed file.
> 
> > Any way I can convinced swup to leave edited files alone?
> 
> Swup does not handle files, it handles packages. The files are handled
> by the package, thus rpm is the place to look. I do not think rpm has
> functionality for letting the user 'hold' specific files, but as I said,
> this should not be needed as the packages have such features internally.

Understood. But in case of a fresh install (as apache-html-2.0.52-7tr
seems to have been from the logs) and an already existing file,
possibly from another package, what happens?

> At least check the contents of index.html.rpmsave, it should be the
> correct one with your changes.

Yes it was. Actually I've "mv index.html.rpmsave index.html" before posting,
because that missing index.html broke our "server up" detection with
disastrous side effects.

> (However, since the whole situation seems
> very strange I cannot tell for sure.) Also check that apache still is
> installed, and maybe verify the installation:
> rpm -V apache (will give output on files that have changed since
> installation.)

# rpm -V apache

All lines come up like:
.....UG.   /home/httpd

which AFAIK means that uid/gid don't match what is expected (httpd/httpd now).

except:

S.5....T c /etc/httpd/conf/httpd.conf

which is quite normal, since it's been customised.

# rpm -V apache-html

Same, all '.....UG.' except:

S.5..UGT c /home/httpd/html/index.html

which, again, doesn't suprise me.

Greets,
_Alain_
_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to