Project

General

Profile

Feature #6038

Feature #14568: Additional Software Packages

Additional software: fix installation of packages requiring manual confirmation

Added by Tails over 4 years ago. Updated 5 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
Due date:
12/15/2017
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Easy:
No
Affected tool:
Additional Software Packages

Description

Currently this feature fails to install packages that require manual confirmation. For example sun-java6-jdk. Setting debconf priority to critical should help.

History

#1 Updated by Tails over 4 years ago

  • Parent task set to #5551

#2 Updated by intrigeri about 4 years ago

  • Category set to Persistence
  • Easy set to No

#3 Updated by BitingBird over 3 years ago

  • Subject changed from additional software: fix installation of packages requiring manual confirmation to Additional software: fix installation of packages requiring manual confirmation

#4 Updated by intrigeri over 3 years ago

  • Type of work changed from Research to Code

Setting debconf priority to critical should be just enough: iirc, it's a violation of the Debian Policy to require interactive input in other ways that debconf on package installation.

#5 Updated by u about 2 months ago

  • Assignee set to alant

I strongly suppose that this will have to be done during or even before the work on a GUI for additional software. Assigning to alan.

#6 Updated by BitingBird about 2 months ago

  • Target version set to 2018

#7 Updated by u about 1 month ago

  • Parent task changed from #5551 to #14568

#8 Updated by u about 1 month ago

  • Parent task changed from #14568 to #5551

#9 Updated by u about 1 month ago

  • Target version changed from 2018 to Tails_3.4
  • Affected tool set to Additional Software Packages

#10 Updated by intrigeri 29 days ago

If I'm not mistaken, this is not formally part of SponsorW_2017. I propose we move it our of that view for now, but keep that in mind for #14592: I doubt many users will install such packages so perhaps we will prefer to focus on polishing & bugfixing that has a greater impact, even though the impact of this bug is pretty bad when it happens.

What do you think?

#11 Updated by sajolida 29 days ago

I agree.

Now, how complicated would it be to detect such packages as part of SponsorW_2017 and display a message saying "Sorry, Additional Software doesn't work with this package because it requires manual confirmation.". So we're not silently failing.

#12 Updated by intrigeri 29 days ago

Now, how complicated would it be to detect such packages as part of SponsorW_2017 and display a message saying "Sorry, Additional Software doesn't work with this package because it requires manual confirmation.". So we're not silently failing.

Probably harder than fixing the problem (which should be easy in itself, so if we have extra time, I'd actually love if we could fix it :)

#13 Updated by u 26 days ago

  • Parent task changed from #5551 to #14568

#14 Updated by u 26 days ago

I'm keeping this ticket in the view for now, but not as a deliverable for Sponsor_W.

#15 Updated by intrigeri 25 days ago

Deliverable for changed from SponsorW_2017 to Tails_3.7

I'm keeping this ticket in the view for now, but not as a deliverable for Sponsor_W.

Setting "Deliverable for" to a Tails version is new and has no well-defined semantics, so I wonder: did you mean to set "Target version: Tails_3.7" instead?

#16 Updated by u 23 days ago

Oops, no, I wanted to unset the deliverable.

#17 Updated by u 5 days ago

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

#18 Updated by u 5 days ago

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

#19 Updated by alant 5 days ago

  • Due date set to 12/15/2017

Also available in: Atom PDF