Package Details: lib32-networkmanager 1.2.2-1

Git Clone URL: https://aur.archlinux.org/lib32-networkmanager.git (read-only)
Package Base: lib32-networkmanager
Description: Network Management daemon, 32bit libraries
Upstream URL: http://www.gnome.org/projects/NetworkManager/
Licenses: GPL2, LGPL2.1
Submitter: oi_wtf
Maintainer: oi_wtf
Last Packager: oi_wtf
Votes: 33
Popularity: 5.475454
First Submitted: 2013-05-31 21:26
Last Updated: 2016-05-19 00:31

Latest Comments

Jeroen0494 commented on 2016-05-28 13:30

The packages fails to build with the following error:

make[1]: Leaving directory '/home/jeroen/.cache/pacaur/lib32-networkmanager/src/NetworkManager-1.2.2/vapi'
Makefile:645: recipe for target 'check-recursive' failed
make: *** [check-recursive] Error 1
make: Target 'check' not remade because of errors.

This errors occurs after the 'Testsuite summary for NetworkManager 1.2.2' which passes with 11/11 tests succesfully run.

Any clue as to why this happens and how to fix it?

WoefulDerelict commented on 2016-05-19 21:41

IwfY: I suspect this is a flaw in lib32-bluez. The file is part of bluez-libs and is not included in lib32-bluez-libs. The dependency goes unsatisfied when the package is installed as it was undeclared and is not pulled in by the other bluez packages.

UPDATE: I've corrected the issue in lib32-bluez-libs. The headers should now be pulled in when a users installs lib32-bluez-libs. Please try building again after updating lib32-bluez-libs.

IwfY commented on 2016-05-19 07:23

When trying to build this I get the following error:

[...]
make[5]: Entering directory '/.../lib32-networkmanager/src/NetworkManager-1.2.2/src/devices/bluetooth'
CC nm-bluez-manager.lo
CC nm-bluez-device.lo
CC nm-bluez4-adapter.lo
CC nm-bluez4-manager.lo
CC nm-bluez5-manager.lo
CC nm-bt-error.lo
CC nm-device-bt.lo
CC nm-bluez5-dun.lo
nm-bluez5-dun.c:24:27: fatal error: bluetooth/sdp.h: No such file or directory
#include <bluetooth/sdp.h>
^
compilation terminated.

Any idea what could help?

oi_wtf commented on 2016-05-19 00:37

Yes, I intended to add bluez as an optional dependency like NM in [extra].
So the lib32-NM gets as close to NM in [extra] as possible.

lib32-bluez builds fine now, so I've added it now.

WoefulDerelict commented on 2016-05-18 20:18

I was simply pointing out that lib32-bluez-libs was a possible dependency for this package and that it will build the a 32-bit plugin for bluetooth if it is detected. I did not express whether this was desired or useful behaviour, only that it existed.

If it is a useful component then I'd suggest adding lib32-bluez-libs as a make depend and lib32-bluez as an optional dependency of the lib32-networkmanager package like the maintainers have done with the networkmanager package in extra.

The build issues with the lib32-bluez package set have been addressed.

felipec commented on 2016-05-17 23:52

Personally I have no interest in getting bluez-libs to build. In my opinion right now either it should be added as a builddep, or the configure should have --disable-bluez5-dun. As the PKGCONFIG stands now it's kind of broken.

oi_wtf commented on 2016-05-17 23:31

One may get a clean package from an "unclean" enviroment, but you can never *expect" it to be.

Anyway, I'd rather have bluez-libs as dependency, so the focus should be on getting that one to build.

felipec commented on 2016-05-17 23:13

Yes you can. Just do --disable-bluez5-dun, the it doesn't matter if the environment is "unclean" (there isn't such thing).

oi_wtf commented on 2016-05-17 23:09

What I wanted to say was: *If* you want a clean package (which you clearly stated), you'll have to use a clean chroot.
You can't expect to get a clean package from an "unclean" build environment.

And I never said I'd force anyone to anything.
As I said, I wanted to say that I expect Users who want clean packages to use a clean chroot. Sorry if I wasn't clear enough before. English is not my native language.

WoefulDerelict commented on 2016-05-17 21:46

I can understand the benefits of testing package quality by forcing the PKGBUILD to construct a proper build enviromnet from a minimal clean chroot from a maintenance perspective; however, I do not expect the end user to do that.

All comments