packages.yml

@@ -1600,8 +1600,6 @@ bible-kjv:
   version: 4.3
   issues:
     - build_id_differences_only
-  bugs:
-    - 1020813
 bibledit-bibletime:
   version: 1.1.1-3
   issues:
@@ -2703,8 +2701,6 @@ checkit-tiff:
     - gcc_captures_build_path
 checkpw:
   version: 1.02-1
-  issues:
-    - timestamps_in_gzip_headers
   bugs:
     - 777299
     - 1020887
@@ -6969,8 +6965,6 @@ gcc-m68hc1x:
   issues:
     - different_due_to_umask
     - users_and_groups_in_tarball
-  bugs:
-    - 536003
 gcc-mingw-w64:
   version: 17
   issues:
@@ -17333,8 +17327,6 @@ msp430-libc:
     - captures_build_path
 msp430mcu:
   version: 20120406-2
-  issues:
-    - captures_build_path
   bugs:
     - 860275
 msxpertsuite:
@@ -22932,8 +22924,6 @@ python-fluids:
     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.
-  bugs:
-    - 1004391
 python-freesasa:
   version: 2.1.0-1
   issues: