X-Debbugs-CC: ti...@debian.org lifong...@gmail.com p...@paulnovo.us Hi Andreas and all yaml-cpp maintainers,
It's a pretty severe situation. The transition of package yaml-cpp from 0.5.x to 0.6.x is a long overdue and with the approach of Buster freeze, we might need to do the transition ASAP or we'd never finish the transition before Buster release. Besides, no upload was made since 2016 and many bugs are unfixed. Andreas, I know you might be overwhelmed by other work either in Debian or outside of Debian (I saw ~1000 packages on your DDPO page...) but I'd like to know you opinion torwards this package since you look like the only one active among the maintainers / uploaders. (Lifeng and Paul: I'd also be glad to hear from you if you are reading this email.) My personal suggestion is that we fix the libboost 1.67 transition first and see if we could finish yaml-cpp 0.6.x transition in the rest of the time. -- Thanks, Boyuan Yang 在 2018-10-26五的 17:09 +0200，Giovanni Mascellani写道： > Package: src:yaml-cpp > Version: 0.5.2-4 > Severity: wishlist > Tags: patch > User: team+bo...@tracker.debian.org > Usertags: boost1.67 > > Dear Maintainer, > > your package fails to build with boost1.67. You can find a build log > attached. If you want to attempt the build yourself, an updated version > of boost-defaults which brings in boost1.67 dependencies can be found > adding this line to your sources.list file: > > deb https://people.debian.org/~gio/reprepro unstable main > > This bug has severity whishlist for the moment, but it will raised to RC > as soon as version 1.67 of Boost is promoted to default. > > More specifically, your package fails building because boost::next and > boost::prior were moved to the header boost/next_prior.hpp. The attached > patch should fix this issue. > > Please consider applying the attached patch as soon as boost1.67 is made > default in order to avoid FTBFS. > > Thanks and all the best, Giovanni.
signature.asc
Description: This is a digitally signed message part
