From nobody Tue Mar 25 04:55:33 2025 X-Original-To: freebsd-current@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 4ZMHfx1354z5s0GY for ; Tue, 25 Mar 2025 04:55:37 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZMHfw6Vncz49yG; Tue, 25 Mar 2025 04:55:36 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1742878537; 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=2jKGe5o9vhTXUEEMxEDrZgko8GGN0YXLfd0dgRUIR3A=; b=aQUZbhkDUzvwNIcXxFg6HXR4v08REu8GbU2mb2MuKHv/ZkL2LMSN6DbdtQm2ONniE4qzJg on7OW1S+agBb6ChTxkpdE1cX+tISwizehaYlEJgX9UzDvkOt3CZLul/0tF68samc3jCQBr muh5yPF6JNxc6lN0mcLl+Yk4M6Y6QCEoVmmgnYjk/ZS4MRfuo0HQInmqylSEKVQOenqS7O IsVdUWYoAg48YPlyatV5bmXuQGwqPWxvkU0Y+sCkgHdIG0RCHNxDtJ8tEh/89rvMcD2u4T UPIYLDi8deIrtd7wY+uNPmNFPPqn/t/aTm43gF8rmYzURWlUWVAuNR1aXz62Cw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1742878536; a=rsa-sha256; cv=none; b=HwIlTIdFB0v8UaLlNGBE0HtU87Md03hjHi6UIC1P1j+BiNopKnWbl2cnGPgxQxxpvgKU3n Nj9eJUUOPBu85Klv7+yP7Y5+gpXwpgsT01iExVSAFjyH/BiwJ/seRX4cDkdxp5mUwAQDGy BN+sDdrMdlH8Eswz2P11hfcdTlUUNNmcFwDN3M/xrTd2GxjcBr4UjEHqBrWiLa0kVFpvCt nDkgFWB4rAWj6gVi9UyBVBSLA8egaiePAGk313saWC1w9iLSMAAyu/8fXpqIOID8ZPoQdl pR+kMVbw5zRDXaS63uuwMLbNOGSESdqgPLJrUPxrdqxk1DdHRKvJvUxMH/3exg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1742878536; 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=2jKGe5o9vhTXUEEMxEDrZgko8GGN0YXLfd0dgRUIR3A=; b=nhgBTRHthTUvcc7uQauKsTwfez6FMX6ZaOlSn/bZvF+ALY8ny3zxnA4XIXguXLmoCVP3ml EMeuNxoL4XLgskvi/NFK6t6Z5DZM2IxAkAlPSNSoeOO5J0bkAaH8vaWaUXx5dDbToe/PHd yYI1v7YvBSJUoJv1A/hQYQ5/6RrG+cdNFaxke5YbMdbUQOjpFwb4Es+pE6MLtTN6JKB2zo IXajPiXkdRlt8dc8fLwim9MZa6pnf5e61exoTDECq6PEM+ccZTpLUBHT2xyGlDeBphsM7/ FgS8Wsp+4zoeTiGcHnXkQcFqF/veJ7dHb/Yg3QPBPEzmW27OpEqgNAqbJMf1jw== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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 did not present a certificate) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4ZMHfw37vhznFg; Tue, 25 Mar 2025 04:55:36 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Mon, 24 Mar 2025 21:55:33 -0700 From: Gleb Smirnoff To: void Cc: freebsd-current Subject: Re: March 2025 stabilization week Message-ID: References: <6bdad901-fef6-4659-9212-562b579ac19a@app.fastmail.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6bdad901-fef6-4659-9212-562b579ac19a@app.fastmail.com> On Mon, Mar 24, 2025 at 09:44:12PM +0000, void wrote: v> > This is an automated email to inform you that the March 2025 stabilization week v> > started with FreeBSD/main at main-n276073-67c1c4dfd1cc, which was tagged as v> > main-stabweek-2025-Mar. v> v> Is the make installworld problem reported in https://lists.freebsd.org/archives/freebsd-current/2025-March/007235.html still present? I don't know about the 14.2 -> 15.0 upgrade path. The report sounds like a problem that definitely needs to be fixed. But it is out of scope of stabilizatoin weeks, which track CURRENT users. However, given that a STABLE user who wants to switch to CURRENT needs this problem fixed, I understand why you ask here :) We will look at this and I will update you with more info. -- Gleb Smirnoff