nightly snapshot for CURRENT ?

[Glen Barber]

On Sat, Jul 25, 2020 at 12:29:42PM +0200, Emmanuel Vadot wrote:
> On Fri, 24 Jul 2020 22:28:39 +0000
> Glen Barber <gjb at freebsd.org> wrote:
> 
> > On Sat, Jul 25, 2020 at 12:14:52AM +0200, Emmanuel Vadot wrote:
> > > On Fri, 24 Jul 2020 22:06:07 +0000
> > > Glen Barber <gjb at freebsd.org> wrote:
> > > 
> > > > On Fri, Jul 24, 2020 at 10:31:35PM +0200, Emmanuel Vadot wrote:
> > > > > On Tue, 9 Jun 2020 22:04:07 +0200
> > > > > Emmanuel Vadot <manu at bidouilliste.com> wrote:
> > > > > 
> > > > > > On Tue, 9 Jun 2020 19:56:30 +0000
> > > > > > Glen Barber <gjb at freebsd.org> wrote:
> > > > > > 
> > > > > > > On Tue, Jun 09, 2020 at 09:47:56PM +0200, 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.
> > > > > > > > 
> > > > > > > 
> > > > > > > Let's revisit this sometime next week after 11.4 is out.
> > > > > > > 
> > > > > > > Glen
> > > > > > > 
> > > > > > 
> > > > > >  Sure, works for me.
> > > > > > 
> > > > > >  Thanks,
> > > > > > 
> > > > > 
> > > > >  Ping ?
> > > > > 
> > > > 
> > > > I thought the artifacts from the jenkins builder for CI were sufficient.
> > > > 
> > > > Glen
> > > > 
> > > 
> > >  Yes and no,
> > > 
> > >  I can add something to poudriere for getting the tarballs from the CI
> > > artifacts but that won't be by default.
> > > 
> > 
> > To be honest, that would be the preferred route, since updating the
> > various *.txz distribution sets would break things like bootonly.iso,
> > mini-memstick.img, and so on.
> 
>  Why would it break things ?
> 

The bootonly.iso and mini-memstick.img do not contain the distribution
sets, only the MANIFEST file.  So, people using these to install
a system would not be able to do so, because the checksums for the sets
would not match that in the MANIFEST.

> > In other words, we already have a system in place that generates these
> > archive files, so I personally see no need to disrupt the "official"
> > snapshot build process to appease a subset of the user base while
> > unnecessarily adding a pain point for the rest.
> > 
> 
>  If only the sets are generated each day I don't see how it can cause a
> pain to anyone.
> 

See above.

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20200727/fbfa85ed/attachment.sig>