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
[-- Attachment #1 --] Quoting Mark Millard <marklmi@yahoo.com> (from Wed, 12 Apr 2023 22:28:13 -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 package. It was consistent no matter how often I was updating the ports tree. Poudriere always failed on port X which was depending on port Y (don't remember the names). The problem was, that port Y was build successfully but an extract of it was not having a file it was supposed to have. IIRC I fixed the issue by building the port Y manually, as re-building port Y with poudriere didn't change the outcome. So it seems this may not be specific to the most recent ZFS version, but could be an older issue. It may be the case that the more recent ZFS version amplifies the problem. It can also be that it is related to a specific use case in poudriere. I remember a recent mail which talks about poudriere failing to copy files in resource-limited environments, see https://lists.freebsd.org/archives/dev-commits-src-all/2023-April/025153.html While the issue you are trying to pin-point may not be related to this discussion, I mention it because it smells to me like we could be in a situation where a similar combination of unrelated to each other FreeBSD features could form a combination which triggers the issue at hand. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF [-- Attachment #2 --] -----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230413085253.Horde.bYgKkPjxGfDPP_pwWqnyTN2>