the attached patch applies to the iotop 0.6-1 source package and creates the iotop 0.6-1u1604+1 source package with the upstream patch(es) in iotop-0.6/debian/patches/Skip_invalid_lines_in__proc_PID_status_files-LP1773383.patch.
apt-get source iotop
patch -p1 <iotop_0.6-1u1604+1.patch
apt-get build-dep iotop
# instead of devscripts you can install dpkg-dev and "dpkg-buildpackage -D -us -uc"
apt-get install devscripts
cd iotop-0.6
debuild -i -us -uc
cd ..
dpkg -i iotop_0.6-1u1604+1_*.deb
Not to bikeshed what Omer Ozarslan (ozars) proposed, but instead to reflect what upstream implemented...
http:// repo.or. cz/iotop. git/commit/ 0392b205b5c3973 a326721c2e9f97f 0fa2eefa82
http:// repo.or. cz/iotop. git/commit/ 7c51ce0e29bd135 c216f18e18f0c4a b769af0d6f
http:// repo.or. cz/iotop. git/blobdiff/ 69107ad1bfa05d2 40dbeac52f7d377 dbb4c29daf. .7c51ce0e29bd13 5c216f18e18f0c4 ab769af0d6f: /iotop/ data.py
the attached patch applies to the iotop 0.6-1 source package and creates the iotop 0.6-1u1604+1 source package with the upstream patch(es) in iotop-0. 6/debian/ patches/ Skip_invalid_ lines_in_ _proc_PID_ status_ files-LP1773383 .patch.
apt-get source iotop 0.6-1u1604+ 1.patch 6-1u1604+ 1_*.deb
patch -p1 <iotop_
apt-get build-dep iotop
# instead of devscripts you can install dpkg-dev and "dpkg-buildpackage -D -us -uc"
apt-get install devscripts
cd iotop-0.6
debuild -i -us -uc
cd ..
dpkg -i iotop_0.