Bug 1729924

Summary:	depend on latest guile
Product:	[Fedora] Fedora	Reporter:	Nikos Mavrogiannopoulos <nmavrogi>
Component:	autogen	Assignee:	Tomas Korbar <tkorbar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	debarshir, green, mlichvar, tkorbar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-16 11:57:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1852703, 1852704, 1852706, 1852707, 1852708, 1852709, 1852711, 1852712
Bug Blocks:

Description Nikos Mavrogiannopoulos 2019-07-15 10:38:51 UTC

Description of problem:
It seems that fedora ships guile22 (which is guile 2.2) and guile (which is 2.0). The guile22 component is available on every system by default (dependency of make), while guile20 is brought by autogen.

It would be great for fedora to have a single version of guile, and autogen could help towards that by depending on guile22 instead of guile.

Comment 1 Tomas Korbar 2019-07-23 09:14:44 UTC

Hi Nikos,
It surely is a good idea. I built autogen with guile22, ran simple test and it seems working. I will need to review all incompatible changes done between guile 2.0 and 2.2.
Packages which require autogen during build will have to be rebuild with new version to ensure we do not break anything, that means:
anjuta
arm-none-eabi-gcc-cs
ebtables
gnutls
grub2
insight
iptables
ntp

Packages which require autogen during runtime will need to be tested to ensure that their way of using autogen remains working.
autogen-libopts - i think this is tested during build because autoopts are using libopts and autoopts has its own tests.
anjuta

I will add this to my TODO list.

Comment 2 Ben Cotton 2019-08-13 16:53:10 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 3 Ben Cotton 2019-08-13 18:57:39 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 4 Ben Cotton 2020-08-11 13:06:30 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 5 Nikos Mavrogiannopoulos 2020-11-16 11:57:23 UTC

This seems to be already addressed.