From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH qemu-server] debian: add maintscript to remove unused file
Date: Thu, 16 Jul 2026 15:02:24 +0200 [thread overview]
Message-ID: <s8ofr1j84v3.fsf@toolbox> (raw)
In-Reply-To: <581c5a4a-01a0-43c1-bc2b-7123923fe335@proxmox.com> (Fiona Ebner's message of "Thu, 16 Jul 2026 14:23:31 +0200")
Fiona Ebner <f.ebner@proxmox.com> writes:
> Am 20.03.26 um 2:51 PM schrieb Maximiliano Sandoval:
>> The conffile was moved to LIDBIR in in 4093c3f4a but there was no
>> associated cleanup.
>>
>> If one starts from a version of Proxmox VE older than 9, then the the
>> configuration would be at /etc. If the machine is then updated to
>> version 9, then both versions will be present, with the version at /etc
>> having a higher priority as per modules-load.d(5). In such a case, any
>> changes made in the packaged configuration will be ignored.
>>
>> The rm_config (see dpkg-maintscript-helper(1)) is used to remove the
>> trailing config if it was not touched by the user. If the file was
>> touched by the user then it is automatically moved and we move it back
>> manually so that it continues to have higher preference.
>>
>> Suggested-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
>
> The versions need to be adapted to match the next qemu-server version
> bump. With that:
>
> Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
>
> One more comment inline:
>
> [..]
Superseded-by: https://lore.proxmox.com/all/20260716130103.406573-1-m.sandoval@proxmox.com/T/#u
--
Maximiliano
prev parent reply other threads:[~2026-07-16 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 13:51 [PATCH qemu-server] debian: add maintscript to remove unused file Maximiliano Sandoval
2026-07-16 12:23 ` Fiona Ebner
2026-07-16 13:02 ` Maximiliano Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s8ofr1j84v3.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.