The changes mentioned in https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/DTEVN7W5K2U6YWGDDQKJRWSCUTOEI7YY/ broke mbs-build local: 2017-09-25 23:29:47,857 - Thread-2 - module_build_service - WARNING - Exception RuntimeError("Failed on ['git', 'ls-remote', 'git://pkgs.fedoraproject.org/rpms/python-jinja2', 'master'], retcode 128, out '', err 'fatal: unable to connect to pkgs.fedoraproject.org:\npkgs.fedoraproject.org[0: 209.132.181.4]: errno=No route to host\n\n'",) raised from <function _run at 0x7f3392fa1a28>. Retry in 30s 2017-09-25 23:29:47,858 - Thread-6 - module_build_service - WARNING - fatal: unable to connect to pkgs.fedoraproject.org: pkgs.fedoraproject.org[0: 209.132.181.4]: errno=No route to host
Can you not use https://src.fedoraproject.org/ ?
git:// is unencrypted and subject to MITM attacks, so we don't want to use it over external internet if we can at all avoid it.
yes, that should work. But a new version of module-build-service with these changes needs to be built and this is the tracker for that.
Ah, fair. Is this blocking you? we could allow a specific ip, or just re-allow git:// until you get it fixed if needed.
I can change my config, no problem.
Arg!
See #714.
So, in this case we should be doing git ls-remote https://src.fedoraproject.org/rpms/python-jinja2 master?
git ls-remote https://src.fedoraproject.org/rpms/python-jinja2 master
yes, that works for me. Please note that fedpkg needs to be fixed, too. mbs-build local runs for example: DEBUG: SCM checkout command: sh -c 'fedpkg clone --anonymous python-jinja2''; git -C python-jinja2 checkout b33ff757001244a02dd8c82c7495a41db206fef3'
The ''fedpkg clone --anonymous' part will fail now for the very same reasons, see https://pagure.io/fedpkg/issue/145
This was inherently fixed by the mbs-build port to rpkg. Will close this now.
mbs-build
Metadata Update from @mprahl: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.