Alan McKinnon <alan.mckin...@gmail.com> wrote:

> On 08/10/2015 10:24, cov...@ccs.covici.com wrote:
> > John Campbell <jdc....@cox.net> wrote:
> > 
> >> On 10/07/2015 11:51 PM, cov...@ccs.covici.com wrote:
> >>> In trying to emerge sysf-fs/zfs today I get the following
> >>> [ebuild   R   *] sys-fs/zfs-9999::gentoo  USE="rootfs -bash-completion
> >>> -custom-cflags -debug (-kernel-builtin) -static-libs -test-suite"
> >>> PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB
> >>> [blocks B      ] >=sys-fs/udev-init-scripts-28
> >>> (">=sys-fs/udev-init-scripts-28" is blocking sys-fs/zfs-9999)
> >>>
> >>> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> >>> Conflict: 1 block (1 unsatisfied)
> >>>
> >>>   * Error: The above package list contains packages which cannot be
> >>>   * installed at the same time on the same system.
> >>>
> >>>    (sys-fs/zfs-9999:0/0::gentoo, ebuild scheduled for merge) pulled in by
> >>>      sys-fs/zfs required by @selected
> >>>      sys-fs/zfs
> >>>
> >>>    (sys-fs/udev-init-scripts-30:0/0::gentoo, installed) pulled in by
> >>>      >=sys-fs/udev-init-scripts-25 required by
> >>>    (sys-apps/systemd-226-r1:0/2::gentoo, installed)
> >>>
> >>>
> >>> Am I reading this correctly, or is there a way to satisfy the block?
> >>
> >> Just from your output and reading the ebuilds you can downgrade to
> >> udev-init-scripts-27
> >>
> > 
> > Thanks so much -- I wonder why portage did not mention this, but it
> > works now -- thanks.
> > 
> 
> Portage DID mention it, here:
> 
> [blocks B      ] >=sys-fs/udev-init-scripts-28
> (">=sys-fs/udev-init-scripts-28" is blocking sys-fs/zfs-9999)
> 
> Note the ">=" and that you are running zfs-9999. Problems like blockers
> are to be expected.
> 
> The block is from zfs-9999, it's ebuild says it must block
> >=udev-init-scripts-28, obviously zfs only works with udev-init-scripts
> up to 27 (or 28 has new features in it that are not supported in zfs yet)
> 
> systemd has nothing to do with this (your subject line), it is merely
> the package that pulls in udev-init-scripts and that is what triggers
> the block. Portage displays that so if the blocker is from an unexpected
> package you can see why it's being pulled in.

OK, thanks.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         cov...@ccs.covici.com

Reply via email to