GNU bug report logs -
#33832
The VPN service 'org.freedesktop.NetworkManager.openvpn' was not installed.
Previous Next
Reported by: swedebugia <at> riseup.net
Date: Sat, 22 Dec 2018 03:30:02 UTC
Severity: serious
Merged with 36422
Done: Jelle Licht <jlicht <at> fsfe.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33832 in the body.
You can then email your comments to 33832 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Sat, 22 Dec 2018 03:30:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
swedebugia <at> riseup.net
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sat, 22 Dec 2018 03:30:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Dec 22 04:21:24 localhost NetworkManager[289]: <info> [1545448884.2537]
audit: op="connection-activate"
uuid="c3d6b24a-d67c-48a9-8695-2e9dd83c1b07" name="Riseup VPN" pid=414
uid=1000 result="fail" reason="The VPN service
'org.freedesktop.NetworkManager.openvpn' was not installed."
Dec 22 04:22:19 localhost NetworkManager[289]: <info> [1545448939.2045]
device (wlp3s0): set-hw-addr: set MAC address to AE:C7:48:B4:FE:7E
(scanning)
Dec 22 04:22:19 localhost vmunix: [ 3281.066433] IPv6:
ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Dec 22 04:22:19 localhost NetworkManager[289]: <info> [1545448939.2203]
device (wlp3s0): supplicant interface state: inactive -> disabled
Dec 22 04:22:19 localhost NetworkManager[289]: <info> [1545448939.2557]
device (wlp3s0): supplicant interface state: disabled -> inactive
config attached were it is installed systemwide.
my user manifest is also attached were it is also installed.
sdb <at> antelope ~/src/guix$ guix --version
guix (GNU Guix) 0.16.0-3.6ddc63e
running from git.
--
Cheers
Swedebugia
[config.scm (text/plain, attachment)]
[sdb.scm (text/plain, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Wed, 09 Jan 2019 12:55:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 33832 <at> debbugs.gnu.org (full text, mbox):
Hi,
swedebugia <at> riseup.net writes:
> Dec 22 04:21:24 localhost NetworkManager[289]: <info> [1545448884.2537]
> audit: op="connection-activate"
> uuid="c3d6b24a-d67c-48a9-8695-2e9dd83c1b07" name="Riseup VPN" pid=414
> uid=1000 result="fail" reason="The VPN service
> 'org.freedesktop.NetworkManager.openvpn' was not installed."
> Dec 22 04:22:19 localhost NetworkManager[289]: <info> [1545448939.2045]
> device (wlp3s0): set-hw-addr: set MAC address to AE:C7:48:B4:FE:7E
> (scanning)
> Dec 22 04:22:19 localhost vmunix: [ 3281.066433] IPv6:
> ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
> Dec 22 04:22:19 localhost NetworkManager[289]: <info> [1545448939.2203]
> device (wlp3s0): supplicant interface state: inactive -> disabled
> Dec 22 04:22:19 localhost NetworkManager[289]: <info> [1545448939.2557]
> device (wlp3s0): supplicant interface state: disabled -> inactive
>
> config attached were it is installed systemwide.
>
> my user manifest is also attached were it is also installed.
>
> sdb <at> antelope ~/src/guix$ guix --version
> guix (GNU Guix) 0.16.0-3.6ddc63e
>
> running from git.
I can confirm the bug; it makes the network-manager-openvpn useless at
what it's supposed to be helpful with ;-).
Given that it seems to be a DBus error, I tried to modify our
network-manager-service-type so that it would consider the VPN plugins
as well when extending the dbus-system-service:
1 file changed, 10 insertions(+), 7 deletions(-)
gnu/services/networking.scm | 17 ++++++++++-------
modified gnu/services/networking.scm
@@ -919,25 +919,28 @@ and @command{wicd-curses} user interfaces."
(stop #~(make-kill-destructor))))))))
(define network-manager-service-type
- (let
- ((config->package
+ (let*
+ ((config->packages
(match-lambda
- (($ <network-manager-configuration> network-manager)
- (list network-manager)))))
+ (($ <network-manager-configuration> network-manager _ vpn-plugins)
+ `(,network-manager ,@vpn-plugins)))))
(service-type
(name 'network-manager)
(extensions
(list (service-extension shepherd-root-service-type
network-manager-shepherd-service)
- (service-extension dbus-root-service-type config->package)
- (service-extension polkit-service-type config->package)
+ (service-extension dbus-root-service-type config->packages)
+ (service-extension polkit-service-type
+ (compose
+ list
+ network-manager-configuration-network-manager))
(service-extension activation-service-type
(const %network-manager-activation))
(service-extension session-environment-service-type
network-manager-environment)
;; Add network-manager to the system profile.
- (service-extension profile-service-type config->package)))
+ (service-extension profile-service-type config->packages)))
(default-value (network-manager-configuration))
(description
"Run @uref{https://wiki.gnome.org/Projects/NetworkManager,
Unfortunately that didn't work... I'll have to read on DBus to debug
this further. Any help would be appreciated :-)
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Thu, 10 Jan 2019 12:52:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 33832 <at> debbugs.gnu.org (full text, mbox):
Debugging a bit further, it seems that my change to the
network-manager-service-type had the following effect:
A file populated at /etc/dbus-1/system-local.conf now has an include
directive for network-manager-openvpn:
--8<---------------cut here---------------start------------->8---
<includedir>/gnu/store/gw3ckmw2pihc44d23lc8pipfw7wr16g7-network-manager-openvpn-1.8.0/etc/dbus-1/system.d</includedir>
--8<---------------cut here---------------end--------------->8---
There is no /etc/dbus-1/system.conf file, which usually should source
the above system-local.conf, although the package holds a copy of it
such as
/gnu/store/5bda3bgy871dyb9cna4k7gnz002j88rq-dbus-1.12.6/share/dbus-1/system.conf,
and this file has:
--8<---------------cut here---------------start------------->8---
<!-- This is included last so local configuration can override what's
in this standard file -->
<include ignore_missing="yes">/etc/dbus-1/system-local.conf</include>
--8<---------------cut here---------------end--------------->8---
I'm not sure if it works though, because using the Emacs dbus support to
view the available definitions, I cannot see the ones from the
system-local.conf file:
--8<---------------cut here---------------start------------->8---
(require 'dbus)
(dbus-list-activatable-names ':system)
;; Results:
("org.freedesktop.DBus" ;
"org.freedesktop.UPower" ;from /etc/dbus-1/system-services
"org.freedesktop.GeoClue2" ;from /etc/dbus-1/system-services
"org.freedesktop.login1" ;from /etc/dbus-1/system-services
"org.freedesktop.UDisks2" ;from /etc/dbus-1/system-services
"org.freedesktop.ColorHelper" ;from /etc/dbus-1/system-services
"org.freedesktop.PolicyKit1" ;from /etc/dbus-1/system-services
"org.freedesktop.Accounts" ;from /etc/dbus-1/system-services
"org.freedesktop.ColorManager" ;from /etc/dbus-1/system-services
"org.freedesktop.nm_dispatcher") ;from /etc/dbus-1/system-services
--8<---------------cut here---------------end--------------->8---
So it could be that the system-local.conf file is not read in.
I've tried stracing the dbus-daemon (by attaching to it) as suggested by
Ludovic on #guix, but that doesn't mention anything about reading the
files.
So, to debug this further, I've added the documentation to dbus [1] and
in `man dbus-daemon`, we can read:
--8<---------------cut here---------------start------------->8---
DEBUGGING
If you're trying to figure out where your messages are going or why you aren't getting messages, there are
several things you can try.
Remember that the system bus is heavily locked down and if you haven't installed a security policy file to
allow your message through, it won't work. For the session bus, this is not a concern.
The simplest way to figure out what's happening on the bus is to run the dbus-monitor program, which comes
with the D-Bus package. You can also send test messages with dbus-send. These programs have their own man
pages.
If you want to know what the daemon itself is doing, you might consider running a separate copy of the daemon
to test against. This will allow you to put the daemon under a debugger, or run it with verbose output,
without messing up your real session and system daemons.
To run a separate test copy of the daemon, for example you might open a terminal and type:
DBUS_VERBOSE=1 dbus-daemon --session --print-address
The test daemon address will be printed when the daemon starts. You will need to copy-and-paste this address
and use it as the value of the DBUS_SESSION_BUS_ADDRESS environment variable when you launch the applications
you want to test. This will cause those applications to connect to your test bus instead of the
DBUS_SESSION_BUS_ADDRESS of your real session bus.
DBUS_VERBOSE=1 will have NO EFFECT unless your copy of D-Bus was compiled with verbose mode enabled. This is
not recommended in production builds due to performance impact. You may need to rebuild D-Bus if your copy
was not built with debugging in mind. (DBUS_VERBOSE also affects the D-Bus library and thus applications
using D-Bus; it may be useful to see verbose output on both the client side and from the daemon.)
If you want to get fancy, you can create a custom bus configuration for your test bus (see the session.conf
and system.conf files that define the two default configurations for example). This would allow you to
specify a different directory for .service files, for example.
--8<---------------cut here---------------end--------------->8---
This should help in further debbugging the issue, along with this local
definition that enables the verbose mode of dbus:
--8<---------------cut here---------------start------------->8---
gnu/packages/glib.scm | 11 +++++++++++
modified gnu/packages/glib.scm
@@ -68,6 +68,7 @@
;; Export variables up-front to allow circular dependency with the 'xorg'
;; module.
#:export (dbus
+ my-dbus
glib
gobject-introspection
dbus-glib
@@ -156,6 +157,16 @@ or through unencrypted TCP/IP suitable for use behind a firewall with
shared NFS home directories.")
(license license:gpl2+))) ; or Academic Free License 2.1
+(define my-dbus
+ (package
+ (inherit dbus)
+ (name "my-dbus")
+ (arguments
+ (substitute-keyword-arguments
+ (package-arguments dbus)
+ ((#:configure-flags flags)
+ `(cons "--enable-verbose-mode" ,flags))))))
+
(define glib
(package
(name "glib")
--8<---------------cut here---------------end--------------->8---
To be continued...
Maxim
[1]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34028
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Tue, 19 Feb 2019 20:11:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 33832 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Thu, Jan 10, 2019 at 07:51:07AM -0500, Maxim Cournoyer wrote:
>Debugging a bit further, it seems that my change to the
>network-manager-service-type had the following effect:
>
>A file populated at /etc/dbus-1/system-local.conf now has an include
>directive for network-manager-openvpn:
>
>--8<---------------cut here---------------start------------->8---
><includedir>/gnu/store/gw3ckmw2pihc44d23lc8pipfw7wr16g7-network-manager-openvpn-1.8.0/etc/dbus-1/system.d</includedir>
>--8<---------------cut here---------------end--------------->8---
>
>There is no /etc/dbus-1/system.conf file, which usually should source
>the above system-local.conf, although the package holds a copy of it
>such as
>/gnu/store/5bda3bgy871dyb9cna4k7gnz002j88rq-dbus-1.12.6/share/dbus-1/system.conf,
>and this file has:
>
>--8<---------------cut here---------------start------------->8---
><!-- This is included last so local configuration can override what's
>
> in this standard file -->
> <include ignore_missing="yes">/etc/dbus-1/system-local.conf</include>
>--8<---------------cut here---------------end--------------->8---
>
>I'm not sure if it works though, because using the Emacs dbus support to
>view the available definitions, I cannot see the ones from the
>system-local.conf file:
>
>--8<---------------cut here---------------start------------->8---
>(require 'dbus)
>(dbus-list-activatable-names ':system)
>
>;; Results:
>("org.freedesktop.DBus" ;
> "org.freedesktop.UPower" ;from /etc/dbus-1/system-services
> "org.freedesktop.GeoClue2" ;from /etc/dbus-1/system-services
> "org.freedesktop.login1" ;from /etc/dbus-1/system-services
> "org.freedesktop.UDisks2" ;from /etc/dbus-1/system-services
> "org.freedesktop.ColorHelper" ;from /etc/dbus-1/system-services
> "org.freedesktop.PolicyKit1" ;from /etc/dbus-1/system-services
> "org.freedesktop.Accounts" ;from /etc/dbus-1/system-services
> "org.freedesktop.ColorManager" ;from /etc/dbus-1/system-services
> "org.freedesktop.nm_dispatcher") ;from /etc/dbus-1/system-services
>--8<---------------cut here---------------end--------------->8---
>
>So it could be that the system-local.conf file is not read in.
>
>I've tried stracing the dbus-daemon (by attaching to it) as suggested by
>Ludovic on #guix, but that doesn't mention anything about reading the
>files.
>
>So, to debug this further, I've added the documentation to dbus [1] and
>in `man dbus-daemon`, we can read:
>
>
>
>--8<---------------cut here---------------start------------->8---
>DEBUGGING
> If you're trying to figure out where your messages are going or why you aren't getting messages, there are
> several things you can try.
>
> Remember that the system bus is heavily locked down and if you haven't installed a security policy file to
> allow your message through, it won't work. For the session bus, this is not a concern.
>
> The simplest way to figure out what's happening on the bus is to run the dbus-monitor program, which comes
> with the D-Bus package. You can also send test messages with dbus-send. These programs have their own man
> pages.
>
> If you want to know what the daemon itself is doing, you might consider running a separate copy of the daemon
> to test against. This will allow you to put the daemon under a debugger, or run it with verbose output,
> without messing up your real session and system daemons.
>
> To run a separate test copy of the daemon, for example you might open a terminal and type:
>
> DBUS_VERBOSE=1 dbus-daemon --session --print-address
>
> The test daemon address will be printed when the daemon starts. You will need to copy-and-paste this address
> and use it as the value of the DBUS_SESSION_BUS_ADDRESS environment variable when you launch the applications
> you want to test. This will cause those applications to connect to your test bus instead of the
> DBUS_SESSION_BUS_ADDRESS of your real session bus.
>
> DBUS_VERBOSE=1 will have NO EFFECT unless your copy of D-Bus was compiled with verbose mode enabled. This is
> not recommended in production builds due to performance impact. You may need to rebuild D-Bus if your copy
> was not built with debugging in mind. (DBUS_VERBOSE also affects the D-Bus library and thus applications
> using D-Bus; it may be useful to see verbose output on both the client side and from the daemon.)
>
> If you want to get fancy, you can create a custom bus configuration for your test bus (see the session.conf
> and system.conf files that define the two default configurations for example). This would allow you to
> specify a different directory for .service files, for example.
>--8<---------------cut here---------------end--------------->8---
>
>This should help in further debbugging the issue, along with this local
>definition that enables the verbose mode of dbus:
>
>--8<---------------cut here---------------start------------->8---
>gnu/packages/glib.scm | 11 +++++++++++
>
>modified gnu/packages/glib.scm
>@@ -68,6 +68,7 @@
> ;; Export variables up-front to allow circular dependency with the 'xorg'
> ;; module.
> #:export (dbus
>+ my-dbus
> glib
> gobject-introspection
> dbus-glib
>@@ -156,6 +157,16 @@ or through unencrypted TCP/IP suitable for use behind a firewall with
> shared NFS home directories.")
> (license license:gpl2+))) ; or Academic Free License 2.1
>
>+(define my-dbus
>+ (package
>+ (inherit dbus)
>+ (name "my-dbus")
>+ (arguments
>+ (substitute-keyword-arguments
>+ (package-arguments dbus)
>+ ((#:configure-flags flags)
>+ `(cons "--enable-verbose-mode" ,flags))))))
>+
> (define glib
> (package
> (name "glib")
>--8<---------------cut here---------------end--------------->8---
>
>To be continued...
You seem to be on very right track. There is another unexpect problem
- NetworkManager doesn't seem to respect NM_VPN_PLUGIN_PATH in the
right place.
Try this quick patch:
From fc8bbfe018b4f19fb383391c71e3518a9c46e0f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tom=C3=A1=C5=A1=20=C4=8Cech?= <sleep_walker <at> gnu.org>
Date: Sun, 17 Feb 2019 13:23:43 +0100
Subject: [PATCH] respect NM_VPN_PLUGIN_DIR
---
src/vpn/nm-vpn-manager.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/src/vpn/nm-vpn-manager.c b/src/vpn/nm-vpn-manager.c
index 8e708d1..86238c9 100644
--- a/src/vpn/nm-vpn-manager.c
+++ b/src/vpn/nm-vpn-manager.c
@@ -223,6 +223,7 @@ nm_vpn_manager_init (NMVpnManager *self)
GSList *infos, *info;
const char *conf_dir_etc = _nm_vpn_plugin_info_get_default_dir_etc ();
const char *conf_dir_lib = _nm_vpn_plugin_info_get_default_dir_lib ();
+ const char *conf_dir_user = _nm_vpn_plugin_info_get_default_dir_user ();
/* Watch the VPN directory for changes */
file = g_file_new_for_path (conf_dir_lib);
@@ -241,6 +242,14 @@ nm_vpn_manager_init (NMVpnManager *self)
G_CALLBACK (vpn_dir_changed), self);
}
+ file = g_file_new_for_path (conf_dir_user);
+ priv->monitor_etc = g_file_monitor_directory (file, G_FILE_MONITOR_NONE, NULL, NULL);
+ g_object_unref (file);
+ if (priv->monitor_etc) {
+ priv->monitor_id_etc = g_signal_connect (priv->monitor_etc, "changed",
+ G_CALLBACK (vpn_dir_changed), self);
+ }
+
/* first read conf_dir_lib. The name files are not really user configuration, but
* plugin configuration. Hence we expect ~newer~ plugins to install their files
* in /usr/lib/NetworkManager. We want to prefer those files.
@@ -255,6 +264,11 @@ nm_vpn_manager_init (NMVpnManager *self)
try_add_plugin (self, info->data);
g_slist_free_full (infos, g_object_unref);
+ infos = _nm_vpn_plugin_info_list_load_dir (conf_dir_user, TRUE, 0, NULL, NULL);
+ for (info = infos; info; info = info->next)
+ try_add_plugin (self, info->data);
+ g_slist_free_full (infos, g_object_unref);
+
priv->active_services = g_hash_table_new_full (g_str_hash, g_str_equal, g_free, NULL);
}
--
2.20.1
HTH,
S_W
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Wed, 06 Mar 2019 13:20:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 33832 <at> debbugs.gnu.org (full text, mbox):
Hi Tomáš,
Tomáš Čech <sleep_walker <at> gnu.org> skribis:
> On Thu, Jan 10, 2019 at 07:51:07AM -0500, Maxim Cournoyer wrote:
[...]
>>To be continued...
>
> You seem to be on very right track. There is another unexpect problem
> - NetworkManager doesn't seem to respect NM_VPN_PLUGIN_PATH in the
> right place.
>
> Try this quick patch:
>
> From fc8bbfe018b4f19fb383391c71e3518a9c46e0f3 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Tom=C3=A1=C5=A1=20=C4=8Cech?= <sleep_walker <at> gnu.org>
> Date: Sun, 17 Feb 2019 13:23:43 +0100
> Subject: [PATCH] respect NM_VPN_PLUGIN_DIR
Does this patch solve the problem for you? How did you get there? :-)
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Wed, 06 Mar 2019 13:30:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 33832 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Ludo,
On Wed, Mar 06, 2019 at 02:19:20PM +0100, Ludovic Courtès wrote:
>Hi Tomáš,
>
>Tomáš Čech <sleep_walker <at> gnu.org> skribis:
>
>> On Thu, Jan 10, 2019 at 07:51:07AM -0500, Maxim Cournoyer wrote:
>
>[...]
>
>>>To be continued...
>>
>> You seem to be on very right track. There is another unexpect problem
>> - NetworkManager doesn't seem to respect NM_VPN_PLUGIN_PATH in the
>> right place.
>>
>> Try this quick patch:
>>
>> From fc8bbfe018b4f19fb383391c71e3518a9c46e0f3 Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?Tom=C3=A1=C5=A1=20=C4=8Cech?= <sleep_walker <at> gnu.org>
>> Date: Sun, 17 Feb 2019 13:23:43 +0100
>> Subject: [PATCH] respect NM_VPN_PLUGIN_DIR
>
>Does this patch solve the problem for you? How did you get there? :-)
Partially. I was not interested in OpenVPN, but L2TP/IPSec VPN (my new
employer is using) so I was using network-manager-l2tp module with the same problems.
(Actually it is much more painful because it requires some more
patching of xl2tpd and strongswan to bring it up together... They have
somehow hardcoded locations for configuration and secrets...)
But with Maxim's DBus related patches and my NM patch it seemed to be
starting daemons at least.
Best regards,
S_W
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Mon, 24 Jun 2019 19:35:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 33832 <at> debbugs.gnu.org (full text, mbox):
Hi S_W, Maxim
Tomáš Čech <sleep_walker <at> gnu.org> writes:
> Hi Ludo,
> [...]
>
> But with Maxim's DBus related patches and my NM patch it seemed to be
> starting daemons at least.
Do you still have the patches for these changes lying around? I am
trying to get network-manager-vpnc packaged+working, but it seems this
issue will also need to be solved first.
>
> Best regards,
>
> S_W
All the best,
Jelle
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33832
; Package
guix
.
(Wed, 26 Jun 2019 08:21:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 33832 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi!
On Mon, Jun 24, 2019 at 09:34:34PM +0200, Jelle Licht wrote:
>Hi S_W, Maxim
>
>Tomáš Čech <sleep_walker <at> gnu.org> writes:
>
>> Hi Ludo,
>> [...]
>>
>> But with Maxim's DBus related patches and my NM patch it seemed to be
>> starting daemons at least.
>
>Do you still have the patches for these changes lying around? I am
>trying to get network-manager-vpnc packaged+working, but it seems this
>issue will also need to be solved first.
I didn't have time to refresh it to our current version - it's just in the mail:
https://www.mail-archive.com/bug-guix <at> gnu.org/msg11776.html
Best regards,
S_W
[signature.asc (application/pgp-signature, inline)]
Merged 33832 36422.
Request was from
Raghav Gururajan <rvgn <at> disroot.org>
to
control <at> debbugs.gnu.org
.
(Fri, 28 Jun 2019 20:03:02 GMT)
Full text and
rfc822 format available.
Severity set to 'serious' from 'normal'
Request was from
Raghav Gururajan <rvgn <at> disroot.org>
to
control <at> debbugs.gnu.org
.
(Tue, 02 Jul 2019 18:58:03 GMT)
Full text and
rfc822 format available.
Reply sent
to
Jelle Licht <jlicht <at> fsfe.org>
:
You have taken responsibility.
(Fri, 27 Sep 2019 20:47:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
swedebugia <at> riseup.net
:
bug acknowledged by developer.
(Fri, 27 Sep 2019 20:47:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 33832-done <at> debbugs.gnu.org (full text, mbox):
> [snip]
> I didn't have time to refresh it to our current version - it's just in the mail:
>
> https://www.mail-archive.com/bug-guix <at> gnu.org/msg11776.html
Closing, this was fixed a while ago in commit
40557aeab594907bf56b0a2a367061dbdd19f4aa.
Reply sent
to
Jelle Licht <jlicht <at> fsfe.org>
:
You have taken responsibility.
(Fri, 27 Sep 2019 20:47:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Raghav Gururajan <rvgn <at> disroot.org>
:
bug acknowledged by developer.
(Fri, 27 Sep 2019 20:47:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 26 Oct 2019 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 177 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.