Going around pytrainer bugs, I found this one, which is not reported against the package but shows up when browsing the list of bugs for pytrainer. I don't really understand why pytrainer is specifically mentioned as affected by this bug and not all other things using (indirectly in the case of pytrainer) libgl1-mesa-glx There's probably something I don't get, which is why a small explanation with the control message sent on March 22nd would have helped, I think..:-) --
Attachment:
signature.asc
Description: Digital signature