When doing arch emulation, dnf gets confused when $releasever is set by not $basearch. This causes some rather ugly messages to be emitted that have no obvious targets until you dig down into the code.
1 new commit added
kojid: permit forcing the target arch within mock per tag
2 new commits added
kojid: permit forcing releasever within mock per tag
:thumbsup:
Instead of string "true/false" we should use same logic as for the other booleans, so 0/1 True/False with bool() conversion.
bool()
Just pushed an updated patch, is that better?
Metadata Update from @tkopecek: - Pull-request tagged with: testing-ready
Added tracking issue #3304
Option 'mock.forcearch' is not present when mock-config is called with option --task. With options --tag and --arch all looks good. Please look at it. Thanks
@mfilip I've added fix in #3358, closing this one.
Pull-Request has been closed by tkopecek
When doing arch emulation, dnf gets confused when $releasever is set by not $basearch. This causes some rather ugly messages to be emitted that have no obvious targets until you dig down into the code.