Skip to content

Update Unbound to 1.19.0 (fixes existing error with trunk version) #369

Description

@gaige

Unbound 1.19.0 fixes a problem that @jperkin reported to the unbound folks (in super detail) about setting IPV6 options mistakenly on an IPv4 socket. I've built locally and tested with the 1.19.0 source against trunk.

If you'd prefer another format for ease of integration (like a pull request of real patch file) let me know.

diff --git a/net/unbound/Makefile b/net/unbound/Makefile
index c4c788ec98c..16edcb6863c 100644
--- a/net/unbound/Makefile
+++ b/net/unbound/Makefile
@@ -1,7 +1,7 @@
 # $NetBSD: Makefile,v 1.100 2023/11/02 12:20:06 wiz Exp $
 
-DISTNAME=      unbound-1.18.0
-PKGREVISION=   2
+DISTNAME=      unbound-1.19.0
+PKGREVISION=   0
 CATEGORIES=    net
 MASTER_SITES=  https://nlnetlabs.nl/downloads/unbound/
 
diff --git a/net/unbound/distinfo b/net/unbound/distinfo
index f51518d56d7..d4b7493ab22 100644
--- a/net/unbound/distinfo
+++ b/net/unbound/distinfo
@@ -1,6 +1,6 @@
 $NetBSD: distinfo,v 1.75 2023/08/30 15:18:26 he Exp $
 
-BLAKE2s (unbound-1.18.0.tar.gz) = e12b30f0e41bceb2418083b26863d5ff0491f6eb1b7f5d6c9bb652a840eb4aa0
-SHA512 (unbound-1.18.0.tar.gz) = 24ca6bfe0ed493eb6aaa5cb1b2b108076ce97c48de7470adf596d1154254351e382b83aae33fcd8d4fa64847e359613e00c979b6f3ba7671215b2d0fd2b03b14
-Size (unbound-1.18.0.tar.gz) = 6315297 bytes
+BLAKE2s (unbound-1.19.0.tar.gz) = c43ad21e86e224c4fe8fc7590d9edcc5eb42e583876cb15bb6240d9d5ee71f82
+SHA512 (unbound-1.19.0.tar.gz) = c7df997ab003d098f53ac97ffb4c8428ab28e24573ff21e21782cbeadca42edadeb5b0db53ce954c9ff3106a5edb36eb47109240c554a44d9aac75727b66aeb4
+Size (unbound-1.19.0.tar.gz) = 6336113 bytes
 SHA1 (patch-configure) = fe43ed9fdcfe12897e30f03833aec631d473529d

Activity

  1. self-assigned this
    on Nov 13, 2023
  2. jperkin commented on Nov 13, 2023

    @jperkin
    Collaborator

    Thanks for working on this! pkgsrc trunk was already updated with this change in NetBSD@68cf603 but it's appreciated.

    The only note to make for future pull requests is that when updating a package version we simply remove any existing PKGREVISION rather than setting it to 0.

  3. added a commit that references this issue on Jan 25, 2024
  4. added a commit that references this issue on Feb 23, 2024
  5. added a commit that references this issue on Mar 4, 2024
  6. added a commit that references this issue on May 8, 2024
    25353dc
  7. added a commit that references this issue on Feb 6, 2025
  8. added a commit that references this issue on Jul 29, 2025
  9. added a commit that references this issue on Oct 27, 2025
  10. 12 remaining items

  11. added a commit that references this issue on May 22, 2026
  12. added a commit that references this issue on Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions