epiphany-extensions uninstallable in lucid (epiphany 2.30 conflicts with epiphany-extensions 2.29)
Bug #563113 reported by
Juha Siltala
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
epiphany-extensions (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
epiphany-extensions-more (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: epiphany-extensions
On Lucid, it is currently impossible to update Epiphany to the stable 2.30 version without removing the extensions and extensions-more packages, because epiphany-extensions is still at version 2.29. We need an updated extensions package.
Changed in epiphany-extensions (Ubuntu): | |
status: | New → Confirmed |
Changed in epiphany-extensions (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- Epiphany 2.30 conflicts with epiphany-extensions 2.29 + epiphany-extensions uninstallable in lucid (epiphany 2.30 conflicts with + epiphany-extensions 2.29) |
Changed in epiphany-extensions-more (Ubuntu): | |
status: | New → Invalid |
Changed in epiphany-extensions (Ubuntu): | |
status: | Fix Released → Fix Committed |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
resetting to new to start request for feature-freeze exception. Please sync epiphany-extensions from Debian unstable.
The rationale is pretty obvious. The current epiphany package specifically breaks any epiphany-extensions package earlier than the one currently in Debian unstable. epiphany-extensions obviously depends on the epiphany-browser package. As such, it is currently not installable. That is only fixable by syncing the version from Debian unstable. There is no Ubuntu-specific delta.