July 2014 - java-sig-commits - Fedora Mailing-Lists

[Bug 1110034] New: bouncycastle-pkix - please provide EL6 and EL7 packages via EPEL

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1110034 Bug ID: 1110034 Summary: bouncycastle-pkix - please provide EL6 and EL7 packages via EPEL Product: Fedora Version: rawhide Component: bouncycastle-pkix Assignee: puntogil(a)libero.it Reporter: dpierce(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: java-sig-commits(a)lists.fedoraproject.org, jochen(a)herr-schmitt.de, msrb(a)redhat.com, puntogil(a)libero.it Please provide RHEL6 and RHEL7 versions of this package via the EPEL repositories. -- 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=UFcrPiWSjm&a=cc_unsubscribe

8 years, 6 months

1
9
0 / 0

[Bug 1093273] New: CVE-2014-0363 smack: incorrect X.509 validation

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1093273 Bug ID: 1093273 Summary: CVE-2014-0363 smack: incorrect X.509 validation Product: Security Response Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: mmcallis(a)redhat.com CC: java-sig-commits(a)lists.fedoraproject.org, puntogil(a)libero.it, weli(a)redhat.com Common Vulnerabilities and Exposures assigned an identifier CVE-2014-0363 to the following vulnerability: Name: CVE-2014-0363 URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0363 Assigned: 20131205 Reference: http://community.igniterealtime.org/blogs/ignite/2014/04/17/asmack-400-rc... Reference: http://issues.igniterealtime.org/browse/SMACK-410 Reference: CERT-VN:VU#489228 Reference: http://www.kb.cert.org/vuls/id/489228 The ServerTrustManager component in the Ignite Realtime Smack XMPP API before 4.0.0-rc1 does not verify basicConstraints and nameConstraints in X.509 certificate chains from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate chain. The man-in-the-middle attacker requires a certificate that is valid for any domain name. Upstream patch: http://fisheye.igniterealtime.org/changelog/smackgit?cs=93030c218c62cf0a0... >From code inspection, this issue affects the 3.2.2 version in Fedora (the CERT advisory mentions version 3.4.1 and possibly earlier versions). -- 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=1wrKeWsHiZ&a=cc_unsubscribe

8 years, 7 months

1
24
0 / 0

[Bug 1107277] New: sbt: FTBFS in rawhide

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1107277 Bug ID: 1107277 Summary: sbt: FTBFS in rawhide Product: Fedora Version: rawhide Component: sbt Assignee: willb(a)redhat.com Reporter: dennis(a)ausil.us QA Contact: extras-qa(a)fedoraproject.org CC: java-sig-commits(a)lists.fedoraproject.org, s(a)shk.io, willb(a)redhat.com Blocks: 1105908 Your package sbt failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=7004931 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1105908 [Bug 1105908] Fedora 21 Mass Rebuild FTBFS Tracker -- 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=AX37IIzz6X&a=cc_unsubscribe

8 years, 9 months

1
8
0 / 0

[Bug 807598] New: aqute-bnd-1.50.0 is available

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: aqute-bnd-1.50.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=807598 Summary: aqute-bnd-1.50.0 is available Product: Fedora Version: rawhide Platform: Unspecified OS/Version: Unspecified Status: NEW Keywords: FutureFeature, Triaged Severity: unspecified Priority: unspecified Component: aqute-bnd AssignedTo: jcapik(a)redhat.com ReportedBy: upstream-release-monitoring(a)fedoraproject.org QAContact: extras-qa(a)fedoraproject.org CC: java-sig-commits(a)lists.fedoraproject.org, jcapik(a)redhat.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Latest upstream release: 1.50.0 Current version in Fedora Rawhide: 0.0.363 URL: http://github.com/bndtools/bnd/blob/master/biz.aQute.bnd/bnd.bnd 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 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

8 years, 9 months

1
28
0 / 0

[Bug 1122149] New: Custom boot.properties cause serious issues

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1122149 Bug ID: 1122149 Summary: Custom boot.properties cause serious issues Product: Fedora Version: 20 Component: sbt Severity: high Assignee: willb(a)redhat.com Reporter: th0br0(a)mkdir.name 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: Running sbt projects with sbt installed from Fedora's repository causes various issues with different projects. From classpath issues to ivy2 issues to ... Also see https://github.com/scalatest/scalatest/issues/248 for some examples. Fix: remove Fedora sbt and install sbt as per http://www.scala-sbt.org/release/tutorial/Manual-Installation.html Prior to Fedora providing a custom ivy root etc. (I last tested on fc17) the Fedora-provided sbt worked just fine AFAIR. Version-Release number of selected component (if applicable): only tested on 0.13.1-5.fc20 How reproducible: Steps to Reproduce: 1. git clone https://github.com/miguno/kafka-storm-starter 2. cd kafka-storm-starter 3. sbt test (4. disable forking or stop NetworkManager ... which somehow seems to fix the issue) Actual results: [error] Uncaught exception when running tests: java.net.NoRouteToHostException: No route to host sbt.ForkMain$ForkError: No route to host Expected results: tests run 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=wpkqnjoTiO&a=cc_unsubscribe

8 years, 9 months

1
3
0 / 0

[Bug 1112196] New: The sbt package should use upstream launch scripts

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1112196 Bug ID: 1112196 Summary: The sbt package should use upstream launch scripts Product: Fedora Version: 20 Component: sbt Assignee: willb(a)redhat.com Reporter: code(a)oleastre.be 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: Current fedora sbt package uses a custom launch script that does not support options provided by upstream. You can find in the upstream rpm package at: http://www.scala-sbt.org/0.13/tutorial/Installing-sbt-on-Linux.html Launch scripts are available at: https://github.com/sbt/sbt-launcher-package Version-Release number of selected component (if applicable): sbt-0.13.1-5.fc20 Current fedora package can probably be used to build rpm packages for some scala based projects, but it can not be used by scala developers for their daily job. -- 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=MXOutkGmg6&a=cc_unsubscribe

8 years, 9 months

1
5
0 / 0

[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

1
2
0 / 0

[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

1
2
0 / 0

[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

1
2
0 / 0

[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

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

java-sig-commits July 2014