Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. build ARM based Fedora 17 (such as on a Raspberry Pi device) 2. yum install syslinux 3. yum list repo Actual results: # yum install syslinux Loaded plugins: langpacks, presto, refresh-packagekit No package syslinux available. Error: Nothing to do # yum repolist Loaded plugins: langpacks, presto, refresh-packagekit repo id repo name status fedora/1 Fedora 17 - arm 19,992 rasp-pi rasp-pi 17 - arm 36 rasp-pi-debuginfo rasp-pi-debuginfo 17 - arm 6 rasp-pi-source rasp-pi-source 17 - arm 0 updates/17/arm Fedora 17 - arm - Updates 7,455 repolist: 27,489 Expected results: Installation of syslinux package. Additional info: # uname -a # uname -a Linux <removed> 3.2.27+ #307 PREEMPT Mon Nov 26 23:22:29 GMT 2012 armv6l armv6l armv6l GNU/Linux # yum update Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update
Saw reference to bug 581650, related yes, but different issue. Syslinux should be in the repo is key to a number of features, including PXE linux support. Makes no sense to be missing from the distribution repo. Unless for some technical reason? But could not find any discussion on why syslinux would be missing from the Fedora 17 ARM distribution.
Not sure what component this is should be, but I know it should not be a 389 component. Can someone please figure out which component this should be and reassign it?
syslinux isn't available on arm because it's only built for i386/x86_64. The syslinux boot loaders are only usable on x86 I imagine. But the syslinux-tftpboot subpackage (at least) could be noarch, since the images are not intended to be executed but rather served up to other systems. I guess that is what the bug reporter has in mind.
Is there a possibility of adding the syslinux package to F21? Files like pxelinux.0 aren't necesarily platform dependant, and not having this package means it's not possibble (from an available packages perspective) to create a network bootserver on ARM.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This is not a packaging issue, as the syslinux package already produces syslinux-tftpboot, which is a noarch subpackage. The problem here is how koji deals with noarch packages. Koji will only import noarch packages if the corresponding srpm generates no archfull subpackage, which is not the case of syslinux. Reassigning to the "distribution" component to see if a koji trick is possible to workaround this.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Now that secondary arch kojis are gone (going?) away and all arches are built in the main koji, this is no longer an issue, right?
syslinux has ExclusiveArch entries to make sure it is only available to x86 arches. With that in place it will not show up elsewhere at all. if the ExclusiveArch line was removed from the tftpboot package it should show up on all arches as being an option, which would enable all arches to serve as tftpboot servers for x86. of course you can easily work around it but would not get updates.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.