From nobody Tue Jun 27 04:12:05 2023 X-Original-To: freebsd-ports@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 4Qqrrq0x2Sz4hkPJ for ; Tue, 27 Jun 2023 04:12:11 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Qqrrq0QfHz3rGQ; Tue, 27 Jun 2023 04:12:11 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1687839131; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7jzLuOME7VwqM2PvEtrU5Yqhv/EhnJFmORPN+Jn0S6U=; b=NdPk6e6tDMBTWucpCD8JdBdg7D151ZeYaarA+ITZ5SBiwTtR7nztNnItoBlfLvQoK8GYpS qrzkmbiZegF+pzryOskZW8iKg3CRyGE9/N3117xVM50WFf5eGZNeFkbZceJ2Eg6xYOB3I2 2vgaoQyTkq5Vb3LV43v50iFDuw7PdAhQL4iTpJLiqC+GH0aoEF93u5wCo2V2gIxn3kANP0 EJ9Kwsg93I4p0UaiwcucV7GB+y10TyQJzJp8SLHJ+38pxMZ33erGz8xCbDJquGoAuU97X7 ogVnIzjUT9JsPoJsMLqUNGGrtZ1zyEl931cK+aHIJtOtb4Rl+Jtxr0UXnwTp1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1687839131; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7jzLuOME7VwqM2PvEtrU5Yqhv/EhnJFmORPN+Jn0S6U=; b=v7cSgE/yqkZzwTAYTBZY6tq956uTsacSEIchRRwQs+eZb4tnqWHWjCzmb/qhWwLQ7nSK8y afhIx5mSEl4OVaR947jJupgCU06aDd0zSfF1iyfLT5DiPMyGUXx2wgVNPmoVY8Z+Wmoi0n v/IMNBxrVc9EqHopfHLUtfirOO1yZnjMwbbFsmLQu1Zrr5oT0L8rdcg8SjLBJwzij6feZs vdUiBGgh5CJHvC+WD6Rxt4p2MCkGlvgK4s/SdlLvX5mSOIzeohiZ72QKxuszxdjNDATeQA ZrMO2Y+utJjdPuV/bRrFgvr39Ir1efhRNn24hHAG+Pcb91X7xZwB7JGH+K9+iw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1687839131; a=rsa-sha256; cv=none; b=NeSZ0xhP/y6eGFSTsQlcw1bBekhtiTHQszdEGLiSl/ooNJAuiedW+1lxkr89oVHOINpr70 aCm9Rm0m+2BEdQKxQNVmugw1ZDhEYm5GxHHiI8T/WCqI58ijBGttfRyxyY0B0suLRr78jF PpGjWPrImFXXnNXT8OZd1mMCKPwwdpWwwcpjL4MzYB68U2X1ejPPsIP5fz8Murcze6BdT7 EIoKoKXYw1di7XpV5ay2+Z3prKGh/bN8q29Iui5DFXk/NhCYi+LkGHVYEI7kKgJpeswvFl 7q3IHzU8F8zFfZ0I/n2Krlp912h9lkDSvaBcf3JWDWc9nDuWI3/+PMH+BtxJZA== Received: by freefall.freebsd.org (Postfix, from userid 1354) id E70A622E94; Tue, 27 Jun 2023 04:12:10 +0000 (UTC) From: Jan Beich To: list_freebsd@bluerosetech.com Cc: freebsd-ports@freebsd.org Subject: Re: How long do main commits take to reach the repos? [Was: Re: git: 70b4957fa52b - main - multimedia/plexmediaserver-plexpass: Update to 1.32.4.7195] In-Reply-To: <821fcfeb-cf45-0826-fe5f-98c557595883@bluerosetech.com> (list freebsd's message of "Mon, 26 Jun 2023 15:22:54 -0700") References: <202306181123.35IBNthY096169@gitrepo.freebsd.org> <821fcfeb-cf45-0826-fe5f-98c557595883@bluerosetech.com> Date: Tue, 27 Jun 2023 06:12:05 +0200 Message-ID: <1qhx-sfvu-wny@FreeBSD.org> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain X-ThisMailContainsUnwantedMimeParts: N list_freebsd@bluerosetech.com writes: > multimedia/plexmediaserver_plexpass was updated to 1.32.4.7195 on the > 18th (8 days ago, see qutoed below), but the public repo still has > 1.32.4.7164. I checked that I'm using /latest, and that a git pull > shows the commit. Normally updates to this port go live pretty > quickly since it's a NO_BUILD=yes. Is there something stalling the > repo updates? Here's my observation based on public data: - some poudriere hosts are slow e.g., beefy6 exceeds timeout on www/chromium - after a build has completed it may take some time to sync mirrors - packages are always built as a set to avoid ABI mismatch - all packages are force-rebuilt on OS updates[1] - incremental builds excessively obsolete existing packages[2] - each build starts on Tue/Thu/Sat/Sun at 01:00 UTC - if the previous build didn't finish yet the next one is skipped To check: 1. Open https://pkg-status.freebsd.org/?all=1&type=package 2. Type desired major version + architecture in Search field e.g., 131amd64 3. Look at Build column and check if the ports commit contains the desired update 4. Confirm Status column is stopped:done 5. Calculate Started + Elapsed (or check timestamp in the last log) 6. Add up to 2 days to sync mirrors depending on how many packages were built For example, 43e248a61351 is probably still syncing mirrors after rebuilding everything caused by the recent security fixes in base system. 1.32.4.7195 landed on 2023-06-18 (Sunday), *after* another build has started that ended up skipping 2023-06-20 (Tuesday) build due to ~1 hour overlap. [1] Precaution against ABI changes on -CURRENT (via __FreeBSD_version bumps) and secfixes on -RELEASEs that may affect headers, static libraries, toolchain, etc. [2] Precaution against PORTREVISION underbumping, obsoleted by shlib_require in pkg(8) See also https://github.com/freebsd/poudriere/issues/822