From owner-freebsd-current@freebsd.org Wed Jun 10 00:56:40 2020 Return-Path: Delivered-To: freebsd-current@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 4E18B342E70 for ; Wed, 10 Jun 2020 00:56:40 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 49hT8S1CjWz4CnQ for ; Wed, 10 Jun 2020 00:56:40 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 289753422E9; Wed, 10 Jun 2020 00:56:40 +0000 (UTC) Delivered-To: current@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 276BF3422E8 for ; Wed, 10 Jun 2020 00:56:40 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49hT8S084cz4CgM; Wed, 10 Jun 2020 00:56:40 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id E37272BD43; Wed, 10 Jun 2020 00:56:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f173.google.com with SMTP id c14so495656qka.11; Tue, 09 Jun 2020 17:56:39 -0700 (PDT) X-Gm-Message-State: AOAM53078O69FBTIiJHVr6+vnZK6ubn5mm+jgiHLWPMYF9/UITz3cOp5 uJ9xKBiVJx+n42o2kkjlKC9ZYlHlVCyVipR8nc0= X-Google-Smtp-Source: ABdhPJw+rjorH9Bs8V729wZlhcta2rdsSJS3x8OLb+OZMXBWz49V8B6MCa/2Una8a42MxEOyOr+V2nePpRT+Yqx2voc= X-Received: by 2002:a05:620a:1114:: with SMTP id o20mr695859qkk.120.1591750599332; Tue, 09 Jun 2020 17:56:39 -0700 (PDT) MIME-Version: 1.0 References: <20200609214756.13e9cbbc2de12bbb78839875@bidouilliste.com> In-Reply-To: From: Kyle Evans Date: Tue, 9 Jun 2020 19:56:27 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: nightly snapshot for CURRENT ? To: Clay Daniels Cc: Emmanuel Vadot , "freebsd-current@freebsd.org" , FreeBSD Release Engineering Team Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2020 00:56:40 -0000 On Tue, Jun 9, 2020 at 7:17 PM Clay Daniels wrote: > > On Tue, Jun 9, 2020 at 2:48 PM Emmanuel Vadot wrote: > > > > > Hello all, > > > > I've just hit again something that I've hit (and probably others too) > > often. > > If a change in base break some ports and it's snapshoted in the txz > > available at download.freebsd.org, you need to wait a week for the next > > tarball to be available. > > Since poudriere uses the tarball when you setup a jail it means that > > the only solution you have is to recreate your jail by building it, and > > since building world nowdays is very expensive that delay your work too > > much. > > Would it be possible to generate the tarballs every day instead of > > every week ? At least for tier-1 arches. > > > > Cheers, > > > > -- > > Emmanuel Vadot > > _______________________________________________ > > > > At first I thought you were referring to the weekly snapshots packaged as > install images: > https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/ > > But I think you are talking about the snapshots of each part, like base, > kernel, ports. src, etc to use as a roll your own install like: > https://download.freebsd.org/ftp/snapshots/arm64/13.0-CURRENT/ > Yes, these are the parts he's talking about. My initial impression is that it'd be nice if we could (somehow) leverage Jenkins artifacts [0] to get even more frequent updates if we really needed to without significantly impacting re@ -- that's a little more difficult, though, because build breakage makes it hard to predict what the latest snapshot you can actually grab is, if any. Perhaps a script that creates a symlink to the 'last known functional across the board' revision periodically... [0] http://artifacts.ci.freebsd.org/snapshot/head/r361934/amd64/amd64/ > From my selfish perspective as a weekly installer of the regular Thursday > image or iso of 13.0 Current, I would hate to lose the pre-rolled > installer, and I think there are probably others like me. As long as you > keep the weekly install snapshots, it will not affect folks like me. I must > say that what you want to do is how NetBSD does their daily cent > snapshots, and they do not even offer pre-rolled install images. > > But you are a real developer and I'm just a retired guy playing with his > hobby, so go ahead and do what you think is best for you. > This was brought up in a public forum, you should probably feel free to make non-obstructive comments like this to make sure a fairly common need is represented. The (light-hearted?) self-deprecation near the end of this makes me a bit uneasy- I certainly hope you didn't feel like it was mandatory to acknowledge that he's a developer and you're a hobbyist, because there's most assuredly more hobbyists (such as myself) lurking with similar needs/desires. =-) Thanks, Kyle Evans