Package Details: mingw-w64-fribidi 1.0.16-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-fribidi.git (read-only, click to copy)
Package Base: mingw-w64-fribidi
Description: A Free Implementation of the Unicode Bidirectional Algorithm (mingw-w64)
Upstream URL: https://github.com/fribidi/fribidi
Licenses: LGPL-2.1-or-later
Submitter: kfg
Maintainer: kfg
Last Packager: kfg
Votes: 8
Popularity: 0.000000
First Submitted: 2013-06-16 15:46 (UTC)
Last Updated: 2024-09-28 00:09 (UTC)

Latest Comments

1 2 3 Next › Last »

grandchild commented on 2024-06-11 13:44 (UTC)

@kfg: While you did add the validpgpkeys entry, you didn't add the key. Please try and build this on a clean system, it will fail downloading the key. Have a look at the native package on how they do it. They include the actual public key file in the package files.

Martchus commented on 2024-05-28 08:14 (UTC)

Right, I also couldn't find it.

grandchild commented on 2024-05-28 07:48 (UTC)

I have not, no. I am not the package maintainer. I just wanted to give a hint as to how this may be done.

The reason why I did that is because I observed that the pubkey 0AD041B27CA166DDA1FE3BAEA7B3409C0CA4ED14 from Dov Grobgeld is not on any keyserver (that is configured on my system anyway). @Martchus, did you observe differently?

Martchus commented on 2024-05-27 16:33 (UTC)

… probably …

Did you actually test whether this will help? (Normally putting keyserver-options auto-key-retrieve into the gpg config file is enough - even though it would of course be nice if relying on an external server could be avoided.)

grandchild commented on 2024-05-27 16:10 (UTC)

Ah, the native package has the pubkey shipped with the PKGBUILD, probably you'd need to do something similar:

https://gitlab.archlinux.org/archlinux/packaging/packages/fribidi/-/tree/main/keys/pgp?ref_type=heads

grandchild commented on 2024-05-27 16:04 (UTC)

does the key 0AD041B27CA166DDA1FE3BAEA7B3409C0CA4ED14 exist? i get

-> 0AD041B27CA166DDA1FE3BAEA7B3409C0CA4ED14, required by: mingw-w64-fribidi
:: Importing keys with gpg...
gpg: keyserver receive failed: No data

Martchus commented on 2020-05-19 11:03 (UTC)

Btw, I've just figured the problem out. (Starting the systemd-nspawn container with --console=interactive is not enough. One needs to set the TERM variable via --setenv=TERM=xterm as well.)

Martchus commented on 2020-05-19 10:49 (UTC)

@kfg Thanks for trying to help. In the meantime I've noticed that other packages trying to use wine fail in the same way. So this has nothing to do with this particular package after all and is just my setup. Apparently WINE needs a terminal but there is none in my systemd-nspawn container which leads to the odd message.

kfg commented on 2020-05-19 10:40 (UTC)

@Martchus Can't really see from the build log what the exact problem is.

The "'unknown': I need something more specific." message looks odd but I have no idea where that is coming from. Can I see the meson.log.txt somewhere?

Martchus commented on 2020-05-17 11:51 (UTC)

When rebuilding against the new GCC I've run into the following error: https://martchus.no-ip.biz/build-data/rebuild-dw2/mingw-w64-fribidi/pkg/build.log

1 2 3 Next › Last »