On Mon, Sep 23, 2019 at 12:20:40AM -0400, Bryan Steele wrote: > On Sun, Sep 22, 2019 at 12:42:25PM -0700, Jonathan Thornburg wrote: > > I'm trying to use syspatch to update a firewall (a PC Engines Alix) > > running 6.5-stable/i386, but syspatch dies with an error message saying > > that the patch file contains inappropriate filenames: > > > > # uname -a > > OpenBSD sodium.bkis-orchard.net 6.5 GENERIC#3 i386 > > # cat /etc/installurl > > https://cdn.openbsd.org/pub/OpenBSD > > # ls -gFlk /bsd* > > -rwx------ 2 root wheel 13518991 Sep 10 18:23 /bsd* > > -rwx------ 2 root wheel 13518991 Sep 10 18:23 /bsd.booted* > > -rw------- 1 root wheel 8843776 May 12 16:43 /bsd.rd > > # syspatch -l > > 001_rip6cksum > > 002_srtp > > 004_bgpd > > 005_libssl > > 006_tcpsack > > 007_smtpd > > 010_frag6ecn > > # syspatch -c > > 011_expat > > # syspatch > > Get/Verify syspatch65-011_expat.tgz 100% |**************| 546 KB 00:00 > > > > Installing patch 011_expat > > > > tar: Pattern matching characters used in file names > > tar: Use --wildcards to enable pattern matching, or --no-wildcards to > > suppress this warning > > tar: @usr/share/relink/kernel/GENERIC.MP/.*@@g: Not found in archive > > tar: Exiting with failure status due to previous errors > > # > > That message is not from OpenBSD's tar(1) implementation.
There is a very good reason why GNU utilities installed from ports and packages are prefixed with a 'g', so as to not conflict with utilites from the base system. You changed the system-wide tar to GNU tar, so you should expect there to be fallout. > > Is this a known issue with this patch? Is there an alternate way > > (besides updating from source) to track -stable ?
