Bug #14650
Package new upstream version of tails-installer -> bpo
80%
Description
and upload to Debian & Ubuntu
Subtasks
Related issues
Related to Tails - |
Resolved | 2018-04-14 | |
Related to Tails - |
Resolved | 2018-01-17 | |
Blocked by Tails - |
Resolved | 2015-02-04 | |
Blocks Tails - |
Resolved | 2018-01-17 | |
Blocks Tails - |
Resolved | 2017-09-17 |
History
#1 Updated by Anonymous about 8 years ago
- Subject changed from tails-installer to Package new upstream version of tails-installer
- Description updated
#2 Updated by Anonymous about 8 years ago
- blocked by
Feature #8859: Get rid of the splash screen of Tails Installer added
#3 Updated by Anonymous about 8 years ago
- Target version set to Tails_3.3
#4 Updated by sajolida about 8 years ago
- blocked by
Feature #14677: Update doc to new Tails Installer without splash screen (in Debian) added
#5 Updated by sajolida about 8 years 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 Feature #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 about 8 years ago
> I guess you are referring here to Tails Installer 4.4.19 which solves Feature #8859.
Hold on by the way, 4.4.19 is not ready to go into Debian as-is.
#7 Updated by intrigeri about 8 years 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 Anonymous about 8 years 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 Anonymous about 8 years ago
- QA Check deleted (
Info Needed)
#10 Updated by intrigeri about 8 years ago
- Parent task deleted (
)Bug #14646
#11 Updated by intrigeri about 8 years ago
- blocks
Bug #14646: Core work 2018Q1 → 2018Q2: Debian added
#12 Updated by anonym about 8 years ago
- Target version changed from Tails_3.3 to Tails_3.5
#13 Updated by Anonymous about 8 years ago
- Status changed from Confirmed to Fix committed
- % Done changed from 0 to 100
Uploaded to Debian.
#14 Updated by Anonymous about 8 years 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.
#15 Updated by intrigeri about 8 years ago
- Status changed from Fix committed to In Progress
- % Done changed from 100 to 80
- Affected tool set to Installer
The package is not in stretch-backports yet (IIRC it was rejected once because it was uploaded before the corresponding version migrated to testing, and a second time because of some “already seen signature” handling or similar protection against upload replay) so I think this ticket should not be “Fix committed” yet.
#16 Updated by Anonymous about 7 years ago
- Target version changed from Tails_3.5 to Tails_3.6
Still missing the backport, I have to rebuild it.
#17 Updated by Anonymous about 7 years ago
- blocks deleted (
)Feature #14677: Update doc to new Tails Installer without splash screen (in Debian)
#18 Updated by Anonymous about 7 years ago
- related to
Feature #14677: Update doc to new Tails Installer without splash screen (in Debian) added
#19 Updated by Anonymous about 7 years ago
- Subject changed from Package new upstream version of tails-installer to Package new upstream version of tails-installer -> bpo
#20 Updated by sajolida about 7 years ago
- related to deleted (
)Feature #14677: Update doc to new Tails Installer without splash screen (in Debian)
#21 Updated by sajolida about 7 years ago
- blocks
Feature #14677: Update doc to new Tails Installer without splash screen (in Debian) added
#22 Updated by intrigeri about 7 years ago
Our end-user doc says we support Tails Installer on Jessie as well but we haven’t uploaded a new installer there for 2 years. I don’t think we can upload a new package to jessie-backports
since it’s not in Stretch, so that would have to go into jessie-sloppy-backports
I think. But that will require an update of our installation assistant. Unless… perhaps it’s time to drop support for Jessie?
#23 Updated by bertagaz about 7 years ago
- Target version changed from Tails_3.6 to Tails_3.7
#24 Updated by Anonymous about 7 years ago
Uploaded new version to unstable today. Will prepare backport next week + Ubuntu PPA versions and version for Ubuntu Bionic.
#25 Updated by intrigeri about 7 years ago
- related to
Bug #15533: Clarify the status of Tails Installer for Jessie added
#26 Updated by intrigeri about 7 years ago
intrigeri wrote:
> Our end-user doc says we support Tails Installer on Jessie as well but we haven’t uploaded a new installer there for 2 years. I don’t think we can upload a new package to jessie-backports
since it’s not in Stretch, so that would have to go into jessie-sloppy-backports
I think. But that will require an update of our installation assistant. Unless… perhaps it’s time to drop support for Jessie?
I think it’s too confusing to handle this problem on this ticket and there’s no reason it blocks the upload to stretch-backports, so I’ve filed a dedicated ticket: Bug #15533.
#27 Updated by Anonymous about 7 years ago
- related to
Bug #15183: Prepare tails-installer release for Ubuntu Bionic Beaver added
#28 Updated by Anonymous about 7 years ago
- Status changed from In Progress to Resolved