Damon McMahon <damon.mcmahon <at> gmail.com> writes:
> Probably no help, but I had similar happen to me upgrading 4.5->4.6 a
> few months ago. Similar problem with pftcl after a diligent upgrade,
> and like you I have been following the upgrade procedure diligently
> since 3.something. I checked the timestamp on pfctl, it didn't seem
> right so I built from source and installed and the issue went away, so
> I assumed I had something wrong and thought nothing of it as generally
> if OpenBSD f*cks up it's down to me and not the developers
Thanks so much! You saved my upcoming weekend. So I am not hallucinating.
Of course, never expected the developers to solve *my* problems; only wanted to
exclude a bug hitting others.
You're better than me, and I only learned yesterday that the install-set files
come back with the time stamp of creation. Had I known this, a lot could have
been spared, because my second post already showed a lot of bad time stamps in
/sbin.
This 'strange' time stamp (see my earlier post) of "May 31 20:28" still prevails
in a number of files on my box:
# ls -lR | grep "May 31 20:28" | wc -l
153
, *after* I replaced the differing files in /sbin.
> I'd be interested to see if there's a common thread here, particularly
> before I upgrade this box to 4.7 which (like yours) is a remote box
> which will be upgraded over serial.
I guess so. By now I'll have the list of the files affecting amd64 and i386 in
these cases, and you should be able to correct everything using these lists.
Maybe interesting enough, this timestamp was *not* when I upgraded the sets. It
was the time when I upgraded the packages, respectively applied the patches.
But from now on I'll be mum (I hope I can!) on this topic until a complete
explanation is available.
Uwe
