On Mon, Dec 15, 2008 at 05:19:02PM -0500, Jesus M. Rodriguez wrote: > On Sun, Dec 14, 2008 at 7:48 AM, Jan Pazdziora <[email protected]> wrote: > > On Sat, Dec 13, 2008 at 11:17:13AM -0500, Jesus M. Rodriguez wrote: > [snip] > > >> It might be needed by a package that we use, which means that the > >> Requires should be fixed on > >> the other dependent package. > > > > Well, in that 5.2.0, it is not in any .java file either. But it's there > > in buildconf/build-props.xml and it's there in > > conf/default/rhn_taskomatic_daemon.conf. And the fact is that adding > > it fixed that Internal Server Error on RHEL 4. > > > > If he has Spacewalk on RHEL 4, I could have tested it more closely, > > with the current setup I'm more like doing the same 5.2.0-ish > > response to the same problem. > > Not satisfied completely with the answer, I did some digging :) this > is really a bug > against jakarta-commons-fileupload packages *NOT* spacewalk-java. > > jakarta-commons-fileupload 1.1.1-3jpp.ep1.1 (1.1.1 in general) has a > BuildRequires > of jakarta-commons-io. But there is no Requires: of jakarta-commons-io. > > $ grep commons-io jakarta-commons-fileupload.spec > BuildRequires: jakarta-commons-io > export CLASSPATH="$(build-classpath commons-io junit portlet-1.0-api \ > > And looking through the source code it is clearly used: > > $ search commons.io \*.java > ./src/java/org/apache/commons/fileupload/disk/DiskFileItem.java:import > org.apache.commons.io.IOUtils; > ./src/java/org/apache/commons/fileupload/disk/DiskFileItem.java:import > org.apache.commons.io.FileCleaner; > ./src/java/org/apache/commons/fileupload/disk/DiskFileItem.java:import > org.apache.commons.io.output.DeferredFileOutputStream; > > This is only a problem with 1.1.1 version of > jakarta-commons-fileupload. In development > of spacewalk we are using 1.0: > > $ grep fileupload ivy.xml > <dependency org="redhat" name="commons-fileupload" rev="1.0" /> > > 1.0 is the latest available in EPEL and Fedora 9.
Right, but in 5.2.0 on RHEL 4, we've shipped jakarta-commons-fileupload-1.1.1-3jpp.ep1.1.noarch.rpm. And I assume that's exactly the same that got used in 5.3.0 and which prompted this bugzilla and change in the first place. And I do not see the thing in EPEL 4. > I'd like to see a bug opened against jakarta-commons-fileupload How do we file a bug against jakarta-commons-fileupload when we don't even really know in what product is providing the thing for us? ;-) -- Jan Pazdziora Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
