Bug 910464

Summary:	app-editors/gedit-44.2: build faliure missing gtk_source_style_scheme_manager_get_scheme_ids
Product:	Gentoo Linux	Reporter:	Jay Faulkner <jay>
Component:	Current packages	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED OBSOLETE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	home.jvf.cc_~jay_gedit-44.2-accept-keywords.txt home.jvf.cc_~jay_gedit-44.2-meson-log.txt home.jvf.cc_~jay_gedit-44.2-build-log.txt

Description Jay Faulkner 2023-07-17 18:47:17 UTC

Build failure building app-editors/gedit-44.2 against a system that's running mostly unstable (~amd64) gnome packages.

Build log: https://home.jvf.cc/~jay/gedit-44.2-build-log.txt
Meson log: https://home.jvf.cc/~jay/gedit-44.2-meson-log.txt
Output of `cat /etc/portage/package.accept_keywords/* | sort -u` (please do not judge me for my use of *): https://home.jvf.cc/~jay/gedit-44.2-accept-keywords.txt

Reproducible: Always

Comment 1 Jay Faulkner 2023-07-17 18:48:13 UTC

gedit-preferences-dialog.c:(.text+0x424): undefined reference to `gtk_source_style_scheme_manager_get_scheme_ids' collect2: error: ld returned 1 exit status

seems to be the meaningful line in the build log

Comment 2 Jay Faulkner 2023-07-17 18:56:24 UTC

Created attachment 865673 [details]
home.jvf.cc_~jay_gedit-44.2-accept-keywords.txt

Comment 3 Jay Faulkner 2023-07-17 18:56:53 UTC

Created attachment 865674 [details]
home.jvf.cc_~jay_gedit-44.2-meson-log.txt

Comment 4 Jay Faulkner 2023-07-17 18:57:34 UTC

Created attachment 865675 [details]
home.jvf.cc_~jay_gedit-44.2-build-log.txt

Comment 5 Jay Faulkner 2023-07-17 18:58:11 UTC

I will note: this is a weird config; I am ~amd64 keywording gedit and expect the bug to disappear. I am filing this bug as a courtesy to document the behavior; please do not prioritize it for my sake :D.

Comment 6 Pacho Ramos gentoo-dev

2023-10-08 11:34:57 UTC

Are you still hitting this? I cannot reproduce it

Comment 7 Jay Faulkner 2023-10-09 17:15:56 UTC

No; like I said it was likely a transient issue running amd64 gedit against ~amd64 (otherwise) gnome. Likely just a wrong bottom version blocker on a dep; but since it's 3 months old I'd imagine it's phased out.