On Wed, Dec 11, 2019 at 1:00 AM Andreas Beckmann <a...@debian.org> wrote: > > I can reproduce this with piuparts on the upgrade path > jessie -> (stretch) -> (buster) -> bullseye > There was no torbrowser-launcher in stretch or buster, therefore the > jessie version was kept installed and finally upgraded to bullseye. > There are no local modfications to these files. > > Setting up torbrowser-launcher (0.3.2-4) ... > > Configuration file '/etc/apparmor.d/local/torbrowser.Browser.firefox' > ==> File on system created by you or by a script. > ==> File also in package provided by package maintainer. > What would you like to do about it ? Your options are: > Y or I : install the package maintainer's version > N or O : keep your currently-installed version > D : show the differences between the versions > Z : start a shell to examine the situation > The default action is to keep your current version. > *** torbrowser.Browser.firefox (Y/I/N/O/D/Z) [default=N] ? dpkg: error > processing package torbrowser-launcher (--configure): > end of file on stdin at conffile prompt
I find this is due to below files were shipped by previous version of torbrowser-launcher, but not as conffile. /etc/apparmor.d/local/torbrowser.Tor.tor /etc/apparmor.d/local/torbrowser.Browser.firefox But now they're shipped with conffile, though in size zero. So new conffiles complain they don't match with existing ones. It can be fixed by removing the old files when they match the checksum of old shipped ones. The fix will be uploaded soon. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
