severty 875313 important kthxbye On Sun, Sep 10, 2017 at 05:24:54PM +0100, Nick Bailey wrote: > Package: yagv > Version: 0.4~20130422 > Severity: grave > Tags: patch > Justification: renders package unusable > > Dear Maintainer, > > If you install and run yagv in Debain stable, it will not run > because of a typo in the python.
It doesn't run on some gcode files. Looks like it's a bug in handling G0 moves. G1 moves are handled fine. And it works for a lot of people because G0 moves aren't actually all that common in gcode files. Slic3r only uses G1 for instance. > In file gcodeParser.py, self.G1 should be replaced with > self.parse.G1 as per the patch reported here: > > https://github.com/chexov/yagv/commit/7d2b3d8fd2534cfb0feff1ef671bf1257e2615dd Thanks, I'll import the patch (and possibly look for a more up-to-date fork to package). > Furthermore, a segfault is generated on (at least) 64b arcitctures > before the graphics are rendered. I believe this is due to a bug > in the version of python-pyglet distributed with stable. Certainly, > I corrected segfault problem by installing the python-pyglet package > from sid. This may be because of > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864936 and if this > is true, should not a later version of python-pyglet be a dependency? I'd just leave this as is, because it actually worked with older versions of pyglet, so the above bug is actually a regression in pyglet itself that rendered pyglet completely useless (iirc there weren't any calls that actually worked in pyglet). > By obtaining the upstream source from github, and installing pyglet from sid, > I was able to obtain a working version of yagv. -- Kind regards, Loong Jin
signature.asc
Description: PGP signature
