Investigate build-manifest discrepancy for Tails 4.0~beta1

So I just successfully built Tails 4.0~beta1 but got this .build-manifest diff (“almost-final” vs final):

--- tails-amd64-testing-4.0~beta1-20190807T1254Z-8be2a69358.build-manifest      2019-08-07 15:18:56.392828125 +0200
+++ tails-amd64-4.0~beta1.build-manifest   2019-08-07 21:09:15.846847112 +0200
@@ -3,7 +3,7 @@
   debian:
     reference: '2019080601'
   debian-security:
-    reference: '2019080702'
+    reference: '2019080703'
   torproject:
     reference: '2019080601'
 packages:
@@ -4488,9 +4488,6 @@
     package: poedit
     version: 2.2.1-2
   - arch: amd64
-    package: policykit-1-gnome
-    version: 0.105-7
-  - arch: amd64
     package: policykit-1
     version: 0.105-25
   - arch: all

So I guess my last minute fixes to config/chroot_local-hooks/98-remove_unwanted_packages, which happened after building the “almost-final” images, caused this, somehow (?).

I’m thinking this diff isn’t problematic. First of all, we don’t install policykit-1-gnome in stretch, which gives some confidence in that it isn’t needed in buster. Second, since the .build-manifest I used to generate 4.0~beta1’s tagged snapshot contains an extra package, there’s no real problem, just an unused package in the snapshot wasting some irrelevant amount of disk space. Correct? If so, I don’t think there’s any problem, and the 4.0~beta1 attempt as of 4e4e18975355e691114fc40ceb9aae5c506952bb can be what we actually release.

Parent Task: #16822 (closed)

Related issues

• Blocks #16209

Original created by @anonym on 16947 (Redmine)