Path: csiph.com!news.neodome.net!weretis.net!feeder8.news.weretis.net!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Steinar Bang Newsgroups: linux.debian.maint.java Subject: What causes a config file to be detected as changed by user? Date: Mon, 01 Sep 2025 16:40:01 +0200 Message-ID: X-Original-To: debian-java@lists.debian.org X-Mailbox-Line: From debian-java-request@lists.debian.org Mon Sep 1 14:40:00 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.997 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MD5_SHA1_SUM=-1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: debian-java@lists.debian.org Organization: Probably a good idea MIME-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:BaJWozVY8OLcu7LqM9MuWj9uJFc= Mail-Copies-To: never X-Mailing-List: archive/latest/23789 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/877byikzj1.fsf@dod.no Approved: robomod@news.nic.it Lines: 32 Sender: robomod@news.nic.it X-Original-Date: Mon, 01 Sep 2025 16:39:30 +0200 X-Original-Message-ID: <877byikzj1.fsf@dod.no> Xref: csiph.com linux.debian.maint.java:13057 I have written, and am maintaining an unofficial debian package, for apache karaf made with standard debian tools https://github.com/steinarb/karaf-debian https://karaf.apache.org This debian package asks me on every upgrade that since /etc/karaf/config.properties have been modified locally do I wish to keep that version or do I wish to install the maintainer's version. Since the config.properties files is a file I have no particular interest of, the answer is always to istall the maintainer's version. But since this is obviously something I have done I'm trying to figure out why this happens. The only place where config.properties appear in the git-versioned code of the debian packaging, is in the postinst script: https://github.com/steinarb/karaf-debian/blob/03157cfac337531b96e5011bac9f14cd68fdcbfc/debian/karaf.postinst#L14 What the postinst script does, is: 1. If not present, create user karaf with group karaf 2. Change ownershipt of /etc/karaf and its contents to karaf:karaf with public read/write removed and group write Is this the wrong way of setting owneship and access of the files? (I did it in postinst since the user and group needs to be present before changing ownership) Why is config.properties the only file affected and not all of the *.cfg files? Thanks!