Bug 2311817

Summary:	xsane-gimp fails to install on Fedora 41
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	xsane	Assignee:	Nils Philippsen <nphilipp>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	41	CC:	jridky, nphilipp, zdohnal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-09-11 21:13:18 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:
Bug Blocks:	2247866

Description Adam Williamson 2024-09-11 21:12:22 UTC

The current stable xsane-gimp for F41 does not install because it's built against the old gimp sonames:

2024-09-10 23:56:34,389 INFO pylorax:   - nothing provides libgimp-2.0.so.0()(64bit) needed by xsane-gimp-0.999-52.fc41.x86_64 from anaconda
2024-09-10 23:56:34,389 INFO pylorax:   - nothing provides libgimpbase-2.0.so.0()(64bit) needed by xsane-gimp-0.999-52.fc41.x86_64 from anaconda
2024-09-10 23:56:34,389 INFO pylorax:   - nothing provides libgimp-2.0.so.0()(64bit) needed by xsane-gimp-0.999-52.fc41.x86_64 from koji-override-0
2024-09-10 23:56:34,389 INFO pylorax:   - nothing provides libgimpbase-2.0.so.0()(64bit) needed by xsane-gimp-0.999-52.fc41.x86_64 from koji-override-0

this is one of two issues preventing the design suite spin from composing ATM.

https://bodhi.fedoraproject.org/updates/FEDORA-2024-55bbab058b would fix this, but is stuck in the freeze. So I'm filing this and proposing it as an FE to let us get a fix in if we have to do another compose.

Comment 1 Adam Williamson 2024-09-11 21:13:18 UTC

sigh, never mind, we already have https://bugzilla.redhat.com/show_bug.cgi?id=2307975 . proposing that as FE instead.

*** This bug has been marked as a duplicate of bug 2307975 ***