From nobody Mon Oct 30 14:25:09 2023 X-Original-To: pkgbase@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 4SJwXV24zxz4y0LL for ; Mon, 30 Oct 2023 14:25:14 +0000 (UTC) (envelope-from bapt@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SJwXV1brBz3Hcw for ; Mon, 30 Oct 2023 14:25:14 +0000 (UTC) (envelope-from bapt@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698675914; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=5GiitPe+FsuDA9JUfMReb/cuWlWEU2NrnOlM48nnL3E=; b=rP0D08tzaMBejD74cP5DHbL9faCkToPcTESC5uMwmSLYOpliOCNGfU5ciIe7TBjuNmwQf0 r9I8OGqCnGR1RrcRkjD4J1rhXqDeMjapnLWwBozbIZ1JgOgySrAnVejtdJymIJ8A3ASMJY +JLwpdLSuBIOApspztFRx4M7AYpQ/30e4KMrJKrRpI+GGMr0L1XPVJbMXOkOpZd2TIUlLv A2bjL3N0qhIanDtmCUby9yWQT81m9N5G+CiSjt5krjzhAbom9yT2DtPbWcBjB7bnSZzFCq qB1FcCXzrBRjnbYxdZ17whjeT1SytdpEt7D2FEb0yL24Ox92KLWwaI542CC5jQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698675914; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=5GiitPe+FsuDA9JUfMReb/cuWlWEU2NrnOlM48nnL3E=; b=goFCO5h15n3yDfllY3vT3QYT78OSlhgVQ/JaKonDuEjB+vH1ftUTdBvGLXbUwHD1/wgdUU Eiv3IGMTRoU38kLcvTu+8rLr9+Y18AUCuB7wMmUBAewvq/Y/75il1MvLqxDo7ZDYke+ZzF C9Bx8rvAeTMCWZxYIUNT5ivmPFSKvRbzDLEu8WRFpx2fJNdkDsgRwNYODGsQisSlWD6TXK hfmH0/VQe5LgJ4Pn7+rdIYnfmp8eGTLvrZNeMhLTjdgbCk1e4wxU7FIYAdiuyLTZ0yk++T Q24IDv7yMcaXV7mssezfWAliJYK1QObn8k+6eveH+ZutLKW3IMYtd8eIel4BwA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698675914; a=rsa-sha256; cv=none; b=WI6mfa6d3L9kVjkg+Y0U7XlfDflnQpCLLKaiVMleWSw6ZK3kYClWoa5lxTlzhIw+fzwRbo 5aIPqu+jhqWbKqOr+Z1RMZsrP7GQbmcIBGgtS+6FA/bhn4j3GhJILajUUM/G3ukH9rJjVy wDRg/0uokxXir6qN88RNmF2Uq7xBxtoeJiyS3meKJgkmKKrOcdmXrFZIsekTwwo1asxej3 BFUMYpNS/wm1tLREfMQ2nh8MpKcn5uNfBqwAptJPjpALlEpu6xDsu0SLefdZigqGDADmkJ /XxdZBaNbsLpid8tjzTPJqfRfdWkdg6LMpDD2osieOlIKDwhKAdfAc/4ex+uSQ== Received: from aniel.nours.eu (nours.eu [176.31.115.77]) (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: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SJwXV003Kz1DJP for ; Mon, 30 Oct 2023 14:25:13 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id 77ACFAF679; Mon, 30 Oct 2023 15:25:09 +0100 (CET) Date: Mon, 30 Oct 2023 15:25:09 +0100 From: Baptiste Daroussin To: pkgbase@freebsd.org Subject: official packages Message-ID: List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello everyone, The project has started building and populated official packages for pkgbase. For people interested: just create a new repo like this: FreeBSD-base { url: pkg+https://pkg.freebsd.org/${ABI}/base_latest signature_type: "fingerprints" fingerprints: "/usr/share/keys/pkg" mirror_type: "srv" } the current build was built last friday, everything is ready to be able to publish in regular basis. Here is my proposal for main and stable branches: - build everything in a end less loop (to detect failures as soon as possible) and twice a day at a fix time, publish it under "base_latest" - every sunday take the last built snapshot and publish it under the base_weekly snapshot at a predictable time. For releng: - built it in a end less loop and publish straight each time there was changes For end users on stable/main the default would be: to end on the base_weekly (does not exists yet) repo, but users can if needed switch to base_latest. For base_release_X for release users base_release_0 for 14.0 for example. all the failures will be published in this mailing list! Is it ok with you? Best regards, Bapt