| 1 |
Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
|
| 3 |
> On 08/10/2015 10:24, covici@××××××××××.com wrote: |
| 4 |
> > John Campbell <jdc.rpv@×××.net> wrote: |
| 5 |
> > |
| 6 |
> >> On 10/07/2015 11:51 PM, covici@××××××××××.com wrote: |
| 7 |
> >>> In trying to emerge sysf-fs/zfs today I get the following |
| 8 |
> >>> [ebuild R *] sys-fs/zfs-9999::gentoo USE="rootfs -bash-completion |
| 9 |
> >>> -custom-cflags -debug (-kernel-builtin) -static-libs -test-suite" |
| 10 |
> >>> PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB |
| 11 |
> >>> [blocks B ] >=sys-fs/udev-init-scripts-28 |
| 12 |
> >>> (">=sys-fs/udev-init-scripts-28" is blocking sys-fs/zfs-9999) |
| 13 |
> >>> |
| 14 |
> >>> Total: 1 package (1 reinstall), Size of downloads: 0 KiB |
| 15 |
> >>> Conflict: 1 block (1 unsatisfied) |
| 16 |
> >>> |
| 17 |
> >>> * Error: The above package list contains packages which cannot be |
| 18 |
> >>> * installed at the same time on the same system. |
| 19 |
> >>> |
| 20 |
> >>> (sys-fs/zfs-9999:0/0::gentoo, ebuild scheduled for merge) pulled in by |
| 21 |
> >>> sys-fs/zfs required by @selected |
| 22 |
> >>> sys-fs/zfs |
| 23 |
> >>> |
| 24 |
> >>> (sys-fs/udev-init-scripts-30:0/0::gentoo, installed) pulled in by |
| 25 |
> >>> >=sys-fs/udev-init-scripts-25 required by |
| 26 |
> >>> (sys-apps/systemd-226-r1:0/2::gentoo, installed) |
| 27 |
> >>> |
| 28 |
> >>> |
| 29 |
> >>> Am I reading this correctly, or is there a way to satisfy the block? |
| 30 |
> >> |
| 31 |
> >> Just from your output and reading the ebuilds you can downgrade to |
| 32 |
> >> udev-init-scripts-27 |
| 33 |
> >> |
| 34 |
> > |
| 35 |
> > Thanks so much -- I wonder why portage did not mention this, but it |
| 36 |
> > works now -- thanks. |
| 37 |
> > |
| 38 |
> |
| 39 |
> Portage DID mention it, here: |
| 40 |
> |
| 41 |
> [blocks B ] >=sys-fs/udev-init-scripts-28 |
| 42 |
> (">=sys-fs/udev-init-scripts-28" is blocking sys-fs/zfs-9999) |
| 43 |
> |
| 44 |
> Note the ">=" and that you are running zfs-9999. Problems like blockers |
| 45 |
> are to be expected. |
| 46 |
> |
| 47 |
> The block is from zfs-9999, it's ebuild says it must block |
| 48 |
> >=udev-init-scripts-28, obviously zfs only works with udev-init-scripts |
| 49 |
> up to 27 (or 28 has new features in it that are not supported in zfs yet) |
| 50 |
> |
| 51 |
> systemd has nothing to do with this (your subject line), it is merely |
| 52 |
> the package that pulls in udev-init-scripts and that is what triggers |
| 53 |
> the block. Portage displays that so if the blocker is from an unexpected |
| 54 |
> package you can see why it's being pulled in. |
| 55 |
|
| 56 |
OK, thanks. |
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
Your life is like a penny. You're going to lose it. The question is: |
| 61 |
How do |
| 62 |
you spend it? |
| 63 |
|
| 64 |
John Covici |
| 65 |
covici@××××××××××.com |
Archives