Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Apr 2023 08:52:53 +0200
From:      Alexander Leidinger <Alexander@leidinger.net>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        Mateusz Guzik <mjguzik@gmail.com>, vishwin@freebsd.org, dev-commits-src-main@freebsd.org, Current FreeBSD <freebsd-current@freebsd.org>, Cy Schubert <Cy.Schubert@cschubert.com>
Subject:   Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75
Message-ID:  <20230413085253.Horde.bYgKkPjxGfDPP_pwWqnyTN2@webmail.leidinger.net>
In-Reply-To: <C8E4A43B-9FC8-456E-ADB3-13E7F40B2B04@yahoo.com>
References:  <C8E4A43B-9FC8-456E-ADB3-13E7F40B2B04.ref@yahoo.com> <C8E4A43B-9FC8-456E-ADB3-13E7F40B2B04@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format and has been PGP signed.

--=_XJcTNEGi5tSrLXujDCZB1br
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Quoting Mark Millard <marklmi@yahoo.com> (from Wed, 12 Apr 2023=20=20
22:28:13=20-0700):

> A fair number of errors are of the form: the build
> installing a previously built package for use in the
> builder but later the builder can not find some file
> from the package's installation.

As a data point, last year I had such issues with one particular=20=20
package.=20It was consistent no matter how often I was updating the=20=20
ports=20tree. Poudriere always failed on port X which was depending on=20=
=20
port=20Y (don't remember the names). The problem was, that port Y was=20=20
build=20successfully but an extract of it was not having a file it was=20=
=20
supposed=20to have. IIRC I fixed the issue by building the port Y=20=20
manually,=20as re-building port Y with poudriere didn't change the=20=20
outcome.

So=20it seems this may not be specific to the most recent ZFS version,=20=
=20
but=20could be an older issue. It may be the case that the more recent=20=
=20
ZFS=20version amplifies the problem. It can also be that it is related=20=
=20
to=20a specific use case in poudriere.

I remember a recent mail which talks about poudriere failing to copy=20=20
files=20in resource-limited environments, see=20=20
https://lists.freebsd.org/archives/dev-commits-src-all/2023-April/025153.ht=
ml
While=20the issue you are trying to pin-point may not be related to this=20=
=20
discussion,=20I mention it because it smells to me like we could be in a=20=
=20
situation=20where a similar combination of unrelated to each other=20=20
FreeBSD=20features could form a combination which triggers the issue at=20=
=20
hand.

Bye,
Alexander.

--=20
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF

--=_XJcTNEGi5tSrLXujDCZB1br
Content-Type: application/pgp-signature
Content-Description: Digitale PGP-Signatur
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIzBAABCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmQ3psQACgkQEg2wmwP4
2IYtNA//TmbSVqDv8LUhp46+N91wzieAFOeiJqQSMIvbmmn8fALAQyCe5qfczV3z
SDsNI6JwNAUxWC6e4v933DoTH56D6ychOigtANR4IMhJt3XkWnsKnz8gby8/JEMG
g1ua2lRRApd0b8cNsoadgWPIWw+y9TiVNrdCWivYkw0IfvpOZmLvsVgghmMIof4Y
8U4T+p9kyw2aezqBftGbncxGHcwIErZWAaYUG7gnt00jX5Nfr2Xg6Fu3LCSwge0U
g5pECfZdmlCMHRsjVm+K2j01a7QWOwzLCFuPZKhMVThazYeaP8YMqSpVLYihwGnG
ntIMz0s1iLe8T+PD/+Y/nNzMi2VM5YQ5TSq8Hhbc/DQGUBhn2nesCdhKWGV5UEUK
qx62XOlSdClZxweShi3ewNfmqqsRaewF5kjZRPj88UBqWvxCQg8LsqzKQDbuSbIN
tj6dvyA9jT8r4DbhLw+VQnczihQR5sZiEC6fre2yD0pTX/3vCYy9BVQqfkFYRcMh
6Uv5O+gfwCrO/QW7seq1wt9ReGCWG3liskakwszlHnAnYiQcY6QA3035M8KpdQ5x
kko69pCpAqaRYP3RKXda//naTzWLNApRa0aOk1RcDQbBSKVEedSqbCPcAWu8nyYl
jFff14YvJ8vVxUK1JMd4XJxJx1iaPSsuvWaSWxFeItO6TbNQxww=
=kBIp
-----END PGP SIGNATURE-----

--=_XJcTNEGi5tSrLXujDCZB1br--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230413085253.Horde.bYgKkPjxGfDPP_pwWqnyTN2>