Your message dated Wed, 22 Nov 2017 16:09:23 +0900
with message-id <c99697289a079556895c61853e5e1...@duckcorp.org>
and subject line Re: redmine: purge fails when /etc/redmine/*/database.yml
doesn't exist
has caused the Debian Bug report #836363,
regarding redmine: purge fails when /etc/redmine/*/database.yml doesn't exist
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
836363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redmine
Version: 3.2.3-1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
During my investigation of bug 835987¹, I noticed that purging redmine fails
when there is no database.yml file. As this file is a configuration file, and
thus can legitimately be removed by the admin, purging shouldn't fail on its
absence.
[ In my case the file was missing exactly due to bug 835987, that caused
failure of redmine installation, but that is not relevant. ]
Relevant parts of the log:
root@sid:# apt-get purge redmine
The following packages will be REMOVED:
redmine*
ls: cannot access '/etc/redmine/*/database.yml': No such file or directory
dirname: missing operand
Try 'dirname --help' for more information.
basename: missing operand
Try 'basename --help' for more information.
dpkg: error processing package redmine (--remove):
subprocess installed post-removal script returned error exit status 123
Errors were encountered while processing:
redmine
The issue is off-course in the postrm script:
instances=$(ls -1 /etc/redmine/*/database.yml | xargs dirname | xargs -n 1
basename)
Paul
¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835987
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJXySvBAAoJEJxcmesFvXUKyREIALEis1qP8/+WQ1BtxkbJFAcu
I8x4/aZxSXLsrf7kc8CQ1GpXbbK1k8pJ0Ct14NSj/q0HClNaRCPb9ZEBvu6AcvVX
PyqelOCFBZFohVcoSAsCvuzo/xnjpB9sWC/lDSHBsdb2KhOZJxQtcECV5aqPGAUk
78z1P6bHjorTz8rORI5bD+HEE7tGJYFhDk5ABZvtOf6H+MnV6uDoshBbkUA+e/X8
Oa6iBAoMCIrB/TqRmf+/8tmPdVy9GZuzr7jIcLyZ1Q4s1gsvIBpG/+ZvHJO1yvdk
xeut/otUs56g+ubmmg1BUQq6QUklIJ3b+p4keRsiFWMZaSyLIZzBj7K1ChWFU3A=
=+rRM
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 3.4.2-1
Quack,
Even if /etc/redmine/ was destroyed completely, it does not fail
anymore.
Fix related to #868955.
Thanks for reporting this problem.
\_o<
--
Marc Dequènes
--- End Message ---
