Tails

#1 Updated by intrigeri 2018-09-02 16:10:55

• Assignee set to intrigeri
• Target version changed from Tails_3.9 to Tails_3.10.1

> In Tails 3.9 (20180817) `mutt` is installed again.

FTR Tails 3.9 has not been released yet and 3.9~rc1 hasn’t mutt installed so “Tails 3.9 (20180817)” is not very useful information.

But after looking around I’ve noticed that mutt is back in the latest build(s) from testing e.g. https://jenkins.tails.boum.org/view/RM/job/build_Tails_ISO_testing/35/artifact/build-artifacts/tails-amd64-testing-3.9-20180902T1222Z-0db0bd1299.iso.packages/*view*/.

I think that’s another problem wrt. priority standard (Bug #15690). See commit:0c55ab304eb85b3bf867c80e045e49d8db095ca5. We should probably do the same trick in config/chroot_local-hooks/98-remove_unwanted_packages as for geoclue i.e. remove only if installed.

In any case it’s not important enough to warrant stressing my overloaded reviewers this close to the final ISO build so that’ll wait for 3.10.

#4 Updated by intrigeri 2018-09-06 13:31:08

• Assignee changed from intrigeri to CyrilBrulebois

Do you want this one? While you’re at it you could fix my shitty code in config/chroot_local-hooks/98-remove_unwanted_packages for which you commented:

no need for -gt 0
if dpkg --get-selections | grep -qs -E '…' ; then … ; fi

#5 Updated by CyrilBrulebois 2018-09-08 06:23:30

• Assignee changed from CyrilBrulebois to intrigeri
• QA Check set to Ready for QA
• Feature Branch set to kibi:bugfix/15904-make-sure-mutt-is-not-installed

Two commits in the bugfix/15904-make-sure-mutt-is-not-installed branch of my repository:

• The first one removes mutt without checking whether it’s installed; contrary to geoclue packages, there are no wildcards involved, so it can be purged without extra checks. Other packages with the same priority issue (due to priority mismatch in main/security archives) could get added in that specific section.
• The second one makes the geoclue vs. dpkg check more idiomatic. I don’t see any such packages getting installed when building the devel branch though.

Comparing .packages files, these packages go away due to the mutt removal, and that seems rather reasonable:

• libnotmuch4 0.23.7-3
• libtokyocabinet9:amd64 1.4.48-11+b1
• mutt 1.7.2-1+deb9u1

For those following at home, an earlier FTBFS needs to be addressed to reach this point (see Bug #15846).

#6 Updated by intrigeri 2018-09-10 09:14:56

• Status changed from Confirmed to In Progress
• Assignee changed from intrigeri to CyrilBrulebois
• % Done changed from 0 to 60
• QA Check changed from Ready for QA to Dev Needed

Looks mostly good to me, thanks! Two things though:

• please rebase this on the stable branch so we can merge it for 3.10 which is a bugfix release; devel is where we prepare the next major release (3.12).
• we don’t need to pass the -c option to grep anymore, do we?

#7 Updated by CyrilBrulebois 2018-09-11 02:11:41

• Assignee changed from CyrilBrulebois to intrigeri
• QA Check changed from Dev Needed to Ready for QA

You’re right on both counts. Rebased on top of stable, and -c option removed. Thanks for the review!

#9 Updated by intrigeri 2018-09-11 09:05:32

• Status changed from In Progress to Fix committed
• Assignee deleted (intrigeri)
• % Done changed from 60 to 100
• QA Check changed from Ready for QA to Pass

Merged, thanks!

#10 Updated by Anonymous 2018-09-13 00:51:13

• Status changed from Fix committed to In Progress

Applied in changeset commit:c716db663a4b6f5f2018d327d5605a3775bd171e.

#11 Updated by intrigeri 2018-09-13 00:51:13

• Status changed from In Progress to Fix committed

Applied in changeset commit:db270a0389f63efffbfa7ae57543f43a158f8b4b.

#12 Updated by intrigeri 2018-10-01 13:29:42

• Target version changed from Tails_3.10.1 to Tails_3.9.1

#13 Updated by anonym 2018-10-04 10:43:00

• Status changed from Fix committed to Resolved