Bug 14534 - edugraphe does not run
Summary: edugraphe does not run
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-11-13 22:41 CET by Alex Loginov
Modified: 2014-12-19 12:56 CET (History)
0 users

See Also:
Source RPM: edugraphe
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Alex Loginov 2014-11-13 22:41:54 CET 
Description of problem:
[user@localhost ~]$ edugraphe
Error: Could not find or load main class edugraphe


Version-Release number of selected component (if applicable): edugraphe-1.1-8.mga5


How reproducible: always


Steps to Reproduce:
1. install edugraphe
2. run edugraphe


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-11-13 22:59:13 CET

Keywords: (none) => Triaged
CC: sysadmin-bugs => (none)
Component: Release (media or process) => RPM Packages
Assignee: bugsquad => remi

Comment 1 Alex Loginov 2014-12-18 18:08:51 CET 
Rémi, hi,

Please test edugraphe-1.1-10.mga5.
I rebuilt locally and it works, needs tests after BS.
This issue is for broken Java stack.
Comment 2 Rémi Verschelde 2014-12-18 18:49:04 CET 
Thanks Alex, I had forgotten about this bug.
I confirm that edugraphe-1.1-9.mga5 does not run, I will test -10.mga5 as soon as it reaches my mirror.
Comment 3 Alex Loginov 2014-12-18 20:15:23 CET 
http://pkgsubmit.mageia.org/uploads/done/cauldron/core/release/20141218170214.alexl.valstar.4473/edugraphe-1.1-10.mga5/build.0.20141218170302.log
100 errors "unmappable character for encoding ASCII", but OK locally.

I added "export JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8" and rebuilt edugraphe-1.1-11.mga5.
Comment 4 Rémi Verschelde 2014-12-19 12:56:36 CET 
I confirm that -11.mga5 fixes the issue, thanks Alexey!

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.