Bug 2352686 (F42Scientific_KDEliveaarch64Oversize) - Fedora 42: Scientific_KDE live aarch64 image exceeds maximum size
Summary: Fedora 42: Scientific_KDE live aarch64 image exceeds maximum size
Keywords:
Status: ASSIGNED
Alias: F42Scientific_KDEliveaarch64Oversize
Product: Fedora
Classification: Fedora
Component: distribution
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aoife Moloney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FedoraOversizeTracker
TreeView+ depends on / blocked
 
Reported: 2025-03-15 09:48 UTC by Fedora QA Tools SIG
Modified: 2025-04-09 15:13 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fedora QA Tools SIG 2025-03-15 09:48:22 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250315.n.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250315.n.0.aarch64.iso from compose Fedora-42-20250315.n.0 is 5068132352 bytes, exceeding the maximum size 5000000000. Canonical maximum sizes can be found at https://docs.fedoraproject.org/en-US/releases/f42/spins/ and https://docs.fedoraproject.org/en-US/releases/f42/blocking/ . 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 Fedora QA Tools SIG 2025-03-19 17:59:00 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250319.n.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250319.n.0.aarch64.iso from compose Fedora-42-20250319.n.0 is 5320837120 bytes, exceeding the maximum size 5000000000.

Comment 2 Fedora QA Tools SIG 2025-03-23 18:30:41 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250323.n.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250323.n.0.aarch64.iso from compose Fedora-42-20250323.n.0 is 5075453952 bytes, exceeding the maximum size 5000000000.

Comment 3 Fedora QA Tools SIG 2025-03-26 09:49:08 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250326.n.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250326.n.0.aarch64.iso from compose Fedora-42-20250326.n.0 is 5075390464 bytes, exceeding the maximum size 5000000000.

Comment 4 Fedora QA Tools SIG 2025-03-29 09:52:10 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250329.n.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250329.n.0.aarch64.iso from compose Fedora-42-20250329.n.0 is 5043214336 bytes, exceeding the maximum size 5000000000.

Comment 5 Fedora QA Tools SIG 2025-04-02 10:21:15 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250402.n.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250402.n.0.aarch64.iso from compose Fedora-42-20250402.n.0 is 5080240128 bytes, exceeding the maximum size 5000000000.

Comment 6 Fedora QA Tools SIG 2025-04-05 19:38:57 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250405.n.1/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-20250405.n.1.aarch64.iso from compose Fedora-42-20250405.n.1 is 5080322048 bytes, exceeding the maximum size 5000000000.

Comment 7 Fedora QA Tools SIG 2025-04-09 15:13:10 UTC
Scientific_KDE live aarch64 image https://kojipkgs.fedoraproject.org/compose/42/Fedora-42-20250409.0/compose/Labs/aarch64/iso/Fedora-Scientific_KDE-Live-42-1.1.aarch64.iso from compose Fedora-42-20250409.0 is 5079631872 bytes, exceeding the maximum size 5000000000.


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