> It means /tmp is full. The tarball is truncated.
>
can't understand why /tmp would be full - its over 1G in size and barely used?

> syspatch does not verify the tarball integrity in ls_missing().
>
> I would argue this is also a defect in syspatch.
>
> Regards
> Lloyd
>
> legrandouef <[email protected]> wrote:
>
>> ~ :$ uname -a
>> OpenBSD obsd.my.domain 7.9 GENERIC.MP#21 amd64
>> ~ :$ doas syspatch -c
>> gzip: stdin: Input/output error
>> tar: End of archive volume 1 reached
>> 045_xserver
>> 046_zlib
>> 047_syszlib
>> 048_libressl
>> 049_kbind
>> 050_libcasr
>>
>> Tried from multiple mirrors
>>
>>
>> Sent with Proton Mail secure email.
>
>
> Sent with Proton Mail secure email.

On inspecting the syspatch repo:

        https://cdn.openbsd.org/pub/OpenBSD/syspatch/7.9/amd64/

there were 4 further patches:

        051_tcpsack
        052_tcpsyn
        053_nd6dad
        054_wscons

dated the same as 045-050 above - 10-Nov-2026 09:49

These syspatches (045-054) were listed in the SHA256 & SHA256.sig files in the 
repo, also dated 10-Nov-2026 09:49.

I manually downloaded the syspatch archives 045-054 along with the SHA256.sig 
file from the repo to a local directory:

        /var/www/htdocs/syspatch/7.9/amd64/

pointed /etc/installurl to:

         file://var/www/htdocs

And ran:

   ~ :$ doas syspatch -c

All the syspatches listed - no errors - then:

   ~ :$ doas syspatch

and the installed correctly - again no errors.

So for some reason the archive volume was truncated at the 6 patch level 
(050_libcasr)?

I checked each syspatch archive downloaded for integrity, which passed, with 
file(1) and gzip -t.

Reply via email to