[aur-general] netcf and the libnl rebuild
Does anyone know netcf[1]? It still needs a rebuild[2] for the libnl 3.2 bump and it seems to be outdated as well (0.1.7 in our repos, 0.1.9 upstream). Ubuntu has libnl 3.2 patches[3] for it, but they don't apply to the upstream 0.1.9 sources. I'd rather have this handled properly instead of just blindly rebuilding against libnl1. [1]: https://www.archlinux.org/packages/community/x86_64/netcf/ [2]: https://www.archlinux.org/todo/124/ [3]: https://launchpad.net/ubuntu/+archive/primary/+files/netcf_0.1.9-2ubuntu3.de...
It doesn't seem like Fedora has any patches either [1]. I'd expect them to be the first ones to have patches, since they are the main developers of netcf, but they haven't upgraded libnl either [2]. There's an (automated) bug report about the new libnl [3]. Hopefully, the developers can do something about it. [1]: http://koji.fedoraproject.org/koji/ [2]: http://koji.fedoraproject.org/koji/packageinfo?packageID=478 [3]: https://bugzilla.redhat.com/show_bug.cgi?id=781384
Date: Sat, 11 Feb 2012 16:13:54 +0100 From: jan.steffens@gmail.com To: aur-general@archlinux.org; arch-dev-public@archlinux.org; pupykin.s@gmail.com Subject: [aur-general] netcf and the libnl rebuild
Does anyone know netcf[1]? It still needs a rebuild[2] for the libnl 3.2 bump and it seems to be outdated as well (0.1.7 in our repos, 0.1.9 upstream).
Ubuntu has libnl 3.2 patches[3] for it, but they don't apply to the upstream 0.1.9 sources.
I'd rather have this handled properly instead of just blindly rebuilding against libnl1.
[1]: https://www.archlinux.org/packages/community/x86_64/netcf/ [2]: https://www.archlinux.org/todo/124/ [3]: https://launchpad.net/ubuntu/+archive/primary/+files/netcf_0.1.9-2ubuntu3.de...
On Sat, Feb 11, 2012 at 4:13 PM, Jan Steffens <jan.steffens@gmail.com> wrote:
Does anyone know netcf[1]? It still needs a rebuild[2] for the libnl 3.2 bump and it seems to be outdated as well (0.1.7 in our repos, 0.1.9 upstream).
Ubuntu has libnl 3.2 patches[3] for it, but they don't apply to the upstream 0.1.9 sources.
I'd rather have this handled properly instead of just blindly rebuilding against libnl1.
[1]: https://www.archlinux.org/packages/community/x86_64/netcf/ [2]: https://www.archlinux.org/todo/124/ [3]: https://launchpad.net/ubuntu/+archive/primary/+files/netcf_0.1.9-2ubuntu3.de...
Seems like we need to build netcf with libnl3, since libvirt links to both libnetcf and libpcap (already built against libnl3). Also see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651033 . Too bad Ubuntu's netcf is so far removed from upstream. Can anyone make a patch, please?
On Sat, Feb 11, 2012 at 6:49 PM, Jan Steffens <jan.steffens@gmail.com> wrote:
Seems like we need to build netcf with libnl3, since libvirt links to both libnetcf and libpcap (already built against libnl3).
Also see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651033 .
Too bad Ubuntu's netcf is so far removed from upstream. Can anyone make a patch, please?
Alternatively, what functionality will we lose if libvirt is build without netcf?
On 02/11/2012 07:06 PM, Jan Steffens wrote:
Alternatively, what functionality will we lose if libvirt is build without netcf?
"--with-netcf libnetcf support to configure physical host network" That's what ./configure tells me for libvirt. Quick google has it that this is used by libvirt to configure network interfaces on the physical host. So keeping netcf support would be a good thing for folks having e.g. bridged network setups using libvirt, which is quite common if one virtualizes is complete server environment. -- Christoph AUR, IRC: kritztopf BBS, Github: kritter
As far as I know, it's also required for NAT to work. ----------------------------------------
Date: Sat, 11 Feb 2012 21:26:00 +0100 From: mail@cvigano.de To: aur-general@archlinux.org Subject: Re: [aur-general] netcf and the libnl rebuild
On 02/11/2012 07:06 PM, Jan Steffens wrote:
Alternatively, what functionality will we lose if libvirt is build without netcf?
"--with-netcf libnetcf support to configure physical host network"
That's what ./configure tells me for libvirt. Quick google has it that this is used by libvirt to configure network interfaces on the physical host.
So keeping netcf support would be a good thing for folks having e.g. bridged network setups using libvirt, which is quite common if one virtualizes is complete server environment.
-- Christoph AUR, IRC: kritztopf BBS, Github: kritter
participants (3)
-
Christoph Vigano
-
Jan Steffens
-
小龙 陈