From nobody Fri Feb 3 15:48:35 2023 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7g740CBrz3kRdH for ; Fri, 3 Feb 2023 15:48:48 +0000 (UTC) (envelope-from ryan@ixsystems.com) Received: from mail-oa1-x2d.google.com (mail-oa1-x2d.google.com [IPv6:2001:4860:4864:20::2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7g735Qcsz3G9Q for ; Fri, 3 Feb 2023 15:48:47 +0000 (UTC) (envelope-from ryan@ixsystems.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-15ff0a1f735so7100985fac.5 for ; Fri, 03 Feb 2023 07:48:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8QbpX6IADm4AGSsLF5wBX3lftHIv3hfERIcJNcOIJnA=; b=TMUnKEJulmzGZ14Jw2QMFjcj9uyEj5VTx85/oviOJVqobQ4hYIWMrvEk1PSDl3v42a ep/sy9nUgZOHuJAs72XjU55Ga8QQ8tuZt8xwA8xU+DTNPBzZpjNFsMkJ7+YgFyt/9B2F h49NTKoGrC5l6BFXLeznIMXSiHBBMsR745HHejbvesx5ZZhPWZ1zgCQGda7+RZAhxOqU OHAtokwZsW4GfK0o/xzDZTio2be4NgtK0wxGz2sVRwU4cuLVl4Dr3m5jHjhn/bZbxL4o hz7VFzNcVNsQfB0sg833ndZoUdlxXEvlm4cWRbKGR8tlh3pKzBUmMFdI7RnDfxdVSN7B obQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8QbpX6IADm4AGSsLF5wBX3lftHIv3hfERIcJNcOIJnA=; b=4MNKJJ9B+51Zwdk0CLThmmtx6gYwdIxDe70xnG1kEW3DtumEJ7s0PepVbVOswip/un woWCYyYLFOtXiyGSqSw/rN0zAJFpChRsXJ+tDnoM9/zQKwMLGmGZTMKNJnnWoAEQXt47 z/jJitrK4V9io6UI7FFMzgI6/v2Hs2q7DPt90hye4yx0WcvkfCwBthy9LpuZ46VQl8PH v2/srJl+RRNccNoODY33pXfFbqaEF8uA+TmdhsQ2rJVJ/6RoI2ryaLVcIWRxPASL/UUm FDCRxx3h3rJKsQ+Oxdxop/uzxmFu7OEx/iJ7gSp87vZ4wAEVjFesdgHqA+HddNQEXRUd YYUw== X-Gm-Message-State: AO0yUKU1Sl6Ul9C6HTl0p2Ih5jNCpIKA5bpkrQX5gUQ2IPe4RRKy9JmR PqMOi8U/qakBPJbrrnCMDdTUMaHUfayF0f+MQyYrDA== X-Google-Smtp-Source: AK7set8vwAyUn54YiGgUJxauNvIwAu0rrpo+XLP3h6ZfiFopVtvMcCSL84VLsUBtIq43rgFqVJOkqQOJ1ZkkGzbhmBA= X-Received: by 2002:a05:6870:b48d:b0:15f:df61:5e9c with SMTP id y13-20020a056870b48d00b0015fdf615e9cmr840367oap.282.1675439326106; Fri, 03 Feb 2023 07:48:46 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 References: <20230202103651.Horde.yAqcbqzfHTSd2KbPO-uxy_y@webmail.leidinger.net> <20230202151432.Horde.B3fD_ijUP7hDeGcTs2Ymmp1@webmail.leidinger.net> <20230203082329.Horde.436Pq-oJxzQuK1EXGeqff_1@webmail.leidinger.net> In-Reply-To: <20230203082329.Horde.436Pq-oJxzQuK1EXGeqff_1@webmail.leidinger.net> From: Ryan Moeller Date: Fri, 3 Feb 2023 10:48:35 -0500 Message-ID: Subject: Re: py-libzfs build failure on current, zpool_search_import() missing To: Alexander Leidinger Cc: Alan Somers , current@freebsd.org, fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4P7g735Qcsz3G9Q X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > The build still fails on -current as of end of Jan with "too few > argument to function call, expected 4, have 3" for zfs_iter_filesystems. > > Is a patch for openzfs in -current missing? I haven't seen a commit to > -current in openzfs in the last 2 days. The openzfs changes aren't that recent, but the py-libzfs port has been out of date for a while. I'll spin up a new snapshot VM and fix whatever is still broken. -- Ryan Moeller iXsystems, Inc. OS Developer Email: ryan@iXsystems.com