Red Hat Bugzilla – Bug 1316285
[abrt] git-remote-bzr: urlutils.py:875:from_string:InvalidURL: Invalid url supplied to transport: "invalid port number kicad in url:
Last modified: 2016-12-20 14:21:47 EST
Description of problem:
Entered a wrong BZR URL in Git
Version-Release number of selected component:
cmdline: /usr/bin/python2 /usr/bin/git-remote-bzr 4.0.x bzr://lp:kicad/4.0
runlevel: N 5
urlutils.py:875:from_string:InvalidURL: Invalid url supplied to transport: "invalid port number kicad in url:
Traceback (most recent call last):
File "/usr/bin/git-remote-bzr", line 952, in <module>
File "/usr/bin/git-remote-bzr", line 926, in main
repo = get_repo(url, alias)
File "/usr/bin/git-remote-bzr", line 806, in get_repo
origin = bzrlib.bzrdir.BzrDir.open(url, possible_transports=transports)
File "/usr/lib64/python2.7/site-packages/bzrlib/controldir.py", line 687, in open
t = _mod_transport.get_transport(base, possible_transports)
File "/usr/lib64/python2.7/site-packages/bzrlib/transport/__init__.py", line 1680, in get_transport
return get_transport_from_url(location_to_url(base), possible_transports)
File "/usr/lib64/python2.7/site-packages/bzrlib/transport/__init__.py", line 1655, in get_transport_from_url
transport, last_err = _try_transport_factories(url, factory_list)
File "/usr/lib64/python2.7/site-packages/bzrlib/transport/__init__.py", line 1687, in _try_transport_factories
return factory.get_obj()(base), None
File "/usr/lib64/python2.7/site-packages/bzrlib/transport/remote.py", line 95, in __init__
File "/usr/lib64/python2.7/site-packages/bzrlib/transport/__init__.py", line 1362, in __init__
self._parsed_url = self._split_url(base)
File "/usr/lib64/python2.7/site-packages/bzrlib/transport/__init__.py", line 1417, in _split_url
File "/usr/lib64/python2.7/site-packages/bzrlib/urlutils.py", line 875, in from_string
InvalidURL: Invalid url supplied to transport: "invalid port number kicad in url:
Local variables in innermost frame:
cls: <class 'bzrlib.urlutils.URL'>
Created attachment 1134646 [details]
Created attachment 1134647 [details]
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.