Hi! On 2016-06-30 at 18:51 (CEST), Larry Gritz wrote: > The current top of RB-1.6 appears to build cleanly with gcc 6.1.1. I'm > intending to tag this as Release-1.6.15 tonight or tomorrow. > > In the bug report you cited, it appears to be talking about OIIO > 1.5.23. That may just be because the issue was filed long ago and is a > placeholder even though you have moved on to newer versions, but I > want you to double check that you're building 1.6. The 1.5 has not > been an official release branch for many months, so I'd like not to > have to make any more patches there if at all possible.
I needed a moment to set up my mind and get the situation at the time of the bug report. In January, you released the first stable 1.6.x (it was 1.6.9, IIRC) and I wanted to upload it soon to unstable suite, but there were a couple of related bugs I wanted to close with that version and one of them required the package to go through the NEW queue process because it added a new binary package (the python bindings, in this case). That's why the bug was opened against a "old" 1.5.23 release: because it was the package in unstable suite at that moment, since the 1.6.9 one was still in experimental for test purposes. So, if the current RB-1.6 is building fine with GCC 6, then it's fine. I'll wait for tomorrow release to update the package and close the related bug for it. Thanks a lot for the quick reply and fix. Cheers. -- Matteo F. Vescovi
signature.asc
Description: PGP signature
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
