This was fixed long ago in the sourceforge repository, but the relaxed release schedule of JAGS means that bugs like this one persist in the release tarball.
I have reached my feature target for release 4.3.0. With a little more testing the new release should be out in June. Thanks Dirk for copying me in the correspondence. I apologize for the inconvenience. Please bear with me. Martyn > On 8 May 2017, at 23:52, Dirk Eddelbuettel <[email protected]> wrote: > > > On 8 May 2017 at 23:41, Rene Engelhard wrote: > | Hi, > | > | On Mon, May 08, 2017 at 04:34:27PM -0500, Dirk Eddelbuettel wrote: > | > Not when you talk to upstream, as I do as maintainer. Upstream's code may > | > well be built against cppunit-config for years to come. > | > | Why? > | > | The point is: you (= upstream) already checks for >= 1.12.1. > | So you already have pkg-config as a given, so you don't need to check for > | cppunit-config as an alternative at all. > > I am at work and have no time to argue with you, but I did poke into > configure.ac for JAGS and it simply has > > AM_PATH_CPPUNIT(1.12.1) > > Methinks that may in fact be an autotools bug that 1.14 is not found. > > In either event we may now have to manually code around this. > > | > And I do not believe into Debian-only patches. > | > | Depending on when the fixed jags will be released and when all the other > | packages will be fixed you will need one. LibreOffice 5.4 does NEED >= 1.14 > | and I want to avoid using the internal copy if possible. > | > | That's the only reason why I am after this :-) > > Sure. Worst case we could park the tests for a bit, but it is preferable to > get it built as before. > > | Doing such things before upstream does and keeping your package building is > | one of your duties of a package maintainer. But as said, yeah, getting it > | fixed upstream is preferrable. > > Yep, we're on the same page. > > Dirk > > | > | Regards, > | > | Rene > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | [email protected] > ----------------------------------------------------------------------- This message and its attachments are strictly confidential. If you are not the intended recipient of this message, please immediately notify the sender and delete it. Since its integrity cannot be guaranteed, its content cannot involve the sender's responsibility. Any misuse, any disclosure or publication of its content, either whole or partial, is prohibited, exception made of formally approved use -----------------------------------------------------------------------
