Description of problem: Entered a wrong BZR URL in Git for a BZR branch Version-Release number of selected component: git-remote-bzr-0.2-4.fc23 Additional info: reporter: libreport-2.6.4 cmdline: /usr/bin/python2 /usr/bin/git-remote-bzr 4.0.x lp:kicad/kicad/4.0 dso_list: bzr-2.6.0-12.fc23.x86_64 executable: /usr/bin/git-remote-bzr kernel: 4.3.5-300.fc23.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: controldir.py:1155:find_format:NotBranchError: Not a branch: "http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/kicad/4.0/". Traceback (most recent call last): File "/usr/bin/git-remote-bzr", line 952, in <module> sys.exit(main(sys.argv)) 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 689, in open _unsupported=_unsupported) File "/usr/lib64/python2.7/site-packages/bzrlib/controldir.py", line 718, in open_from_transport find_format, transport, redirected) File "/usr/lib64/python2.7/site-packages/bzrlib/transport/__init__.py", line 1719, in do_catching_redirections return action(transport) File "/usr/lib64/python2.7/site-packages/bzrlib/controldir.py", line 706, in find_format probers=probers) File "/usr/lib64/python2.7/site-packages/bzrlib/controldir.py", line 1155, in find_format raise errors.NotBranchError(path=transport.base) NotBranchError: Not a branch: "http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/kicad/4.0/". Local variables in innermost frame: prober_kls: <class 'bzrlib.bzrdir.BzrProber'> probers: [<class 'bzrlib.bzrdir.RemoteBzrProber'>, <class 'bzrlib.bzrdir.BzrProber'>] transport: <bzrlib.transport.http._urllib.HttpTransport_urllib url=http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/kicad/4.0/> prober: <bzrlib.bzrdir.BzrProber object at 0x7f8a0cebe790> klass: <class 'bzrlib.controldir.ControlDirFormat'>
Created attachment 1134648 [details] File: backtrace
Created attachment 1134649 [details] File: environ
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' of '23'. 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.