Package Details: skype

Git Clone URL: (read-only)
Package Base: skype
Description: P2P software for high-quality voice communication
Upstream URL:
Licenses: custom
Submitter: Rhinoceros
Maintainer: Rhinoceros
Last Packager: Rhinoceros
Votes: 142
Popularity: 11.763938
First Submitted: 2016-07-30 06:34
Last Updated: 2017-04-25 12:02

Pinned Comments

Rhinoceros commented on 2017-06-05 03:07

According to Microsoft, this version of Skype "will be retired on July 1, 2017" [a].

See here [b] to install the beta version (web version in a wrapper).


Rhinoceros commented on 2017-05-14 01:49

lib32-qt4 4.8.7-13 has been updated to fix the lib32-openssl issues. lib32-openssl-1.0 is no longer required. If you are still having issues with skype, please make sure everything is up to date.

Latest Comments

Rhinoceros commented on 2017-06-10 06:15

@cdkitching What version of lib32-qt4 are you running?

cdkitching commented on 2017-06-10 06:09

Still seems to depend on multilib/lib32-openssl-1.0 - had to install that manually to make this work.

Rhinoceros commented on 2017-06-05 03:07

According to Microsoft, this version of Skype "will be retired on July 1, 2017" [a].

See here [b] to install the beta version (web version in a wrapper).


WoefulDerelict commented on 2017-05-30 15:26

Rhinoceros: With any luck the new fangled electron blob will actually replace the legacy Qt blob in earnest and this package can depart the AUR. I do not use the service but the application is free and it worked for testing. A handful of users have insisted that they have a use for the webkit engine in 32-bit Qt 4 apps on multilib systems and they were disappointed it wasn't available in lib32-qt4. While they inconveniently failed to mention which 32-bit binaries they used that needed the qt 4 port of the web engine I knew Skype did so I was able to build and test a lib32-qtwebkit package for them.

Sadly the scope of a UI toolkit and a web engine is quite large so these sources will react to any extraneous software in the build environment they find .pc files for via autoconf. While I find building packages in a clean chroot via the devtools scripts stupid simple it is not /easy/ for everyone and will always be time consuming for Qt 4 and WebKit as they are large, complex blobs that do lots of things and provide those features for other software to use.

One can not make anyone build and use the packages, the recipies have simply been provided as a convenience to users who still have a use for a legacy UI toolkit and web engine to support 32-bit binaries and other madness.

Rhinoceros commented on 2017-05-30 04:02

@WoefulDerelict Yes, I had always thought better of Arch users, but apparently reading comments isn't so easy.

If I had needed {,lib32-}qtwebkit for myself, I'd be happy to build in a chroot. However, making all the skype users go through that, and then dealing with the fallout here would be too masochistic of me! Even if stable versions hit [archlinuxgr], I think the packages need to be *easily* buildable from the AUR before I'd be comfortable adding lib32-qtwebkit as a dependency.

I agree that using the newer version of webkit is the best alternative, in terms of security and stability. However, given the above issues, and given that skype is EOL, and that the web-wrapper beta skype is getting close to feature parity, it's not really worth worrying about too much IMO. This version of Skype is probably riddled with vulnerabilities anyway!

WoefulDerelict commented on 2017-05-29 22:16

ranger: In this instance the tangible gain is one more dependency for Skype on multilib systems (I'm sure no one wanted that, especially one that takes forever to build); however, this results in the removal of an old binary library from the Skype package on x86_64 systems. 32-bit qtwebkit libraries have been sourced from an old lib32-qt4 build in the ALA to hack this package together in order to get the software to work at all as there simply wasn't a viable 32-bit qtwebkit library available in the repos after an update to lib32-qt4. lib32-qtwebkit does need the base Qt 4 framework to build against which is provided by lib32-qt: so it builds atop that to produce a Qt 4 port of webkit. They intentionally do not overlap.

The software distributed to Arch Linux users since the source of 32-bit qtwebkit library used here was built has seen some pretty drastic changes which likely impact the function of qt and webkit. Like all web engines webkit is a massive piece of software with a cornucopia of functions it uses to render web content: many of which reach out to other libraries to ask for help with tasks like audio. There is no telling when an update could introduce a breaking change that disables some feature or causes this old binary to segfault. One could also make the argument, given that this is webkit and skype and the webkit library is being used to handle authentication of the user's skype credentials, old unmaintained binaries present a security risk.

qtwebkit reaches out to gstreamer to help with audio which looks very different on arch systems now, especially since gstreamer0.10 was dropped from the repos. Then there are of course the recent changes to OpenSSL and the dual deployment of versioned 1.1 and 1.0 libraries on many systems. qt4 and consequently lib32-qt4 both needed patches to get through that in working order.

As one understands it both qt4 and lib32-qt4 were built with webkit as part of the package until an update in GCC refused to build that source. The maintainers were able to build qtwebkit separately from an alternate source blob so the decision was made to split the package. This was never mirrored in multilib so qtwebkit support evaporated and absolutely no work was done to correct this even tho bug reports were filed. After this multilib qt4 and qtwebkit were dropped from the official repositories as there are no longer any official packages that required them and they were proving to be legacy pains in the ass. Further changes to GCC, the libraries on Arch Linux systems and patches to Qt 4 have resolved the build issues with the internal webkit build which have allowed some users to build it themselves.

While it would be possible to revert lib32-qt4's PKGBUILD to produce a build that includes webkit that process could easily take upwards of 3 hours for some users who may not even require the web engine. As the standard qt4 package doesn't contain webkit and qt5 also splits it out mirroring this behaviour for multilib seemed straightforward and humane as users who didn't need the webkit engine could avoid the longest portion of the build.

The purpose of lib32-qtwebkit is to provide a properly packaged 32-bit version of the webkit engine for qt 4 so multilib users who utilize legacy applications from sources like the AUR, GoG and Steam built against it can run these binaries on their Arch Linux systems reliably.

ranger commented on 2017-05-29 18:16

qtwebkit is already in archlinuxgr.

I tried to build skype using your PKGBUILD. This pulled lib32-qtwebkit and it's deps.I installed this package (it's in the repo) and it seems to work as usual.
But as lib32-qt4 is still a dep, what exactly do you gain from this?

WoefulDerelict commented on 2017-05-29 15:05

Rhinoceros: Given that lib32-qt4 is similarly troublesome and has generated quite a bit of headache one can understand wanting to wait till the issues there are properly sorted. One had hoped errors could be found and eliminated by users brave enough to follow along with the comments before subjecting everyone to it and generating an unnecessary wave of breakage.

Interesting that your system is tossing a different error than the declaration conflict most users report for qtwebkit. I haven't completely run it to ground yet but that issue seems to be caused by something in how libxslt interacts with libxml2 and qtwebkit after the ICU feature update. This issue can at least be resolved via building in a clean chroot as libxslt isn't required to build the package.

Hopefully once everything is sorted ranger will add qtwebkit to [archlinuxgr] and users can avoid the build headaches that come with finniky legacy toolkits. As I regularly conduct builds of this, lib32-qt4 and lib32-qtwebkit in a clean chroot using the devtools scripts one has offered to sign these and provide them to the repo as part of the update cycle.

Rhinoceros commented on 2017-05-29 05:01

@WoefulDerelict Thank you for all of that information and the package. Unfortunately, I couldn't build qtwebkit (which is a dependency of lib32-qtwebkit). I didn't troubleshoot in a chroot, but from the AUR page, I'm not the only one with those issues. (I actually got different errors to that in the comments, building with your PKGBUILD.)

I agree that the current situation with the skype PKGBUILD is hacky, and adding lib32-qtwebkit as a dependency is probably the "correct" way, but I'm going to hold off for now until the issues with qtwebkit are sorted. If I change the skype PKGBUILD now, it's just going to open the floodgates in these comments (again)!

ranger commented on 2017-05-27 23:55

lib32-qtwebkit is already in archlinuxgr repo, for everyone wanting to try the new PKGBUILD for skype

All comments