From owner at bugs.debian.org Tue Dec 10 15:51:03 2019 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 10 Dec 2019 15:51:03 +0000 Subject: [Resolvconf-devel] Processed: fixed 832394 in 1.80 References: <1575992959-1121-bts-andrewsh@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > fixed 832394 1.80 Bug #832394 [resolvconf] Broken $PATH is propagated to hook scripts There is no source info for the package 'resolvconf' at version '1.80' with architecture '' Unable to make a source version for version '1.80' Marked as fixed in versions 1.80. > thanks Stopping processing here. Please contact me if you need assistance. -- 832394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832394 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Tue Dec 10 16:09:03 2019 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 10 Dec 2019 16:09:03 +0000 Subject: [Resolvconf-devel] Bug#832394: marked as done (Broken $PATH is propagated to hook scripts) References: <20160725004515.GA2400@mycre.ws> Message-ID: Your message dated Tue, 10 Dec 2019 16:06:10 +0000 with message-id and subject line Bug#832394: fixed in resolvconf 1.80 has caused the Debian Bug report #832394, regarding Broken $PATH is propagated to hook scripts to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 832394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832394 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Robert Edmonds Subject: Broken $PATH is propagated to hook scripts Date: Sun, 24 Jul 2016 20:45:15 -0400 Size: 3152 URL: -------------- next part -------------- An embedded message was scrubbed... From: Andrej Shadura Subject: Bug#832394: fixed in resolvconf 1.80 Date: Tue, 10 Dec 2019 16:06:10 +0000 Size: 7530 URL: From owner at bugs.debian.org Tue Dec 10 16:09:06 2019 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 10 Dec 2019 16:09:06 +0000 Subject: [Resolvconf-devel] Bug#847440: marked as done (resolvconf: run resolvconf service before any networking service) References: <148118966718.19296.12582304967135804514.reportbug@foudres> Message-ID: Your message dated Tue, 10 Dec 2019 16:06:10 +0000 with message-id and subject line Bug#847440: fixed in resolvconf 1.80 has caused the Debian Bug report #847440, regarding resolvconf: run resolvconf service before any networking service to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 847440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Ryan Harper Subject: resolvconf: run resolvconf service before any networking service Date: Thu, 08 Dec 2016 03:34:27 -0600 Size: 3770 URL: -------------- next part -------------- An embedded message was scrubbed... From: Andrej Shadura Subject: Bug#847440: fixed in resolvconf 1.80 Date: Tue, 10 Dec 2019 16:06:10 +0000 Size: 7493 URL: From owner at bugs.debian.org Tue Dec 10 16:09:09 2019 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 10 Dec 2019 16:09:09 +0000 Subject: [Resolvconf-devel] Bug#877695: marked as done (resolvconf: systemd predictable interface names in interface-order?) References: <150712213101.32414.10525021078307792915.reportbug@annuminas.mathom.us> Message-ID: Your message dated Tue, 10 Dec 2019 16:06:10 +0000 with message-id and subject line Bug#877695: fixed in resolvconf 1.80 has caused the Debian Bug report #877695, regarding resolvconf: systemd predictable interface names in interface-order? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 877695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877695 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Michael Stone Subject: resolvconf: systemd predictable interface names in interface-order? Date: Wed, 04 Oct 2017 09:02:11 -0400 Size: 2878 URL: -------------- next part -------------- An embedded message was scrubbed... From: Andrej Shadura Subject: Bug#877695: fixed in resolvconf 1.80 Date: Tue, 10 Dec 2019 16:06:10 +0000 Size: 7529 URL: From owner at bugs.debian.org Tue Dec 10 16:09:11 2019 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 10 Dec 2019 16:09:11 +0000 Subject: [Resolvconf-devel] Bug#905907: marked as done (resolvconf: /etc/resolvconf/interface-order uses legacy device name patterns like @(br|eth)*) References: <0d3297d8-0cfc-3c4a-8c48-b65a2496b646@telemetry.co.uk> Message-ID: Your message dated Tue, 10 Dec 2019 16:06:11 +0000 with message-id and subject line Bug#905907: fixed in resolvconf 1.80 has caused the Debian Bug report #905907, regarding resolvconf: /etc/resolvconf/interface-order uses legacy device name patterns like @(br|eth)* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 905907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905907 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: markMLl.debian at telemetry.co.uk Subject: resolvconf: /etc/resolvconf/interface-order uses legacy device name patterns like @(br|eth)* Date: Sat, 11 Aug 2018 13:12:25 +0000 Size: 3109 URL: -------------- next part -------------- An embedded message was scrubbed... From: Andrej Shadura Subject: Bug#905907: fixed in resolvconf 1.80 Date: Tue, 10 Dec 2019 16:06:11 +0000 Size: 7530 URL: