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
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
Control: severity -1 important
Hi Mathieu,
On Sat, Feb 18, 2017 at 3:46 PM, Mathieu Basille
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 b
Control: tags -1 + unreproducible moreinfo
Hi Mathieu,
On Sat, Feb 18, 2017 at 3:46 PM, Mathieu Basille
wrote:
> 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.
> Run
Package: revelation
Version: 0.4.14-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
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.
Running reve
5 matches
Mail list logo