issues.yml

@@ -2326,3 +2326,17 @@ 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.
+    .
+    stlink=1.7.0+ds-1 is currently in both bullseye and sid; is reproducible on
+    the former but not on the latter; and has this issue.  The issue could be
+    caused by a difference in some build dependency between the two suites (for
+    some common build dependency of all packages having this issue); or by
+    a difference in the variations tested in the two suites.
+    .
+    The only difference in variations (per current "Variations tested" page) is
+    the build path variation.
+    .
+    So, is there any any chance that this issue is caused by the build path
+    variation?  <wild speculation>Perhaps the number of extra bytes is 2
+    because the build path in build #2 is two bytes longer than in build
+    #1?</wild speculation>

packages.yml

@@ -17630,6 +17630,12 @@ okteta:
   issues:
     - build_id_differences_only
     - ftbfs_due_to_f-file-prefix-map
+okular:
+  version: 4:21.08.3-1
+  comments: |
+    There are also random differences at the start of the strings(1) output.
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 oldsys-preseed:
   version: '3.22'
   bugs:
@@ -29453,6 +29459,10 @@ stimfit:
   version: 0.15.4-1
   issues:
     - build_id_differences_only
+stlink:
+  version: 1.7.0+ds-1
+  issues:
+    - dynstr_section_longer_by_two_bytes_which_are_NULs
 stoken:
   version: 0.91-1
   issues: