Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44574 - [webkit2gtk] Webkit2gtk breaks after updating GNUTLS.
Attached to Project:
Arch Linux
Opened by Neeks (neeks) - Monday, 13 April 2015, 19:18 GMT
Last edited by Jan de Groot (JGC) - Monday, 13 April 2015, 19:47 GMT
Opened by Neeks (neeks) - Monday, 13 April 2015, 19:18 GMT
Last edited by Jan de Groot (JGC) - Monday, 13 April 2015, 19:47 GMT
|
DetailsDescription:
If user has staging repo enabled and upgrades "gnutls" and "nettle" - Webkit2gtk will fail because it is looking for libgnutls.so.28, not libgnutls.so.30. Users can temporarily make a symlink from "libgnutls.so.30" to "libgnutls.so.28" but certain apps actually check the gnutls version called regardless of the binary file called. Also as of 4/13/2015, 'glib-networking' was introduced into the staging repo and will cause webkit policy errors regardless of symlinking. Is there anyway to signal this package to recompile automatically and push to staging if gnutls/glib-networking is upgraded? I tried a couple times over the weekend to compile the svn repo locally and it fails on me usually between 93% to 99% percent. It wouldn't be that much of a hassle to trial and error my own PKGBUILD's - but it takes like 5 to 6 hours to compile. Additional info: * webkit2gtk-2.8.0-2 Steps to reproduce: * enable staging repo in pacman.conf * upgrade gnutls, nettle and glib-networking * attempt to open epiphany, gnome-control-center via the console and it will output errors. |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 13 April 2015, 19:47 GMT
Reason for closing: Not a bug
Additional comments about closing: It's called staging for a reason.
Monday, 13 April 2015, 19:47 GMT
Reason for closing: Not a bug
Additional comments about closing: It's called staging for a reason.