I'd like to release updated ABRT packages but I'm not sure if I should
wait for this patch or not because I'm not sure what is the purpose of
this patch? Is this patch related to any bugzilla bug or github issue?
On Mon, 2013-09-09 at 14:31 +0200, Denys Vlasenko wrote:
Signed-off-by: Denys
- pushed, thanks
On 09/10/2013 03:53 PM, Jakub Filak wrote:
Closes #695
Signed-off-by: Jakub Filak jfi...@redhat.com
---
src/cli/list.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/cli/list.c b/src/cli/list.c
index cd446a3..1e65073 100644
--- a/src/cli/list.c
+++
- missing ticket number
On 09/09/2013 02:52 PM, Michal Toman wrote:
Signed-off-by: Michal Toman mto...@redhat.com
---
lib/abrt.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/abrt.c b/lib/abrt.c
index 53f84cd..f7d9824 100644
--- a/lib/abrt.c
+++ b/lib/abrt.c
@@
Pushed. Thank you!
Please, try to use correct ticket ids.
#690 issue comes from ABRT's repository therefore you must write
abrt/abrt#690
Please, read this articles. It will save much work for all of us :)
https://help.github.com/articles/closing-issues-via-commit-messages
On 09/11/2013 10:32 AM, Jakub Filak wrote:
I'd like to release updated ABRT packages but I'm not sure if I should
wait for this patch or not because I'm not sure what is the purpose of
this patch? Is this patch related to any bugzilla bug or github issue?
It is a simplification. It does not
According to commit b0d6d3dd99417a46e6ba641fef99235e78ead4d1 we should
modify abrt-action-analyze-core to create build_ids file with
umask(0002) or at least with read permission for others because it is
necessary to successfully
run /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache which
Fixed, pushed, thanks.
The debuginfo installer currently expects both build-ids and user input from a
pipe with analaze-core, when run from an UI.
We need to change it so that it passes the build-ids through a temporary file
and only uses stdin to communicate with the user.
Also makes the output file from analyze-core
