WITHOUT_CAPSICUM|CASPER option ignored: it is no longer supported

In exercising the build options on 14.0-BETA4, WITHOUT_CAPSICUM and WITHOUT_CASPER appear to be in an ambiguous state: They are present but ignored. Fortunately src.conf(5) now reports "This option has no effect." Will these be removed prior to the final release? Are they staying to be reimple

Re: something magic about the size of a ports tree

On 2023-10-03 12:24, Dag-Erling Smørgrav wrote: Matthias Apitz writes: I have on my poudriere build host a ports tree and wanted to move it to the host where the resulting packages are installed: root@jet:/usr/local/poudriere/ports # du -sh ports20230806 397Mports20230806 root@jet:/usr/loc

Re: something magic about the size of a ports tree

Warner Losh writes: > Do we support any compression on top of that? Has support for > poudriere been added for it? Yes (zstd) and no. DES -- Dag-Erling Smørgrav - d...@freebsd.org

Re: something magic about the size of a ports tree

On Tue, Oct 3, 2023, 10:24 AM Dag-Erling Smørgrav wrote: > Matthias Apitz writes: > > I have on my poudriere build host a ports tree and wanted to move it to > > the host where the resulting packages are installed: > > > > root@jet:/usr/local/poudriere/ports # du -sh ports20230806 > > 397Mpo

Re: something magic about the size of a ports tree

> On 3. Oct 2023, at 18:27, Matthias Apitz wrote: > > El día martes, octubre 03, 2023 a las 06:14:23p. m. +0200, Olivier Certner > escribió: > >> Hi Matthias, >> >> Some ZFS dataset with zstd compression on jet, and no compression on >> c720-1400094? >> > > Yes, on jet it is ZFS: > > r

Re: something magic about the size of a ports tree

With ZFS, you might be using transparent compression. "du -sh" will show you a file's compressed size. But "ls -lh" will show you the logical size. That's probably why the tarball looked so much bigger than the ports tree on the first system. If you do "du -sh" on the tarball, I bet you'll see

Re: something magic about the size of a ports tree

El día martes, octubre 03, 2023 a las 06:14:23p. m. +0200, Olivier Certner escribió: > Hi Matthias, > > Some ZFS dataset with zstd compression on jet, and no compression on > c720-1400094? > Yes, on jet it is ZFS: root@jet:/usr/local/poudriere/ports # mount | grep ports2023 poudriere/poudrie

Re: something magic about the size of a ports tree

Matthias Apitz writes: > I have on my poudriere build host a ports tree and wanted to move it to > the host where the resulting packages are installed: > > root@jet:/usr/local/poudriere/ports # du -sh ports20230806 > 397Mports20230806 > root@jet:/usr/local/poudriere/ports # tar cf p.tar ports2

Re: something magic about the size of a ports tree

Hi Matthias, Some ZFS dataset with zstd compression on jet, and no compression on c720-1400094? -- Olivier Certner

something magic about the size of a ports tree

I have on my poudriere build host a ports tree and wanted to move it to the host where the resulting packages are installed: root@jet:/usr/local/poudriere/ports # du -sh ports20230806 397Mports20230806 root@jet:/usr/local/poudriere/ports # tar cf p.tar ports20230806 root@jet:/usr/local/poudrie

base-krb5 issues (segfaults when adding principals in openssl)

Hi, has someone else issues with krb5 on -current when adding principals? With -current as of 2023-09-11 I get a segfault in openssl: ---snip--- Reading symbols from /usr/bin/kadmin... Reading symbols from /usr/lib/debug//usr/bin/kadmin.debug... [New LWP 270171] btCore was generated by `kadmin -

Re: crashinfo fails on 'version'

On Mon, 2 Oct 2023 20:15:30 + (UTC) "Bjoern A. Zeeb" wrote: > On Fri, 29 Sep 2023, Bjoern A. Zeeb wrote: > > > On Fri, 29 Sep 2023, Warner Losh wrote: > > > >> On Fri, Sep 29, 2023, 3:56 PM Bjoern A. Zeeb > >> > >> wrote: > >> > >>> Hi, > >>> > >>> saveinfo wrote a good core, but crashinfo b