Re: request for exception to policy 10.7.3
On Sat, Oct 11, 2014 at 10:01:39AM +0200, Niels Thykier wrote:
> On 2014-10-11 07:44, Bart Martens wrote:
> > Hi debian-release,
> >
> > Bug 760388 still happens with pepperflashplugin-nonfree 1.7 depending on which
> > version of chromium is used. [...]
>
> I am guessing you are needing a chromium (>= 37.0.2062.120-4) for
> avoiding the issue?
It is true that the relevant change in chromium is in chromium 37.0.2062.120-4.
>
> > So I now have two options :
> >
> > [...]
> >
> > OK for you to follow option 2 ?
> >
> > Regards,
> >
> > Bart Martens
> >
> >
>
> Can we solve this by adding such a dependency on the newer chromium
That would be somewhat wrong, because pepperflashplugin-nonfree could be useful
with browsers other than chromium, which is why chromium is currently in
"Suggests", not in "Depends".
> and then fixing #760388 for Jessie?
Depending on how one looks at this, pepperflashplugin-nonfree 1.7 is already
fixed for Jessie.
> 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
Reply to: