On 2014-10-12 10:02, Bart Martens wrote: > On Sat, Oct 11, 2014 at 10:01:39AM +0200, Niels Thykier wrote: >> [...] >> Beyond chromium needing to migrate, is this solution missing something? > > No, nothing else is needed. > > I see now two alternative approaches : > > 1. Modify pepperflashplugin-nonfree to never violate policy 10.7.3, and close > bug 760388. As a consequence, pepperflashplugin-nonfree becomes useless for > users of an older version of chromium. I can make that explicit by adding > "Conflicts: chromium (< 37.0.2062.120-4)". > > 2. Keep pepperflashplugin-nonfree as it is now (1.7), tolerating that it still > violates policy 10.7.3 for old versions of chromium, and close bug 760388 > because it won't violate policy 10.7.3 for new versions of chromium, so > somewhat bending policy on this. As a consequence, pepperflashplugin-nonfree > remains useful for users of older and newer chromium versions. > > I guess you prefer approach 1 ? > > Regards, > > Bart Martens > >
Yes, I believe we would greatly prefer the 1) listed above. ~Niels -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
