Project

General

Profile

Bug #14650

Package new upstream version of tails-installer

Added by u 3 months ago. Updated 19 days ago.

Status:
Fix committed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
09/13/2017
Due date:
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Debian
Blueprint:
Starter:
Affected tool:

Description

and upload to Debian & Ubuntu


Related issues

Blocked by Tails - Feature #8859: Get rid of the splash screen of Tails Installer Resolved 02/04/2015
Blocked by Tails - Feature #14677: Update doc to new Tails Installer without splash screen (in Debian) Confirmed 09/17/2017
Blocks Tails - Bug #14646: Core work 2017Q3 & 2017Q4: Debian Confirmed 09/13/2017

History

#1 Updated by u 3 months ago

  • Subject changed from tails-installer to Package new upstream version of tails-installer
  • Description updated (diff)

#2 Updated by u 3 months ago

  • Blocked by Feature #8859: Get rid of the splash screen of Tails Installer added

#3 Updated by u 3 months ago

  • Target version set to Tails_3.3

#4 Updated by sajolida 3 months ago

  • Blocked by Feature #14677: Update doc to new Tails Installer without splash screen (in Debian) added

#5 Updated by sajolida 3 months ago

  • QA Check set to Info Needed

Would it make sense for you to specify the version number in the title of such tickets?

I guess you are referring here to Tails Installer 4.4.19 which solves #8859.

Then I'd like to coordinate with you so that the documentation is updated at the same time as the new package lands in Debian and Ubuntu (+/- 1/2 days). For that to work, would it be possible for you to send me the new package so I can test it in Debian and update the documentation accordingly? And then only push it to Debian and merge my doc?

#6 Updated by intrigeri 3 months ago

I guess you are referring here to Tails Installer 4.4.19 which solves #8859.

Hold on by the way, 4.4.19 is not ready to go into Debian as-is.

#7 Updated by intrigeri 3 months ago

For that to work, would it be possible for you to send me the new package so I can test it in Debian

You could fetch it from our custom APT repo already :)

#8 Updated by u 3 months ago

sajolida wrote:

Would it make sense for you to specify the version number in the title of such tickets?

Maybe sometimes but in this particular case I did not look it up yet and will do so only once the ticket is done.

Then I'd like to coordinate with you so that the documentation is updated at the same time as the new package lands in Debian and Ubuntu (+/- 1/2 days). For that to work, would it be possible for you to send me the new package so I can test it in Debian and update the documentation accordingly? And then only push it to Debian and merge my doc?

As migrating from Debian unstable -> testing & backports takes at least five days, I don't think it's necessary that I wait for you before pushing.

#9 Updated by u 3 months ago

  • QA Check deleted (Info Needed)

#10 Updated by intrigeri 3 months ago

  • Parent task deleted (#14646)

#11 Updated by intrigeri 3 months ago

  • Blocks Bug #14646: Core work 2017Q3 & 2017Q4: Debian added

#12 Updated by anonym 27 days ago

  • Target version changed from Tails_3.3 to Tails_3.5

#13 Updated by u 19 days ago

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 100

Uploaded to Debian.

#14 Updated by u 19 days ago

And all relevant Ubuntu releases, i.e. LTS 16.04 XenialXerus, 17.04 ZestyZapus and 17.10 ArtfulAardvark. People using non LTS versions of Ubuntu, like Yakkety cannot profit from the package as Ubuntu restricts updating packages for these releases.

Also available in: Atom PDF