[Bug 1475842] New: testng 6.11 breaks jing-trang build
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1475842
Bug ID: 1475842
Summary: testng 6.11 breaks jing-trang build
Product: Fedora
Version: rawhide
Component: testng
Assignee: puntogil(a)libero.it
Reporter: ville.skytta(a)iki.fi
QA Contact: extras-qa(a)fedoraproject.org
CC: jaromir.capik(a)email.cz,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, puntogil(a)libero.it
testng 6.11 breaks jing-trang's build somehow:
https://kojipkgs.fedoraproject.org//work/tasks/9362/20779362/build.log
mod.catalog.test-unit:
[mkdir] Created dir:
/builddir/build/BUILD/jing-trang-20131210/build/mod/catalog/test-unit
[testng] Exception in thread "main" org.testng.TestNGException:
[testng] Cannot load class from file:
/builddir/build/BUILD/jing-trang-20131210/build/mod/catalog/classes/test/com/thaiopensource/resolver/catalog/CatalogResolverTest.class
[testng] at
org.testng.internal.ClassHelper.fileToClass(ClassHelper.java:602)
[testng] at org.testng.TestNG.configure(TestNG.java:1476)
[testng] at org.testng.TestNG.privateMain(TestNG.java:1437)
[testng] at org.testng.TestNG.main(TestNG.java:1416)
BUILD FAILED
Downgrading to testng-6.9.12-5.fc27.noarch from koji fixes it.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 10 months
Broken dependencies: aether-ant-tasks
by buildsys@fedoraproject.org
aether-ant-tasks has broken dependencies in the rawhide tree:
On x86_64:
1:aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
On armhfp:
1:aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
On ppc64le:
1:aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
On aarch64:
1:aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
On ppc64:
1:aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
On i386:
1:aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
Please resolve this as soon as possible.
6 years, 10 months
[Bug 1406703] New: smack: TLS SecurityMode.required bypass via StripTLS attack
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1406703
Bug ID: 1406703
Summary: smack: TLS SecurityMode.required bypass via StripTLS
attack
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: anemec(a)redhat.com
CC: aileenc(a)redhat.com, alazarot(a)redhat.com,
chazlett(a)redhat.com, etirelli(a)redhat.com,
gvarsami(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jcoleman(a)redhat.com, kconner(a)redhat.com,
kverlaen(a)redhat.com, ldimaggi(a)redhat.com,
lpetrovi(a)redhat.com, mbaluch(a)redhat.com,
mwinkler(a)redhat.com, nwallace(a)redhat.com,
pavelp(a)redhat.com, projects.rg(a)smart.ms,
puntogil(a)libero.it, rrajasek(a)redhat.com,
rwagner(a)redhat.com, rzhang(a)redhat.com,
soa-p-jira(a)post-office.corp.redhat.com,
tcunning(a)redhat.com, tkirby(a)redhat.com
A vulnerability in the Smack XMPP library was reported where the security of
the TLS connection is not always enforced. By stripping the "starttls"
feature from the server response with a man-in-the-middle tool, an attacker
can force the client to authenticate in clear text even if the
"SecurityMode.required" TLS setting has been set.
References:
http://seclists.org/oss-sec/2016/q4/716
https://community.igniterealtime.org/blogs/ignite/2016/11/22/smack-securi...
Upstream bug:
https://issues.igniterealtime.org/browse/SMACK-739
Upstream patches:
https://github.com/igniterealtime/Smack/commit/059ee99ba0d5ff7758829acf5a...
https://github.com/igniterealtime/Smack/commit/a9d5cd4a611f47123f9561bc5a...
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 10 months
[Bug 1344641] New: builddep mojo NPE on pomless projects
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1344641
Bug ID: 1344641
Summary: builddep mojo NPE on pomless projects
Product: Fedora
Version: rawhide
Component: xmvn
Assignee: mizdebsk(a)redhat.com
Reporter: msimacek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mat.booth(a)redhat.com, mizdebsk(a)redhat.com,
msimacek(a)redhat.com, msrb(a)redhat.com
Description of problem:
XMVn builddep mojo crashes with NPE on tycho-pomless projects. This is because
Model.getLocation("") returns null for these. I inspected the object in
debugger and location hashmap contains only "properties" key which probably got
there via pom inheritance. I'm not sure of a correct solution. AFAIK location
tracking is not mandatory in maven, so XMVn, shouldn't rely on it (determine
whether dep/plugin was inherited by walking the graph?). Or it would probably
be more straightforward to patch polyglot to set the location. Or use the
"properties" key.
Stacktrace:
[ERROR] Failed to execute goal org.fedoraproject.xmvn:xmvn-mojo:2.5.0:builddep
(default-cli) on project eclipse-abrt: Execution default-cli of goal
org.fedoraproject.xmvn:xmvn-mojo:2.5.0:builddep failed. NullPointerException ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.fedoraproject.xmvn:xmvn-mojo:2.5.0:builddep (default-cli) on project
eclipse-abrt: Execution default-cli of goal
org.fedoraproject.xmvn:xmvn-mojo:2.5.0:builddep failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal org.fedoraproject.xmvn:xmvn-mojo:2.5.0:builddep failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.NullPointerException
at org.fedoraproject.xmvn.mojo.BuilddepMojo.execute(BuilddepMojo.java:143)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Version-Release number of selected component (if applicable):
xmvn-0:2.5.0-7.fc25.noarch
How reproducible:
always
Steps to Reproduce:
1. rebuild eclipse-abrt
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 10 months
[Bug 1353905] CVE-2016-5007 springframework-security: spring: Path matching inconsistency [fedora-all]
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1353905
--- Comment #3 from Fedora End Of Life <jkurik(a)fedoraproject.org> ---
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '24'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 10 months
[Bug 1353904] CVE-2016-5007 springframework: spring: Path matching inconsistency [fedora-all]
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1353904
--- Comment #3 from Fedora End Of Life <jkurik(a)fedoraproject.org> ---
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '24'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 10 months