https://bugzilla.redhat.com/show_bug.cgi?id=1493222
Hooman Broujerdi <hghasemb(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|impact=moderate,public=2017 |impact=moderate,public=2017
|0919,reported=20170919,sour |0919,reported=20170919,sour
|ce=internet,cvss3=5.3/CVSS: |ce=internet,cvss3=5.3/CVSS:
|3.0/AV:N/AC:L/PR:N/UI:N/S:U |3.0/AV:N/AC:L/PR:N/UI:N/S:U
|/C:L/I:N/A:N,cwe=CWE-200,rh |/C:L/I:N/A:N,cwe=CWE-200,rh
|el-7/tomcat=wontfix,rhscl-2 |el-7/tomcat=wontfix,rhscl-2
|/rh-java-common-tomcat=nota |/rh-java-common-tomcat=nota
|ffected,jbews-2/tomcat7=won |ffected,jbews-2/tomcat7=won
|tfix,jws-3/tomcat7=affected |tfix,jws-3/tomcat7=affected
|,jws-3/tomcat8=notaffected, |,jws-3/tomcat8=notaffected,
|jdg-6/jbossweb=notaffected, |jdg-6/jbossweb=notaffected,
|jdv-6/jbossweb=notaffected, |jdv-6/jbossweb=notaffected,
|eap-6/jbossweb=wontfix,fuse |eap-6/jbossweb=wontfix,fuse
|-6/jbossweb=new,jon-3/jboss |-6/jbossweb=notaffected,jon
|web=wontfix,jpp-6/jbossweb= |-3/jbossweb=wontfix,jpp-6/j
|wontfix,openshift-1/jbosswe |bossweb=wontfix,openshift-1
|b=affected,fedora-all/tomca |/jbossweb=affected,fedora-a
|t=notaffected,epel-6/tomcat |ll/tomcat=notaffected,epel-
|=affected,rhel-6/tomcat6=wo |6/tomcat=affected,rhel-6/to
|ntfix |mcat6=wontfix
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495235
Bug ID: 1495235
Summary: [fop] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: fop
Assignee: r.landmann(a)redhat.com
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: c.david86(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com,
rhbugs(a)n-dimensional.de, r.landmann(a)redhat.com
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
fop-2.0-7.fc28
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495234
Bug ID: 1495234
Summary: [hamcrest] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: hamcrest
Assignee: dwalluck(a)redhat.com
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, dwalluck(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, mizdebsk(a)redhat.com,
msimacek(a)redhat.com
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
hamcrest-1.3-21.fc27
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495239
Bug ID: 1495239
Summary: [ws-jaxme] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: ws-jaxme
Assignee: hdegoede(a)redhat.com
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dbhole(a)redhat.com, hdegoede(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, puntogil(a)libero.it,
rgrunber(a)redhat.com
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
ws-jaxme-0.5.2-21.fc27
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495233
Bug ID: 1495233
Summary: [java_cup] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: java_cup
Assignee: puntogil(a)libero.it
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, puntogil(a)libero.it
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
java_cup-0.11b-6.fc27
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495232
Bug ID: 1495232
Summary: [kxml] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: kxml
Assignee: mizdebsk(a)redhat.com
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
kxml-2.3.0-14.fc27
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495243
Bug ID: 1495243
Summary: [qdox] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: qdox
Assignee: akurtako(a)redhat.com
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
qdox-2.0-0.10.M7.fc28
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1495247
Bug ID: 1495247
Summary: [xpp3] zip -u in spec file causes race condition
Product: Fedora
Version: rawhide
Component: xpp3
Assignee: mat.booth(a)redhat.com
Reporter: tdawson(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dbhole(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, mat.booth(a)redhat.com,
mizdebsk(a)redhat.com, puntogil(a)libero.it
Description of problem:
zip -u is being used to update META-INF/MANIFEST.MF in jar files
zip -u will "Update existing entries if newer on the file system"
Unfortunately zip is only looking at the minute that a file is updated. We are
finding on fast test machines that the content of the jar, and the new
META-INF/MANIFEST.MF, are being created in the same minute. Thus when the zip
-u is ran, the MANIFEST.MF isn't updated, zip returns a non 0 error code, and
the build fails.
"zip -u" should be changed to "zip", which changes the zip command from
"update" to "add"
zip (add) will "Update existing entries and add new files. ... This is the
default mode."
If you can change your spec files to use just "zip" instead of "zip -u", that
will solve this race condition
Version-Release number of selected component (if applicable):
xpp3-1.1.4-16.c.fc27
How reproducible:
5-95% - depending on the speed of the machine.
Steps to Reproduce:
1. koji build
2.
3.
Actual results:
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Bad exit status from /var/tmp/rpm-tmp.oh6WeU (%build)
Child return code was: 1
Expected results:
...
+ zip -u build/lib/<jar-name>.jar META-INF/MANIFEST.MF
updating: META-INF/MANIFEST.MF (deflated 56%)
...
--
You are receiving this mail because:
You are on the CC list for the bug.