Your message dated Wed, 06 Jan 2021 18:08:07 +0000
with message-id <[email protected]>
and subject line Bug#943735: fixed in resolvconf 1.87
has caused the Debian Bug report #943735,
regarding ITS: resolvconf -- name server information handler
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 [email protected]
immediately.)


-- 
943735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943735
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:resolvconf
Severity: important

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

X-Debbugs-CC: Thomas Hood <[email protected]>, Marco Nenciarini 
<[email protected]>, resolvconf maintainers 
<[email protected]>, [email protected]

Dear Maintainers,

The resolvconf package hasn’t seen much development or bugfixing in
Debian, and as someone who uses it a lot, I’d like to take care of it.
I intend to start with the Git repo Thomas keeps at his GitLab [1] and
review and cherry-pick fixes from Ubuntu and the bug tracker. I have
currently mirrored the above mentioned Git repo at Salsa [2] where I
plan to keep it in future.

Should you have any objections or anything else to share, I’d be happy
to hear from you.

References:
 [1]: https://gitlab.com/jdthood/resolvconf
 [2]: https://salsa.debian.org/debian/resolvconf

- -- 
Cheers,
  Andrej

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

iQFIBAEBCAAyFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl23Xh0UHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQXkCM2RzYOdL1EAf/Z/ulX7yw7uHVOkL7rytjrZr+Azwz
nLCY9plqSh2ca5AEtJ3fmP72UxzTI9lLBClYpnHNFp3mOUdhB1RUF9bCBLn8zSxV
9aAeSEU2tZWF5e0A0ZtYsb1QjRlYmRWEgIux1hedwxpsl2tTnWl5RqqvzNYezgL6
obad4jUM/mTeaDzlxv4EIJFIEK5sYH9JDtCv0C6eXX5JEtV3TcCbJ6FP7fRPRhr6
0bzuc6KXWKra2c+ve9ro7rg55YoQUiUdUE9i3wplJ12i3way+pvZXz0BwnT7YzBa
0DNR4hbNoFRaxMKJXtrOD157q156X8gPF5JlhEmkl71KTxqk5/rFkSjYew==
=51Cl
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.87
Done: Andrej Shadura <[email protected]>

We believe that the bug you reported is fixed in the latest version of
resolvconf, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura <[email protected]> (supplier of updated resolvconf 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 [email protected])


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

Format: 1.8
Date: Wed, 06 Jan 2021 18:54:17 +0100
Source: resolvconf
Architecture: source
Version: 1.87
Distribution: unstable
Urgency: medium
Maintainer: resolvconf team <[email protected]>
Changed-By: Andrej Shadura <[email protected]>
Closes: 943735 979431 979436
Changes:
 resolvconf (1.87) unstable; urgency=medium
 .
   * Undo the damage on an incorrect merge commit:
     - Fix the maintainer’s address (Closes: #943735)
     - Revert "Skip pulling data into resolvconf, if isc-dhcp/ifupdown
       already push the same data to systemd-resolved and it is in use".
       Debian does not ship said hooks in ifupdown or isc-dhcp-client,
       so these fixes won’t work. Also, they use systemctl unconditionally
       which is fine in Ubuntu but not in Debian.
       (Closes: #979431)
   * Clean up the old conffile (Closes: #979436)
Checksums-Sha1:
 a3cd188fbd03edd2ddf7cfdfd8fe130d5faf1992 1483 resolvconf_1.87.dsc
 4c85aa4482f9ed933cb2c2efdd9ce8531ff1877a 73452 resolvconf_1.87.tar.xz
Checksums-Sha256:
 22c98325f1ba298a9b00f461a1943f00c36b419d9fdfba94a1624c81654560a1 1483 
resolvconf_1.87.dsc
 e86869b6c0ed3e9b4cab2b409e27d28294df8c71ef361c10545c81243c48e39f 73452 
resolvconf_1.87.tar.xz
Files:
 e269ce79e7ca79eabd0304d7c6928734 1483 net optional resolvconf_1.87.dsc
 3da444b2152726d84e6957b9d93687bd 73452 net optional resolvconf_1.87.tar.xz

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

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/1+aUACgkQXkCM2RzY
OdLCjwgAhxeA9j817F6godyCAWxCpP9OeEHcsqX5vbRvrVx7JufpmtXNIK5h+FQE
HBj3erl+EDo+FXhaTeN8ZDrGr8pK/eRiQ4nc9XMNHE+rjesqbfXCnqu2V3Ff39NK
q1HmCtFOnLLUL4pj5JCnSEv9gKHKB1N5unAle7cPAiEeqX3dyWfvb1t+zjzbYimn
D8samJy/B5VYbBFUzIt/S89BMZ7mx89D/nDLCnO5yBg87ucu7v+//0hqI6VwRVuv
2rCEQhKa5niItAPzg4+oAndnLLNlVEOrtTa2K774TFfFG4M74NCM7UsDbxqGmxad
QNYZYr61ks9+BdsBx69vzfpH5zckvQ==
=Zftd
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to