On 05/26/2011 04:40 AM, Michael Droettboom wrote: > On 05/25/2011 05:36 PM, Eric Firing wrote: >> On 05/25/2011 10:53 AM, Dieter Schön wrote: >> >>> hi list, >>> >>> first, thanks for providing matplotlib, i am using it in several projects. >>> >>> i had problems with several png files and decided to upgrade libpng. >>> this broke matplotlib. >>> as you can see in the documentation of libpng15, it is no longer possible >>> to directly access png_infop. >>> >>> i have created the following patch: >>> >> Dieter, >> >> Thank you, but the modification has already been made to the master >> branch. I did not consider this as a bug fix, so I applied it only to >> master, not to the maintenance branch. >> > It seems to have been applied to the maintenance branch... Maybe > someone backported it?
Mike, I think you did--unintentionally! If you look at the graph with qgit (or presumably any other such tool) in the vicinity of your commits on May 6, you will see that this one a50874b711983cba505ecdb2801c4996eccf3812 made v1.0.x branch off of master; the v1.0.x line was broken by the previous commit. To confirm that this break had the effect of propagating the change in _png.cpp into what is now v1.0.x, you can look at the diff between two commits on "v1.0.x", one of which is a bit before the break, the other after: git diff 069c21d 0e6dad src/_png.cpp You will see that the file was changed. Eric > > https://github.com/matplotlib/matplotlib/blob/v1.0.x/src/_png.cpp > > Mike ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel