From: Jelle Licht <jlicht@fsfe.org>
To: 37759@debbugs.gnu.org
Subject: bug#37759: network-manager-openvpn broken since network-manager-applet update
Date: Tue, 15 Oct 2019 10:26:40 +0200 [thread overview]
Message-ID: <87a7a24dof.fsf@jlicht.xyz> (raw)
Commit 8fc3a337ab420dc9f80472ce057eae603fc892d3, the update of
network-manager-applet to 1.8.24, broke network-manager-openvpn:
--8<---------------cut here---------------start------------->8---
checking for LIBNM_GTK... no
configure: error: Package requirements (libnm-gtk >= 1.7.0) were not met:
No package 'libnm-gtk' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBNM_GTK_CFLAGS
and LIBNM_GTK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
command "/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash" "./configure" "CONFIG_SHELL=/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash" "SHELL=/gnu/store/29jhbbg1hf557x8j53f9sxd9imlmf02a-bash-minimal-5.0.7/bin/bash" "--prefix=/gnu/store/0rgybwyxiy7b74byqr3ld303l7iy99jx-network-manager-openvpn-1.8.4" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--enable-absolute-paths" "--localstatedir=/var" failed with status 1
builder for `/gnu/store/jbbzxdd8jqjdp7hj1jskd09cyggrrl0k-network-manager-openvpn-1.8.4.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---
I already verified that updating network-manager-openvpn to the latest
release (1.8.10) does not fix this issue.
next reply other threads:[~2019-10-15 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 8:26 Jelle Licht [this message]
2019-10-15 13:59 ` bug#37759: network-manager-openvpn broken since network-manager-applet update Tobias Geerinckx-Rice via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7a24dof.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=37759@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).