Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-11 Thread Chris Lawrence
On Sat, Aug 8, 2015 at 2:39 PM Dirk Eddelbuettel wrote: > Abort. I just wasted a few hours on this (luckily while doing other > stuff). I am not going to split libjags, libjags-dev off but simply rebuild > depending on g++ (>= 4:5.2). > > Chris can then depend on this version, and that is all th

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Dirk Eddelbuettel
On 8 August 2015 at 09:03, Dirk Eddelbuettel wrote: | | On 8 August 2015 at 14:34, Jonathan Wiltshire wrote: | | On 8 August 2015 at 13:08, Julien Cristau wrote: | | > However, instead of being properly split out as required by | | > policy, the libraries are shipped as part of the 'jags' binary

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Dirk Eddelbuettel
On 8 August 2015 at 16:08, Julien Cristau wrote: | On Sat, Aug 8, 2015 at 09:06:35 -0500, Dirk Eddelbuettel wrote: | | > | > Related question, though: how do I chroot/pbuilder build against experimental? | > | > I am only setup for unstable. I'd rather not create a new chroot just for | > th

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Julien Cristau
On Sat, Aug 8, 2015 at 09:06:35 -0500, Dirk Eddelbuettel wrote: > > Related question, though: how do I chroot/pbuilder build against > experimental? > > I am only setup for unstable. I'd rather not create a new chroot just for > this. Is there another way? > You don't need to build against

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Dirk Eddelbuettel
Related question, though: how do I chroot/pbuilder build against experimental? I am only setup for unstable. I'd rather not create a new chroot just for this. Is there another way? Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- To UNSUBSCRIBE, email to debian-b

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Dirk Eddelbuettel
On 8 August 2015 at 14:34, Jonathan Wiltshire wrote: | On 8 August 2015 at 13:08, Julien Cristau wrote: | > However, instead of being properly split out as required by | > policy, the libraries are shipped as part of the 'jags' binary package, | > which makes this a bit of a pain. | | On Sat, Aug

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Jonathan Wiltshire
On 8 August 2015 at 13:08, Julien Cristau wrote: > However, instead of being properly split out as required by > policy, the libraries are shipped as part of the 'jags' binary package, > which makes this a bit of a pain. On Sat, Aug 08, 2015 at 06:50:44AM -0500, Dirk Eddelbuettel wrote: > I don't

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Dirk Eddelbuettel
On 8 August 2015 at 13:08, Julien Cristau wrote: | Control: severity -1 serious | Control: tag -1 confirmed | | On Fri, Jul 3, 2015 at 13:10:42 +, Matthias Klose wrote: | | > Background [1]: libstdc++6 introduces a new ABI to conform to the | > C++11 standard, but keeps the old ABI to not b

Bug#791081: jags: library transition may be needed when GCC 5 is the default

2015-08-08 Thread Julien Cristau
Control: severity -1 serious Control: tag -1 confirmed On Fri, Jul 3, 2015 at 13:10:42 +, Matthias Klose wrote: > Background [1]: libstdc++6 introduces a new ABI to conform to the > C++11 standard, but keeps the old ABI to not break existing binaries. > Packages which are built with g++-5 fr