Hi coldtobi, coldtobi <t...@coldtobi.de> writes: > Maybe new imput: > On drizzle I had the same issue with database files. > My solution was to ask the user (debconf) if the files should be removed on > purge, and defaulted that to yes. This is compliant with the policy and you > can > still explain why this file is needed and why systemd suggests to keep the > file. I don’t think this is a good idea. Users should not be bothered with technical details such as this just for following the policy to the word.
> BTW, *why* does systemd needs this file to be constant? Google did not have an > answer for me... Do you have a pointer? I only found a reference that it can > be > regenerated on stateless systems, so out of this I assume things will not > break > if someone purges systemd and later reinstall it. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619244#45 > (Please note that this bug has a huge impact on piuparts testing, as all > packages directly and indirectly depending on systemd will not be tested until > this is fixed policy-like) Then please work on fixing it…? :) I think the best option (as discussed in this bug already) is to move the file to a more central package like base-files. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
