From owner-freebsd-questions@freebsd.org Sun Dec 15 19:25:32 2019 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4CCF21CC13B for ; Sun, 15 Dec 2019 19:25:32 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47bZB24qsSz3M22 for ; Sun, 15 Dec 2019 19:25:30 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: by mail-qv1-xf2e.google.com with SMTP id z3so1851566qvn.0 for ; Sun, 15 Dec 2019 11:25:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seibercom.net; s=google; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :organization:mime-version; bh=5LQVdi6t4m0DtwhxO+EmZTi3w36SujcLzSCgV0zxAo4=; b=bfhv55e49vCkFSL45nC90rUQ3k2FQuPMyy8zY38E4FwBomFuoBonRyGk40yh4x5cBc rAOT3WdjDypzuQFqhfRfl/f8IrN0MwjJ1BA9TJkWpAW3tHI5Nw/ZIV+tbsRySzvMZvSc aPrOwdgXDcXl2V4e8Ko1AQJbxQfvXBP2lR2C8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:reply-to:organization:mime-version; bh=5LQVdi6t4m0DtwhxO+EmZTi3w36SujcLzSCgV0zxAo4=; b=ONdCyJz1G+Bwe8fHO5zmjdR3Wfpv/+RdYon2+cqrQ4nPvS8kR47hFdTia+VVO2vTZj scDlXCnpNA73atwJZBjiNmBQUuqhNAl6m1Dn/FVE2ZZCmFe6Rk5NBvfSCIkIi95z8Z0t Epcp8nzFe9M/2Z45swLGnTipAdABM5DolUCjHbdlk6DMxOMEBbk54/LElzScvEH1W9oc zaFCD36SHKgUVlJY2OA+4TWa++YtqPxzjYf/HNvW6UcsEQ4tx6/K8fKzMD4rwXSHQxsw unHChbCDkhrCosjWG0h91pNlzj5NakQPv/hWgCuaon5xsHbSBbrq1b4UBRy+yhnJCFUu w4og== X-Gm-Message-State: APjAAAVzzAS45vxPC18Xvn6ym2MBuMuW3am7ubvzlAVGCNml+jMTprJn 76LRF33C5G3K564Oq+/ECAXx4q3BSps= X-Google-Smtp-Source: APXvYqyzzpkPekCu1taixse6qDfw1TVTGJ79Y2PFlIOBgF+csRtPtLB042aBSOi0ngKgDHDq+5g6dQ== X-Received: by 2002:a05:6214:8cb:: with SMTP id da11mr21636200qvb.228.1576437928983; Sun, 15 Dec 2019 11:25:28 -0800 (PST) Received: from scorpio.seibercom.net (cpe-174-109-225-250.nc.res.rr.com. [174.109.225.250]) by smtp.gmail.com with ESMTPSA id e64sm5954614qtd.45.2019.12.15.11.25.27 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 15 Dec 2019 11:25:28 -0800 (PST) Received: from localhost (HP-ENVY [192.168.0.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: jerry@seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 47bZ9y2Cthz4QmB for ; Sun, 15 Dec 2019 14:25:26 -0500 (EST) Date: Sun, 15 Dec 2019 14:25:18 -0500 From: Jerry To: freebsd-questions@freebsd.org Subject: Re: Why does poudriere insist on rebuilding the same packages over and over Message-ID: <20191215142518.000002c9@seibercom.net> In-Reply-To: <2f765131-c56f-f963-2f28-22d71e857ab8@FreeBSD.org> References: <20191215075741.5df439b4@scorpio> <2f765131-c56f-f963-2f28-22d71e857ab8@FreeBSD.org> Reply-To: freebsd-questions@freebsd.org Organization: seibercom.net X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/OdsNriTw32JSHF182r4Y0yB"; protocol="application/pgp-signature" X-Rspamd-Queue-Id: 47bZB24qsSz3M22 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=seibercom.net header.s=google header.b=bfhv55e4; dmarc=none; spf=pass (mx1.freebsd.org: domain of jerry@seibercom.net designates 2607:f8b0:4864:20::f2e as permitted sender) smtp.mailfrom=jerry@seibercom.net X-Spamd-Result: default: False [-0.43 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd-questions@freebsd.org]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[seibercom.net:+]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-0.83)[ipnet: 2607:f8b0::/32(-2.20), asn: 15169(-1.91), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RECEIVED_SPAMHAUS_PBL(0.00)[250.225.109.174.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; REPLYTO_EQ_TO_ADDR(5.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[seibercom.net:s=google]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[seibercom.net]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Dec 2019 19:25:32 -0000 --Sig_/OdsNriTw32JSHF182r4Y0yB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, 15 Dec 2019 14:37:39 +0000, Matthew Seaman commented: >On 15/12/2019 12:57, Gerard E. Seibert wrote: >> This is probably a dumb question, but I'll ask it anyway. Why does >> 'poudriere' insist on rebuild the same package, over and over, when >> there has been no change. >>=20 >> EXAMPLE: >>=20 >> This morning I decided to install /usr/ports/x11/xscreensaver. >> Poudriere insisted on rebuilding hundreds of ports, >> including "ports-mgmt/pkg", even though they had not changed. I had >> just updated the ports tree with poudriere and updated all of the >> files on my system. There was no reason to rebuild all of the >> existing files. It seems that the "ports-mgmt/pkg" file is rebuild >> every time poudriere runs. >>=20 >> Is there a configuration setting to stop? It wastes a lot of time and >> resources to continually rebuild everything. >>=20 >> NOTE: >>=20 >> I made on change on an installed port the other day, and poudriere >> insisted on rebuild 1039 ports. That is just crazy. =20 > >That's not normal. poudriere shouldn't need to rebuild as much as that >-- and anything it does rebuild it will print out the reason why. In >particular, seeing pkg(8) continually being rebuilt without good reason >is a sign of something gone awry. > >Off-hand I can think of three reasons off hand why poudriere might want >to rebuild /every/ package: > > 1) You updated the poudriere jail -- that is, you ran > > poudriere jail -j yourjail -u > > or similar, so that you updated the OS within your jail. > poudriere will rebuild all packages when the underlying jail gets > updated. Just updating a ports tree wouldn't have this effect. > > In many cases, you don't need to always apply every available > update to your poudriere jails straight away. poudriere jails > are relatively inexposed to attack, and typically the packages you > build will not be affected at all by any vulerabilities in > software within the build jail. Just keep your host system > scrupulously up to date and you'll be fine. > > The biggest exception to this rule are packages that install > statically linked binaries on occasions where there is a > vulnerability in one of the system libraries. Thankfully that > combination is pretty rare. > > 2) You're giving 'poudriere bulk' the '-c' flag, which says to clean > and rebuild everything. This is just poudriere doing what you > tell it to. > > 3) Your system clock is doing weird things, and poudriere is getting > confused because it can't tell what time it is. > > > Cheers, > > Matthew I created a script file to handle the formating of the poudriere command line. Regarding # 2, I found I did have a "-c" in the line. I am not sure why I put it there. I removed it. Would a "-C" make any difference? In any case, I will try it out the next time the ports tree is updated or I need to install a new file. Thanks for your assistance. --=20 Jerry --Sig_/OdsNriTw32JSHF182r4Y0yB Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEIQb/tTwl6I1ueEVtOHMGOIfexWQFAl32iJ4ACgkQOHMGOIfe xWQXTQf8CmXLxkUGoxFHmANTZRBT5UDfMZ2Eps8aqu83nnILEcWeTUyunJTBPaPN e14vWLw9KVtjF4L0+jNrd9KEm1yu0dN+nPYqqsTAFHhI7rymyvKVxyt0VqafJ6d0 xNw4MSQ1sQSAe/G0WBEvDl2mCdjugWFTWonDIlffymKQMUPiuMT2S9ayEUKnSceJ dvtkACKsDmafD4EwDfaIMkubSmBFF+W9oSiTuPy17n0mfjllLaCqqcGvPW+oBPJm 4jQfNHtP0DCwNtVE5Bw+7AEADdrb4w1F9DenmzkX6Da47Ew1hyEvMEkp8sOkzMQ7 YNTGZ9XbP3HoyUQE+CxAZBNQ/w1xjQ== =G/OG -----END PGP SIGNATURE----- --Sig_/OdsNriTw32JSHF182r4Y0yB--