Yes, that is another symptom of having an old checkout of wip.
cd /usr/pkgsrc/wip
git pull
Thomas
On Tue, Sep 14, 2021 at 04:12:34PM +0200, Mario Marietto wrote:
> netbsd-marietto# ping google.itPING google.it (216.58.209.35): 56 data
> bytes64 bytes from 216.58.209.35: icmp_seq=0 ttl=112 time=22.236755
> ms64 bytes from 216.58.209.35: icmp_seq=1 ttl=112 time=22.115848
> ms^C----google.it PING Statistics----2 packets transmitted, 2 packets
> received, 0.0% packet lossround-trip min/avg/max/stddev =
> 22.115848/22.176302/22.236755/0.085494 msnetbsd-marietto# make=>
> Bootstrap dependency digest>=20010302: found digest-20190127=>
> Checksum SHA1 OK for virt-manager-2.2.1.tar.gz=> Checksum RMD160 OK
> for virt-manager-2.2.1.tar.gz=> Checksum SHA512 OK for
> virt-manager-2.2.1.tar.gz===> Installing dependencies for
> virt-manager-2.2.1==========================================================================The
> following variables will affect the build process of this
> package,virt-manager-2.2.1. Their current value is shown below:
> * PYTHON_VERSION_DEFAULT = 38Based on these variables, the following
> variables have been set: * PYPACKAGE = python38You may want to
> abort the process now with CTRL-C and change the valueof variables in
> the first group before continuing. Be sure to run`/usr/bin/make
> clean' after the
> changes.===========================================================================>
> Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.68.3=> Tool
> dependency intltool>=0.40.0: found intltool-0.51.0nb6=> Tool
> dependency perl>=5.0: found perl-5.34.0nb2=> Build dependency
> x11-links>=1.34: found x11-links-1.34=> Build dependency
> cwrappers>=20150314: found cwrappers-20180325=> Full dependency
> py38-gobject3-[0-9]*: found py38-gobject3-3.36.1nb1=> Full dependency
> py38-libvirt-[0-9]*: found py38-libvirt-5.8.0=> Full dependency
> libosinfo>=1.2.0: found libosinfo-1.2.0=> Full dependency
> libvirt-glib>=2.0.0: NOT found=> Verifying reinstall for
> ../../wip/libvirt-glib=> Bootstrap dependency digest>=20010302: found
> digest-20190127=> Fetching v2.0.0.tar.gz=> Total size: 245817
> bytesRequesting
> https://github.com/libvirt/libvirt-glib/archive/2.0.0.tar.gzRedirected
> to https://codeload.github.com/libvirt/libvirt-glib/tar.gz/2.0.0Requesting
> https://codeload.github.com/libvirt/libvirt-glib/tar.gz/2.0.0ftp:
> Error retrieving file `404 Not Found'fetch: Unable to fetch expected
> file v2.0.0.tar.gzTrying [2a04:4e42::262]:80 ...ftp: Can't connect to
> `2a04:4e42::262:80': No route to hostTrying [2a04:4e42:200::262]:80
> ...ftp: Can't connect to `2a04:4e42:200::262:80': No route to
> hostTrying [2a04:4e42:400::262]:80 ...ftp: Can't connect to
> `2a04:4e42:400::262:80': No route to hostTrying
> [2a04:4e42:600::262]:80 ...ftp: Can't connect to
> `2a04:4e42:600::262:80': No route to hostTrying 151.101.1.6:80
> ...Requesting http://cdn.NetBSD.org/pub/pkgsrc/distfiles/libvirt-glib/v2.0.0.tar.gzftp:
> Error retrieving file `404 Not Found'fetch: Unable to fetch expected
> file v2.0.0.tar.gzftp: Can't connect to `2001:470:a085:999::21:80': No
> route to hostftp: Can't connect to `ftp6.NetBSD.org:http'fetch: Unable
> to fetch expected file v2.0.0.tar.gzTrying
> [2001:660:3302:282a:204:75ff:fe9f:9e11]:80 ...ftp: Can't connect to
> `2001:660:3302:282a:204:75ff:fe9f:9e11:80': No route to hostTrying
> 132.227.74.11:80 ...Requesting
> http://ftp.fr.NetBSD.org/pub/pkgsrc/distfiles/libvirt-glib/v2.0.0.tar.gzftp:
> Error retrieving file `404 Not Found'fetch: Unable to fetch expected
> file v2.0.0.tar.gzTrying [2001:470:a085:999::21]:80 ...ftp: Can't
> connect to `2001:470:a085:999::21:80': No route to hostTrying
> 199.233.217.201:80 ...Requesting
> http://ftp.NetBSD.org/pub/pkgsrc/distfiles/libvirt-glib/v2.0.0.tar.gzftp:
> Error retrieving file `404 Not Found'fetch: Unable to fetch expected
> file v2.0.0.tar.gz
>
>
> Il giorno mar 14 set 2021 alle ore 15:28 Thomas Klausner <wiz%netbsd.org@localhost>
> ha scritto:
>
> > On Tue, Sep 14, 2021 at 02:18:05PM +0100, Chavdar Ivanov wrote:
> > > On Tue, 14 Sept 2021 at 13:58, Mario Marietto <marietto2008%gmail.com@localhost>
> > wrote:
> > > >
> > > > So,let's make a recap of what I've experimented :
> > > >
> > > > 1) if I make the installation of virt-manager using pkgin virt-manager
> > I see the error :
> > > >
> > > > netbsd-marietto# virt-manager
> > > > Traceback (most recent call last):
> > > > File "/usr/pkg/share/virt-manager/virt-manager.py", line 386, in
> > <module>
> > > > main()
> > > > File "/usr/pkg/share/virt-manager/virt-manager.py", line 247, in
> > main
> > > > from virtManager import cli
> > > > File "/usr/pkg/share/virt-manager/virtManager/cli.py", line 29, in
> > <module>
> > > > import libvirt
> > > > ImportError: No module named libvirt
> > > >
> > > > 2) and if I go under the folder /usr/pkgsrc/wip/virt-manager and I do
> > a make I get the following error :
> > > >
> > > > => Automatic manual page handling
> > > > => Generating post-install file lists
> > > > pkg_create: can't stat
> > `/usr/pkgsrc/wip/libosinfo/work/.destdir/usr/pkg/share/vala/vapi/libosinfo-1.0.vapi'
> > >
> > >
> > > You probably have a problem with lang/vala. My version is 0.52.4 and
> > > the file you indicate as missing is correctly generated in my build.
> >
> > The package was missing the vala dependency completely, so I guess Mario
> > needs to update the wip checkout.
> > Thomas
> >
>
>
> --
> Mario.