Version-Release number of selected component: git-bz-0-0.2.20130906git5ae7a50.fc21 Additional info: reporter: libreport-2.3.0 cmdline: /usr/bin/python /usr/bin/git-bz attach 747dc25 730499 executable: /usr/bin/git-bz kernel: 3.17.0-301.fc21.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: git-bz:172:git_run:CalledProcessError: Command 'git rev-list --pretty=format:%s 730499' returned non-zero exit status 128 Traceback (most recent call last): File "/usr/bin/git-bz", line 2434, in <module> do_attach(*args) File "/usr/bin/git-bz", line 1827, in do_attach commits = get_commits(commit_or_revision_range) File "/usr/bin/git-bz", line 231, in get_commits commits = rev_list_commits(commit_or_revision_range) File "/usr/bin/git-bz", line 203, in rev_list_commits output = git.rev_list(*args, **kwargs_copy) File "/usr/bin/git-bz", line 190, in f return git_run(command, *args, **kwargs) File "/usr/bin/git-bz", line 172, in git_run raise CalledProcessError(process.returncode, " ".join(to_run)) CalledProcessError: Command 'git rev-list --pretty=format:%s 730499' returned non-zero exit status 128 Local variables in innermost frame: error: "fatal: ambiguous argument '730499': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\n" input: None to_run: ['git', 'rev-list', '--pretty=format:%s', '730499'] process: <subprocess.Popen object at 0x7ffc39c65190> kwargs: {'pretty': 'format:%s'} k: 'pretty' strip: True args: ('730499',) quiet: False command: 'rev_list' v: 'format:%s' return_stderr: False output: '' interactive: False
Created attachment 948117 [details] File: backtrace
Created attachment 948118 [details] File: environ
This was caused by attempting to use google-chrome-stable with git-bz.
Cc'ing upstream. BTW looks like you entered the arguments to attach in the wrong order, bug reference comes before commit id.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.