Learn more about these different git repos.
Other Git URLs
In getBuildConfig tag.extra values are effectively inherited. However, there is no way for a tag to unset a value that an ancestor has set. You can set it to None, but that is not the same as unset.
getBuildConfig
None
This matters because we have code that distinguishes when values are unset. One case is the code that checks for mock.new_chroot. It is only when this value is unset that neither --old-chroot nor --new-chroot is passed. Legacy builders with an older mock might not be able to handle these options.
mock.new_chroot
There could easily be other examples.
Metadata Update from @tkopecek: - Custom field Size adjusted to None - Issue set to the milestone: 1.23
PR #2495
Metadata Update from @tkopecek: - Issue tagged with: testing-ready
Metadata Update from @jcupova: - Issue tagged with: testing-done
Commit 5e8ed0c fixes this issue
Commit 08494de fixes this issue
Commit 0bbb817 fixes this issue
Commit 0b5638c relates to this ticket
Login to comment on this ticket.