Re: Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

2019-06-26 Thread Viktor Ransmayr
Hello Matt & Community, Am Mittwoch, 26. Juni 2019 08:41:56 UTC+2 schrieb Matt Wilkie: > > Believed fixed as of a few minutes ago. Thanks for documenting the > problem, one less thing for me to do when I ran into it myself. I didn't > have to spend time figuring out if it was just me :) > > It s

Re: Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

2019-06-25 Thread Matt Wilkie
Believed fixed as of a few minutes ago. Thanks for documenting the problem, one less thing for me to do when I ran into it myself. I didn't have to spend time figuring out if it was just me :) It seems we need to require PyQt 5.12+ now because of upstream changes in how the libraries are named

Re: Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

2019-06-19 Thread Viktor Ransmayr
Hello Edward, Am Mittwoch, 19. Juni 2019 07:50:17 UTC+2 schrieb Edward K. Ream: > > On Wed, Jun 19, 2019 at 12:44 AM Viktor Ransmayr > wrote: > >> As I reported yesterday into the announcement thread of Leo 6.0 beta 1 >> installation into a **new** virtual environment using pip & PyPI is working

Re: Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

2019-06-18 Thread Edward K. Ream
On Wed, Jun 19, 2019 at 12:44 AM Viktor Ransmayr wrote: > As I reported yesterday into the announcement thread of Leo 6.0 beta 1 > installation into a **new** virtual environment using pip & PyPI is working > as well. > > However, when I tried to install Leo 6.0 beta 1 into **existing* virtual >

Problem when trying to upgrade a version of Leo in an existing VE to Leo 6.0 beta 1

2019-06-18 Thread Viktor Ransmayr
As I reported yesterday into the announcement thread of Leo 6.0 beta 1 installation into a **new** virtual environment using pip & PyPI is working as well. However, when I tried to install Leo 6.0 beta 1 into **existing* virtual environments I ran into trouble. - See attached logs. @Matt Wilk