Bug 1756604 (F31Cinnamonlivex86_64Oversize)

Summary:	Fedora 31: Cinnamon live x86_64 image exceeds maximum size
Product:	[Fedora] Fedora	Reporter:	Fedora QA Tools SIG <qa-tools-sig>
Component:	cinnamon	Assignee:	leigh scott <leigh123linux>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	alt-gtk-de-sig, awilliam, jcpunk, kevin, leigh123linux
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-06-12 06:21:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Fedora QA Tools SIG 2019-09-28 11:19:34 UTC

Cinnamon live x86_64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-31-20190928.n.0/compose/Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-31-20190928.n.0.iso from compose Fedora-31-20190928.n.0 is 2201616384 bytes, exceeding the maximum size 2000000000.Canonical maximum sizes can be found at https://fedoraproject.org/wiki/Releases/31/Spins and https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking . This check is run by the 'relval' tool, which has its own list of maximum sizes derived from those pages. If the maximum size used for this comparison is wrong, please add a comment and file a bug against relval at https://pagure.io/fedora-qa/relval/issues and it will be corrected. If you believe the canonical maximum size for an image should be changed, please follow the appropriate process before filing a relval bug.

Comment 1 Adam Williamson 2019-09-30 15:27:36 UTC

Re-assigning to a more appropriate component.

Comment 2 Fedora Admin user for bugzilla script actions 2020-06-12 02:45:52 UTC

This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 3 Adam Williamson 2020-06-12 06:21:51 UTC

well, we're not gonna do anything about this now.