On Sat, Dec 09 2017, Mikolaj Kucharski <miko...@kucharski.name> wrote: > On Thu, Dec 07, 2017 at 11:12:29PM +0100, Jeremie Courreges-Anglas wrote: >> On Wed, Nov 29 2017, Mikolaj Kucharski <miko...@kucharski.name> wrote: >> > Hi, >> > >> > Update to the latest release on GitHub. Ports changes: >> > >> > - drop patches included by upstream >> > - adapt pledge(2) patches after files moved into src/ subdir >> > - use GitHub variables >> > - drop uneeded variables after previous >> > >> > The biggest change which I'm aware from user perspective is author >> > inversed the behaviour of -N option in version 0.7.0. If you are >> > using par2cmdline with that option, you should drop it after attached >> > update. If you want to bring back behaviour of par2cmdline from before >> > version 0.7.0, then you need to add -N to your scripts or apps. I >> > personally was relaying on -N, so now I can remove it. >> > >> > Changes between versions by upstream can be seen at: >> > >> > https://github.com/Parchive/par2cmdline/releases >> > >> > I personally didn't had a chance to test this release properly yet, but >> > posting if someone else is using par2cmdline too. >> > >> > Regress tests pass on amd64: >> > >> > # TOTAL: 28 >> > # PASS: 28 >> > # SKIP: 0 >> > # XFAIL: 0 >> > # FAIL: 0 >> > # XPASS: 0 >> > # ERROR: 0 >> >> This update looks good, just one question: why switch to >> github-generated tarballs? Upstream still provides tarballs as usual. > > It looks like a mistake. I don't remember why I did it. Thanks for > catching this. Updated diff below, switching back to a release > tarball.
Committed, thanks. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE