Am 08.09.18 um 19:05 schrieb Laurent Bigonville:
> Package: network-manager
> Version: 1.12.2-3
> Severity: normal
> File: /etc/NetworkManager/dispatcher.d/01-ifupdown
>
> Hi,
>
> In the /etc/NetworkManager/dispatcher.d/01-ifupdown file there is a
> comment that states that the pre-up is not impl
Processing commands for cont...@bugs.debian.org:
> forcemerge 568954 908340
Bug #568954 [network-manager] ifupdown: network-manager does not support
pre-up/pre-down commands
Bug #518368 [network-manager] network-manager: NM doesn't seem to use
/etc/network/if-* directories anymore
Bug #540123 [n
Package: network-manager
Version: 1.12.2-3
Severity: normal
File: /etc/NetworkManager/dispatcher.d/01-ifupdown
Hi,
In the /etc/NetworkManager/dispatcher.d/01-ifupdown file there is a
comment that states that the pre-up is not implemented.
But looking at the linked bugreport it seems that this is
Your message dated Sat, 08 Sep 2018 17:04:20 +
with message-id
and subject line Bug#907902: fixed in network-manager-applet 1.8.18-1
has caused the Debian Bug report #907902,
regarding network-manager-openvpn won't save changes in username or password
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 08 Sep 2018 18:42:36 +0200
Source: network-manager-applet
Binary: network-manager-gnome libnma0 libnma-dev gir1.2-nma-1.0
Architecture: source
Version: 1.8.18-1
Distribution: unstable
Urgency: medium
Maintainer: Ut
network-manager-applet_1.8.18-1_source.changes uploaded successfully to
localhost
along with the files:
network-manager-applet_1.8.18-1.dsc
network-manager-applet_1.8.18.orig.tar.xz
network-manager-applet_1.8.18-1.debian.tar.xz
network-manager-applet_1.8.18-1_source.buildinfo
Greetings,
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 08 Sep 2018 18:23:20 +0200
Source: network-manager
Binary: network-manager network-manager-dev libnm0 libnm-dev gir1.2-nm-1.0
network-manager-config-connectivity-debian
Architecture: source
Version: 1.13.90-1
Dist
network-manager_1.13.90-1_source.changes uploaded successfully to localhost
along with the files:
network-manager_1.13.90-1.dsc
network-manager_1.13.90.orig.tar.xz
network-manager_1.13.90-1.debian.tar.xz
network-manager_1.13.90-1_source.buildinfo
Greetings,
Your Debian queue daemo
Processing commands for cont...@bugs.debian.org:
> tags 907902 - moreinfo
Bug #907902 [network-manager-gnome] network-manager-openvpn won't save changes
in username or password
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
907902: https
Processing commands for cont...@bugs.debian.org:
> tags 907902 = fixed-upstream
Bug #907902 [network-manager-gnome] network-manager-openvpn won't save changes
in username or password
Added tag(s) fixed-upstream; removed tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> reassign 908310 network-manager 1.12.2-3
Bug #908310 [network-manager-vpnc] Original DNS kept in resolv.conf when
resolved is used
Bug reassigned from package 'network-manager-vpnc' to 'network-manager'.
No longer marked as found in versions netw
Package: network-manager-vpnc
Version: 1.2.6-1
Severity: important
Hi,
It seems that when the VPN connection is established, the original DNS
servers are kept and the DNS coming from the VPN are added at the top.
This was OK before, but this is not OK anymore if resolved is used as
resolved migh
12 matches
Mail list logo