Your message dated Sun, 20 Sep 2020 13:09:30 +0200
with message-id
<CAB9B7UtM5EDOetBTHb_RNbHOs=r51ponrmwrwu4jkfpnxx9...@mail.gmail.com>
and subject line Re: Bug#944419: postrm script broken
has caused the Debian Bug report #944419,
regarding postrm script broken
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 [email protected]
immediately.)
--
944419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944419
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tiger
Version: 1:3.2.4~rc1-1
Dear maintainer,
The postrm script contains the following bug.
When run with the ``purge'' argument,
the following command is run:
find "$dir" -type d -exec rmdir {} \;
This will always fail and the script is `set -e'.
As a consequence, running ``apt purge'' will fail.
However, running ``apt purge'' for a second time does succeed
as this line does not get executed the second time
since "$dir" will have been deleted the first time around.
Regards,
B.R.S.R.
--- End Message ---
--- Begin Message ---
Version: 1:3.2.4~rc1-1
done
Dear B.R.S.R.
On Sat, 9 Nov 2019 at 17:18, <[email protected]> wrote:
>
> The postrm script contains the following bug.
> When run with the ``purge'' argument,
> the following command is run:
> find "$dir" -type d -exec rmdir {} \;
>
In version 1:3.2.4~rc1-1 the command is not as shown above, when the
package is purged the following is run:
for dir in /var/log/tiger/ /var/lib/tiger/work
/var/lib/tiger/ /var/run/tiger/
do
[ -d "$dir" ] && {
find "$dir" -type f | xargs rm -f
rmdir "$dir"
}
done
This change was documented in the changelog:
* debian/postrm: Remove depth in find when purging to avoid warnings
(LP: #665453)
In previous versions of Tiger the command was actually different and caused
some issues.
To confirm that there are indeed no issues I installed Tiger in a chroot
and purged it both right after installing as well as after a Tiger report.
In both cases no errors were reported.
Consequently, I'm closing this bug. If you think this is a mistake, please
reopen it and provide additional information with the latest Tiger version
installed.
Thanks for your help.
Best regards,
Javier Fernandez-Sanguino
--- End Message ---
