Package Details: glib2-static 2.62.4-4

Git Clone URL: (read-only, click to copy)
Package Base: glib2-static
Description: Low level core library: Static library
Upstream URL:
Licenses: LGPL2.1
Submitter: sergej
Maintainer: nightuser
Last Packager: nightuser
Votes: 11
Popularity: 0.043100
First Submitted: 2013-10-11 17:41
Last Updated: 2020-02-17 17:10

Latest Comments

1 2 3 4 Next › Last »

nightuser commented on 2020-02-17 17:06

@DDoSolitary: did you download a snapshot or clone the package's repo? I usually do the latter and hence didn't catch the error. Will fix this in a moment, sorry.

DDoSolitary commented on 2020-02-17 05:41

The package no longer builds after you adding the patch:

error: --3way outside a repository

And even if you remove --3way option, the patch won't be applied properly because 1) You're in $srcdir rather than the source code directory extracted from the .tar.gz file; 2) It seems that git apply doesn't work when not in a git repository. If you run git apply --verbose ../CVE-2020-6750.patch in the correct directory, you will still see Skipped patch 'gio/gsocketclient.c'.

So I think it's better to apply the patch using the patch utility:

cd glib-$pkgver
patch -Np1 -i ../CVE-2020-6750.patch

nightuser commented on 2019-11-29 08:08

RX14: Why do you think this is bad? Except for the time, obviously.

RX14 commented on 2019-11-28 22:51

Could we please turn off lto for the build (-D b_lto=false), since compiling the spec suite with LTO means essentially compiling and optimizing glib2-static for every single test binary.

nightuser commented on 2019-10-26 20:45

I updated the package. For now, I had to disable utf8-pointer test since it fails with a static build and -O2 in CFLAGS. I shall investigate the issue thoroughly on a clean Arch install and report the bug upstream if it's the case.

UPD: I was able to reproduce the issue, see

UPD2: I temporarily fixed the issue by disabling optimisations for this exact test. It'll probably be fixed upstream soon.

UPD3: fixed.

s123 commented on 2019-10-18 09:37

I confirm, this error reproduces 100% times on my pc:
glib:gio+slow / gdbus-threading FAIL (killed by signal 5 SIGTRAP)
Solution: edit the line in PKGBUILD meson test --num-processes 1 -C build

nightuser commented on 2019-10-02 10:34


I got "192/256 glib:gio+slow / gdbus-threading FAIL 9.10 s (killed by signal 5 SIGTRAP)" error during the test phase. Can you reproduce the error?

PedroHLC commented on 2019-08-26 13:06

To build with 2.61.2: * update pkgver * remove patches (.diff) from source (and checksum) * change to commit 6bebef16 * remove prepare * replace -D selinux=false with -D selinux=disabled

Compilation works, but then 1 test fails with:

77/261 glib:glib / utf8-pointer                FAIL     7.81 s (killed by
signal 6 SIGABRT)

DDoSolitary commented on 2019-04-10 02:15

Sorry for the delay. I've been rather busy recently.

  • I'm not sure if tmp would work because the directory it normally a mounted tmpfs.

  • Yes, I agree that using a mounted home isn't a bad setup at all. I just assumed that it's not very common.

  • "Expected failure" has a different semantic I think. It means that the test intentionally feeds an invalid input and expects the code to detect the error and report it as some sort of failure. It's not the case for the trash test.

greyltc commented on 2019-04-01 14:28

Would the trash test work if it took place in /tmp or /var/tmp? Maybe we could use one of those?

Re. the trashing test failure in a "mounted" location: My /home folder is just a separate btrfs subvolume from /. That doesn't feel like like a very exotic setup to me and building the package in one's home directory also doesn't feel so out of the ordinary.

Another option would be to patch to allow the results of this test to go into the "Expected Fail" category. That way the build could continue normally if it takes place in some location where gio trashing is broken.