Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: New release PakType-Release-2017-06-25.zip https://sourceforge.net/projects/paktype/files/PakType-Release-2017-06-25.zip/download Version-Release number of selected component (if applicable): paktype-naskh-basic-fonts-4.1-8.fc27.noarch How reproducible: everytime Steps to Reproduce: 1. Check version in Fedora 2. Check in upstream https://sourceforge.net/projects/paktype/files/PakType-Release-2017-06-25.zip/download 3. Actual results: downstream is not updated. Expected results: Should be updated to latest version Additional info: Please do this for other paktype-* as well.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Still the same situation, need upgrade to latest upstream.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
PakType font package previously had individual(paktype-ajrak, paktype-naskh-basic, paktype-naqsh, paktype-tehreer) font releases, so paktype-fonts(https://src.fedoraproject.org/rpms/paktype-fonts) was split into https://src.fedoraproject.org/rpms/paktype-tehreer-fonts https://src.fedoraproject.org/rpms/paktype-ajrak-fonts https://src.fedoraproject.org/rpms/paktype-naqsh-fonts https://src.fedoraproject.org/rpms/paktype-naskh-basic-fonts But now the latest release has single release tar ball https://sourceforge.net/projects/paktype/files Are we planning to sub package paktype-fonts or continue current state?
If upstream does not want to publish the font files separately anymore yes that will require subpackaging. But, in that case, I would avise waiting for FPC to be done on https://pagure.io/packaging-committee/pull-request/934 as that will significantly simplify the font subpackaging mecanisms available in Fedora (of course FPC is slooooooow; feel free to ping them in pagure)
+1 with what nim says. * Unfortunately upstream has remained unpredictable with release pattern. Good to ask once upstream about their plan from release perspective. * If they are going to follow same release pattern in future, good to go as per guidelines, infact this is good refresh for paktype after sometime. Thanks Vishal for taking this up.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.