June 2022

June 6, 2022

Week 22 (May 31st - June 6th) #

• Packit shows basic information about allowlisting in the status description when your namespace is not allowed. (packit-service#1533)

Week 23 (June 7th - June 13th) #

• The creation of Bodhi updates should not time out anymore, because we no longer get the latest build of a package via Bodhi. (packit#1612)
• We have fixed a regression where string values for the targets and dist_git_branches configuration keys were not accepted. (packit#1608)
• We improved the reporting for the test job if we are not able to find any FMF metadata and the skip_build option is enabled. (packit-service#1539)

Week 24 (June 14th - June 21st) #

• Git ref name that Packit works with during propose-downstream is now made more obvious in logs. (packit#1626)
• Packit now correctly handles creation of custom archives in root while a specfile is in a subdirectory. (packit#1622)
• There is a new check for git projects that are allowed to use a custom Copr project. There will be a better integration in the form of a new config field in Copr settings that Packit can use. In the meantime, the mapping is defined and maintained by the Packit team. Let us know if you need a project to be allowed. (packit-service#1556)
• A link to Copr build logs was updated: it now points to a place where logs are available once a build starts. (packit-service#1554)

Week 25 (June 21st - June 27th) #

• Packit Bash completion file is no longer needlessly executable. (packit#1634)
• Packit now works with Bodhi 5 and Bodhi 6 authentication mechanism. (packit#1629)
• Git ref name that Packit works with during propose-downstream is now made more obvious in logs. (packit#1626)
• We have fixed the incorrect displaying of propose downstream results in our dashboard. (packit-service#1553)