issues.yml

@@ -2322,3 +2322,7 @@ non_deterministic_doc_base_file_for_javadoc:
     Some packages have both a hand-written .doc-base file and a .doc-base
     file generated from Javadoc, and non-deterministically install one
     or the other. Example: https://bugs.debian.org/1001218
+dynstr_section_longer_by_two_bytes_which_are_NULs:
+  description: |
+    The .dynstr section on the right build is longer by two bytes.
+    The value of those two bytes is 0x00 0x00.

packages.yml

@@ -3232,6 +3232,10 @@ cpp-hocon:
   version: 0.1.7-1
   issues:
     - captures_build_path
+cppad:
+  version: 2021.00.00.8-1
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 cppdb:
   version: 0.3.1+dfsg-4
   issues:
@@ -4420,6 +4424,10 @@ dropbear:
   version: 2016.74-3
   issues:
     - gcc_captures_build_path
+dsdcc:
+  version: 1.9.3-1
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 dsdp:
   version: 5.8-9.4
   bugs:
@@ -5420,6 +5428,10 @@ fastx-toolkit:
   version: 0.0.14-4
   issues:
     - libtool_captures_shell_build-flags_build-path_path-env
+faudio:
+  version: 22.01-1
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 fauhdlc:
   version: 20130704-1.1
   issues:
@@ -20731,6 +20743,16 @@ python-fluids:
   version: 1.0.9-1
   bugs:
     - 1004391
+python-fluids:
+  version: 1.0.9-1
+  comments: |
+    Captures date of build:
+    .
+    copyright = u'2016 - %s, Caleb Bell <Caleb.Andrew.Bell@gmail.com>' %datetime.datetime.now().year
+    .
+    That line says "2016 - %s" and the build outputs (as of today) are "2022 - 2022" and "2022 - 2023".
+    The difference between 2022 and 2023 is because the second build runs in the future.
+    The difference between 2016 (in the source file) and 2022 (in the LHS of both builds' outputs) was reproduced in a plain `dpkg-buildpackage` build in a fresh sid chroot.  It doesn't affect reproducibility.
 python-fudge:
   version: 1.1.1-1
   comments: |
@@ -21409,6 +21431,10 @@ qdbm:
   issues:
     - timestamps_in_jar
     - captures_build_path
+qdmr:
+  version: 0.101-1
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 qemu:
   version: 1:5.0-5
   comments: |
@@ -27695,6 +27721,13 @@ ruby-psych:
   version: 3.0.3~pre1-2
   issues:
     - gcc_captures_build_path
+ruby-pygments.rb:
+  version: 2.3.0+ds-1 
+  comments: |
+    The 0020 (S_IWGRP) bit differs.  Also, quilt metadata (.pc/*) are included.
+    .
+    I think it's due to this line in pygments.rb.gemspec:
+      s.files = (Dir.glob('**/*', File::FNM_DOTMATCH) - Dir.glob('debian/**/*', File::FNM_DOTMATCH)).reject { |f| File.directory?(f) }
 ruby-raindrops:
   version: 0.17.0-1
   issues:
@@ -29670,6 +29703,10 @@ swish-e:
     - captures_shell_variable_in_autofoo_script
     - captures_build_path
     - records_build_flags
+sword:
+  version: 1.9.0+dfsg-4
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 swtchart:
   version: 0.8.0-1
   issues: