Learn more about these different git repos.
Other Git URLs
change introduced in #1595 is effectively blocking such builds. It would be easier, if mock could have some "force" option to print warning and continue instead of waiting for input. If it is not possible, let's revert this patch.
@praiskup Do you think, it makes sense to file such request to mock, or is it something you don't want to do?
The dnf_warning = True was always blocking, I think.
Do you want some very very "verbose" warning? In (not yet released) pull request [1] we added change which makes dnf_warning = True blocking both on yum systems (when building against dnf chroot) and on dnf systems (when building against yum systems). Which means it is going to block in even more situations.
If user specifies dnf_warning = False, then we throw INFO message like INFO: Using 'dnf' instead of 'yum'.
dnf_warning = False
INFO: Using 'dnf' instead of 'yum'
If you never want to be blocked in Koji, I'd much rather make the INFO message more verbose than changing the old semantics. But it depends what did you want to achieve by dnf_warning = True initially.
dnf_warning = True
[1] https://github.com/rpm-software-management/mock/pull/417
I think, that it is easier for us to just revert that commit and only copy that INFO message. Original intent was to show user, that he has probably wrongly configured tags for given product. But INFO message is doing almost the same.
Metadata Update from @tkopecek: - Custom field Size adjusted to None
removed in #2353
Metadata Update from @tkopecek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.