[Bug 1294230] New: Please provide support for EPEL7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1294230
Bug ID: 1294230
Summary: Please provide support for EPEL7
Product: Fedora
Version: rawhide
Component: powermock
Severity: medium
Assignee: rkennke(a)redhat.com
Reporter: projects.rg(a)smart.ms
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, msimacek(a)redhat.com,
neugens(a)redhat.com, projects.rg(a)smart.ms,
rkennke(a)redhat.com
Description of problem:
There are packages for EPEL6 and 5. Please apply it also for EPEL7.
Version-Release number of selected component (if applicable):
-
How reproducible:
yes
Steps to Reproduce:
1. run an EPEL7 system
2. dnf install powermock
3.
Actual results:
no package found.
Expected results:
powermock gets installed with success.
Additional info:
DEBUG util.py:393: Getting requirements for powermock-1.6.2-2.el7.src
DEBUG util.py:393: --> maven-local-3.4.1-11.el7.noarch
DEBUG util.py:393: --> apache-commons-logging-1.1.2-7.el7.noarch
DEBUG util.py:393: --> tomcat-servlet-3.0-api-7.0.54-2.el7_1.noarch
DEBUG util.py:393: --> junit-4.11-8.el7.noarch
DEBUG util.py:393: --> cglib-2.2-18.el7.noarch
DEBUG util.py:393: --> maven-plugin-bundle-2.3.7-12.el7.noarch
DEBUG util.py:393: --> javassist-3.16.1-10.el7.noarch
DEBUG util.py:393: --> mockito-1.9.0-19.el7.noarch
DEBUG util.py:393: --> mockito-1.9.0-19.el7.noarch
DEBUG util.py:393: --> objenesis-1.2-18.el7.noarch
DEBUG util.py:393: --> sonatype-oss-parent-7-6.el7.noarch
DEBUG util.py:393: Error: No Package found for mvn(cglib:cglib-nodep)
DEBUG util.py:393: Error: No Package found for mvn(org.easymock:easymock)
--
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=GemvJMgqTe&a=cc_unsubscribe
6 years, 10 months
[Bug 1377280] New: CVE-2016-5017 zookeeper: Buffer overflow vulnerability in C cli shell
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1377280
Bug ID: 1377280
Summary: CVE-2016-5017 zookeeper: Buffer overflow vulnerability
in C cli shell
Product: Security Response
Component: vulnerability
Keywords: Security
Severity: low
Priority: low
Assignee: security-response-team(a)redhat.com
Reporter: anemec(a)redhat.com
CC: abhgupta(a)redhat.com, aileenc(a)redhat.com,
alazarot(a)redhat.com, aszczucz(a)redhat.com,
chazlett(a)redhat.com, ctubbsii(a)fedoraproject.org,
dmcphers(a)redhat.com, ethan(a)ethantuttle.com,
etirelli(a)redhat.com, felias(a)redhat.com,
gvarsami(a)redhat.com, hchiorea(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jcoleman(a)redhat.com, jialiu(a)redhat.com,
jokerman(a)redhat.com, jolee(a)redhat.com,
kconner(a)redhat.com, kseifried(a)redhat.com,
kverlaen(a)redhat.com, ldimaggi(a)redhat.com,
lmeyer(a)redhat.com, lpetrovi(a)redhat.com,
mbaluch(a)redhat.com, mmccomas(a)redhat.com,
mwinkler(a)redhat.com, nwallace(a)redhat.com,
pavelp(a)redhat.com, rrajasek(a)redhat.com,
rwagner(a)redhat.com, rzhang(a)redhat.com,
soa-p-jira(a)post-office.corp.redhat.com, s(a)shk.io,
tcunning(a)redhat.com, tiwillia(a)redhat.com,
tkirby(a)redhat.com, tstclair(a)redhat.com,
vhalbert(a)redhat.com
The ZooKeeper C client shells "cli_st" and "cli_mt" have a buffer overflow
vulnerability associated with parsing of the input command when using the
"cmd:<cmd>" batch mode syntax. If the command string exceeds 1024 characters a
buffer overflow will occur. There is no known compromise which takes advantage
of this vulnerability, and if security is enabled the attacker would be limited
by client level security constraints. The C cli shell is intended as a
sample/example of how to use the C client interface, not as a production tool -
the documentation has also been clarified on this point.
References:
http://seclists.org/bugtraq/2016/Sep/29
Upstream fix:
https://git-wip-us.apache.org/repos/asf?p=zookeeper.git;a=commitdiff;h=27...
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 11 months
[Bug 1402199] New: netty build for EPEL7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1402199
Bug ID: 1402199
Summary: netty build for EPEL7
Product: Fedora
Version: 25
Component: netty
Assignee: jerboaa(a)gmail.com
Reporter: iwienand(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, msimacek(a)redhat.com
Hi,
We would like to get zookeeper packages for EPEL7, and netty is one hard
requirement for getting that to work.
---
DEBUG util.py:421: Error: No Package found for mvn(io.netty:netty-tcnative)
DEBUG util.py:421: Error: No Package found for mvn(log4j:log4j:12)
DEBUG util.py:421: Error: No Package found for
mvn(org.jboss.logging:jboss-logging)
DEBUG util.py:421: Error: No Package found for
mvn(org.jboss.marshalling:jboss-marshalling)
---
A COPR build [1] suggests maybe it's not too far off. I'm filing this bug for
tracking and coordination of interested parties.
[1]
https://copr-be.cloud.fedoraproject.org/results/iwienand/centos7-zookeepe...
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 1 month
[Bug 1401161] New: Updating to latest packages of jenkins prevents jenkins from properly starting
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1401161
Bug ID: 1401161
Summary: Updating to latest packages of jenkins prevents
jenkins from properly starting
Product: Fedora
Version: 25
Component: jenkins
Assignee: msrb(a)redhat.com
Reporter: dhill(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msrb(a)redhat.com
Description of problem:
Updating to latest packages of jenkins prevents jenkins from properly starting
java.io.FileNotFoundException: /usr/share/jenkins/webroot/WEB-INF/lib/jtidy.jar
(Too many levels of symbolic links)
java.io.FileNotFoundException:
/usr/share/jenkins/webroot/WEB-INF/lib/mina-core.jar (Too many levels of
symbolic links)
java.io.FileNotFoundException:
/usr/share/jenkins/webroot/WEB-INF/lib/mina-core.jar (Too many levels of
symbolic links)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at
org.eclipse.jetty.util.resource.FileResource.getInputStream(FileResource.java:286)
at org.eclipse.jetty.webapp.JarScanner.matched(JarScanner.java:151)
at
org.eclipse.jetty.util.PatternMatcher.matchPatterns(PatternMatcher.java:100)
at org.eclipse.jetty.util.PatternMatcher.match(PatternMatcher.java:82)
at org.eclipse.jetty.webapp.JarScanner.scan(JarScanner.java:84)
at
org.eclipse.jetty.webapp.MetaInfConfiguration.preConfigure(MetaInfConfiguration.java:84)
at
org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
at
winstone.HostConfiguration$1.preConfigure(HostConfiguration.java:166)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:282)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at winstone.Launcher.<init>(Launcher.java:152)
at winstone.Launcher.main(Launcher.java:352)
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 Main._main(Main.java:290)
at Main.main(Main.java:104)
Dec 02, 2016 11:19:13 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started SelectChannelConnector@0.0.0.0:8080
Dec 02, 2016 11:19:13 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Dec 02, 2016 11:23:06 PM winstone.Logger logInternal
INFO: JVM is terminating. Shutting down Winstone
Dec 02, 2016 11:23:07 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.1.17.v20150415
Dec 02, 2016 11:23:07 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Failed startup of context
w.{,file:/usr/share/jenkins/webroot/},/usr/share/jenkins/webroot
java.io.FileNotFoundException:
/usr/share/jenkins/webroot/WEB-INF/lib/mina-core.jar (Too many levels of
symbolic links)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at
org.eclipse.jetty.util.resource.FileResource.getInputStream(FileResource.java:286)
at org.eclipse.jetty.webapp.JarScanner.matched(JarScanner.java:151)
at
org.eclipse.jetty.util.PatternMatcher.matchPatterns(PatternMatcher.java:100)
at org.eclipse.jetty.util.PatternMatcher.match(PatternMatcher.java:82)
at org.eclipse.jetty.webapp.JarScanner.scan(JarScanner.java:84)
at
org.eclipse.jetty.webapp.MetaInfConfiguration.preConfigure(MetaInfConfiguration.java:84)
at
org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
at
winstone.HostConfiguration$1.preConfigure(HostConfiguration.java:166)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:282)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at winstone.Launcher.<init>(Launcher.java:152)
at winstone.Launcher.main(Launcher.java:352)
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 Main._main(Main.java:290)
at Main.main(Main.java:104)
Version-Release number of selected component (if applicable):
Dec 02 22:52:35 DEBUG ---> Package jenkins.noarch 1.651.3-1.fc25 will be
upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins.noarch 1.651.3-2.fc25 will be an
upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-webapp.noarch 1.651.3-1.fc25 will be
upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-webapp.noarch 1.651.3-2.fc25 will be
an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-cli.noarch 1.651.3-1.fc25 will be
upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-cli.noarch 1.651.3-2.fc25 will be an
upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-core.noarch 1.651.3-1.fc25 will be
upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-core.noarch 1.651.3-2.fc25 will be
an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting.noarch 2.59-1.fc25 will be
upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting.noarch 2.62.3-1.fc25 will
be an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting-webapp.noarch 2.59-1.fc25
will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting-webapp.noarch 2.62.3-1.fc25
will be an upgrade
How reproducible:
This time
Steps to Reproduce:
1. Update from 2.62.3-1 to 2.62.3-2
2.
3.
Actual results:
Fails to properly start
Expected results:
Start properly
Additional info:
I deleted the symlinks and restarted the service which started but idk in which
state is now my jenkins instance.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 1 month