1. Forum
  2. FidoNet
  3. linux.debian.user

  • Breakages on Debian upgrade

    From alain williams@3:633/10 to All on Wednesday, September 16, 2026 21:30:02
    I updated a server y/day from Debian 12 -> Debian 13. This broke things.

    The one that annoys me and I do not know why is happened is bind.

    A had files in /etc/bind/ with names like db.local which got renamed to db.local.dpkg-remove

    Why ??? Why did it just not leave them alone ? The result was that my bind config broke.

    Creating updated (ie newer) versions of files as .dpkg-dist is fine - I can look at them and decide if I want to import things from there.

    It also copied files so named.conf.default-zones was copied to named.conf.default-zones.dpkg-backup -- both files are the same but named.conf.default-zones has today's timestamp, named.conf.default-zones.dpkg-backup is a couple of years old.

    Also Dovecot - changed the syntax of the config files -- sigh. I do not blame Debian for that.

    --
    Alain Williams
    Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
    +44 (0) 787 668 0256 https://www.phcomp.co.uk/
    Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html
    #include <std_disclaimer.h>

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From alain williams@3:633/10 to All on Wednesday, September 16, 2026 23:20:01
    On Wed, Sep 16, 2026 at 10:04:37PM +0200, Michel Verdier wrote:
    On 2026-09-16, alain williams wrote:

    A had files in /etc/bind/ with names like db.local which got renamed to db.local.dpkg-remove
    [...]
    It also copied files so named.conf.default-zones was copied to named.conf.default-zones.dpkg-backup -- both files are the same but named.conf.default-zones has today's timestamp, named.conf.default-zones.dpkg-backup is a couple of years old.

    Also Dovecot - changed the syntax of the config files -- sigh. I do not blame
    Debian for that.

    You should have some warnings about these changes during upgrade. If you missed them you could retrieve them in /var/log/apt/term.log

    In theory ... but that file is 678k (7,840 lines) in size - that will take some time to look through - meanwhile my system is broken.

    Best just leave files that it knows nothing about alone. My config files I do by hand and they go back to 2007.

    --
    Alain Williams
    Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
    +44 (0) 787 668 0256 https://www.phcomp.co.uk/
    Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html
    #include <std_disclaimer.h>

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jim Jackson@3:633/10 to All on Thursday, September 17, 2026 11:00:01
    On 2026-09-16, Michel Verdier <listes@verdier.net> wrote:
    On 2026-09-16, alain williams wrote:

    You should have some warnings about these changes during upgrade. If you >>> missed them you could retrieve them in /var/log/apt/term.log

    In theory ... but that file is 678k (7,840 lines) in size - that will take some
    time to look through - meanwhile my system is broken.

    grep or search with less/vi needs only a bunch of seconds to find your files

    Best just leave files that it knows nothing about alone. My config files I do
    by hand and they go back to 2007.

    Upgrade don't change your files without asking. Unless you used a force parameter or you choose to change them. I never break bind with an
    upgrade. And I was warned about dovecot syntax changes.

    That's my experience too.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)