Debian Bug report logs - #1031236
ifupdown: dns-nameservers with systemd-resolved is broken

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Dmytro Kolesnykov <gray@bunker.org.ua>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Cc: Dmytro Kolesnykov <gray@bunker.org.ua>

Subject: ifupdown: dns-nameservers with systemd-resolved is broken

Date: Mon, 13 Feb 2023 20:38:23 +0200

Package: ifupdown
Version: 0.8.41
Severity: normal

Dear Maintainer,

I was doing my network setup, which included statically configured
logical interfaces. So there were dns-nameservers entries in my
/etc/network/interfaces. My configuration files is below (the actual
IPs and MACs is wiped).

I noted that ifup with my setup is producing error messages like this:

...
guessnet: Started tests
guessnet: 3 candidates
guessnet: Got ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX
guessnet: ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX matches
guessnet: Notified success of scan peer 192.168.0.1 XX:XX:XX:XX:XX:XX
guessnet: Removing candidate enp4s0-direct
guessnet: Keeping candidate enp4s0-router
guessnet: We had changes, notifying the listener
guessnet: Got ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX
/etc/network/if-up.d/resolved: 69: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-enp4s0: DNS=192.168.0.1 192.168.0.12: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument

I have found discussion about similar problem there:
https://unix.stackexchange.com/questions/714901/dns-broken-when-using-ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0

Also I had a look into the /etc/network/if-up.d/resolved and I assume
this is a typo in the line 69:
https://salsa.debian.org/debian/ifupdown/-/blob/master/debian/if-up.d/resolved#L69

Then I edited mine /etc/network/if-up.d/resolved this way:

--- a/network/if-up.d/resolved
+++ b/network/if-up.d/resolved
@@ -43,11 +43,11 @@ if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
     fi
     if  [ -n "$NEW_DNS" ]; then
         cat <<EOF >"$mystatedir/ifupdown-${ADDRFAM}-$interface"
-"$DNS"="$NEW_DNS"
+$DNS="$NEW_DNS"
 EOF
         if  [ -n "$NEW_DOMAINS" ]; then
             cat <<EOF >>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
-"$DOMAINS"="$NEW_DOMAINS"
+$DOMAINS="$NEW_DOMAINS"
 EOF
         fi
     fi
@@ -66,7 +66,7 @@ EOF
     # ignore errors due to nonexistent file
     md5sum "$mystatedir/isc-dhcp-v4-$interface" "$mystatedir/isc-dhcp-v6-$interface" "$mystatedir/ifupdown-inet-$interface" "$mystatedir/ifupdown-inet6-$interface" > "$newstate" 2> /dev/null || true
     if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
-        DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
+        # DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
         # v4 first
         if [ -e "$mystatedir/isc-dhcp-v4-$interface" ]; then
             . "$mystatedir/isc-dhcp-v4-$interface"

And now it works well.

I'm guessing that someone might also have a static network
configuration at the same time as systemd-resolved installed, so I hope
this information can help someone.

Kind regards,
Dmytro


-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# allow-hotplug enp4s0
# iface enp4s0 inet dhcp
# This is an autoconfigured IPv6 interface
# iface enp4s0 inet6 auto

allow-hotplug wlp0s20f3
iface wlp0s20f3 inet manual
    wpa-driver wext
    wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

iface default inet dhcp

allow-hotplug enp4s0

mapping enp4s0
    script /usr/sbin/guessnet-ifupdown
    map autofilter: true
    map verbose: true
    map debug: true
    map default: enp4s0-guest

# sorry, I do not wish to publish the actual addresses there

iface enp4s0-router inet static
    address 192.168.0.44
    netmask 255.255.255.0
    gateway 192.168.0.1
    test peer address 192.168.0.1 mac XX:XX:XX:XX:XX:XX source
    dns-nameservers 192.168.0.1
    dns-nameservers 192.168.0.12

iface enp4s0-direct inet static
    address XX.XX.XXX.XX
    netmask 255.255.255.0
    gateway XX.XX.XXX.X
    test peer address XX.XX.XXX.X mac XX:XX:XX:XX:XX:XX source
    dns-nameservers XX.XX.XXX.XXX
    dns-nameservers XX.XXX.XXX.XXX

iface enp4s0-guest inet dhcp


--- /etc/network/interfaces.d/*:
cat: '/etc/network/interfaces.d/*': No such file or directory

--- up and down scripts installed:
/etc/network/if-down.d:
total 8
-rwxr-xr-x 1 root root 372 Apr 21  2020 openvpn
-rwxr-xr-x 1 root root 759 Sep 27 16:09 resolved
lrwxrwxrwx 1 root root  32 Jan 31 13:58 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh

/etc/network/if-post-down.d:
total 4
-rwxr-xr-x 1 root root 1409 Jun  5  2018 wireless-tools
lrwxrwxrwx 1 root root   32 Jan 31 13:58 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh

/etc/network/if-pre-up.d:
total 8
-rwxr-xr-x 1 root root 4191 Sep 15  2018 wireless-tools
lrwxrwxrwx 1 root root   32 Jan 31 13:58 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh

/etc/network/if-up.d:
total 12
-rwxr-xr-x 1 root root  385 Apr 21  2020 openvpn
-rwxr-xr-x 1 root root 4661 Feb 13 19:47 resolved
lrwxrwxrwx 1 root root   32 Jan 31 13:58 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable'), (600, 'unstable'), (500, 'stable-security'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifupdown depends on:
ii  adduser   3.131
ii  iproute2  6.1.0-1
ii  libc6     2.36-8

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.4.3-P1-1.1

Versions of packages ifupdown suggests:
ii  ppp     2.4.9-1+1.1+b1
pn  rdnssd  <none>

-- Configuration Files:
/etc/network/if-up.d/resolved changed:
case "$ADDRFAM" in
    inet|inet6) : ;;
    *) exit 0 ;;
esac
if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
    interface=$IFACE
    if [ ! "$interface" ]; then
        return
    fi
    # TODO handle lo interface settings
    if [ "$interface" = "lo" ]; then
        return
    fi
    ifindex=$(cat "/sys/class/net/$interface/ifindex")
    if [ ! "$ifindex" ]; then
        return
    fi
    mystatedir=/run/network
    mkdir -p $mystatedir
    statedir=/run/systemd/resolve/netif
    mkdir -p $statedir
    chown systemd-resolve:systemd-resolve $statedir
    oldstate="$(mktemp)"
    # ignore errors due to nonexistent file
    md5sum "$mystatedir/isc-dhcp-v4-$interface" "$mystatedir/isc-dhcp-v6-$interface" "$mystatedir/ifupdown-inet-$interface" "$mystatedir/ifupdown-inet6-$interface" > "$oldstate" 2> /dev/null || true
    NEW_DEFAULT_ROUTE=$IF_DNS_DEFAULT_ROUTE
    NEW_DNS=$(echo $IF_DNS_NAMESERVERS $IF_DNS_NAMESERVER)
    NEW_DOMAINS=$(echo $IF_DNS_DOMAIN $IF_DNS_SEARCH)
    DNS=DNS
    DOMAINS=DOMAINS
    if [ "$ADDRFAM" = "inet6" ]; then
        DNS=DNS6
        DOMAINS=DOMAINS6
    fi
    if  [ -n "$NEW_DNS" ]; then
        cat <<EOF >"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
        if  [ -n "$NEW_DOMAINS" ]; then
            cat <<EOF >>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
        fi
    fi
    case "$NEW_DEFAULT_ROUTE" in
        1|yes|true|on) NEW_DEFAULT_ROUTE=yes ;;
        0|no|false|off) NEW_DEFAULT_ROUTE=no ;;
        *) NEW_DEFAULT_ROUTE= ;;
    esac
    if [ -n "$NEW_DEFAULT_ROUTE" ]; then
        cat <<EOF >>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
DEFAULT_ROUTE="$NEW_DEFAULT_ROUTE"
EOF
    fi
    newstate="$(mktemp)"
    # ignore errors due to nonexistent file
    md5sum "$mystatedir/isc-dhcp-v4-$interface" "$mystatedir/isc-dhcp-v6-$interface" "$mystatedir/ifupdown-inet-$interface" "$mystatedir/ifupdown-inet6-$interface" > "$newstate" 2> /dev/null || true
    if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
        # DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
        # v4 first
        if [ -e "$mystatedir/isc-dhcp-v4-$interface" ]; then
            . "$mystatedir/isc-dhcp-v4-$interface"
        fi
        # v4 manual config overrides
        if [ -e "$mystatedir/ifupdown-inet-$interface" ]; then
            . "$mystatedir/ifupdown-inet-$interface"
        fi
        # v6 preffered
        if [ -e "$mystatedir/isc-dhcp-v6-$interface" ]; then
            . "$mystatedir/isc-dhcp-v6-$interface"
        fi
        # v6 manual config overrides
        if [ -e "$mystatedir/ifupdown-inet6-$interface" ]; then
            . "$mystatedir/ifupdown-inet6-$interface"
        fi
        resolvectl_failed=
        if [ "$DNS" ] || [ "$DNS6" ] ; then
            cat <<EOF >"$statedir/$ifindex"
LLMNR=yes
MDNS=no
SERVERS=$(echo $DNS6 $DNS)
DOMAINS=$(echo $DOMAINS6 $DOMAINS)
EOF
            if [ -n "$DEFAULT_ROUTE" ]; then
                cat <<EOF >>"$statedir/$ifindex"
DEFAULT_ROUTE=$DEFAULT_ROUTE
EOF
            fi
            chown systemd-resolve:systemd-resolve "$statedir/$ifindex"
            # In addition to creating the state file (needed if we run before
            # resolved is started), also feed the information directly to
            # resolved.
            if systemctl --quiet is-active systemd-resolved; then
                resolvectl llmnr "$ifindex" yes || resolvectl_failed=$?
                resolvectl mdns "$ifindex" no || resolvectl_failed=$?
                if [ "$DOMAINS6" ] || [ "$DOMAINS" ]; then
                    resolvectl domain "$ifindex" $DOMAINS6 $DOMAINS || resolvectl_failed=$?
                else
                    resolvectl domain "$ifindex" "" || resolvectl_failed=$?
                fi
                resolvectl dns "$ifindex" $DNS6 $DNS || resolvectl_failed=$?
                if [ "$DEFAULT_ROUTE" ]; then
                    resolvectl default-route "$ifindex" $DEFAULT_ROUTE || resolvectl_failed=$?
                fi
            fi
        else
            rm -f "$statedir/$ifindex"
            if systemctl --quiet is-active systemd-resolved; then
                resolvectl revert "$ifindex" || resolvectl_failed=$?
            fi
        fi
        # resolved was running, but without dbus, it means state files
        # will not be read & resolvectl commands failed, restart it
        if [ "$resolvectl_failed" ]; then
                systemctl try-restart systemd-resolved
        fi
    fi
    rm -f "$oldstate" "$newstate"
fi


-- no debconf information

Message #10 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: Santiago Ruano Rincón <santiagorr@riseup.net>

To: Dmytro Kolesnykov <gray@bunker.org.ua>, 1031236@bugs.debian.org

Subject: Re: Bug#1031236: ifupdown: dns-nameservers with systemd-resolved is broken

Date: Wed, 15 Feb 2023 14:16:57 +0100

[Message part 1 (text/plain, inline)]

Control: tags -1 + patch
Control: severity -1 important

El 13/02/23 a las 20:38, Dmytro Kolesnykov escribió:
> Package: ifupdown
> Version: 0.8.41
> Severity: normal
> 
> Dear Maintainer,

Dear ifupdown user,

> 
> I was doing my network setup, which included statically configured
> logical interfaces. So there were dns-nameservers entries in my
> /etc/network/interfaces. My configuration files is below (the actual
> IPs and MACs is wiped).
> 
> I noted that ifup with my setup is producing error messages like this:
> 
> ...
> guessnet: Started tests
> guessnet: 3 candidates
> guessnet: Got ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX
> guessnet: ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX matches
> guessnet: Notified success of scan peer 192.168.0.1 XX:XX:XX:XX:XX:XX
> guessnet: Removing candidate enp4s0-direct
> guessnet: Keeping candidate enp4s0-router
> guessnet: We had changes, notifying the listener
> guessnet: Got ARP reply from 192.168.0.1 XX:XX:XX:XX:XX:XX
> /etc/network/if-up.d/resolved: 69: DNS: not found
> /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-enp4s0: DNS=192.168.0.1 192.168.0.12: not found
> Failed to parse DNS server address: DNS
> Failed to set DNS configuration: Invalid argument
> 
> I have found discussion about similar problem there:
> https://unix.stackexchange.com/questions/714901/dns-broken-when-using-ifupdown-and-systemd-resolved-after-upgrade-to-ubuntu-22-0
> 
> Also I had a look into the /etc/network/if-up.d/resolved and I assume
> this is a typo in the line 69:
> https://salsa.debian.org/debian/ifupdown/-/blob/master/debian/if-up.d/resolved#L69
> 

[...]

Thanks for reporting this issue, and for proposing the patch.

Have you had the chance to test an IPv6 configuration?
I'll need to change my setup for testing that. And I'd love add tests to
check this.

Cheers,

 -- Santiago

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: Ken Milmore <ken.milmore@gmail.com>

To: 1031236@bugs.debian.org

Subject: Re: Bug#1031236: ifupdown: dns-nameservers with systemd-resolved is broken

Date: Sun, 7 May 2023 23:52:57 +0100

[Message part 1 (text/plain, inline)]

With a minor modification, the suggested patch seems to work correctly for me on both IPv4 and IPv6 static configurations.

The modification I have added is to clear the variables DNS, DNS6, DOMAINS, DOMAINS6, DEFAULT_ROUTE before importing the state files,
otherwise their previous contents may be carried through. Without this, I was getting a search domain of "DOMAINS" configured in resolved.

I have attached a source patch against ifupdown master on Salsa.

I note that the resolved hook script we're working with here seems to be derived from the (fairly hacky) dhclient hook scripts being shipped by Ubuntu.
To get DNS working for DHCP cases as well as for static ones, will require a corresponding hook script for dhclient in Debian: see bug #1025062.

Note also in ifupdown it is possible to have independent DHCP and/or static configurations for IPv4 and IPv6 on the same interface.
I'm not sure how common those cases are, but the hook scripts for ifupdown and dhclient would have to use the same protocol and state file for it to work with all the possible combinations. I'm going to post a comment and patch against bug #1025062 to this effect.

-Ken.

[ifupdown-resolved.patch (text/x-patch, attachment)]

Message #24 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: Uwe Kleine-König <ukleinek@debian.org>

To: 1031236@bugs.debian.org

Cc: Ken Milmore <ken.milmore@gmail.com>, Dmytro Kolesnykov <gray@bunker.org.ua>

Subject: ifupdown: diff for NMU version 0.8.41+nmu1

Date: Wed, 21 Jun 2023 19:10:32 +0200

[Message part 1 (text/plain, inline)]

Control: tags 1031236 + pending

Dear maintainer,

I've prepared an NMU for ifupdown (versioned as 0.8.41+nmu1) and intend
to upload it to DELAYED/10 once I properly tested the patch.
(Unfortunately I locked myself out of the affected machine while
reconfiguring the network devices. So testing will have to wait until I
find someone with physical access to that machine.)

The change is effectively what Ken Milmore proposed.

Best regards
Uwe

[ifupdown-0.8.41+nmu1-nmu.diff (text/x-diff, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #31 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: Santiago Ruano Rincón <santiagorr@riseup.net>

To: Uwe Kleine-König <ukleinek@debian.org>, 1031236@bugs.debian.org

Cc: Ken Milmore <ken.milmore@gmail.com>, Dmytro Kolesnykov <gray@bunker.org.ua>

Subject: Re: Bug#1031236: ifupdown: diff for NMU version 0.8.41+nmu1

Date: Wed, 21 Jun 2023 14:58:36 -0300

[Message part 1 (text/plain, inline)]

El 21/06/23 a las 19:10, Uwe Kleine-König escribió:
> Control: tags 1031236 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for ifupdown (versioned as 0.8.41+nmu1) and intend
> to upload it to DELAYED/10 once I properly tested the patch.
> (Unfortunately I locked myself out of the affected machine while
> reconfiguring the network devices. So testing will have to wait until I
> find someone with physical access to that machine.)
> 
> The change is effectively what Ken Milmore proposed.

Thanks for this. Would you like to prepare a MR instead. I would like to
handle the switch to dependency on dhcpcd-base along.

Cheers,

 -- Santiago

[signature.asc (application/pgp-signature, inline)]

Message #36 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: Uwe Kleine-König <ukleinek@debian.org>

To: Santiago Ruano Rincón <santiagorr@riseup.net>, 1031236@bugs.debian.org

Cc: Ken Milmore <ken.milmore@gmail.com>, Dmytro Kolesnykov <gray@bunker.org.ua>

Subject: Re: Bug#1031236: ifupdown: diff for NMU version 0.8.41+nmu1

Date: Wed, 21 Jun 2023 22:13:41 +0200

Hello Santiago,

On 6/21/23 19:58, Santiago Ruano Rincón wrote:
> El 21/06/23 a las 19:10, Uwe Kleine-König escribió:
>> Control: tags 1031236 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for ifupdown (versioned as 0.8.41+nmu1) and intend
>> to upload it to DELAYED/10 once I properly tested the patch.
>> (Unfortunately I locked myself out of the affected machine while
>> reconfiguring the network devices. So testing will have to wait until I
>> find someone with physical access to that machine.)
>>
>> The change is effectively what Ken Milmore proposed.
> 
> Thanks for this. Would you like to prepare a MR instead. I would like to
> handle the switch to dependency on dhcpcd-base along.

Sure:
https://salsa.debian.org/debian/ifupdown/-/merge_requests/20

Best regards
Uwe

Message #41 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: <clement.nussbaumer@postfinance.ch>

To: <1031236@bugs.debian.org>

Date: Wed, 29 Nov 2023 14:16:11 +0000

[Message part 1 (text/plain, inline)]

Hi,

We’ve encountered this bug on our systems as well. I wanted to know when the fixed ifupdown package will be released ?

That the DOMAINS search domain is appended to your search domains is quite problematic for Kubernetes environments, where lots of DNS queries end with cluster.local: indeed, because *.local.domains resolves to an actual IP address (3.64.163.50, registered on AWS according to whois), this bug is not only problematic (wrong DNS resolution for some endpoints), it could also prove dangerous.

Best,
Clément

Remarque concernant la sécurité:
Ce courriel provenant de PostFinance est signé. Vous trouverez d'autres informations à ce sujet sous: 
https://www.postfinance.ch/e-signature.
Ne divulguez jamais vos éléments de sécurité à des tiers.

[Message part 2 (text/html, inline)]

[smime.p7s (application/pkcs7-signature, attachment)]

Message #46 received at 1031236@bugs.debian.org (full text, mbox, reply):

From: <rolf.zimmerli@postfinance.ch>

To: <1031236@bugs.debian.org>

Subject: Bug pending since more than one year

Date: Thu, 7 Mar 2024 14:56:57 +0000

[Message part 1 (text/plain, inline)]

Dear Maintainer,


this important bug in /etc/network/if-up.d/resolved is pendent since more than one year.

In Ubuntu this was already fixed in November 2023:

https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu3.1



When will this be fixed in Debian 12 ?



My customers are thinking about a change from Debian to Ubuntu ☹



Kind regards

Rolf Zimmerli




Freundliche Grüsse

Rolf Zimmerli
Systemspezialist UNIX

PostFinance AG
CD & Infrastructure Services, PF85-62 DT Linux
Engehaldenstrasse 37
CH-3030 Bern

Telefon: +41 79 500 87 53
rolf.zimmerli@postfinance.ch<mailto:rolf.zimmerli@postfinance.ch>
www.postfinance.ch<http://www.postfinance.ch/>


Sicherheitshinweis:
Dieses E-Mail von PostFinance ist signiert. Weitere Informationen finden Sie unter: 
https://www.postfinance.ch/e-signature.
Geben Sie Ihre Sicherheitselemente niemals Dritten bekannt.

[Message part 2 (text/html, inline)]

[smime.p7s (application/pkcs7-signature, attachment)]

Message #51 received at 1031236-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1031236-close@bugs.debian.org

Subject: Bug#1031236: fixed in ifupdown 0.8.42

Date: Sun, 10 Mar 2024 20:59:39 +0000

[Message part 1 (text/plain, inline)]

Source: ifupdown
Source-Version: 0.8.42
Done: Santiago Ruano Rincón <santiago@debian.org>

We believe that the bug you reported is fixed in the latest version of
ifupdown, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031236@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Ruano Rincón <santiago@debian.org> (supplier of updated ifupdown package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 10 Mar 2024 17:17:50 -0300
Source: ifupdown
Architecture: source
Version: 0.8.42
Distribution: unstable
Urgency: medium
Maintainer: Josué Ortega <josue@debian.org>
Changed-By: Santiago Ruano Rincón <santiago@debian.org>
Closes: 1031236 1059919
Changes:
 ifupdown (0.8.42) unstable; urgency=medium
 .
   [ Uwe Kleine-König ]
   * Fix if-up.d/resolved hook to properly work with nameservers and search
     domains. Thanks to Dmytro Kolesnykov and Ken Milmore for the bug report
     and a proposed patch. (Closes: #1031236)
 .
   [ Guillem Jover ]
   * Use relative names when executing programs
 .
   [ Santiago Ruano Rincón ]
   * DEP17: Move files to /usr. Thanks to Helmut Grohne <helmut@subdivi.de>
     (Closes: #1059919)
Checksums-Sha1:
 e1df2db1fd61fe9ff580ffce9a27f7ddf1cdfa79 986 ifupdown_0.8.42.dsc
 1f431b70b6bfa1dce78d0a519c5706a0c51508b7 82428 ifupdown_0.8.42.tar.xz
 8761e899536040e9c70e83c4a046fe044d9a0bd3 5584 ifupdown_0.8.42_amd64.buildinfo
Checksums-Sha256:
 0d5c2edb2275b9ad5d08bbea5cfbfeee7cfe76a953aff39c43ba19829c3a964c 986 ifupdown_0.8.42.dsc
 7e2dc1498415c2518a3826e3b875ced871d0622a421a71390627cc35bd247964 82428 ifupdown_0.8.42.tar.xz
 d84060a45b16a8c7a976ae2f7c34dd2f7f4655ad86c1751fdeeb543fdb0d0cda 5584 ifupdown_0.8.42_amd64.buildinfo
Files:
 0ed8c040b07b75a570034e884a4d539f 986 admin important ifupdown_0.8.42.dsc
 a5681694a2229f2a3fe12ae035c97174 82428 admin important ifupdown_0.8.42.tar.xz
 667c9e5a5e9f5a4e6c5a5cf0fea078fb 5584 admin important ifupdown_0.8.42_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCZe4WOwAKCRBitBCJKh26
HYa1AQD9Pv/AleDf4++yFX20xdIcAcCQzNg5NOfVlCeUgIBLpgEA6jlKlAn/Uj10
4M0r/tx/WsYKjAdToLWib1pBESBTZAo=
=I0mo
-----END PGP SIGNATURE-----

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.