Am 29.01.25 um 14:47 schrieb Michael Biebl:
HiAm 29.01.25 um 14:36 schrieb Yavor Doganov:Michael Biebl wrote:I'm not a aware of a good way to turn a postinst generated configuration file into a proper conffile, but one thing you could do is store a hash (or a list of known hashes) of the postinst generated configuration file and remove /etc/GNUstep/gdomap_probes in *preinst* if it has not been modified by the user. # md5sum /etc/GNUstep/gdomap_probes 0350e9dc3fb96577e6cc2d8873f2fde5 /etc/GNUstep/gdomap_probesBut mine is different (bookworm, i386) and I haven't modified it:
Just curious: What does `hostname -i` return for your system?
$ md5sum /etc/GNUstep/gdomap_probes d9d712469c9cec8898136e52142a19d1 /etc/GNUstep/gdomap_probe Since the old postinst runs "hostname -i" (bad idea, I know) I guess the file is going to be different across various systems, depending on the configuration.Ok, thanks for the additional info. So this rules out https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094636#10What you could do then, is to generate the list of known hashes on-the- fly by taking "hostname -i" into account. Instead of hard-coding the hashsums, you generate them in preinst in exactly the same way as previous versions did.Does that make sense?
I'm aware that the configuration of the system might have changed between the initial installation of gnustep-base-runtime and the upgrade to trixie. So the above recommendation wouldn't cover a 100%.
Do you think that the `hostname -i` output is somewhat stable? Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
