Bug 1306505 - c project creation results in python exception
Summary: c project creation results in python exception
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: devassistant-dap-c
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Bohuslav "Slavek" Kabrda
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-11 04:40 UTC by Philip Kovacs
Modified: 2016-12-20 18:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 18:37:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Philip Kovacs 2016-02-11 04:40:50 UTC
Description of problem:

Creation of either c or cpp project results in python exception.

Fixed in upstream version 0.12 with this commit: 

https://github.com/devassistant/dap-c/commit/ee16e6688524da23ce9be0a2d1d352a0bb766412#diff-249b58dcaf3c8212b4501a8c8f540b43


Version-Release number of selected component (if applicable):

devassistant-dap-c.noarch                                        0.11-2.fc23

How reproducible:


Steps to Reproduce:
1. da create c -n test-c
2. da create c -n test-cpp
3.

Actual results:

INFO: Project name will be converted to lowercase letters (test-c)
INFO: Copying c source tree to project destination
[devassistant]$ cp -r /usr/share/devassistant/files/crt/c/. "./test-c"
DevAssistant traceback (most recent call last):
File /usr/share/devassistant/assistants/crt/c.yaml:
  {'$clemail~': '$clemail1@$clemail1'}
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/devassistant/excepthook.py", line 49, in excepthook
    current_command_dict = frame.f_locals['command_dict']
KeyError: 'command_dict'


Expected results:


Additional info:

Comment 1 Philip Kovacs 2016-02-11 04:46:40 UTC
Steps to Reproduce (correction):

1. da create c -n test-c
2. da create cpp -n test-cpp

Comment 2 Philip Kovacs 2016-02-11 05:07:43 UTC
Filed bug 1306506 for devassistant-dap-cpp.  Same bug appears in both the c and cpp packages.

Comment 3 Philip Kovacs 2016-02-12 04:21:35 UTC
More information: you will not see the bug *if* you have a .gitconfig with an email address in it.

Comment 4 Fedora End Of Life 2016-11-24 15:30:04 UTC
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.

Comment 5 Fedora End Of Life 2016-12-20 18:37:02 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.