[Bug 1090765] New: Scala projects containing the sbteclipse plugin fail to build
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1090765
Bug ID: 1090765
Summary: Scala projects containing the sbteclipse plugin fail
to build
Product: Fedora
Version: 20
Component: sbt
Severity: high
Assignee: willb(a)redhat.com
Reporter: gvdmer(a)gmail.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:
Scala project will not build in sbt 0.13.1 and Scala 2.10.3 unless I DO NOT try
to add the sbteclipse plugin (2.4.0)
Version-Release number of selected component (if applicable):
sbt 0.13.1
How reproducible:
Every time.
Steps to Reproduce:
1. "yum install -y java", "yum install -y scala", and "yum install -y sbt."
This installed OpenJDK 1.7.0_51, Scala 2.10.3, and sbt 0.13.1.
2. plugins.sbt contains the line "addSbtPlugin("com.typesafe.sbteclipse" %
"sbteclipse-plugin" % "2.4.0")"
Actual results:
Building the project generates the following error:
"sbt.ResolveException: unresolved dependency:
org.scala-lang#scala-library;2.10.3: configuration not found in
org.scala-lang#scala-library;2.10.3: 'compile'."
Expected results:
Project builds.
Additional info:
This is a problem whether the plugins.sbt is located in /project, or in
~/.sbt/0.13/plugins.
I encountered this problem attempting to build
https://github.com/liftmodules/widgets
When I comment-out the "addSbtPlugin.... sbteclipse-plugin" line from the
plugins.sbt, the build functions normally.
I recreated the problem using a simple test project that just creates a single
Scala class with a one-line print statement. The problem continues to occur
independently of whatever other plugins, repositories, or library dependencies
I define in the plugins.sbt and build.sbt files.
--
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=1ghlw6cYfy&a=cc_unsubscribe
8 years, 9 months
[Bug 1083130] New: Memory options should not be set in /usr/bin/sbt
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1083130
Bug ID: 1083130
Summary: Memory options should not be set in /usr/bin/sbt
Product: Fedora
Version: 20
Component: sbt
Assignee: willb(a)redhat.com
Reporter: rocketraman(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
skottler(a)redhat.com, willb(a)redhat.com
Description of problem:
/usr/bin/sbt sets the JVM memory options for sbt. Also, the values are not sane
-- the max perm gen size is left at the default of 64 MB which is too small.
When running the upstream version of sbt, the memory and GC options by default
are:
-Xms1024m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=128m
When running the Fedora version of sbt, the options are:
-Xms512M -Xmx1536M -Xss1M -XX:+CMSClassUnloadingEnabled
This is surprising behavior to say the least. In addition, the Fedora options
cannot be overwridden because /usr/bin/sbt does not check if JAVA_OPTS is
already defined before clobbering it.
Version-Release number of selected component (if applicable):
sbt-0.13.1-5.fc20.noarch
--
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=lrpKiQOfRe&a=cc_unsubscribe
8 years, 9 months
[Bug 1021292] New: Transaction check error when upgrading jogl2
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1021292
Bug ID: 1021292
Summary: Transaction check error when upgrading jogl2
Product: Fedora
Version: 20
Component: jogl2
Assignee: c.david86(a)gmail.com
Reporter: asaha(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: c.david86(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org
Description of problem:
# rpm -q jogl2
jogl2-2.0-0.11.rc12.fc20.x86_64
# yum -y update jogl2
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package jogl2.x86_64 0:2.0-0.11.rc12.fc20 will be updated
---> Package jogl2.x86_64 0:2.0.2-1.fc20 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
==============================================================================================================================================================================================
Package Arch
Version Repository
Size
==============================================================================================================================================================================================
Updating:
jogl2 x86_64
2.0.2-1.fc20 updates-testing
4.0 M
Transaction Summary
==============================================================================================================================================================================================
Upgrade 1 Package
Total size: 4.0 M
Downloading packages:
Running transaction check
Running transaction test
Transaction check error:
file /usr/share/doc/jogl2/bouml from install of jogl2-2.0.2-1.fc20.x86_64
conflicts with file from package jogl2-2.0-0.11.rc12.fc20.x86_64
Error Summary
-------------
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. See above
2.
3.
Actual results:
Expected results:
Clean ugpgrade
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=YU8riko2Sl&a=cc_unsubscribe
8 years, 9 months
[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, 9 months
[Bug 1138344] New: [abrt] plotutils: pl_flinerel_r(): plot killed by SIGSEGV
by Red Hat Bugzilla
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
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