Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1057936 - The package cannot be installed because it requires the wrong .so
Summary: The package cannot be installed because it requires the wrong .so
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: tango
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Christopher Meng
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 992772
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-26 04:04 UTC by Alberto Ruiz
Modified: 2015-02-18 11:19 UTC (History)
3 users (show)

Fixed In Version: derelict-3-26.201410303git9570453.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 11:19:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alberto Ruiz 2014-01-26 04:04:09 UTC
Description of problem:
Cannot install tango package because it depends on libphobos-ldc.so.60, but ldc-phobos provides .so.63

How reproducible:
Always

Steps to Reproduce:
1. excute dnf/yum install tango

Actual results:
$ sudo dnf install tango
Resolving dependencies
--> Starting dependency resolution
--> Finished dependency resolution
Error: nothing provides libphobos-ldc.so.60 needed by tango-2-12.20120821git7b92443.fc19.i686

Expected results:
tango should be installable

Comment 1 Michael Schwendt 2014-01-26 11:47:37 UTC
It must have been on the list of broken deps in the Rawhide report during F20 development for a long time. There are four failed builds since 2013-08-09:
  http://koji.fedoraproject.org/koji/packageinfo?packageID=10769

Current package in dist git master builds successfully for F20 x86_64. Change compared with f20 branch is

  +# https://github.com/ldc-developers/ldc/issues/116
  +ExcludeArch:    %{arm}

so I guess the failed builds in koji have been related to ARM. The old build failure logs have expired, and bug 992772 doesn't comment on the failure.

Comment 2 Fedora Update System 2014-03-10 22:13:25 UTC
derelict-3-26.201410303git9570453.fc20, dustmite-1-17.20140107git1f0a0cd.fc20, gtkd-2.0.0-45.20140301gitaf01da8.fc20, gl3n-0.20140301-11.fc20, ldc-2-56.20140305git6e908ff.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2014-3671/derelict-3-26.201410303git9570453.fc20,dustmite-1-17.20140107git1f0a0cd.fc20,gtkd-2.0.0-45.20140301gitaf01da8.fc20,gl3n-0.20140301-11.fc20,ldc-2-56.20140305git6e908ff.fc20

Comment 3 Tim Wegener 2014-03-17 02:43:54 UTC
Still broken (even with enabling updates-testing repo):

# yum install tango
Loaded plugins: etckeeper, langpacks
Resolving Dependencies
--> Running transaction check
---> Package tango.x86_64 0:2-12.20120821git7b92443.fc19 will be installed
--> Processing Dependency: libphobos-ldc.so.60()(64bit) for package: tango-2-12.20120821git7b92443.fc19.x86_64
--> Finished Dependency Resolution
Error: Package: tango-2-12.20120821git7b92443.fc19.x86_64 (ifedora)
           Requires: libphobos-ldc.so.60()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Comment 4 Fedora Update System 2014-03-27 04:51:00 UTC
derelict-3-26.201410303git9570453.fc20, dustmite-1-17.20140107git1f0a0cd.fc20, gtkd-2.0.0-45.20140301gitaf01da8.fc20, gl3n-0.20140301-11.fc20, ldc-2-56.20140305git6e908ff.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Tim Wegener 2014-03-30 22:26:03 UTC
This bug should not have been closed. The problem still persists:


yum install updates-testing tango
...
Resolving Dependencies
--> Running transaction check
---> Package tango.x86_64 0:2-12.20120821git7b92443.fc19 will be installed
--> Processing Dependency: libphobos-ldc.so.60()(64bit) for package: tango-2-12.20120821git7b92443.fc19.x86_64
--> Finished Dependency Resolution
Error: Package: tango-2-12.20120821git7b92443.fc19.x86_64 (ifedora)
           Requires: libphobos-ldc.so.60()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Comment 6 Michael Schwendt 2014-03-31 09:03:00 UTC
Reproducible also with F20:

Error: Package: tango-2-12.20120821git7b92443.fc19.x86_64 (fedora)
           Requires: libphobos-ldc.so.60()(64bit)

The linked bodhi ticket for F20 doesn't include a new build for tango.

And the original report mentions F19 builds.

Comment 7 Alberto Ruiz 2014-05-01 12:38:23 UTC
Seriously guys, if we cannot fix this we should probably remove the package altogether, I opened this bug _5 months_ ago and the package is still broken.

Comment 8 Tim Wegener 2014-05-03 11:51:41 UTC
The fix for this is simple:

- Update the source tarball from current git, so that it compiles with current ldc version.

- Rebuild the RPM package against current F20 packages.


Rough instructions if others want to work around this in the meantime:

(assuming %_topdir in ~/.rpmmacros points to $HOME/rpmbuild, and that rpmdevtools has been installed)

# Get the SRPM:
yumdownloader --source tango

# Get the snapshot tango code from the git repo:
git clone git://github.com/SiegeLord/Tango-D2.git
cd Tango-D2
# Find current revision:
git rev-parse --short HEAD
git checkout d170ee4
# Generate an updated tango tarball:
git archive --prefix=tango-20140404gitd170ee4/ HEAD --format=tar | xz > ../tango-20140404gitd170ee4.xz
# Copy the tarball to the rpmbuild SOURCES directory:
cp ../tango-20140404gitd170ee4.xz ~/rpmbuild/SOURCES/


Then edit ~/rpmbuild/SPECS/tango.spec and update the following fields to match the tango revision:

%global     alphatag            20140404
%global     tango_revision      gitd170ee4


Now rebuild the RPM:

rpmbuild -ba ~/rpmbuild/SPECS/tango.spec


Then install the new RPM:

yum install .../rpmbuild/RPMS/x86_64/tango-2-12.20140404gitd170ee4.fc20.x86_64.rpm

Comment 9 Tim Wegener 2014-05-03 12:00:12 UTC
Or even easier:

Download the appropriate current RPM from:

http://koji.fedoraproject.org/koji/buildinfo?buildID=503394

E.g.:

http://kojipkgs.fedoraproject.org//packages/tango/2/17.fc20/x86_64/tango-2-17.fc20.x86_64.rpm

...and install via yum: 'yum install tango-2-17.fc20.x86_64.rpm'


It's not clear to me why that hasn't been pushed to the repos.
It's been available there since 09 Mar 2014.

Comment 10 Michael Schwendt 2014-05-03 12:52:56 UTC
> It's not clear to me why that hasn't been pushed to the repos.
> It's been available there since 09 Mar 2014.

 - "koji" is the Fedora Build System.

 - "bodhi" is the Fedora Updates System, where builds made within koji need to be submitted as updates. That hasn't happened for Fedora 20 yet:
https://admin.fedoraproject.org/updates/search/tango

Comment 11 Tim Wegener 2014-05-03 14:03:27 UTC
(In reply to Michael Schwendt from comment #10)
> > It's not clear to me why that hasn't been pushed to the repos.
> > It's been available there since 09 Mar 2014.
...
>  - "bodhi" is the Fedora Updates System, where builds made within koji need
> to be submitted as updates. That hasn't happened for Fedora 20 yet:
> https://admin.fedoraproject.org/updates/search/tango


Can someone please "make it so"?

Comment 12 Michael Schwendt 2014-05-04 09:57:40 UTC
Normally, the package owner(s) would do that:
https://admin.fedoraproject.org/pkgdb/acls/name/tango

If they don't respond, that can be an indication that they don't want to maintain the packages anymore and would welcome somebody else signing up as new maintainer or co-maintainer.

Comment 13 MERCIER Jonathan 2014-05-20 16:58:51 UTC
Hi sorry for the time. I took back they are some day this package i will take a look if problem exist yet.

Comment 14 Fedora Update System 2014-05-20 17:40:15 UTC
tango-2-18.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/tango-2-18.fc19

Comment 15 Fedora Update System 2014-05-21 23:18:30 UTC
Package tango-2-18.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tango-2-18.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-6545/tango-2-18.fc19
then log in and leave karma (feedback).

Comment 16 Tim Wegener 2014-05-22 05:37:32 UTC
Can you please submit an update for Fedora 20 as well?

Comment 17 Fedora End Of Life 2015-01-09 22:40:57 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 18 Fedora End Of Life 2015-02-18 11:19:42 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.