On Monday, October 3, 2016 8:53:41 AM CEST Pavel Raiskup wrote: > On Monday, October 3, 2016 8:12:50 AM CEST Pavel Raiskup wrote: > > On Thursday, September 22, 2016 12:45:32 PM CEST Pavel Raiskup wrote: > > > Thanks a lot for this discussion. I'll go (probably) the hacky > > > ExclusiveArch way, just because I want to give it a try. Once this > > > becomes too tiring (because the package has non-trivial amount of > > > run-time-only dependencies), I'll talk to releng team. > > > > The approach is here: > > http://pkgs.fedoraproject.org/cgit/rpms/vim-syntastic.git/commit/?id=8f4bf0f6e30fa048bc8 > > > > One issue happened to me during the first build attempt -- aarch64 builder > > was used while aarch64 was _not_ in all _sub_packages' ExclusiveArch: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=15918394 > > > > The second attempt on x86_64 has been successful: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=15918430 > > > > Is this related to? > > https://pagure.io/koji/issue/19 > > > > What is the work-around? Do I have to specify 'BuildArch: noarch' for all > > subpackages (would that help)? Do I have to try re-building until I get the > > right machine? > > Even more interesting, %arm is not on ExclusiveArch list for > 'vim-syntastic-d' package, while the build on arm machine succeeded: > http://koji.fedoraproject.org/koji/taskinfo?taskID=15919447 > > What is the reason to fail on aarch64 then? Heh, here it comes :) | vim-syntastic has broken dependencies in the rawhide tree: | On aarch64: | vim-syntastic-lisp-3.7.0-8.fc26.noarch requires clisp | On aarch64: | vim-syntastic-d-3.7.0-8.fc26.noarch requires ldc | On armhfp: | vim-syntastic-d-3.7.0-8.fc26.noarch requires ldc | On aarch64: | vim-syntastic-cs-3.7.0-8.fc26.noarch requires mono-core | Please resolve this as soon as possible. Seems like the ExclusiveArch for subset of sub-packages did not help at all. Pavel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
