Bug 1375821 - midori must not depend on webkitgtk
Summary: midori must not depend on webkitgtk
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: midori
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: webkit1-removal
TreeView+ depends on / blocked
 
Reported: 2016-09-14 04:55 UTC by Michael Catanzaro
Modified: 2017-08-12 03:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-27 19:09:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Catanzaro 2016-09-14 04:55:07 UTC
The webkitgtk package will be removed from rawhide after Fedora 26 is branched due to the high number of unfixed security vulnerabilities. You must remove this dependency or your package will not be present in Fedora 27.

Please refer to [1] for a FAQ on this matter and be advised that for some packages this may require a substantial amount of work.

Note: I recommend removing Midori immediately without waiting, as its current security situation is fairly egregious [2] and quite unlikely to be fixed anytime soon.

[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/AKVB363GFCHHJ5MTHGVYHYT6NLLTF5VM/
[2] https://blogs.gnome.org/mcatanzaro/2016/02/03/on-subresource-certificate-validation/

Comment 1 Kevin Fenzi 2016-12-27 19:09:43 UTC
I've given up waiting on a upstream release and switched to the webKitTwoOnly branch that builds against webkit2. 

It's a bit unstable under wayland (unless you run it with 'GDK_BACKEND=x11 midori'), but it does work. 

Hopefully upstream will release a real version soon.

Comment 2 Jeremy Bicha 2017-08-12 03:44:14 UTC
midori has been removed from Debian and Ubuntu development releases. midori was a project from elementary OS, but the latest version of elementary OS uses Epiphany as the default browser.


Note You need to log in before you can comment on or make changes to this bug.