[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Potential spiped 1.6.2 release, take two -- please test



On Fri, Dec 17, 2021 at 03:08:35PM -0500, James Turner wrote:
> On Fri, Dec 17, 2021 at 10:41:12AM -0800, Colin Percival wrote:
> > Hi spiped users,
> > 
> > I've just uploaded a tarball which may be (modulo version number update)
> > spiped 1.6.2.  Please test this -- even if all you have time to do is check
> > that it compiles on your platform, that's better than nothing, but running
> > 'make all test' and/or testing with live usage would be much better.
> > 
> > You can download the spiped code at
> >    https://www.tarsnap.com/spiped/spiped-1.6.1.99.1.tgz
> > and the tarball has SHA256 hash
> >    8a95c78a52ad1edad56536c812a9acbcdfe88c69a722b287887fc0bcb46b7f74
> > .  You can also see the tree from which I rolled this almost-release at
> > https://github.com/Tarsnap/spiped if you find it useful to crawl through
> > VCS history.
> > 
> > Changes since 1.6.1.99 (the first "potential 1.6.2"):
> > * Fix to the arm32 build.
> > * Tests are now cleaned as part of 'make clean'.
> > * ENOPROTOOPT is ignored from SO_REUSEADDR (as far as we know, only Hurd
> > does this, but it's allowed by POSIX).
> > 
> > Assuming nobody finds any more problems, I'll deliver spiped 1.6.2 as
> > a Christmas present.  If other issues show up, it might be a New Years'
> > present.  As always, Tarsnap bug bounties apply to issues found in spiped.
> > 
> > -- 
> > Colin Percival
> > Security Officer Emeritus, FreeBSD | The power to serve
> > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
> 
> Looks good here on OpenBSD -current. Tho I do see the following warnings
> with clang.


So sorry these are warnings you added! Doh