Bug 1028476
Summary: | Ivy not working with rpm install of ant | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Ivan Varga <ivan.varga.83.os> |
Component: | apache-ivy | Assignee: | Matt Spaulding <mspaulding06> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | mspaulding06, orion |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | apache-ivy-2.3.0-1.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-24 18:38:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ivan Varga
2013-11-08 14:35:13 UTC
This was fixed in Fedora with: $ git show fa4267fc3d8fe26664658401c7ae77670820cf27 commit fa4267fc3d8fe26664658401c7ae77670820cf27 Author: Alexander Kurtakov <akurtako> Date: Wed Jul 6 12:14:33 2011 +0300 Fix ant integration. diff --git a/apache-ivy.spec b/apache-ivy.spec index dc496e5..7492258 100644 --- a/apache-ivy.spec +++ b/apache-ivy.spec @@ -1,6 +1,6 @@ Name: apache-ivy Version: 2.2.0 -Release: 1%{?dist} +Release: 2%{?dist} Summary: Java-based dependency manager Group: Development/Tools @@ -20,6 +20,7 @@ BuildRequires: jpackage-utils Requires: jpackage-utils Requires: jakarta-oro Requires: jsch +Requires: ant Requires: jakarta-commons-httpclient %description @@ -79,16 +80,22 @@ install -p -m644 build/artifact/jars/ivy.jar $RPM_BUILD_ROOT%{_javadir}/ivy. install -d $RPM_BUILD_ROOT%{_javadocdir}/%{name} cp -rp build/doc/reports/api/. $RPM_BUILD_ROOT%{_javadocdir}/%{name} +mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/ant.d +echo "ivy" > $RPM_BUILD_ROOT%{_sysconfdir}/ant.d/%{name} + %files -%defattr(-,root,root,-) %{_javadir}/* +%{_sysconfdir}/ant.d/%{name} %doc RELEASE_NOTES CHANGES.txt LICENSE NOTICE README %files javadoc -%defattr(-,root,root,-) %{_javadocdir}/* +%doc LICENSE %changelog +* Wed Jul 6 2011 Alexander Kurtakov <akurtako> 2.2.0-2 +- Fix ant integration. + * Fri Feb 25 2011 Alexander Kurtakov <akurtako> 2.2.0-1 - Update to 2.2.0. Would there be any problem with updating to ivy 2.3.0 from Fedora? Or should we just backport the fixes? apache-ivy-2.3.0-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/apache-ivy-2.3.0-1.el6 Package apache-ivy-2.3.0-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing apache-ivy-2.3.0-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12072/apache-ivy-2.3.0-1.el6 then log in and leave karma (feedback). (In reply to Fedora Update System from comment #3) > Package apache-ivy-2.3.0-1.el6: > * should fix your issue, > * was pushed to the Fedora EPEL 6 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=epel-testing apache-ivy-2.3.0-1.el6' > as soon as you are able to. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12072/apache-ivy-2. > 3.0-1.el6 > then log in and leave karma (feedback). [root@localhost e1]# yum update --enablerepo=epel-testing apache-ivy-2.3.0-1.el6 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile epel/metalink | 25 kB 00:00 epel-testing/metalink | 25 kB 00:00 * base: mirror.lihnidos.org * epel: mirror.slu.cz * epel-testing: mirror.slu.cz * extras: mirror.lihnidos.org * rpmforge: merlin.fit.vutbr.cz * updates: mirror.lihnidos.org base | 3.7 kB 00:00 epel | 4.2 kB 00:00 epel/primary_db | 5.7 MB 00:04 epel-testing | 4.2 kB 00:00 epel-testing/primary_db | 366 kB 00:00 extras | 3.4 kB 00:00 rpmforge | 1.9 kB 00:00 updates | 3.4 kB 00:00 Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package apache-ivy.noarch 0:2.1.0-1.el6 will be updated ---> Package apache-ivy.noarch 0:2.3.0-1.el6 will be an update --> Processing Dependency: jsch for package: apache-ivy-2.3.0-1.el6.noarch --> Processing Dependency: jakarta-oro for package: apache-ivy-2.3.0-1.el6.noarch --> Processing Dependency: jakarta-commons-httpclient for package: apache-ivy-2.3.0-1.el6.noarch --> Running transaction check ---> Package jakarta-commons-httpclient.x86_64 1:3.1-0.7.el6_3 will be installed --> Processing Dependency: jakarta-commons-logging >= 1.0.3 for package: 1:jakarta-commons-httpclient-3.1-0.7.el6_3.x86_64 ---> Package jakarta-oro.x86_64 0:2.0.8-6.6.el6 will be installed ---> Package jsch.noarch 0:0.1.41-2.2.el6 will be installed --> Processing Dependency: jzlib >= 1.0.5 for package: jsch-0.1.41-2.2.el6.noarch --> Running transaction check ---> Package jakarta-commons-logging.noarch 0:1.0.4-10.el6 will be installed ---> Package jzlib.x86_64 0:1.0.7-7.5.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ======================================================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================================================== Updating: apache-ivy noarch 2.3.0-1.el6 epel-testing 1.1 M Installing for dependencies: jakarta-commons-httpclient x86_64 1:3.1-0.7.el6_3 updates 587 k jakarta-commons-logging noarch 1.0.4-10.el6 base 52 k jakarta-oro x86_64 2.0.8-6.6.el6 base 191 k jsch noarch 0.1.41-2.2.el6 base 203 k jzlib x86_64 1.0.7-7.5.el6 base 123 k Transaction Summary ======================================================================================================================================================================== Install 5 Package(s) Upgrade 1 Package(s) Total download size: 2.2 M Is this ok [y/N]: y Downloading Packages: (1/6): apache-ivy-2.3.0-1.el6.noarch.rpm | 1.1 MB 00:00 (2/6): jakarta-commons-httpclient-3.1-0.7.el6_3.x86_64.rpm | 587 kB 00:00 (3/6): jakarta-commons-logging-1.0.4-10.el6.noarch.rpm | 52 kB 00:00 (4/6): jakarta-oro-2.0.8-6.6.el6.x86_64.rpm | 191 kB 00:00 (5/6): jsch-0.1.41-2.2.el6.noarch.rpm | 203 kB 00:00 (6/6): jzlib-1.0.7-7.5.el6.x86_64.rpm | 123 kB 00:00 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Total 1.0 MB/s | 2.2 MB 00:02 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : jzlib-1.0.7-7.5.el6.x86_64 1/7 Installing : jsch-0.1.41-2.2.el6.noarch 2/7 Installing : jakarta-commons-logging-1.0.4-10.el6.noarch 3/7 Installing : 1:jakarta-commons-httpclient-3.1-0.7.el6_3.x86_64 4/7 Installing : jakarta-oro-2.0.8-6.6.el6.x86_64 5/7 Updating : apache-ivy-2.3.0-1.el6.noarch 6/7 Cleanup : apache-ivy-2.1.0-1.el6.noarch 7/7 Verifying : jakarta-oro-2.0.8-6.6.el6.x86_64 1/7 Verifying : 1:jakarta-commons-httpclient-3.1-0.7.el6_3.x86_64 2/7 Verifying : apache-ivy-2.3.0-1.el6.noarch 3/7 Verifying : jakarta-commons-logging-1.0.4-10.el6.noarch 4/7 Verifying : jzlib-1.0.7-7.5.el6.x86_64 5/7 Verifying : jsch-0.1.41-2.2.el6.noarch 6/7 Verifying : apache-ivy-2.1.0-1.el6.noarch 7/7 Dependency Installed: jakarta-commons-httpclient.x86_64 1:3.1-0.7.el6_3 jakarta-commons-logging.noarch 0:1.0.4-10.el6 jakarta-oro.x86_64 0:2.0.8-6.6.el6 jsch.noarch 0:0.1.41-2.2.el6 jzlib.x86_64 0:1.0.7-7.5.el6 Updated: apache-ivy.noarch 0:2.3.0-1.el6 Complete! [root@localhost e1]# ant Buildfile: build.xml test: BUILD SUCCESSFUL Total time: 0 seconds Works like a charm. :) apache-ivy-2.3.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |