There is a bug against the Federa Server Edition armhfp installation iso
see https://bugzilla.redhat.com/show_bug.cgi?id=1963007
The F35 build exceeds the current max size of 700 mb (by about 20 mb)
There are obviously 2 options:
(a) reduce the size by removing some packages (b) Determine a new max size
According to my recent experimentation with aarch64 server iso the arm build is a splendid materialization of the current concept of Fedora Server Edition. Therefore, I'm hesitant to remove packages. I would also have no idea which ones could be dispensable. Therefore, from a user/admin perspective, I would opt to set 750 as the new maximum size and proceed with the current build.
Unfortunately, I am not (yet) familiar with the ARM architecture and have no idea what technical or practical problems or side effects might arise from that.
Therefore I would like to ask the Arm experts here for a recommendation on how to proceed.
I believe the 700 MiB limit is imposed by the typical 80-minute CD-R media. If it’s increased even a little bit, it may as well be raised to 4.7 GB since DVD media would now be required.
On Fri, Aug 20, 2021, at 4:27 PM, Peter Boy wrote:
There is a bug against the Federa Server Edition armhfp installation iso
see https://bugzilla.redhat.com/show_bug.cgi?id=1963007
The F35 build exceeds the current max size of 700 mb (by about 20 mb)
There are obviously 2 options:
(a) reduce the size by removing some packages (b) Determine a new max size
According to my recent experimentation with aarch64 server iso the arm build is a splendid materialization of the current concept of Fedora Server Edition. Therefore, I'm hesitant to remove packages. I would also have no idea which ones could be dispensable. Therefore, from a user/admin perspective, I would opt to set 750 as the new maximum size and proceed with the current build.
Unfortunately, I am not (yet) familiar with the ARM architecture and have no idea what technical or practical problems or side effects might arise from that.
Therefore I would like to ask the Arm experts here for a recommendation on how to proceed.
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Am 20.08.2021 um 23:03 schrieb Ben Beasley code@musicinmybrain.net:
I believe the 700 MiB limit is imposed by the typical 80-minute CD-R media. If it’s increased even a little bit, it may as well be raised to 4.7 GB since DVD media would now be required.
Thanks for the info. I take it as there are no known arm-32 specific technical reasons for the existing limit.
Thanks Peter
On Fri, Aug 20, 2021, at 4:27 PM, Peter Boy wrote:
There is a bug against the Federa Server Edition armhfp installation iso
see https://bugzilla.redhat.com/show_bug.cgi?id=1963007
The F35 build exceeds the current max size of 700 mb (by about 20 mb)
There are obviously 2 options:
(a) reduce the size by removing some packages (b) Determine a new max size
According to my recent experimentation with aarch64 server iso the arm build is a splendid materialization of the current concept of Fedora Server Edition. Therefore, I'm hesitant to remove packages. I would also have no idea which ones could be dispensable. Therefore, from a user/admin perspective, I would opt to set 750 as the new maximum size and proceed with the current build.
Unfortunately, I am not (yet) familiar with the ARM architecture and have no idea what technical or practical problems or side effects might arise from that.
Therefore I would like to ask the Arm experts here for a recommendation on how to proceed.
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Fri, Aug 20, 2021 at 1:28 PM Peter Boy pboy@uni-bremen.de wrote:
There is a bug against the Federa Server Edition armhfp installation iso
see https://bugzilla.redhat.com/show_bug.cgi?id=1963007
The F35 build exceeds the current max size of 700 mb (by about 20 mb)
There are obviously 2 options:
(a) reduce the size by removing some packages (b) Determine a new max size
According to my recent experimentation with aarch64 server iso the arm build is a splendid materialization of the current concept of Fedora Server Edition. Therefore, I'm hesitant to remove packages. I would also have no idea which ones could be dispensable. Therefore, from a user/admin perspective, I would opt to set 750 as the new maximum size and proceed with the current build.
Unfortunately, I am not (yet) familiar with the ARM architecture and have no idea what technical or practical problems or side effects might arise from that.
Therefore I would like to ask the Arm experts here for a recommendation on how to proceed.
In the past, there was some large kernel modules that were not needed that were removed. (the biggest module actually had a whole kernel built in it. It was literally as big as the rest of the kernel)
Usually it just requires taking the last build that is small enough, and compare it with the build that is bigger. And then you hope that it's something obvious like a massive kernel module that snuck in.
Troy
Am 20.08.2021 um 23:07 schrieb Troy Dawson tdawson@redhat.com:
In the past, there was some large kernel modules that were not needed that were removed. (the biggest module actually had a whole kernel built in it. It was literally as big as the rest of the kernel)
Usually it just requires taking the last build that is small enough, and compare it with the build that is bigger. And then you hope that it's something obvious like a massive kernel module that snuck in.
Troy
Good to know. I’ll pass the info
Thanks Peter
On Fri, Aug 20, 2021 at 1:28 PM Peter Boy pboy@uni-bremen.de wrote: There is a bug against the Federa Server Edition armhfp installation iso
...
Therefore I would like to ask the Arm experts here for a recommendation on how to proceed.