Control: tags 1123468 + patch
Control: tags 1123468 + pending
Control: tags 1123468 + fixed-upstream

Dear maintainer,

I've prepared an NMU for ruby-public-suffix (versioned as 6.0.2-1.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I should delay
it longer.

This NMU is based on an upstream commit which I minimized just to fix
the FTBFS, cf. the patch headers. FWIW, this commit is part of the new
upstream release 7.0.0, so maybe you'd just prefer to package that one
instead.

Cheers,
Flo
diff -Nru ruby-public-suffix-6.0.2/debian/changelog ruby-public-suffix-6.0.2/debian/changelog
--- ruby-public-suffix-6.0.2/debian/changelog	2025-10-24 19:14:02.000000000 +0200
+++ ruby-public-suffix-6.0.2/debian/changelog	2025-12-29 11:08:03.000000000 +0100
@@ -1,3 +1,12 @@
+ruby-public-suffix (6.0.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add d/patches/replace-bd-tests.patch to replace .bd tests with .er tests
+    allowing the package to build again after recent publicsuffix changes
+    (Closes: #1123468)
+
+ -- Florian Ernst <[email protected]>  Mon, 29 Dec 2025 11:08:03 +0100
+
 ruby-public-suffix (6.0.2-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-public-suffix-6.0.2/debian/patches/replace-bd-tests.patch ruby-public-suffix-6.0.2/debian/patches/replace-bd-tests.patch
--- ruby-public-suffix-6.0.2/debian/patches/replace-bd-tests.patch	1970-01-01 01:00:00.000000000 +0100
+++ ruby-public-suffix-6.0.2/debian/patches/replace-bd-tests.patch	2025-12-29 11:06:52.000000000 +0100
@@ -0,0 +1,46 @@
+Description: Replace .bd tests with .er tests
+ Upstream has changed the handling of .bd domains, cf.
+ https://github.com/publicsuffix/list/commit/30f4f4244cfef423c0150cfab53a5d89bc734f65,
+ causing this package's .bd tests to fail, so replace them with a suitable
+ substitute domain, cf.
+ https://github.com/weppos/publicsuffix-ruby/commit/edadce0f1091cbda3ce39f97cc0f654ad21f43d6.
+Author: Florian Ernst <[email protected]>
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123468
+
+Index: ruby-public-suffix-6.0.2/test/acceptance_test.rb
+===================================================================
+--- ruby-public-suffix-6.0.2.orig/test/acceptance_test.rb
++++ ruby-public-suffix-6.0.2/test/acceptance_test.rb
+@@ -34,7 +34,7 @@ class AcceptanceTest < Minitest::Test
+ 
+ 
+   INVALID_CASES = [
+-    ["nic.bd", PublicSuffix::DomainNotAllowed],
++    ["nic.er", PublicSuffix::DomainNotAllowed],
+     [nil,                       PublicSuffix::DomainInvalid],
+     ["",                        PublicSuffix::DomainInvalid],
+     ["  ",                      PublicSuffix::DomainInvalid],
+Index: ruby-public-suffix-6.0.2/test/unit/public_suffix_test.rb
+===================================================================
+--- ruby-public-suffix-6.0.2.orig/test/unit/public_suffix_test.rb
++++ ruby-public-suffix-6.0.2/test/unit/public_suffix_test.rb
+@@ -89,8 +89,8 @@ class PublicSuffixTest < Minitest::Test
+   end
+ 
+   def test_self_parse_with_unallowed_domain
+-    error = assert_raises(PublicSuffix::DomainNotAllowed) { PublicSuffix.parse("example.bd") }
+-    assert_match(/example\.bd/, error.message)
++    error = assert_raises(PublicSuffix::DomainNotAllowed) { PublicSuffix.parse("example.er") }
++    assert_match(/example\.er/, error.message)
+   end
+ 
+   def test_self_parse_with_uri
+@@ -130,7 +130,7 @@ class PublicSuffixTest < Minitest::Test
+   end
+ 
+   def test_self_domain_with_unallowed_name
+-    assert_nil PublicSuffix.domain("example.bd")
++    assert_nil PublicSuffix.domain("example.er")
+   end
+ 
+   def test_self_domain_with_blank_sld
diff -Nru ruby-public-suffix-6.0.2/debian/patches/series ruby-public-suffix-6.0.2/debian/patches/series
--- ruby-public-suffix-6.0.2/debian/patches/series	2025-10-24 19:09:37.000000000 +0200
+++ ruby-public-suffix-6.0.2/debian/patches/series	2025-12-29 10:38:19.000000000 +0100
@@ -1,2 +1,3 @@
 0001-Use-system-public-suffix-list.patch
 patch-use-of-git-in-gemspec.patch
+replace-bd-tests.patch

Attachment: signature.asc
Description: PGP signature

Reply via email to