Gnome-Terminal-Transparency Fails To Build

A4orce84 · 30 March 2024 17:57

Hi Everyone,

Getting the following error when building this package:

AUR Explicit (1): gnome-terminal-transparency-3.52.0-1
:: PKGBUILD up to date, skipping download: gnome-terminal-transparency
  1 gnome-terminal-transparency      (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  1 gnome-terminal-transparency      (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
==> Making package: gnome-terminal-transparency 3.52.0-1 (Sat 30 Mar 2024 12:53:33 PM CDT)
==> Retrieving sources...
  -> Found gnome-terminal-3.52.0.tar.gz
  -> Found transparency.patch
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with b2sums...
    gnome-terminal-3.52.0.tar.gz ... Passed
    transparency.patch ... Passed
:: (1/1) Parsing SRCINFO: gnome-terminal-transparency
==> Making package: gnome-terminal-transparency 3.52.0-1 (Sat 30 Mar 2024 12:53:34 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found gnome-terminal-3.52.0.tar.gz
  -> Found transparency.patch
==> Validating source files with b2sums...
    gnome-terminal-3.52.0.tar.gz ... Passed
    transparency.patch ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting gnome-terminal-3.52.0.tar.gz with bsdtar
==> Starting prepare()...
patching file src/org.gnome.Terminal.gschema.xml
patching file src/preferences.ui
patching file src/profile-editor.cc
patching file src/terminal-schemas.hh
patching file src/terminal-screen.cc
patching file src/terminal-window.cc
patching file src/terminal-window.cc
patching file src/terminal-screen.cc
patching file src/terminal-window.cc
patching file po/am.po
patching file po/an.po
patching file po/ar.po
patching file po/as.po
patching file po/ast.po
patching file po/az.po
patching file po/be.po
patching file po/be@latin.po
patching file po/bg.po
patching file po/bn.po
patching file po/bn_IN.po
patching file po/br.po
patching file po/bs.po
patching file po/ca.po
patching file po/ca@valencia.po
patching file po/cs.po
patching file po/cy.po
patching file po/da.po
patching file po/de.po
patching file po/dz.po
patching file po/el.po
patching file po/en@shaw.po
patching file po/en_CA.po
patching file po/en_GB.po
patching file po/eo.po
patching file po/es.po
patching file po/et.po
patching file po/eu.po
patching file po/fa.po
patching file po/fi.po
patching file po/fr.po
patching file po/fur.po
patching file po/ga.po
patching file po/gl.po
patching file po/gu.po
patching file po/he.po
patching file po/hi.po
patching file po/hr.po
patching file po/hu.po
patching file po/hy.po
patching file po/id.po
patching file po/it.po
patching file po/ja.po
patching file po/ka.po
patching file po/kk.po
patching file po/km.po
patching file po/kn.po
patching file po/ko.po
patching file po/ku.po
patching file po/lt.po
patching file po/lv.po
patching file po/mai.po
patching file po/mg.po
patching file po/mk.po
patching file po/ml.po
patching file po/mn.po
patching file po/mr.po
patching file po/ms.po
patching file po/nb.po
patching file po/nds.po
patching file po/ne.po
patching file po/nl.po
patching file po/nn.po
patching file po/oc.po
patching file po/or.po
patching file po/pa.po
patching file po/ps.po
patching file po/pt.po
patching file po/pt_BR.po
patching file po/ro.po
patching file po/ru.po
patching file po/rw.po
patching file po/si.po
patching file po/sk.po
patching file po/sl.po
patching file po/sq.po
patching file po/sr.po
patching file po/sr@latin.po
patching file po/sv.po
patching file po/ta.po
patching file po/te.po
patching file po/tg.po
patching file po/th.po
patching file po/tr.po
patching file po/ug.po
patching file po/uk.po
patching file po/vi.po
patching file po/wa.po
patching file po/xh.po
patching file po/zh_CN.po
patching file po/zh_HK.po
patching file po/zh_TW.po
==> Sources are ready.
==> Making package: gnome-terminal-transparency 3.52.0-1 (Sat 30 Mar 2024 12:53:36 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
+ exec meson setup --prefix /usr --libexecdir lib --sbindir bin --buildtype plain --auto-features enabled --wrap-mode nodownload -D b_pie=true -D python.bytecompile=1 gnome-terminal-3.52.0 build -D b_lto=false
The Meson build system
Version: 1.4.0
Source dir: /home/aahmad/.cache/yay/gnome-terminal-transparency/src/gnome-terminal-3.52.0
Build dir: /home/aahmad/.cache/yay/gnome-terminal-transparency/src/build
Build type: native build
Project name: gnome-terminal
Project version: 3.52.0
C compiler for the host machine: ccache cc (gcc 13.2.1 "cc (GCC) 13.2.1 20230801")
C linker for the host machine: cc ld.bfd 2.42.0
C++ compiler for the host machine: ccache c++ (gcc 13.2.1 "c++ (GCC) 13.2.1 20230801")
C++ linker for the host machine: c++ ld.bfd 2.42.0
Host machine cpu family: x86_64
Host machine cpu: x86_64
Compiler for C supports arguments -std=gnu11: YES 
gnome-terminal-3.52.0/meson.build:121: WARNING: Consider using the built-in option for language standard version instead of using "-std=gnu11".
Compiler for C++ supports arguments -std=gnu++14: YES 
gnome-terminal-3.52.0/meson.build:129: WARNING: Consider using the built-in option for language standard version instead of using "-std=gnu++14".
Library dl found: YES
Checking for function "dlsym" with dependency -ldl: YES 
Compiler for C supports arguments -Waggregate-return: YES 
Compiler for C supports arguments -Wall: YES 
Compiler for C supports arguments -Wcast-align: YES 
Compiler for C supports arguments -Wendif-labels: YES 
Compiler for C supports arguments -Werror=init-self: YES 
Compiler for C supports arguments -Werror=missing-include-dirs: YES 
Compiler for C supports arguments -Werror=pointer-arith: YES 
Compiler for C supports arguments -Wextra: YES 
Compiler for C supports arguments -Wfloat-equal: YES 
Compiler for C supports arguments -Wformat-signedness: YES 
Compiler for C supports arguments -Wimplicit: YES 
Compiler for C supports arguments -Wlogical-op: YES 
Compiler for C supports arguments -Wmissing-declarations: YES 
Compiler for C supports arguments -Wmissing-format-attribute: YES 
Compiler for C supports arguments -Wmissing-include-dirs: YES 
Compiler for C supports arguments -Wmissing-noreturn: YES 
Compiler for C supports arguments -Wnested-externs: YES 
Compiler for C supports arguments -Wno-maybe-uninitialized: YES 
Compiler for C supports arguments -Wno-missing-field-initializers: YES 
Compiler for C supports arguments -Wno-switch-enum: YES 
Compiler for C supports arguments -Wno-unused-parameter: YES 
Compiler for C supports arguments -Wold-style-definition: YES 
Compiler for C supports arguments -Wpacked: YES 
Compiler for C supports arguments -Wshadow: YES 
Compiler for C supports arguments -Wsign-compare: YES 
Compiler for C supports arguments -Wstrict-aliasing=2: YES 
Compiler for C supports arguments -Wstrict-prototypes: YES 
Compiler for C supports arguments -Wundef: YES 
Compiler for C supports arguments -Wuninitialized: YES 
Compiler for C supports arguments -Wunsafe-loop-optimizations: YES 
Compiler for C supports arguments -Wvla: YES 
Compiler for C supports arguments -Wwrite-strings: YES 
Compiler for C supports arguments -fdiagnostics-show-option: YES 
Compiler for C supports arguments -fno-common: YES 
Compiler for C supports arguments -fstack-protector: YES 
Compiler for C supports arguments -fstack-protector-strong: YES 
Compiler for C supports arguments -fvisibility=hidden: YES 
Compiler for C supports arguments -fno-strict-aliasing: YES 
Compiler for C supports arguments -Waggregate-return: YES (cached)
Compiler for C supports arguments -Werror=implicit-function-declaration: YES 
Compiler for C supports arguments -Werror=missing-prototypes: YES 
Compiler for C supports arguments -Wimplicit: YES (cached)
Compiler for C supports arguments -Wimplicit-fallthrough=3: YES 
Compiler for C supports arguments -Wmissing-parameter-type: YES 
Compiler for C supports arguments -Wnested-externs: YES (cached)
Compiler for C supports arguments -Wold-style-declaration: YES 
Compiler for C supports arguments -Wold-style-definition: YES (cached)
Compiler for C supports arguments -Woverride-init: YES 
Compiler for C supports arguments -Wsign-compare: YES (cached)
Compiler for C supports arguments -Wstrict-prototypes: YES (cached)
Compiler for C supports arguments -fvisibility=hidden: YES (cached)
Compiler for C++ supports arguments -Waggregate-return: YES 
Compiler for C++ supports arguments -Wall: YES 
Compiler for C++ supports arguments -Wcast-align: YES 
Compiler for C++ supports arguments -Wendif-labels: YES 
Compiler for C++ supports arguments -Werror=init-self: YES 
Compiler for C++ supports arguments -Werror=missing-include-dirs: YES 
Compiler for C++ supports arguments -Werror=pointer-arith: YES 
Compiler for C++ supports arguments -Wextra: YES 
Compiler for C++ supports arguments -Wfloat-equal: YES 
Compiler for C++ supports arguments -Wformat-signedness: YES 
Compiler for C++ supports arguments -Wimplicit: NO 
Compiler for C++ supports arguments -Wlogical-op: YES 
Compiler for C++ supports arguments -Wmissing-declarations: YES 
Compiler for C++ supports arguments -Wmissing-format-attribute: YES 
Compiler for C++ supports arguments -Wmissing-include-dirs: YES 
Compiler for C++ supports arguments -Wmissing-noreturn: YES 
Compiler for C++ supports arguments -Wnested-externs: NO 
Compiler for C++ supports arguments -Wno-maybe-uninitialized: YES 
Compiler for C++ supports arguments -Wno-missing-field-initializers: YES 
Compiler for C++ supports arguments -Wno-switch-enum: YES 
Compiler for C++ supports arguments -Wno-unused-parameter: YES 
Compiler for C++ supports arguments -Wold-style-definition: NO 
Compiler for C++ supports arguments -Wpacked: YES 
Compiler for C++ supports arguments -Wshadow: YES 
Compiler for C++ supports arguments -Wsign-compare: YES 
Compiler for C++ supports arguments -Wstrict-aliasing=2: YES 
Compiler for C++ supports arguments -Wstrict-prototypes: NO 
Compiler for C++ supports arguments -Wundef: YES 
Compiler for C++ supports arguments -Wuninitialized: YES 
Compiler for C++ supports arguments -Wunsafe-loop-optimizations: YES 
Compiler for C++ supports arguments -Wvla: YES 
Compiler for C++ supports arguments -Wwrite-strings: YES 
Compiler for C++ supports arguments -fdiagnostics-show-option: YES 
Compiler for C++ supports arguments -fno-common: YES 
Compiler for C++ supports arguments -fstack-protector: YES 
Compiler for C++ supports arguments -fstack-protector-strong: YES 
Compiler for C++ supports arguments -fvisibility=hidden: YES 
Compiler for C++ supports arguments -fno-strict-aliasing: YES 
Compiler for C++ supports arguments -Wimplicit-fallthrough=5: YES 
Compiler for C++ supports arguments -Wnon-virtual-dtor: YES 
Compiler for C++ supports arguments -Wstrict-null-sentinel: YES 
Compiler for C++ supports arguments -fvisibility-inlines-hidden: YES 
Compiler for C++ supports arguments -fvisibility=hidden: YES (cached)
Compiler for C++ supports arguments -fvisibility-inlines-hidden: YES (cached)
Compiler for C++ supports arguments -fvisibility=hidden: YES (cached)
Compiler for C supports arguments -Werror=format=2 -Werror=format-nonliteral -Werror=format-security: YES 
gnome-terminal-3.52.0/meson.build:356: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
gnome-terminal-3.52.0/meson.build:356: WARNING: Consider using the built-in warning_level option instead of using "-Wextra".
gnome-terminal-3.52.0/meson.build:357: WARNING: Consider using the built-in warning_level option instead of using "-Wall".
gnome-terminal-3.52.0/meson.build:357: WARNING: Consider using the built-in warning_level option instead of using "-Wextra".
Found pkg-config: YES (/usr/bin/pkg-config) 2.1.1
Dependency vte-2.91 found: NO found 0.74.2 but need: '>=0.76.0'
Found CMake: /usr/bin/cmake (3.29.0)
Run-time dependency vte-2.91 found: NO (tried cmake)

gnome-terminal-3.52.0/meson.build:361:16: ERROR: Dependency lookup for vte-2.91 with method 'pkgconfig' failed: Invalid version, need 'vte-2.91' ['>=0.76.0'] found '0.74.2'.

A full log can be found at /home/aahmad/.cache/yay/gnome-terminal-transparency/src/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: gnome-terminal-transparency-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
gnome-terminal-transparency - exit status 4

Checking the main AUR page, I see no information on the error:
https://aur.archlinux.org/packages/gnome-terminal-transparency

Anyone else seeing this issue? Thanks!

anon51566685 · 30 March 2024 18:12

No, because we don’t use stable branch and AUR.

Wollie · 30 March 2024 18:24

… with other words switch to unstable branch or wait until version 0.76.0 reaches your currently used branch.

Yochanan · 30 March 2024 19:04

By the way, we have gnome-terminal-fedora in our repos that includes transparency.

A4orce84 · 30 March 2024 19:28

What’s the advantage of the fedora version?

linuxghost · 31 March 2024 10:21

/usr/bin/vte-2.91 is owned by vte3 0.74.2-1
Must be a misconfiguration in the PKGBUILD.
Being no expert i sent a message to the AUR maintainer.

Teo · 31 March 2024 12:19

I marked the solution as such to stop pointless discussions about what is obvious. Please do not use AUR if you do not understand how it works (summary: is an arch thing and expects arch versions of libraries, which roughly equals to manjaro unstable branch)

linux-aarhus · 31 March 2024 13:06

Just some links for future readers

TL:DR

sudo pacman-mirrors -aS unstable
sudo pacman -Syu base-devel

A4orce84 · 31 March 2024 17:41

Thanks everyone for the comments and information!

@linux-aarhus - Thank you for the detailed links! I’ll go through everything and see what specific AUR packages I am using.

Question:
If I wanted to go back to the STABLE Manjaro branch, is the best approach to remove all my AUR (Custom Packages) packages to get things back to a ‘normal’ state?

Thanks everyone for your time and help, it is greatly appreciated!

Teo · 31 March 2024 17:47

You can leave them, but some of them might stop working (like this terminal which requires the newer version of the library will only work on unstable).
There are however many aur packages that work with stable, although this approach is not recomennded. They are usually just unpacked ubuntu versions, and ubuntu/debian usually uses older versions of the libraries.

And removing AUR does not revert you to stable branch. The way is

sudo pacman-mirrors -aS stable
sudo pacman -Syuu

A4orce84 · 31 March 2024 17:57

Correct, I know you actually need to switch to the stable branch via the pacman-mirrors command. I wanted to remove my AUR packages to prevent future issues similar to this terminal one by removing my AUR packages (as @linux-aarhus calls for) and basically do some “AUR cleanup.”

@Yochanan - Any quick steps on how to remove the “manjaro terminal” and use this Fedora version?

system · 2 April 2024 05:58

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.