Bug#825304: Package: libwebkitgtk-3.0-0
Dave Cole
dave at nk7z.net
Wed May 25 19:47:58 UTC 2016
Package: libwebkitgtk-3.0-0
The webkit package should be rebuild
against gtk+ 3.20.0+. It is built against an earlier package I
believe. Causes white selected text and background under Evolution, in
preview pane.
Package: libwebkitgtk-3.0-0
Version: 2.4.11-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
After a recent update in the testing channel, Evolution Email suddenly
began selecting all text within teh preview pane as white, against a
white background.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Asked for help, and quickly watched the discussion go well beyond my
understanding... I believe I downloaded source, then rebult, but there
was an error during the rebuild.
* What was the outcome of this action?
No change, but as I said it never finished...
* What outcome did you expect instead?
Would have been nice if Evolution, (latest in testing), stopped
selecting text as white, on a white background.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libwebkitgtk-3.0-0 depends on:
ii libatk1.0-0 2.20.0-1
ii libc6 2.22-7
ii libcairo-gobject2 1.14.6-1+b1
ii libcairo2 1.14.6-1+b1
ii libegl1-mesa [libegl1-x11] 11.2.2-1
ii libenchant1c2a 1.6.0-11+b1
ii libfontconfig1 2.11.0-6.4
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.1.1-3
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libgl1-mesa-glx [libgl1] 11.2.2-1
ii libglib2.0-0 2.48.1-1
ii libgstreamer-plugins-base1.0-0 1.8.1-1
ii libgstreamer1.0-0 1.8.1-1
ii libgtk-3-0 3.20.4-1
ii libharfbuzz-icu0 1.0.1-1+b1
ii libharfbuzz0b 1.0.1-1+b1
ii libicu55 55.1-7
ii libjavascriptcoregtk-3.0-0 2.4.11-1
ii libjpeg62-turbo 1:1.4.2-2
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii libpangoft2-1.0-0 1.40.1-1
ii libpng16-16 1.6.21-4
ii libsecret-1-0 0.18.3-1
ii libsoup2.4-1 2.54.1-1
ii libsqlite3-0 3.12.2-1
ii libstdc++6 6.1.1-3
ii libwebp5 0.4.4-1+b2
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxdamage1 1:1.1.4-2+b1
ii libxfixes3 1:5.0.1-2+b2
ii libxml2 2.9.3+dfsg1-1
ii libxrender1 1:0.9.9-2
ii libxslt1.1 1.1.28-3
ii libxt6 1:1.1.5-1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages libwebkitgtk-3.0-0 recommends:
ii geoclue-2.0 2.4.3-1
ii gstreamer1.0-plugins-base 1.8.1-1
ii gstreamer1.0-plugins-good 1.8.1-1
libwebkitgtk-3.0-0 suggests no packages.
-- no debconf information
Here is some info from the Evolution mail list which may save time…
========================CUT========================
Hi,
On Wed, 18 May 2016 09:29:14 +0200, Milan Crha wrote:
>Note that you can build against one version of the library and run
>against another, especially when the two library versions do not change
>API/ABI.
I already explained this, but my mails are censored. However, the sense
of building against the soname is, that there should be no issues, if
backwards-compatibility gets dropped, then the soname should change,
IOW should become GTK4. Dropping backwards-compatibility without
increasing the soname is plain wrong.
"If the interface of a library changes in such a way that the dependent
programs would be broken, the soname would be incremented, e.g. from
libX.so.5 to libX.so.6." - https://en.wikipedia.org/wiki/Soname .
>Your distribution should have some sort of build system, where users
>might be able to check what sources had been used to build the package
>and what packages had been installed when the build was made. For
>example Fedora has Koji ( http://koji.fedoraproject.org/koji ), Arch
>Linux has something else (I do not use Arch Linux, I do not have a
>link)
No, Arch Linux has nothing like that, however, the OP is using Debian
testing.
Arch Linux packages follow releases from upstream, it's a _real_
rolling release. If the soname of a dependency didn't change, then
packages will not be rebuild, unless somebody reports a bug.
Actually there is the above explained reason, that the "NEEDED" lib is
libgtk-3.so.0, against what ever dot release it was linked at build
time.
If it was build against 3.18, nothing should break when 3.20 is
provided at runtime.
[rocketmouse at archlinux ~]$ objdump -p /usr/lib/libwebkitgtk-3.0.so |
grep libgtk
NEEDED libgtk-3.so.0
Arch packages usually don't provide release information for the
dependencies, for the above explained reason.
[rocketmouse at archlinux ~]$ grep epend /var/abs/extra/webkitgtk/PKGBUILD
depends=(libxt libxslt sqlite libsoup enchant libgl geoclue2 gst-
plugins-base-libs
makedepends=(gtk3 gtk2 gperf gobject-introspection python2 mesa ruby)
optdepends=('gst-plugins-base: free media decoding'
depends+=(gtk3)
optdepends+=('gtk2: Netscape plugin support')
depends+=(gtk2)
Debian and Ubuntu come with the Debian tracker.
https://tracker.debian.org/pkg/webkit2gtk
"libgtk-3-dev (>= 3.20.0)" -
https://tracker.debian.org/media/packages/w/webkit2gtk/control-2.12.2-1
IOW the current version in testing _is_ build against 3.20. The OP
mentioned to use 2.4.11-1 yesterday, so the OP today should run
sudo apt-get update && sudo apt-get dist-upgrade
Regards,
Ralf
--
73's, and thanks,
Dave (NK7Z)
For software/hardware reviews see:
http://www.nk7z.net
More information about the Pkg-webkit-maintainers
mailing list