[Bug 1008091] New: Building with tycho seems to fail on arm builders
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1008091
Bug ID: 1008091
Summary: Building with tycho seems to fail on arm builders
Product: Fedora
Version: 20
Component: tycho
Assignee: rgrunber(a)redhat.com
Reporter: gerard(a)ryan.lt
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
kdaniel(a)redhat.com, mizdebsk(a)redhat.com,
rgrunber(a)redhat.com
Description of problem:
I'm trying to build eclipse-jbosstools, but every time that an arm builder is
chosen in koji, the build fails. I'm not sure exactly if the problem is with
tycho, but it looks like it's tycho/maven related.
How reproducible:
It seems to be only on armv7hl. Also, I've only run into the problem on f20,
since that's the only place I seem to have been given arm builders. Incredibly,
on my 4 attempts, the two scratch builds have been done on x86, so then I go to
do a real build, thinking everything is fine, and I get an arm one and it
fails.
Passes:
http://koji.fedoraproject.org/koji/taskinfo?taskID=5933066
http://koji.fedoraproject.org/koji/taskinfo?taskID=5925100
Failures:
http://koji.fedoraproject.org/koji/taskinfo?taskID=5925234
http://koji.fedoraproject.org/koji/taskinfo?taskID=5933332
Here's the build.log from one of the failures (I think those get cleared after
a week or so): http://galileo.fedorapeople.org/arm-build.log
Additional info:
I was talking to Dennis Gilmore on #fedora-devel about this, and he mentioned
that if necessary, he can provide access to arm systems to test/debug on.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ZGobfEfjEs&a=cc_unsubscribe
8 years, 9 months
[Bug 1111502] New: Build with $RPM_OPT/LD_FLAGS, show native build output
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1111502
Bug ID: 1111502
Summary: Build with $RPM_OPT/LD_FLAGS, show native build output
Product: Fedora
Version: rawhide
Component: netty
Assignee: mizdebsk(a)redhat.com
Reporter: ville.skytta(a)iki.fi
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jon.vanalten(a)redhat.com,
mizdebsk(a)redhat.com, msimacek(a)redhat.com,
msrb(a)redhat.com
I wonder if it's possible to additionally package the native lib
outside of a jar so a proper debuginfo package could be created?
Anyway if not I suppose this leaves the *.so containing debug symbols
inside the jar and thus that one can be used for debugging. If so, the
-debuginfo package should be disabled.
'git am'able fix attached (sans disabling the -debuginfo part). While
at it, fixed one bogus date in %changelog.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Mia2H8glng&a=cc_unsubscribe
8 years, 10 months
[Bug 1091711] New: sbt does not work if I go into the console
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1091711
Bug ID: 1091711
Summary: sbt does not work if I go into the console
Product: Fedora
Version: 20
Component: sbt
Severity: urgent
Assignee: willb(a)redhat.com
Reporter: rwobben(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org, s(a)shk.io,
willb(a)redhat.com
Description of problem:
When I start sbt and do the command console. The console starts up and I see
the scala prompt. And then the terminal does not respond anymore to the
keyboard.
See ths output:
[info] Starting scala interpreter...
[info]
Welcome to Scala version
2.10.3-20130923-e2fec6b28dfd73482945ffab85d9b582d0cb9f17 (OpenJDK 64-Bit Server
VM, Java 1.7.0_55).
Type in expressions to have them evaluated.
Type :help for more information.
scala>
Version-Release number of selected component (if applicable):
sbt launcher version 0.13.1
How reproducible: every time
Steps to Reproduce:
1. start sbt
2. enter console
3.
Actual results:
Prompt does not respond to anything
Expected results:
Prompt responds and I can test some things.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=zybqdVFyQJ&a=cc_unsubscribe
8 years, 10 months
[Bug 1043158] New: zookeeper-server service silently fails while starting on FC20
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1043158
Bug ID: 1043158
Summary: zookeeper-server service silently fails while starting
on FC20
Product: Fedora
Version: 20
Component: zookeeper
Assignee: tstclair(a)redhat.com
Reporter: rudcy(a)broadbandninja.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jeff(a)ocjtech.us, skottler(a)redhat.com,
tstclair(a)redhat.com
Description of problem:
zookeeper-server on fc20 silently fails to start after a fresh install
due to unit file precondition on missing file .
Version-Release number of selected component (if applicable):
zookeeper-server-3.4.5-12.fc20.noarch
Steps to Reproduce:
1. Fresh install of fc20
2. install zookeeper-server (and zookeeper?)
3. sudo cp /etc/zoo-sample.cfg /etc/zoo.cfg
4. sudo systemctl start zookeeper
5. journalctl -f shows:
```
Dec 14 14:18:32 localhost.localdomain systemd[1]: Started Apache ZooKeeper.
```
Actual results:
The service has aborted when trying to start, the errors it
reported are not logged to the journal nor /var/log/zookeeper/*
Expected results:
the service should be running, or log an error to the journal.
Additional info:
```
% cat /usr/lib/systemd/system/zookeeper.service
...
ConditionPathExists=/var/lib/zookeeper/data/myid
```
Creating /var/lib/zookeeper/data/myid and chowning it over to zookeeper makes
the next restart "stick" and zookeeper then logs to the journal (too verbosely,
btw).
I've found nothing on setting up zookeeper-server on fedora on google,
but I'm new here, I may have missed it.
So no docs on what is myid or what's it for, zookeeper runs fine without
it if it's launched manually.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ItjXVYdpch&a=cc_unsubscribe
8 years, 10 months
[Bug 1133789] New: CVE-2013-7397 async-http-client: SSL/TLS certificate verification is disabled under certain conditions [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1133789
Bug ID: 1133789
Summary: CVE-2013-7397 async-http-client: SSL/TLS certificate
verification is disabled under certain conditions
[fedora-all]
Product: Fedora
Version: 20
Component: async-http-client
Keywords: Security, SecurityTracking
Severity: high
Priority: high
Assignee: mizdebsk(a)redhat.com
Reporter: djorm(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com,
msrb(a)redhat.com
Blocks: 1133769 (CVE-2013-7397)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1133769
[Bug 1133769] CVE-2013-7397 async-http-client: SSL/TLS certificate
verification is disabled under certain conditions
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=corEJzycHn&a=cc_unsubscribe
8 years, 11 months