lzma-utils blocking xz-utils with linux-sabayon-2.6.31

[Odysseus]

I like to keep my system up-to-date with portage as I have recompiled all of my system to my "native" pentium-m processor. I tried to run emerge world today and got this blocker

Code: Select all

Conflict: 2 blocks (2 unsatisfied)
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/local/portage/layman/sabayon

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  ('ebuild', '/', 'app-arch/xz-utils-4.999.9_beta', 'merge') pulled in by
    app-arch/xz-utils required by ('ebuild', '/', 'app-arch/libarchive-2.7.1', 'merge')
    app-arch/xz-utils required by ('ebuild', '/', 'sys-devel/libtool-2.2.6a', 'merge')
    app-arch/xz-utils required by ('ebuild', '/', 'media-libs/netpbm-10.46.00-r1', 'merge')
    (and 12 more)

  ('ebuild', '/', 'app-arch/lzma-utils-4.32.7', 'merge') pulled in by
    app-arch/lzma-utils required by ('ebuild', '/', 'sys-kernel/linux-sabayon-2.6.31', 'merge')


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

I then did some research online and found that lzma-utils package has been deprecated in favor of xz-utils many months ago. Xz-utils is fully backward compatible to lzma-utils which is no longer maintained. There are several notices about this in the Gentoo forums as well as in their bug reports and user groups. All state to switch to xz-utils ASAP. This dependency issue needs to be addressed here with Sabayon or else others will get caught in this dependency trap. The ebuilds for all of the Sabayon kernels and sources in the current tree need to be edited to reflect this change ASAP in order for anyone to stay current with portage.

I hope this helps

Ciao

Edit: I have reported this issue to the bug tracker.

[joost]

This is done in branch 5 (Entropy).
Not sure if it will make the final ISO.

I had to wait a bit to push this in our tree.

[Thev00d00]

lzma-utils package has been deprecated in favor of xz-utils

Heh, I did say to joost a while ago about switching...

[joost]

I know you did and you've seen what some gentoo-devs said about it.
So it was smart to wait a bit.

Anyway. case closed.

[Odysseus]

This is done in branch 5 (Entropy).
Not sure if it will make the final ISO.

I had to wait a bit to push this in our tree.

Weird, that you say this is already done in branch 5, because I hopped to branch 5 at least a week or two ago and I was running branch 5 when I discovered the issue a couple of days ago. I "equo update && emerge --sync && layman -S && emerge -uvND @system @world && revdep-rebuild" every few nights or so. That way portage doesn't get too far ahead of me. So I don't end up with my machine compiling all night and day trying to get caught up. (I used Sabayon core as quick way to get up and running), but have recompiled my system/kernel to my native Pentium-m processor. I like running Sabayon-sources as you don't change as often as portage (which seems to change kernel sources every few days or so).

So this must be a new decision, made within the last couple of days. I realized shortly after posting that the problem had an easy workaround as I was already running my own kernel. The issue was with the precompiled kernel's dependencies not the source files, so I just told equo to remove the problem kernel then updated without a hitch.

Thank you so much for the quick responses.

Ciao

[joost]

Well actually you reminded me to look at this.



For your information, most updates on sabayon branch 5 go into the limbo (testing) repository now.
Package diff between mainline repository and sabayon-limbo is around 700 packages already and its pretty much in sync with portage.

You could concider this work towards Sabayon 5.1

[Odysseus]

Well actually you reminded me to look at this.



For your information, most updates on sabayon branch 5 go into the limbo (testing) repository now.
Package diff between mainline repository and sabayon-limbo is around 700 packages already and its pretty much in sync with portage.

You could concider this work towards Sabayon 5.1

Then you've brought up another issue as well. How does one hop to limbo? I'm not adverse to working with unstable/broken packages, and could perhaps contribute to stabilization even if I'm only using Sabayon as my overlay. But if I'm unable to do that, running "limbo" instead of the released "stable" version would at least keep me more in line with portage ~x86 and allow me to discover/uncover and report problems quicker.

I have another idea/suggestion/question that I'm sure has been posed before but I've been unable to find a satisfactory solution by searching, but don't want to pollute this thread. So I'll start another here: viewtopic.php?f=54&t=18354&p=104761#p104761

TIA

Ciao

[joost]

Sure I'm not a support guy myself but IF you want to have DAILY UNTESTED entropy builds:

Code: Select all

repository|sabayon-limbo|Sabayon Linux Limbo|http://svn.sabayonlinux.org/entropy|http://svn.sabayonlinux.org/entropy


^^ 1 line

Add this line to /etc/entropy/repositories.conf and you will be 5+ but also have the RAW gentoo builds.

I don't have to support this unless something is really really broken, you can poke me in IRC.