Package Details: wp-desktop 8.0.0-1

Git Clone URL: (read-only, click to copy)
Package Base: wp-desktop
Description: Desktop client
Upstream URL:
Keywords: Client Desktop WordPress
Licenses: GPL2
Submitter: ValHue
Maintainer: mauriciodelima
Last Packager: mauriciodelima
Votes: 10
Popularity: 0.002786
First Submitted: 2017-06-19 08:38 (UTC)
Last Updated: 2023-07-01 07:13 (UTC)

Latest Comments

1 2 Next › Last »

ValHue commented on 2020-11-03 17:37 (UTC)

The WordPress Desktop project is now part of the Calypso monorepo

socialfoxes commented on 2020-07-18 16:11 (UTC)

Unable to build the package by running makepkg -s due to the presence of the gconf dependency. Removing this dependency allows you to build the package and then install it. Once installed everything works as expected, except there is no icon showing up in the fast app switcher "alt + tab" in the Gnome 3 DE.

ValHue commented on 2020-03-31 07:46 (UTC)

@svinto Thank you for your contributions. I recognize that the current way of carrying the versions is somewhat primitive, but that it worked, because the application warned me when there was a new version and then I updated the PKGBUILD.

I update and introduce your ideas, they seem very timely. Thanks again.

svinto commented on 2020-03-30 20:14 (UTC) (edited on 2020-03-30 20:16 (UTC) by svinto)

The download URL used in PKGBUILD always gives the latest version, so the version set in pkgver is ignored, and checksum fails after download. I propose changing it to:$pkgver/WordPressDesktop-$pkgver.tar.gz

Also, cd "${srcdir}"/WordPress* (first line of function package) complains for me (cd: too many arguments). I propose adding a slash at the end so only directories are matched:

cd "${srcdir}"/WordPress*/

Also (again), latest version 5.0.0 seems to work without pango-legacy.

ValHue commented on 2019-11-17 12:41 (UTC) (edited on 2019-11-17 12:45 (UTC) by ValHue)

I haven't updated the PKGBUILD because since pango reached the version 1.44.2 I've noticed that it gives an error

(wpcom:135829): Pango-ERROR **: 13:36:26.613: Harfbuzz version too old (1.4.2)

as long as i don't figure out how to make it work again I find precipitously released a new version. If anyone has an idea...

He discovered that with the version of Pango 1.44.1 he does not give the error, but the solution should not be a downgrade and that affects the entire system.

I am studying how to install pango 1.44.1 and that it coexists in the system with the current version without affecting it. For this I have thought about creating a new package, but it is not yet operational.

Kaliwaal commented on 2019-10-24 15:43 (UTC) (edited on 2019-10-24 15:44 (UTC) by Kaliwaal)

I calculated the sha256sum of the x64* file downloaded from

and found it to be: sha256sums_x86_64=('1c11008a472e502d686e7ea71b680804a436f4663c7185fde02f3648ddd47110')

I have replaced both the URL and and the checksum in PKGBUILD and wp-desktop has installed without a glitch.

p.s here is the breakdown:

1: Copy the contents of PKGBUILD file from here to a /build/wordpress/PKGBUILD file. 2: download the file from the above URL. preferably to above directory. 2: navigate to directory in terminal and type: $ sha256sum wp-desktop-linux-x64-4.2.0.tar.gz (the version number may vary in your case if you are reading it later on.

4: open PKGBUILD in your fav text editor and replace the download URL as well as the generated checksum in appropriate places

5: makepkg -si

Hope it helps.

gonesimera commented on 2019-06-20 17:52 (UTC)

Still not validating.

I installed using trizen.

trizen -S wp-desktop --skipinteg

All working fine

caseyjp1 commented on 2018-11-19 06:49 (UTC)

This still fails validity check. ==> Validating source_x86_64 files with sha256sums... wp-desktop-linux-x64-3.6.0.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! :: Unable to build wp-desktop - makepkg exited with code: 1 =>> Try again? [y/N]:

This has been the situation for quite awhile now.

TechZerker commented on 2018-08-20 18:29 (UTC)

x64 Package Today is failing validity check, and reporting bsdtar: corrupt tar package. I expect probably just a new version release or update?