Bug #6783

Test whether Windows installation method creates unexpected files

Added by sajolida 2014-02-26 20:54:34 . Updated 2014-07-28 22:20:46 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Installation
Target version:
Start date:
2014-02-26
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

I’m starting to think that the Windows USB installer thing we’re recommending might be the one who creates a hidden directory that then breaks upgrades, after the stick created by that installer is used to install another stick with Tails Installer.

Subtasks

Related issues

Related to Tails - Bug #7678: Tails Installer crashes on upgrade if cruft files with same name are present on both sides Resolved 2014-07-28

History

#1 Updated by sajolida 2014-06-29 14:40:05

  • Status changed from Confirmed to In Progress
  • Assignee changed from sajolida to intrigeri
  • Type of work changed from Test to Research
  • Starter changed from Yes to No

This is what I got after the procedure described in https://mailman.boum.org/pipermail/tails-testers/2014-June/000047.html:

.disk
EFI
license.txt
live
syslinux
Uni-USB-Installer-Copying.txt
Uni-USB-Installer-Readme.txt
utils
uui

Reassigning for further analysis to intrigeri who proposed that test.

#2 Updated by intrigeri 2014-07-28 22:19:08

  • related to Bug #7678: Tails Installer crashes on upgrade if cruft files with same name are present on both sides added

#3 Updated by intrigeri 2014-07-28 22:20:46

  • Category changed from 178 to Installation
  • Status changed from In Progress to Resolved

Thanks. Then, I think that it’s the same issue that has been properly analyzed and documented on Bug #7678. Going to bump its priority accordingly.