I decided to try removing tclx from the system and once that got done it
broke no other dependency and the upgrade went off without a hitch. That
tclx package had 8.4 for a version number so wasn't keeping up with the
rest of tcl.
--
On Mon, Aug 21, 2017 at 09:34:30PM -0400, Jude DaShiell wrote:
> I have the tcl and tclx packages installed since those are emacspeak
> dependencies and I use emacspeak for now.
> Earlier today I had this upgrade failure:
>
> error: failed to prepare transaction (could not satisfy dependencies)
>
I have the tcl and tclx packages installed since those are emacspeak
dependencies and I use emacspeak for now.
Earlier today I had this upgrade failure:
error: failed to prepare transaction (could not satisfy dependencies)
:: tclx: installing tcl (8.6.7-1) breaks dependency 'tcl=8.6.6'
Do I nee
On Mon, Aug 21, 2017 at 5:48 PM, Damjan Georgievski via arch-general <
arch-general@archlinux.org> wrote:
> > I use psycopg2 for postgres access in my pyramid web-app, and like most
> > (all?) python developers all the dependencies are in a virtualenv,
> > including psycopg2 itself.
> >
> > This m
So reinstalling psycopg2 with `pip install --no-binary :all: psycopg2`
works. Still wondering whether this is an issue to raise upstream.
On Mon, Aug 21, 2017 at 5:41 PM, Oon-Ee Ng wrote:
> I use psycopg2 for postgres access in my pyramid web-app, and like most
> (all?) python developers all the
> I use psycopg2 for postgres access in my pyramid web-app, and like most
> (all?) python developers all the dependencies are in a virtualenv,
> including psycopg2 itself.
>
> This means, of course, that the psycopg2 wheel is precompiled.
>
> With the recent glibc-2.26 update, I can no longer impor
I use psycopg2 for postgres access in my pyramid web-app, and like most
(all?) python developers all the dependencies are in a virtualenv,
including psycopg2 itself.
This means, of course, that the psycopg2 wheel is precompiled.
With the recent glibc-2.26 update, I can no longer import psycopg2.
7 matches
Mail list logo
