Clemente Aguiar posted
<[EMAIL PROTECTED]>,
excerpted below,  on Sat, 28 Jan 2006 15:10:20 +0000:

> 
> A few weeks ago, with the installation of kde, I emerged hal, dbus and
> ivan.
> 
> I update the system regularly with:
> 
> emerge -uD world
> 
> Recently this command resulted in an updated hal and dbus.
> 
> But now when I "pretend" to update it wants to downgrade these two
> packages again, and I found that the culprit is ivman.
> 
> # emerge -uDp --tree world
> 
> These are the packages that I would merge, in reverse order:
> 
> Calculating world dependencies ...done!
> [nomerge      ] sys-apps/ivman-0.5_pre2
> [ebuild     UD]  sys-apps/hal-0.4.8 [0.5.5.1-r3]
> [ebuild     UD]   sys-apps/dbus-0.23.4-r1 [0.60-r3]
> 
> What can I do to solve this upgrade/downgrade "problem"?

$grep hal /p/sys-apps/ivman/ivman-0.5_pre2.ebuild
         =sys-apps/hal-0.4*"
        einfo "existing rules, replace %m with \$hal.volume.mount_point\$ and"
        einfo "replace %d with \$hal.block.device\$.  Individual users may also"

That's the problem right there.  It's requiring hal-0.4* specifically, no
higher, and you have higher so it wants to downgrade you.

You may wish to consider adding sys-apps/ivman to package.keywords as
~amd64.  This will give you the 0.6.8 version, which deps on
>=sys-apps/hal-0.4.0.  However, a quick grep reveals the following warning
in the ebuild, so be aware:

        if has_version "<sys-apps/hal-0.5.0"; then
                einfo "Ivman was built against HAL 0.4.x.  If you later upgrade 
to HAL 0.5,"
                einfo "you must re-merge Ivman."
                echo
        else
                einfo "Ivman was built against HAL 0.5.x.  If you later 
downgrade to HAL 0.4,"
                einfo "you must re-merge Ivman."
                echo

-- 
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 in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
[email protected] mailing list

Reply via email to