Michael,
as the problem occured in tomcat, and the only related package i could find in the testing updates i done is the tomcat-native, i think it could be the problem and downgraded it. But it didn't solve the problem.
The next suspect is the glibc, because the tomcat-native depends on it, but i think it's impossible to downgrade it, because almost everything depends on it. so i couldn't test glibc to report if would solve the problem.
I will report the bug anyway.
Thanks
as the problem occured in tomcat, and the only related package i could find in the testing updates i done is the tomcat-native, i think it could be the problem and downgraded it. But it didn't solve the problem.
The next suspect is the glibc, because the tomcat-native depends on it, but i think it's impossible to downgrade it, because almost everything depends on it. so i couldn't test glibc to report if would solve the problem.
I will report the bug anyway.
Thanks
On Tue, Jul 15, 2008 at 10:32 AM, Michael Schwendt <mschwendt.tmp0701.nospam@xxxxxxxx> wrote:
On Tue, 15 Jul 2008 10:15:21 -0300, Bruno Medeiros wrote:If you don't report your findings and if nobody else does either,
> Tanks, Michael.
>
> I'll fill the bug report, but a don't know exactly which packages caused the
> problem, i think it's the tomcat-native with glibc, but i could affirm. Can
> I fill the bug report anyway?
you risk that the test updates will be pushed to stable.
Btw, there is a quick way to query for open bug reports:
http://bugz.fedoraproject.org/SOURCE-RPM-PACKAGENAME-HERE
With Yum's log (or "rpm -qa --last|less") you can find out which packages
you installed recently. You could remove them and downgrade to the previous
stable releases to narrow down the selection of bad test updates.
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
