canonical-partner-dev team mailing list archive

[Nathanaël Naeri <1544409@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1633678 ***
    https://bugs.launchpad.net/bugs/1633678

> As regards having adobe-flashplugin and pepperflashplugin-nonfree
> conflict to each other [...] Since it can't be done easily, I
> guess we have to live with this inconvenience. I've closed the
> adobe-flashplugin and pepperflashplugin-nonfree tasks.

I understand why the Conflicts can't be added. I can think of one last
way of fixing this inconvenience in published releases: make
pepperflashplugin-nonfree a metapackage Depending on adobe-flashplugin
(assuming this is possible since the later is in Canonical Partner).
This would transparently substitute the former with the later.

> As regards which package browser-plugin-freshplayer-pepperflash
recommends, it's about to be fixed via bug #1633678. Marking this bug as
a duplicate.

Agreed. Looking forward to your work making its way into the published
releases, and we can close this bug.

> As regards the future of pepperflashplugin-nonfree, we don't need it
in Ubuntu any longer since we have adobe-flashplugin.

Unless Canonical Partner can't be enabled for new desktop installations,
isn't it?

> a reasonable measure would probably be to drop it from the Ubuntu
archive in 17.04

I would love to see that happening. How does one go about stopping a
package from being imported from Debian?

-- 
You received this bug notification because you are a member of Canonical
Partner Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1544409

Title:
  Flash plugin from pepperflashplugin-nonfree is installed as a
  Recommends of browser-plugin-freshplayer-pepperflash (source:
  freshplayerplugin) even if it is already installed from another
  package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1544409/+subscriptions