From: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin@cygwin.com, Jason Pyeron <jpyeron@pdinc.us>
Subject: Re: RE: libxml2 and python not happy... solution downgrade libxml2
Date: Mon, 1 Apr 2024 18:58:02 +0100 [thread overview]
Message-ID: <e0c57470-ffc5-4760-b566-3777510791e0@dronecode.org.uk> (raw)
In-Reply-To: <23ace91b-ac92-3382-8b78-e63cf6f65255@dronecode.org.uk>
On 20/05/2023 17:30, Jon Turney via Cygwin wrote:
> On 10/05/2023 15:20, Jason Pyeron via Cygwin wrote:
>> I guess I will have to adopt the virt-manager package... please put it
>> on my plate :(
>
> Well, that wasn't quite the response I was expecting, but thanks very
> much for helping!
>
> I have added 'virt-manager' to your packages.
So, cleaning up the final python2 bits, I got around back to looking at
this again. I've made minor updates to python-libvirt and virt-manager,
which gets something which runs.
But it just sits there, apparently trying to connect to a local QEMU
hypervisor I don't have, but that's what the previous, python2 version
does as well...
I'm guessing that perhaps the only sensible way to run this on Cygwin is
with the '--connect' option to a remote hypervisior. Or maybe it's
totally broken.
> [...]
>>> -----Original Message-----
>>> From: Jon Turney <jon.turney@dronecode.org.uk>
>>> Sent: Wednesday, May 10, 2023 10:05 AM
>>> To: Jason Pyeron <jpyeron@pdinc.us>; The Cygwin Mailing List
>>> <cygwin@cygwin.com>
>>> Subject: Re: libxml2 and python not happy... solution downgrade libxml2
>>>
>>> On 09/05/2023 23:33, Jason Pyeron via Cygwin wrote:
>>>> $ virt-manager
>>>> Traceback (most recent call last):
>>>> File "/usr/share/virt-manager/virt-manager", line 35, in <module>
>>>> from virtinst import util as util
>>>> File "/usr/share/virt-manager/virtinst/__init__.py", line 18, in
>>>> <module>
>>>> from virtcli import CLIConfig as _CLIConfig
>>>> File "/usr/share/virt-manager/virtcli/__init__.py", line 3, in
>>>> <module>
>>>> from .cliconfig import CLIConfig
>>>> File "/usr/share/virt-manager/virtcli/cliconfig.py", line 24, in
>>>> <module>
>>>> import ConfigParser
>>>> ModuleNotFoundError: No module named 'ConfigParser'
>>>>
>>> [...]
>>>>
>>>> #downgrade libxml2...
>>>>
>>>> $ cygcheck -c libxml2 python27-libxml2
>>>> Cygwin Package Information
>>>> Package Version Status
>>>> libxml2 2.9.10-2 OK
>>>> python27-libxml2 2.9.10-2 OK
>>>>
>>>> jpyeron@blackfat ~
>>>> $ ./test.py
>>>>
>>>> jpyeron@blackfat ~
>>>> $ virt-manager
>>>
>>> Right. The real problem here is that virt-manager is still using
>>> python2, which long past EOL, and is planned to be removed.
>>>
>>> The current plan, per [1] is for virt-manager to become uninstallable
>>> after this, and see if anyone complains.
>>>
>>> If virt-manager is important to you, perhaps you could help us bring it
>>> up to date?
>>>
>>> [1] https://cygwin.com/pipermail/cygwin-apps/2023-April/042778.html
prev parent reply other threads:[~2024-04-01 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 22:33 Jason Pyeron
2023-05-10 14:05 ` Jon Turney
2023-05-10 14:20 ` Jason Pyeron
2023-05-20 16:30 ` Jon Turney
2024-04-01 17:58 ` Jon Turney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0c57470-ffc5-4760-b566-3777510791e0@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=jpyeron@pdinc.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).