[Pkg-privacy-maintainers] Bug#838817: Cannot reproduce

[intrigeri]

intrigeri:
> I *thought* I had fixed this bug already:

> torbrowser-launcher (0.2.5-1) unstable; urgency=medium
> […]
>   * Remove obsolete conffile /etc/apparmor.d/torbrowser.start-tor-browser
>     thanks to Paul Wise. (Closes: #805706)

> … but apparently I failed to get the rm_conffile line right.

FWIW I think I understood the problem… after seeing something very
similar while trying to stop installing
/etc/apparmor.d/usr.bin.torbrowser-launcher: upstream's setup.py still
installs that file, so removing the corresponding cp command from
debian/rules is not enough, and rm_conffile is effectively a noop
given the version number we pass to it. To really get rid of it I had
to:

 - remove the file from the cp command in debian/rules
 - add "rm debian/torbrowser-launcher/etc/apparmor.d/usr.bin.torbrowser-launcher"
   in debian/rules' override_dh_install
 - use rm_conffile

Now, this works because I've noticed this before uploading.

For this very bug I'm not sure. But I suspect that bumping the version
number passed to rm_conffile might be enough (we don't ship
torbrowser.start-tor-browser anymore).

Cheers!
-- 
intrigeri