par2 1.0.0

[Greg Troxel]

I see there's a been a big update from 0.8.1.

Any cautions, experiences?

[Rob Browning]

Greg Troxel <g...@lexort.com> writes:

> I see there's a been a big update from 0.8.1.

They broke some things, but we've made accommodations (you can see par2
in the past year or so(?) in the commit log --- and I think the main and
0.33.x release notes off and on).

As far as I know it still works, but I just checked, and it's not in
debian stable, so I'm still running 0.8.1 "everywhere". But others must
be using it, given the reports (and then fixes).

I suppose I might start with testing if you're concerned (i.e, try "make
check" with it in the PATH --- or perhaps just "./pytest
test/ext/test-fsck", since that may be the only place we test it right
now).

--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

[Greg Troxel]

Rob Browning <r...@defaultvalue.org> writes:

> Greg Troxel <g...@lexort.com> writes:
>
>> I see there's a been a big update from 0.8.1.
>
> They broke some things, but we've made accommodations (you can see par2
> in the past year or so(?) in the commit log --- and I think the main and
> 0.33.x release notes off and on).
>
> As far as I know it still works, but I just checked, and it's not in
> debian stable, so I'm still running 0.8.1 "everywhere". But others must
> be using it, given the reports (and then fixes).
>
> I suppose I might start with testing if you're concerned (i.e, try "make
> check" with it in the PATH --- or perhaps just "./pytest
> test/ext/test-fsck", since that may be the only place we test it right
> now).

par2 was just updated to 1.0.0 in pkgsrc on 2025-12-27.


I just rebuilt it, resulting in par2-1.0.0 on my main system, and then
ran "make check" and it was fine (NetBSD 10 amd64). So looks good from
here. Thanks to everyone who who fixed things before release, making my
question turn out to feel uninteresting. (Most big updates result in a
lot of downstream scrambling....)