[Bug 297405] dns/bind920 Update LMDB dependency to databases/lmdb (1.x)

[email protected]
Newsgroups gmane.os.freebsd.devel.ports.bugs
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297405

            Bug ID: 297405
           Summary: dns/bind920 Update LMDB dependency to databases/lmdb
                    (1.x)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
                CC: [email protected], [email protected]

Created attachment 273583
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=273583&action=edit
dns/bind920 update for lmdb 1.x support

This PR updates dns/bind920 to build against databases/lmdb (1.x) instead of
the legacy databases/lmdb0 port.

Summary of changes:
- Makefile: Switch LMDB_LIB_DEPENDS from databases/lmdb0 to databases/lmdb.
- Makefile: Bump PORTREVISION (dns/bind920 only).
- files/pkg-message.in: Add an upgrade instruction block warning administrators
about the on-disk format incompatibility introduced in LMDB 1.x. Existing
.nzd/.mdb files must be removed prior to restarting named to avoid startup
failures ('operational/LMDB error').

QA / Testing performed:
- Successfully built and tested on FreeBSD via portmaster.
- Verified pkg-message rendering for both fresh install and upgrade contexts.
- Confirmed that bind-tools slave port is unaffected (LMDB option remains
excluded).



Maybe to include something like this in /usr/ports/UPDATING:
20260810:
  AFFECTED: dns/bind920
  AUTHOR: [email protected]

  dns/bind920 has been updated to build against databases/lmdb (1.x).

  LMDB 1.x alters the on-disk database format. Existing LMDB database files
  (.nzd, .mdb, .nzf) created with LMDB 0.x are incompatible with 1.x and
  will cause named to fail at startup with an 'operational/LMDB error'.

  Before restarting named after upgrading:
  1. Sync dynamic updates to disk:
     # rndc sync -clean
  2. Stop the daemon:
     # service named stop
  3. Remove old LMDB state files:
     # rm -f /usr/local/etc/namedb/working/*.nzd
     # rm -f /usr/local/etc/namedb/working/*.mdb
  4. Start named (it will recreate clean 1.x files automatically):
     # service named start

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.