Package: python-serial Version: 2.6-1.1 Severity: normal pyserial 2.7 has been up on pypi and sf.net since late 2013, but the debian package is only 2.6 and is older than that... is there some reason I'm missing that it was held back at the time? I don't see anything in the changelog.Debian suggesting one (or was it just the NMU'er not wanting to go to far?)
I'm particularly interested in this fix that's already in 2.7: http://sourceforge.net/p/pyserial/patches/29/ - without this fix, if you're using setitimer at all, pyserial basically doesn't work. (I'll try to follow up with packaging updates in the next week or two.) _Mark_ <eic...@thok.org> Debian Package Maintainer -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-serial depends on: ii python 2.7.9-1 python-serial recommends no packages. Versions of packages python-serial suggests: ii python-wxgtk3.0 3.0.1.1+dfsg-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
