Date: Sun, 22 Oct 2023 13:50:45 +0000 From: void <void@f-m.fm> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: rust 1.72.0 in poudriere-devel keeps getting rebuilt Message-ID: <d03195a6-3b51-4eae-8ff2-e3b8b3d4f18f@app.fastmail.com> In-Reply-To: <42EF6FE9-AF6B-46A1-A4EF-86A1EC74DABF@yahoo.com> References: <d94d5b82-1d7c-4c8f-b846-b7b7cf94e996@app.fastmail.com> <057159E4-7E05-49A3-8520-3E2815C4A6A0@yahoo.com> <d08fb10a-62c6-4202-a799-c9548068c98c@app.fastmail.com> <42EF6FE9-AF6B-46A1-A4EF-86A1EC74DABF@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Oct 2023, at 04:21, Mark Millard wrote: > Please report historical examples of what poudriere is telling you > about that, such as: > > [00:00:10] Deleting rust-1.72.0.pkg: missing dependency: curl-8.3.0_1 Before initially posting about the issue, I completely removed and reinstalled poudriere and its data in an effort to solve it on my own, so i don't have the historical data. I thought maybe I'd broken the installation somehow, so started afresh. My confusion was thinking "oh rust is being rebuilt all the time, what's changing in rust that's causing this because the version numbers for rust are identical and surely it would change if a dependency (in contrast to an option) changed." I created a brand new poudriere jail instance called testvm and told it to install one port: textproc/ripgrep which i know depends on rust. rust was downloaded and got deleted because of curl [00:01:05] Package fetch: Using cached copy of rust-1.72.0 [00:01:05] Sanity checking the repository [00:01:06] Deleting rust-1.72.0.pkg: missing dependency: curl-8.4.0 [00:01:06] Deleting stale symlinks... done [00:01:06] Deleting empty directories... done [00:01:06] Package fetch: Generating logs for fetched packages [00:01:14] Unqueueing existing packages [00:01:14] Unqueueing orphaned build dependencies [00:01:14] Sanity checking build queue [00:01:14] Processing PRIORITY_BOOST [00:01:14] Balancing pool [testvm-default] [2023-10-22_12h56m09s] [balancing_pool:] Queued: 26 Built: 0 Failed: 0 Skipped: 0 Ignored: 0 Fetched: 25 Tobuild: 1 Time: 00:01:08 [00:01:14] Recording filesystem state for prepkg... done [00:01:14] Building 1 packages using up to 1 builders [00:01:14] Hit CTRL+t at any time to see build progress and stats [00:01:14] [01] [00:00:00] Builder starting [00:01:15] [01] [00:00:01] Builder started [00:01:15] [01] [00:00:00] Building ports-mgmt/pkg | pkg-1.20.8 [00:02:32] [01] [00:01:17] Finished ports-mgmt/pkg | pkg-1.20.8: Success [00:02:33] Stopping 1 builders [00:02:33] Creating pkg repository [00:02:33] Signing repository with key: /usr/local/etc/ssl/keys/poudriere.key Creating repository in /tmp/packages: 100% Packing files for repository: 100% [00:02:33] Signing pkg bootstrap with method: pubkey [00:02:33] Committing packages to repository: /usr/local/poudriere/data/packages/testvm-default/.real_1697975922 via .latest symlink [00:02:33] Removing old packages [00:02:33] Built ports: ports-mgmt/pkg [00:02:33] Fetched ports: devel/libedit textproc/ripgrep devel/libuv devel/libffi archivers/brotli lang/ruby31 devel/ruby-gems textpro c/rubygem-asciidoctor print/indexinfo dns/libpsl www/libnghttp2 security/libssh2 devel/pkgconf archivers/liblz4 math/mpdecimal textpro c/expat2 dns/public_suffix_list textproc/libyaml devel/jsoncpp converters/libiconv dns/libidn2 devel/libunwind devel/autoconf-switch d evel/libunistring devel/pcre2 [testvm-default] [2023-10-22_12h56m09s] [committing:] Queued: 26 Built: 1 Failed: 0 Skipped: 0 Ignored: 0 Fetched: 25 Tobuild: 0 Time: 00:02:28 [00:02:33] Logs: /usr/local/poudriere/data/logs/bulk/testvm-default/2023-10-22_12h56m09s Then, ran poudriere bulk with ftp/curl, same sort of result, the package was fetched, not built. Then another build - but just with lang/rust, same result now. So either the problem is solved at the moment or I've misunderstood/misreported it. I understand that if a dependency *of rust* changes, then rust will need local building if that change is in the ports tree but not on pkg.freebsd.org, which appears to be what happened with curl. What *appeared to be happening* before was that packages that use rust (i.e. are dependent *on* rust) changed and that seemed to trigger the rust rebuilding and I couldn't understand why. > This is the way of figuring out what leads to the updates the most > often. It might lead to suggestions for the rust port for avoiding > depending on things that change more frequently if there are > reasonable alternatives. Just my $0.02 but I think version number should change if a dependency of that pkg changes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d03195a6-3b51-4eae-8ff2-e3b8b3d4f18f>