Package Details: i3-gaps-next-git 4.16.1.r107.g41264e54-2

Git Clone URL: https://aur.archlinux.org/i3-gaps-next-git.git (read-only)
Package Base: i3-gaps-next-git
Description: A fork of i3wm tiling window manager (development branch) with more features, including gaps
Upstream URL: https://github.com/Airblader/i3/tree/gaps-next
Keywords: gaps i3
Licenses: BSD
Groups: i3-vcs
Conflicts: i3-gaps, i3-gaps-git, i3-git, i3-wm, i3bar, i3bar-git
Provides: i3-wm
Submitter: bandali
Maintainer: Airblader
Last Packager: Airblader
Votes: 125
Popularity: 1.028366
First Submitted: 2015-01-04 04:40
Last Updated: 2019-01-29 07:47

Dependencies (22)

Required by (28)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Airblader commented on 2019-03-29 08:23

@Megumi_fox Can you please report this on GitHub upstream in i3?

Megumi_fox commented on 2019-03-29 04:54

when building on many threads concurrently, the generated Makefile may try to compile i3-config-wizard before i3-config-parser.stamp and result an error where GCC cannot find the to-be-generated header file. This error happens at a low possibility.

  GEN      docs/debugging.html
  GEN      docs/lib-i3test.html
  GEN      docs/lib-i3test-test.html
  GEN      docs/hacking-howto.html
  GEN      docs/userguide.html
../../i3/i3-config-wizard/main.c:109:10: fatal error: GENERATED_config_enums.h: No such file or directory
 #include "GENERATED_config_enums.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile:2774: i3-config-wizard/i3_config_wizard-main.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/build/i3-gaps-next-git/src/i3/build'
make: *** [Makefile:1332: all] Error 2
 [1m [31m==> ERROR: (B [m [1m A failure occurred in build(). (B [m

chrhasse commented on 2019-03-21 07:52

I can confirm it's working now. Thanks for the merge.

Airblader commented on 2019-03-21 07:44

@chrhasse @callen @rhssk A fix should have been merged now, could you verify please?

Airblader commented on 2019-03-20 08:19

Thanks, I've reported this upstream for now: https://github.com/i3/i3/issues/3652

chrhasse commented on 2019-03-20 04:22

Saving this patch as 0001-fix-pango-update.patch

diff --git a/Makefile.am b/Makefile.am
index ee71b7f2..79201b98 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -277,6 +277,8 @@ i3_LDADD = \

 libi3_CFLAGS = \
    $(AM_CFLAGS) \
+   $(GLIB2_CFLAGS) \
+   $(GOBJECT2_CFLAGS) \
    $(XCB_CFLAGS) \
    $(XCB_UTIL_CFLAGS) \
    $(XCB_UTIL_XRM_CFLAGS) \
@@ -285,6 +287,8 @@ libi3_CFLAGS = \

 libi3_LIBS = \
    $(top_builddir)/libi3.a \
+   $(GLIB2_LIBS) \
+   $(GOBJECT2_LIBS) \
    $(XCB_LIBS) \
    $(XCB_UTIL_LIBS) \
    $(XCB_UTIL_XRM_LIBS) \
diff --git a/configure.ac b/configure.ac
index 6088699d..556b4be3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -101,6 +101,8 @@ PKG_CHECK_MODULES([XKBCOMMON], [xkbcommon xkbcommon-x11])
 PKG_CHECK_MODULES([YAJL], [yajl])
 PKG_CHECK_MODULES([LIBPCRE], [libpcre >= 8.10])
 PKG_CHECK_MODULES([PANGOCAIRO], [cairo >= 1.14.4 pangocairo])
+PKG_CHECK_MODULES([GLIB2], [glib-2.0])
+PKG_CHECK_MODULES([GOBJECT2], [gobject-2.0])

 # Checks for programs.
 AC_PROG_AWK

and modifying the PKGBUILD to patch apply it like so

source=('git://github.com/Airblader/i3#branch=gaps-next' '0001-fix-pango-update.patch')
sha1sums=('SKIP'
          'c8820c20daee3af60ee6b5ccbfecbbc1bc2bf3aa')

_gitname='i3'

pkgver() {
  cd "$srcdir/$_gitname"
  git describe --long | sed 's/\([^-]*-g\)/r\1/;s/-/./g'
}

prepare() {
    cd "$srcdir/$_gitname"
    patch -Np1 -i "$srcdir/0001-fix-pango-update.patch"
}

fixes the issue for me. It would probably be better to depend on glib-2.0 and gobject-2.0 explicitly as well.

callen commented on 2019-03-19 21:53

Also seeing the same issue

rhssk commented on 2019-03-19 18:32

pango was updated to 1.43.0 (https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/pango) and the good old

undefined reference to symbol 'g_utf8_make_valid'

is back.

madscience commented on 2019-01-29 15:24

That worked perfectly, thanks!

Airblader commented on 2019-01-29 07:49

@madscience I've changed the pkgver now according to the guidelines[1]. Probably one reinstall is necessary to update the local version, though. Let me know if you have issues still. Thanks!

[1] https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function