Bug #15383

libc6-dev fails to install

Added by singuliere 2018-03-06 10:58:23 . Updated 2018-03-14 11:03:55 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.6
Start date:
2018-03-06
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Additional Software Packages
Deliverable for:

Description

libc6 is 2.24.11+deb9u3 and apt-get install libc6-dev will fail because it depends on 2.24.11+deb9u1. apt-get install libpython2.7-dev will also fail for the same reason.

Subtasks

Related issues

Blocked by Tails - Feature #15341: Upgrade to Stretch 9.4 Resolved 2018-02-11

History

#1 Updated by intrigeri 2018-03-06 11:13:31

> libc6 is 2.24.11+deb9u3 and apt-get install libc6-dev will fail because it depends on 2.24.11+deb9u1. apt-get install libpython2.7-dev will also fail for the same reason.

Ouch, sorry. Assuming this happens only on 3.6~rc1, I believe that’s due to the mismatch between APT sources used during the build (that include stretch-proposed-updates) and APT sources enabled at runtime (that don’t include stretch-proposed-updates, on purpose, which is generally a good thing except when it’s not). This problem will be solved in Tails 3.6 final: once Feature #15341 is done the {build,run}time APT sources will be back in sync.

#2 Updated by intrigeri 2018-03-06 11:13:50

#3 Updated by intrigeri 2018-03-06 11:14:23

  • Status changed from New to Confirmed
  • Assignee set to intrigeri
  • Affected tool set to Additional Software Packages

#4 Updated by intrigeri 2018-03-06 11:34:56

As a temporary workaround you can add stretch-proposed-updates to your APT sources.

#5 Updated by intrigeri 2018-03-11 09:14:32

  • Assignee changed from intrigeri to bertagaz
  • QA Check set to Ready for QA

#6 Updated by bertagaz 2018-03-11 17:45:33

  • Status changed from Confirmed to Fix committed
  • Assignee deleted (bertagaz)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

intrigeri wrote:
> Ouch, sorry. Assuming this happens only on 3.6~rc1, I believe that’s due to the mismatch between APT sources used during the build (that include stretch-proposed-updates) and APT sources enabled at runtime (that don’t include stretch-proposed-updates, on purpose, which is generally a good thing except when it’s not). This problem will be solved in Tails 3.6 final: once Feature #15341 is done the {build,run}time APT sources will be back in sync.

Seems that’s the reason, they install fine once Feature #15341 is merged.

#7 Updated by bertagaz 2018-03-14 11:03:55

  • Status changed from Fix committed to Resolved