Bug#847099:

2017-03-29 Thread Patrick Beeson
0.5.2-4 fix in Ubuntu Zesty works great! Thanks. At the very least now I can installed the two .deb files in 16.04. Any chance this could get pushed upstream to Xenial?

Bug#847099: yaml-cpp 0.5.2 is broken, please update to 0.5.3

2017-03-21 Thread Gianfranco Costamagna
Hello, > You have more than one option to get this bug fixed. Can someone please > fix this package? I uploaded a fix for ubuntu zesty, please test and ping back. thanks G. signature.asc Description: OpenPGP digital signature

Bug#847099: yaml-cpp 0.5.2 is broken, please update to 0.5.3

2017-03-20 Thread Akim Demaille
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847099 On Tue, 10 Jan 2017 21:18:22 -0600 Patrick Beeson wrote: > Bump. At the very least the single line change needs to be made to imp.h > > https://github.com/jbeder/yaml-cpp/pull/303/files HELP!!! You have more than one opti

Bug#847099: yaml-cpp 0.5.2 is broken, please update to 0.5.3

2017-01-10 Thread Patrick Beeson
Bump. At the very least the single line change needs to be made to imp.h https://github.com/jbeder/yaml-cpp/pull/303/files

Bug#847099: Please, update!!!

2016-12-20 Thread Akim Demaille
This is a very severe limitation, this version is broken! Please, upgrade asap to the next version, which does work.

Bug#847099: yaml-cpp 0.5.2 is broken, please update to 0.5.3

2016-12-16 Thread Patrick Beeson
I agree that this needs to be fixed ASAP. 0.5.2 has a broken API in the header when using the remove() call. 0.5.3 fixes this, but I've had issues linking to libraires that use 0.5.2 when I'm using 0.5.3. The package maintainer seems to be ignoring this completely.

Bug#847099: yaml-cpp 0.5.2 is broken, please update to 0.5.3

2016-12-05 Thread Younes Khoudli
Package: libyaml-cpp-dev Version: 0.5.2-4 Hi, yaml-cpp 0.5.2 contains a major bug causing compilation errors when trying to remove a node. (ie. ``` /usr/include/yaml-cpp/node/detail/impl.h:136:15: error: ‘equals’ was not declared in this scope if (equals(*it->first, key, pMemory)) { ``