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=5933066http://koji.fedoraproject.org/koji/taskinfo?taskID=5925100
Failures:
http://koji.fedoraproject.org/koji/taskinfo?taskID=5925234http://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
https://bugzilla.redhat.com/show_bug.cgi?id=1163170
Bug ID: 1163170
Summary: maven-surefire-2.18 is available
Product: Fedora
Version: rawhide
Component: maven-surefire
Keywords: FutureFeature, Triaged
Assignee: mizdebsk(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jcapik(a)redhat.com, mizdebsk(a)redhat.com,
msimacek(a)redhat.com, msrb(a)redhat.com
Latest upstream release: 2.18
Current version/release in Fedora Rawhide: 2.17-6.fc22
URL: http://repo2.maven.org/maven2/org/apache/maven/surefire/surefire/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service
will be implemented by a new system: https://github.com/fedora-infra/anitya/
It will require to manage monitored projects via a new web interface. Please
make yourself familiar with the new system to ease the transition.
--
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=ojIh8ZUn1F&a=cc_unsubscribe
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
https://bugzilla.redhat.com/show_bug.cgi?id=1138344
Bug ID: 1138344
Summary: [abrt] plotutils: pl_flinerel_r(): plot killed by
SIGSEGV
Product: Fedora
Version: 20
Component: plotutils
Assignee: mizdebsk(a)redhat.com
Reporter: ssabcew(a)mail.bg
QA Contact: extras-qa(a)fedoraproject.org
CC: branto(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
lemenkov(a)gmail.com, mizdebsk(a)redhat.com,
msimacek(a)redhat.com, msrb(a)redhat.com
Version-Release number of selected component:
plotutils-2.6-10.fc20
Additional info:
reporter: libreport-2.2.3
backtrace_rating: 4
cmdline: plot test.dat using 1:2 title s1response
crash_function: pl_flinerel_r
executable: /usr/bin/plot
kernel: 3.15.10-200.fc20.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (2 frames)
#0 pl_flinerel_r at g_relative.c:117
#1 read_plot at plot.c:1289
--
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=lr5LfY1Ltp&a=cc_unsubscribe
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
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