Hi Stuart, You're right. It's a policy violation. I guess I shouldn't have uploaded pepperflashplugin-nonfree until chromium had /etc/chromium.d.
This was somewhat already fixed in pepperflashplugin-nonfree 1.4 with #752286. I say "somewhat", because I see now that pepperflashplugin-nonfree still needlessly updates /etc/chromium/default if it exists even if also /etc/chromium.d exists. I'll modify pepperflashplugin-nonfree now to use the /etc/chromium.d approach only if /etc/chromium.d is available regardless of whether /etc/chromium/default exists. Then pepperflashplugin-nonfree will no longer violate policy with newer versions of chromium. Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
