-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing PyGObject fails with pip on Debian Testing #183
Comments
If you mean pip install pygobject being broken on Debian sid/Ubuntu focal. Yes, I've noticed that it's broken, and it worked 1-2 weeks ago, and I don't quite know why it fails. I've only checked with Arch so far where things still seem to work, so I hope it's a temporary error :/ |
ok, i just added more info... does that help? |
yes root@ant(47)~# dpkg -l | grep python3.8-dev |
yeah, just noticed the i386 part. That's... really weird. This error is different to what I meant btw (and might only affect Debian sid) |
that is ok :) glad someone is listening even if i don't know what is going on. i'm too much of a python newbie to really understand how it does some things... still learning... :) thanks, i appreciate it even if it ends up the error is elsewhere... |
So somehow your compiler gets passed "-m32" (see in your logs) which makes it try to compile for 32 bit which in turn makes it look for the 32bit Python dev files. Not sure why. Do you have any CFLAGS set in your environment? |
i actually do! oh my... how dumb of me. another project does use them and i didn't switch them off... i think this is python and not C... oops. |
ok, progress! at least not that error any more:
no idea what that means either, but at least it is getting past previous error. :) thanks |
Yes, that's the error I'm currently having as well. No idea sadly :( |
that is ok, good thing this isn't world critical just something i was going play with. can i backtrack on dependencies to get a previous gobject version that will work (or something else)? i've not changed any of my code so it is only some other thing that is causing this. |
Old versions also fail to install, so I don't have a workaround right now. |
ok, thank you, i guess you can close this then. :) hope you have a good day in the middle of all the rest of what is going on... |
I've filed a bug report with pip: pypa/pip#7946 |
i'm nosing around. wondering if this is the base issue... looks related. no idea where the solution might be. pypa/wheel#344 not sure... |
The workaround is to install pip via pypi as the Debian version is broken: (in the venv) |
great! thank you so much! :) i verify that this fixed all the problems. :) |
Thanks for confirming. I think we can close this. |
ok, i'm not sure if this error is in Debian Testing or in Pycairo so I am sorry if this error should be filed with Debian or not. As they are in the middle of the 3.8 transition perhaps it is an issue there, but I can't tell myself as I'm not really sure what is going on.
to me it looks like the build process is trying to set up a 32 bit executable (-m32) and my system is a 64 bit.
while i do now have some i386 chunks on my system this error was happening before i added them (trying to see if it would make it work). so far no luck.
thanks for any ideas or feedback. :)
The text was updated successfully, but these errors were encountered: