Bug 1083157 - rebuild against new ImageMagick
Summary: rebuild against new ImageMagick
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1082411
TreeView+ depends on / blocked
 
Reported: 2014-04-01 15:00 UTC by Tim Waugh
Modified: 2014-04-03 17:36 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-03 17:36:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tim Waugh 2014-04-01 15:00:59 UTC
Description of problem:
When trying to rebuild a2ps I see the following failure:

Getting requirements for a2ps-4.14-23.fc21.src
 --> gperf-3.0.4-7.fc20.x86_64
 --> 1:emacs-24.3-14.fc21.x86_64
 --> flex-2.5.37-4.fc21.x86_64
 --> libtool-2.4.2-23.fc21.x86_64
 --> texinfo-5.2-2.fc21.x86_64
 --> groff-1.22.2-8.fc21.x86_64
 --> ImageMagick-6.8.8.10-1.fc21.x86_64
 --> groff-perl-1.22.2-8.fc21.x86_64
 --> 1:cups-1.7.1-8.fc21.x86_64
 --> gettext-0.18.3.2-1.fc21.x86_64
 --> bison-3.0.2-1.fc21.x86_64
 --> psutils-1.23-2.fc21.x86_64
 --> 3:texlive-dvips-svn32665.0-8.fc21.noarch
 --> 3:texlive-latex-svn32901.0-8.fc21.noarch
 --> html2ps-1.0-0.16.b7.fc21.noarch
Error: Package: 1:emacs-24.3-14.fc21.x86_64 (fedora)
           Requires: libMagickWand-6.Q16.so.1()(64bit)
Error: Package: 1:emacs-24.3-14.fc21.x86_64 (fedora)
           Requires: libMagickCore-6.Q16.so.1()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

However, the current version of ImageMagick provides "*.so.2" versions of those libraries. I think emacs needs a rebuild to pick up the newer ImageMagick library sonames.

Version-Release number of selected component (if applicable):
emacs-24.3-14.fc21

Additional info:
This is delaying a security fix being built in rawhide.

Comment 1 Tim Waugh 2014-04-03 17:36:55 UTC
Seems to be fixed now.


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