So after some aggressive cleaning of packages installed with pip, then purge of revelation with apt, and finally reinstall of revelation, I have now revelation up and running!
Thanks László for the pointers: it was indeed not a Debian bug, but I guess a conflict in python packages provided by the Debian repository (and necessary to revelation), and python packages installed by pip. Unfortunately, I am not sure which python package was at fault here, could be any of: babel backports blinker bs4 clonevirtualenv dateutil extras fixtures flask flask_babel flask_gravatar flask_htmlmin flask_login flask_mail flask_principal flask_security flask_sqlalchemy flask_wtf format_sql html5lib htmlmin itsdangerous jinja2 linecache2 mimeparse ordereddict passlib pbr pgadmin4 pvectorc pyrsistent pytz shutil_backports simplejson speaklater sqlalchemy sqlparse stevedore streamlink streamlink_cli testscenarios testtools traceback2 unittest2 virtualenv virtualenv_support werkzeug wtforms In the end this bug report can be safely closed. Mathieu. On 02/22/2017 03:56 PM, Mathieu Basille wrote: > Thanks László for taking a look at it, and trying to narrow the problem > down. And sorry for the late response. It's really a good news to me that > you don't have a problem running Revelation! That means that I just need to > find out what's wrong on my side… > > To answer your question, yes I do use APT pining on my system, so I may > have packages coming from Sid. So I checked every Revelation's dependency: > > gconf2 > gnome-extra-icons > gnome-icon-theme > python > python-cracklib > python-crypto > python-dbus > python-gnome2 > python-gobject > python-gtk2 > shared-mime-info > > and all come from Stretch (and most have the same version number in Sid > anyway). But I think you pointed me in the right direction: I recently > installed pgadmin4 (v 1.2), and one of the steps involved python packages: > > sudo pip install virtualenvwrapper cryptography pyopenssl ndg-httpsclient > pyasn1 > > Could that come from the 'cryptography' package then? > > Thanks, > Mathieu. > > > On 02/22/2017 03:34 PM, László Böszörményi (GCS) wrote: >> Control: severity -1 important >> >> Hi Mathieu, >> >> On Sat, Feb 18, 2017 at 3:46 PM, Mathieu Basille >> <mathieu....@basille.net> wrote: >>> Package: revelation >>> Version: 0.4.14-3 >>> Severity: grave >>> Justification: renders package unusable >> [...] >>> Using Debian Stretch (testing), I am now unable to run revelation. There >>> must have been an update in the meanwhile, since I used to be able to use >>> it just a few days ago. >> As unreproducible and asked for more information, but none given yet, >> I lower the severity. >> Please give me at least pointers how may I reproduce this issue. >> >> Thanks, >> Laszlo/GCS >> >
