[Debian-med-packaging] Bug#935345: microbegps: Qt4 removal from Bullseye

[Andreas Tille]

Hi Dmitry,

On Fri, Sep 06, 2019 at 02:28:48PM +0300, Dmitry Shachnev wrote:
> On Fri, Sep 06, 2019 at 01:18:33PM +0200, Andreas Tille wrote:
> > since upstream is currently inactive I tried my best to do the
> > porting of this package in Git[1].  The Python3 port went quite
> > smoothly and I have the feeling I made quite some progress with
> > Qt5 port.  However, when I build HEAD from the packaging Git[1]
> > install the package and try to start the binary I get:
> >
> > [...]
> >   File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1005, in initUI
> >     self.treeView.header().setClickable(True)
> > AttributeError: 'QHeaderView' object has no attribute 'setClickable'
> 
> As the next line connects to sectionClicked signal, I think the code author
> meant setSectionsClickable() here too.
> 
> https://doc.qt.io/qt-5/qheaderview.html#setSectionsClickable

Now I see at least a flash of a window before I get:


$ MicrobeGPS 
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1571, in run
    nodes,ranks = taxonomy.parse_nodes_dmp(pkg_resources.resource_stream('microbegps','data/taxonomy/nodes.dmp'))
  File "/usr/lib/python3/dist-packages/microbegps/taxonomy.py", line 15, in parse_nodes_dmp
    fields = line.rstrip('\t|\n').split('\t|\t')
TypeError: a bytes-like object is required, not 'str'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/microbegps/gui.py", line 1573, in run
    self.failed.emit('<b><font color="DarkRed">Error loading NCBI taxonomy!</font></b><br>Message: <i>'+e.message+'</i>')
AttributeError: 'TypeError' object has no attribute 'message'


... but hmmmm, this looks like a Python2 - Python3 conversion issue
rather than a Qt4 - Qt5 conversion problem.  If there is no other clue
from the Qt-experts I might redirect my question to debian-python list
...

Kind regards and thanks for your patience

       Andreas.

-- 
http://fam-tille.de