Re: Use specific FreeBSD patch version with poudriere

This is reportedly fixed in 13.0-RELEASE-p9, which I upgraded to shortly
after release. Pleased to confirm I've not experienced any data corruption
since.

I can't speak for the 13.1 betas but can only assume it's been fixed there
too.

Regards
Andrew

On 2022-03-19 14:12:47, Ralf van der Enden (tremere@cainites.net) wrote:

> Hi,
>
> I've experienced the same. Did a rollback to -p7 (but the jail is on -p8). After that everything builds okay again.
>
> I also suspect the latest ZFS patches.
>
> Hopefully 13.1 doesn't suffer from this issue. I can hold out until that has been released.
>
> Regards,
> Ralf van der Enden
>
> -----Original Message-----
> From: owner-freebsd-questions@freebsd.org <owner-freebsd-questions@freebsd.org> On Behalf Of andrew clarke
> Sent: zaterdag 19 maart 2022 03:03
> To: Ralf van der Enden <tremere@cainites.net>
> Cc: 'Matthias Fechner' <idefix@fechner.net>; freebsd-questions@freebsd.org
> Subject: Re: Use specific FreeBSD patch version with poudriere
>
> Today I experienced the same problem after upgrading to 13.0-RELEASE-p8 from -p7.
>
> My poudriere jail was still on -p5, though.
>
> Looking at https://pkg.cainites.net/data/amd64-13-0-default/2022-03-16_22h53m32s/logs/errors/libevdev-1.9.1.20200928.log
> I see:
>
> "ValueError: source code string cannot contain null bytes"
>
> I also encountered null bytes in recently written files on my -p8 system.
> The .h files were installed on the host from packages created by the poudriere jail.
>
> These recently-installed packages were flagged as having bad checksums in the daily security output cron job this morning:
>
> Checking for packages with mismatched checksums:
> glib-2.70.4_1,2: /usr/local/include/glib-2.0/gio/gactiongroupexporter.h
> glib-2.70.4_1,2: /usr/local/include/glib-2.0/gio/gactionmap.h
> glib-2.70.4_1,2: /usr/local/include/glib-2.0/gio/gbytesicon.h
> vulkan-headers-1.3.208: /usr/local/share/vulkan/registry/vk.xml
>
> When reading the above files manually they consisted entirely of null bytes.
>
> I doubt this is related to poudriere. Rather I suspect this is a serious bug in the recent ZFS patches that were released with -p8.
>
> Not wanting to risk further data loss I've since rolled back to -p7 with "freebsd-update rollback".
>
> So far I've not had any data corruption problems after the rollback.
>
> Regards
> Andrew
>
> On 2022-03-19 02:39:14, Ralf van der Enden (tremere@cainites.net) wrote:
>
> > Hi,
> >
> > I've seen weird behaviour as well rebuilding all my ports using poudriere.
> >
> > After an upgrade (even a small one going from -p7 to -p8) triggers a rebuild of all my packages. A lot of them fail with extremely weird reasons.
> >
> > I've downgraded my box to -p7 and then rebuilt everything in -p8 jails, which works fine. Reinstalling -p8, fetching the latest port updates and then rebuilding just the new ports also causes issues.
> >
> > I've tried removing poudriere/packages/amd13-0-default and clearing my /var/cache/ccache directories, but that didn't help either.
> >
> > Here's a poudriere run where both the host and jail are on -p8:
> > https://pkg.cainites.net/build.html?mastername=amd64-13-0-default&buil
> > d=2022-03-16_22h53m32s And here’s the one where the host is on -p7 and
> > the jail on -p8:
> > https://pkg.cainites.net/build.html?mastername=amd64-13-0-default&buil
> > d=2022-03-18_20h31m12s (it's actually still in progress as I write
> > this mail, but should be done soon)
> >
> > Kind regards,
> >
> > Ralf van der Enden
>
>
>