Bug 832690 – x11-libs/vte-0.64.2 with the 'vala' USE flag needs >dev-lang/vala:0.46

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description segmentation fault 2022-02-04 11:08:08 UTC]

Trying to upgrade vte, I got:

FAILED: bindings/vala/vte-2.91.vapi

Reproducible: Always

Steps to Reproduce:
1. emerge -1av x11-libs/vte
2.
3.
Actual Results:  
FAILED: bindings/vala/vte-2.91.vapi
/usr/bin/vapigen-0.46 --quiet --library=vte-2.91 --directory=/XXXXXX/portage/x11-libs/vte-0.64.2/work/vte-0.64.2-build/bindings/vala --pkg=gio-2.0 --pkg=glib-2.0 --pkg=pango --pkg=gtk+-3.0 --metadatadir=/XXXXXX/portage/x11-libs/vte-0.64.2/work/vte-0.64.2/bindings/vala /XXXXXX/portage/x11-libs/vte-0.64.2/work/vte-0.64.2-build/bindings/gir/Vte-2.91.gir
Vte-2.91.gir:7146.5-7146.19: error: unknown child element `docsection' in `namespace'
Vte-2.91.gir:7152.5-7152.29: error: unknown child element `docsection' in `namespace'
Vte-2.91.gir:7163.5-7163.27: error: unknown child element `docsection' in `namespace'
GModule-2.0.gir:377.5-377.19: error: unknown child element `docsection' in `namespace'

Expected Results:  
No error.

Reason
------

My vte had the 'vala' USE flag set and I only had versions
0.32.1, 0.36.15, 0.44.11 and 0.46.7, none of which obviously worked.
I updated the 0.46 slot of vala and retried vte. This time, it failed with

Vala compiler for the host machine: /usr/bin/valac-0.46 (valac 0.46.13)
...
FAILED: bindings/vala/vte-2.91.vapi

So I added vala:0.52 and retried vte. This time it said:

Vala compiler for the host machine: /usr/bin/valac-0.52 (valac 0.52.5)

- and it worked. Didn't try with vala:048 and vala:0.50.


Solution
--------

Add 

vala? ( >dev-lang/vala:0.46 )

to the dependencies in the ebuild. You might want to also check vala:0.48 and vala:0.50.

You may close this issue as resolved.

Some info:

Portage 3.0.28 (python 3.8.12-final-0, default/linux/amd64/17.1/hardened, gcc-11.2.0, glibc-2.30-r8, 5.4.168-gentoo x86_64)
=================================================================
System uname: Linux-5.4.168-gentoo-x86_64-Intel-R-_Core-TM-_i7-6700HQ_CPU_@_2.60GHz-with-glibc2.2.5


Timestamp of repository gentoo: Sat, 22 Jan 2022 


sh bash 5.1_p8
ld GNU ld (Gentoo 2.37_p1 p0) 2.37
app-misc/pax-utils:        1.3.3::gentoo
app-shells/bash:           5.1_p8::gentoo
dev-java/java-config:      2.3.1::gentoo
dev-lang/perl:             5.34.0-r6::gentoo
dev-lang/python:           2.7.18_p13::gentoo, 3.6.10-r2::gentoo, 3.7.7-r2::gentoo, 3.8.12_p1-r1::gentoo, 3.9.9-r1::gentoo, 3.10.0_p1-r1::gentoo
dev-lang/rust:             1.53.0::gentoo
dev-lang/rust-bin:         1.53.0::gentoo
dev-util/cmake:            3.21.4::gentoo
dev-util/meson:            0.60.3::gentoo
sys-apps/baselayout:       2.7-r3::gentoo
sys-apps/openrc:           0.42.1::gentoo
sys-apps/sandbox:          2.25::gentoo
sys-devel/autoconf:        2.13-r1::gentoo, 2.69-r4::gentoo
sys-devel/automake:        1.11.6-r3::gentoo, 1.12.6::gentoo, 1.13.4-r2::gentoo, 1.14.1::gentoo, 1.15.1-r2::gentoo, 1.16.4::gentoo
sys-devel/binutils:        2.33.1-r1::gentoo, 2.37_p1::gentoo
sys-devel/binutils-config: 5.4::gentoo
sys-devel/clang:           7.0.0::gentoo, 8.0.1::gentoo, 9.0.1::gentoo, 10.0.0::gentoo, 12.0.1::gentoo, 13.0.0::gentoo
sys-devel/gcc:             7.5.0::gentoo, 8.3.0-r1::gentoo, 8.4.0::gentoo, 9.3.0::gentoo, 11.2.0::gentoo
sys-devel/gcc-config:      2.5-r1::gentoo
sys-devel/libtool:         2.4.6-r6::gentoo
sys-devel/lld:             13.0.0::gentoo
sys-devel/llvm:            7.0.0-r1::gentoo, 8.0.1::gentoo, 9.0.1::gentoo, 10.0.0::gentoo, 12.0.1::gentoo, 13.0.0::gentoo
sys-devel/make:            4.3::gentoo
sys-kernel/linux-headers:  5.4-r1::gentoo (virtual/os-headers)
sys-libs/glibc:            2.30-r8::gentoo

[Comment 1 Matt Turner 2022-02-04 23:17:04 UTC]

Thanks. I really don't know how to check what the minimum required vala version is, except by just manually testing everything :(

[Comment 2 segmentation fault 2022-02-07 18:12:10 UTC]

(In reply to Matt Turner from comment #1)
> Thanks. 

You're welcome. :-)

>I really don't know how to check what the minimum required vala
> version is, except by just manually testing everything :(

That's why I thought I'd report it. In the old times it was upstream (the developers) that would say "this software needs...list of *minimum* versions necessary here...to work". It seems this good habit is lost nowadays...

[Comment 3 Larry the Git Cow 2022-02-07 19:03:29 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=35d64791f372f87fb4bb302bc2f01b01ea8280e5

commit 35d64791f372f87fb4bb302bc2f01b01ea8280e5
Author:     Matt Turner <[e-mail]>
AuthorDate: 2022-02-07 18:57:02 +0000
Commit:     Matt Turner <[e-mail]>
CommitDate: 2022-02-07 19:03:19 +0000

    x11-libs/vte: Raise required vala version
    
    Closes: https://bugs.gentoo.org/832690
    Signed-off-by: Matt Turner <[e-mail]>

 x11-libs/vte/vte-0.64.2.ebuild | 2 +-
 x11-libs/vte/vte-0.66.2.ebuild | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)