public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: media-gfx/imagemagick-6.4.0.6 and media-video/transcode-1.0.4
Date: Fri, 4 Jul 2008 12:14:43 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.07.04.12.14.42@cox.net> (raw)
In-Reply-To: 486E0686.1050900@asyr.hopto.org

Thanasis <thanasis@asyr.hopto.org> posted 486E0686.1050900@asyr.hopto.org,
excerpted below, on  Fri, 04 Jul 2008 14:16:22 +0300:

> A few days ago, after doing a
>  emerge -DNu world
> portage upgraded media-gfx/imagemagick to version 6.4.0.6. Since then,
> doing a
> revdep-rebuild
> always tries to rebuild media-video/transcode-1.0.4, but it fails as it
> tries to link to libraries of the older imagemagick-6.3.8.3-r1 no longer
> available.

Hmm... I've not seen any problems, but then I'm on ~arch and always do --
deep so my libraries are all kept updated too.  I currently have merged: 

Calculating dependencies ... done!
[ebuild   R   ] media-gfx/imagemagick-6.4.2.0
[ebuild   R   ] media-video/transcode-1.0.6_rc2-r1

So ~arch is several bumps ahead of where you are with stable and perhaps 
even stale stable due to not using --deep.

If it's trying to link to even older versions, you probably have stale 
*.la files left around, for some reason.  I'd look into that, using 
equery belongs or whatever to double-check that they aren't attached to 
any package before deleting them.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-07-04 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 11:16 [gentoo-amd64] media-gfx/imagemagick-6.4.0.6 and media-video/transcode-1.0.4 Thanasis
2008-07-04 12:14 ` Duncan [this message]
2008-07-04 12:36 ` Ferris McCormick
2008-07-07  3:34 ` Andy Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2008.07.04.12.14.42@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox