Description of problem: It was found during bug #1839870, review of dependent mk-files, that it does not contain license text. While bmake sources contain original mk-files, it still does not contain any license text. Version-Release number of selected component (if applicable): bmake-20200524-1.fc33 How reproducible: always Steps to Reproduce: 1. fedpkg clone bmake 2. cd bmake && fedpkg prep 3. cd bmake && ls COPY* LICENS* Actual results: ls: nelze přistoupit k 'COPY*': Adresář nebo soubor neexistuje ls: nelze přistoupit k 'LICENS*': Adresář nebo soubor neexistuje p Expected results: At least one exists Additional info: Upstream was notified.
FEDORA-2020-4b58dae6d9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4b58dae6d9
FEDORA-2020-07ff7357dd has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-07ff7357dd
FEDORA-2020-4b58dae6d9 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4b58dae6d9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4b58dae6d9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-07ff7357dd has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-07ff7357dd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-07ff7357dd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-07ff7357dd has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4b58dae6d9 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.