From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-167912-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id A2AD413888F
for <garchives@archives.gentoo.org>; Thu, 8 Oct 2015 08:38:04 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 8517321C001;
Thu, 8 Oct 2015 08:37:52 +0000 (UTC)
Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 38A18E07F5
for <gentoo-user@lists.gentoo.org>; Thu, 8 Oct 2015 08:37:51 +0000 (UTC)
Received: by lbos8 with SMTP id s8so38347766lbo.0
for <gentoo-user@lists.gentoo.org>; Thu, 08 Oct 2015 01:37:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-type:content-transfer-encoding;
bh=HEbCrc+uFkH183Vjq9pDQDFgXjHmez6mElQzgDBHADA=;
b=MdtlnKIXEYrB1/+PI43rGrWAt/5Xlfyf1iQH2YSTQVev1k5haYKcNn8SBN9n5t1qcU
A810i4umnzO0X1x0NLQpQCDl4i+rqCl249ufi0Liolv8Z7wyHZU1xSqhI/JFBcuX0whr
i7Y8Zzc6hN34MsQ0JKySLH7DfOgOI05J90iukG5nYec3C5iFjTwkuNeeYIsNyedgIl8a
c7yU6oqz2rRphsruNHx7WCbW52ciQvvk0FCUtxRU7UrMWiRpUJvUewIH7OuLyBKgn1bT
xEYQGVi5O90UCuMTQE5qRHmlSaGiP1zUHZZoYGA/Sb8flYKgftgUQormxCNK7iscetY/
uPIw==
X-Received: by 10.112.168.228 with SMTP id zz4mr2971160lbb.73.1444293469781;
Thu, 08 Oct 2015 01:37:49 -0700 (PDT)
Received: from [172.20.0.41] ([105.210.54.110])
by smtp.googlemail.com with ESMTPSA id a138sm7112814lfe.19.2015.10.08.01.37.47
for <gentoo-user@lists.gentoo.org>
(version=TLSv1/SSLv3 cipher=OTHER);
Thu, 08 Oct 2015 01:37:49 -0700 (PDT)
Subject: Re: [gentoo-user] is zfs no longer compatible with systemd?
To: gentoo-user@lists.gentoo.org
References: <SWry1r00p1kktTk01WrzEG> <561619FB.8090003@cox.net>
<4426.1444292691@ccs.covici.com>
From: Alan McKinnon <alan.mckinnon@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56162B38.1000101@gmail.com>
Date: Thu, 8 Oct 2015 10:37:12 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.3.0
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
In-Reply-To: <4426.1444292691@ccs.covici.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Archives-Salt: c652fd20-4050-432b-911c-29411fdf0518
X-Archives-Hash: 05ec7729903b013b618080bbe3fefeda
On 08/10/2015 10:24, covici@ccs.covici.com wrote:
> John Campbell <jdc.rpv@cox.net> wrote:
>
>> On 10/07/2015 11:51 PM, covici@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.
--
Alan McKinnon
alan.mckinnon@gmail.com