Project

General

Profile

Bug #16289

Broken chroot configuration in feature/buster?

Added by CyrilBrulebois 6 months ago. Updated 6 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Build system
Target version:
-
Start date:
01/05/2019
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Here's the current configuration:

$ ls -l config/chroot_sources/*
lrwxrwxrwx 1 kibi kibi    10 Sep  9  2016 config/chroot_sources/sid.binary -> sid.chroot
-rw-r--r-- 1 kibi kibi    63 Oct  1 16:48 config/chroot_sources/sid.chroot
lrwxrwxrwx 1 kibi kibi    12 Sep  9  2016 config/chroot_sources/tails.binary -> tails.chroot
lrwxrwxrwx 1 kibi kibi    16 Sep  9  2016 config/chroot_sources/tails.binary.gpg -> tails.chroot.gpg
-rw-r--r-- 1 kibi kibi  5909 Oct  1 16:48 config/chroot_sources/tails.chroot.gpg
lrwxrwxrwx 1 kibi kibi    17 Sep  9  2016 config/chroot_sources/torproject.binary -> torproject.chroot
lrwxrwxrwx 1 kibi kibi    21 Sep  9  2016 config/chroot_sources/torproject.binary.gpg -> torproject.chroot.gpg
-rw-r--r-- 1 kibi kibi    57 Jan  5 14:24 config/chroot_sources/torproject.chroot
-rw-r--r-- 1 kibi kibi 45068 Jan  4 14:20 config/chroot_sources/torproject.chroot.gpg

which means tails.binary is a broken symlink to tails.chroot.

This doesn't lead to an FTBFS but that should probably be fixed?

History

#1 Updated by CyrilBrulebois 6 months ago

On second thought maybe that file is automatically generated, will try to double check myself while looking at getting experimental enabled.

#2 Updated by intrigeri 6 months ago

On second thought maybe that file is automatically generated,

I think so: we have the same on the stable branch.

#3 Updated by intrigeri 6 months ago

  • Status changed from New to Rejected
  • Target version deleted (Tails_4.0)

Also available in: Atom PDF