From nobody Mon Oct 30 15:30:17 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 4SJxzn4Hncz4y4N1 for ; Mon, 30 Oct 2023 15:30:29 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SJxzn2Pqxz3NBc for ; Mon, 30 Oct 2023 15:30:29 +0000 (UTC) (envelope-from dfr@rabson.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-5a90d6ab962so41485927b3.2 for ; Mon, 30 Oct 2023 08:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabson-org.20230601.gappssmtp.com; s=20230601; t=1698679828; x=1699284628; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2mfKOH5RorFbq6wTSr1qVmkvatoZmWohu4ah4ryEHSw=; b=fb1h5a754YoNs+mKX/OdgyFsLOMhEqlZCre0yfFHIxXHuMZEHoXueKsFLmP/tONtNi qzqkvG1nTpURcCEMxx2kF106YhGAX6sgyebdrFAf0ySCQkONJpzUDFJm/Ll/PaWMnQoI rVevS4jlVBzM2UIkcgwbmxVGEd56HZGIjvtmRjSPA/+HznjWyIZFyO69M14NIP8OmQbP YDrFJb7U3QkZj6Cs6M8Dig7V2as5X3uft8FG7aPLqvvtVjR0x0N/vWUwzEuQfz6aexfG 6SmYC8ael4bUv9xsWW2YI9V3x88+kw8FFsmzFEEB+hnlsV/Tk6/7sAWiQU6et1KRHjIr 3IZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698679828; x=1699284628; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2mfKOH5RorFbq6wTSr1qVmkvatoZmWohu4ah4ryEHSw=; b=Xo5CexOgIsDRefVg2/bjMoI2C3Ym19nRjsRmLkDFX+/hSytz3y1YbO9xWIK40LzvTY WNU5UPfz/kp8S1odMwT9cDCQb9Yyi/q4EIyA2IQlzjbWs+vYmul0ug/uL2/IM+z3v8eK ckXyFo1SLtM2vkreueAxrHvMOx+NTBZrdlKnIIN4xLyu7C8GaocqfvI1E3QJB/n9c8C4 CvKekV/IN/zkg3BopALqmfY7bQpYP2sPWwJbgX0LvNCM1SLdWOwQaq/3JncR6VHsUAqc vdLKbl+vG/ahZYXcZ+GlarQX78hOQGmpey/lfRLe325zdoTD+sNRKqY0bYQBN4+IEcNv hnfg== X-Gm-Message-State: AOJu0YxTEOijrt68IQ8POpM8RVFTNrMi144IR7VViDK/Q1Hq5KrmKLal LXIuyFuJZn+G575Ls/anEAbLkzWFEWRP/EzjH4IcjdvXIHZIysVC5CU= X-Google-Smtp-Source: AGHT+IFZIWOm72GFjvTXcre9chrNhEcM5YXFoJzYkEzOsONPA31ZcvogDOImMslsHw5AAfA+yiqWUAo+kr7p4+ckfCY= X-Received: by 2002:a81:d007:0:b0:5a8:5137:b5fb with SMTP id v7-20020a81d007000000b005a85137b5fbmr11289986ywi.47.1698679828287; Mon, 30 Oct 2023 08:30:28 -0700 (PDT) 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 References: In-Reply-To: From: Doug Rabson Date: Mon, 30 Oct 2023 15:30:17 +0000 Message-ID: Subject: Re: official packages To: Baptiste Daroussin Cc: pkgbase@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c0a90e0608f0b7bc" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SJxzn2Pqxz3NBc --000000000000c0a90e0608f0b7bc Content-Type: text/plain; charset="UTF-8" On Mon, 30 Oct 2023 at 14:25, Baptiste Daroussin wrote: > 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? > This is great news, thanks for all the work getting this far. I see packages available for 15 already. If I understand you correctly, packages for stable/13 and stable/14 are planned - is that right? --000000000000c0a90e0608f0b7bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, 30 Oct 2023 at 14:25, Baptist= e Daroussin <bapt@freebsd.org>= ; wrote:
Hello everyone,

The project has started building and populated official packages for pkgbas= e.

For people interested: just create a new repo like this:

FreeBSD-base {
=C2=A0 url: pkg+https://pkg.freebsd.org/${ABI}/base_la= test
=C2=A0 signature_type: "fingerprints"
=C2=A0 fingerprints: "/usr/share/keys/pkg"
=C2=A0 mirror_type: "srv"
}

the current build was built last friday, everything is ready to be able to<= br> 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 possib= le) and
=C2=A0 twice a day at a fix time, publish it under "base_latest"<= br> - every sunday take the last built snapshot and publish it under the base_w= eekly
=C2=A0 snapshot at a predictable time.

For releng:
- built it in a end less loop and publish straight each time there was chan= ges

For end users on stable/main the default would be: to end on the base_weekl= y
(does not exists yet) repo, but users can if needed switch to base_latest.<= br>
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?

This is great news, = thanks for all the work getting this far. I see packages available for 15 a= lready. If I understand you correctly, packages for stable/13 and stable/14= are planned - is that right?
=C2=A0
--000000000000c0a90e0608f0b7bc--