Your package mysql-connector-java failed to build from source in current rawhide.
For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Created attachment 904328 [details]
Created attachment 904329 [details]
Created attachment 904330 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Created attachment 1041244 [details]
- adapt to current guideline
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=10170472
Unfortunately, the patch does not help in Fedora 22.
It seems that MySQL Connector/J needs Java 1.5 and Java 1.6, while there is only Java 1.8 available in Fedora 22.
I will try to find the way how to build it with Java 1.8, but I am not sure that it is possible.
(In reply to Jakub Dorňák from comment #6)
> Unfortunately, the patch does not help in Fedora 22.
> It seems that MySQL Connector/J needs Java 1.5 and Java 1.6, while there is
> only Java 1.8 available in Fedora 22.
> I will try to find the way how to build it with Java 1.8, but I am not sure
> that it is possible.
I don't understand what is the problem this release build in rawhide with Java8.
Please, can you attached a build.log?
I see, I've been already working with mysql-connector-java-5.1.35.
It really works with mysql-connector-java-5.1.28.
I just wait for my commit right to be approved to push your changes.
Thanks Gil, I will commit your patch as a provenpackager
mysql-connector-java-5.1.28-6.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mysql-connector-java-5.1.28-6.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mysql-connector-java-5.1.28-6.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.