Bug 1756604 (F31Cinnamonlivex86_64Oversize) - Fedora 31: Cinnamon live x86_64 image exceeds maximum size
Summary: Fedora 31: Cinnamon live x86_64 image exceeds maximum size
Keywords:
Status: CLOSED CANTFIX
Alias: F31Cinnamonlivex86_64Oversize
Product: Fedora
Classification: Fedora
Component: cinnamon
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-28 11:19 UTC by Fedora QA Tools SIG
Modified: 2022-01-18 00:19 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-06-12 06:21:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.