note that this bug was brought to our attention by upstream, and they released 1.0.6 for us (the fix had been already in 1.1.0 released in March 22nd)
note that this bug was brought to our attention by upstream, and they released 1.0.6 for us (the fix had been already in 1.1.0 released in March 22nd)