josch/mmdebstrap
2
3
Fork 6
Code Issues 8 Pull requests 1 Projects Releases Wiki Activity

Absolute symlinks are wrong in mode=dir #16

New issue
Closed
opened 2021-10-28 09:43:48 +00:00 by Ghost · 2 comments
Ghost commented 2021-10-28 09:43:48 +00:00
Copy link

When I run mmdebstrap with --mode=fakechroot --format=dir then absolute symlinks in the generated tree contain the full real path:

ROOT/etc/localtime -> /home/nils/packetalarm/is/OUT/ROOT/usr/share/zoneinfo/Etc/UTC

When I run it with --format=tar the same symlink is generated correctly as:

localtime -> /usr/share/zoneinfo/Etc/UTC

(The /etc/localtime symlink is just an example. All absolute symlinks in the generated tree contain the actual complete filenames)

But imho the only real use of an output with --format=dir is either to chroot to it, or to create a tarball of it myself. In both cases, the absolute symlinks point to the wrong location.

When I run mmdebstrap with --mode=fakechroot --format=dir then absolute symlinks in the generated tree contain the full real path: ROOT/etc/localtime -> /home/nils/packetalarm/is/OUT/ROOT/usr/share/zoneinfo/Etc/UTC When I run it with --format=tar the same symlink is generated correctly as: localtime -> /usr/share/zoneinfo/Etc/UTC (The /etc/localtime symlink is just an example. All absolute symlinks in the generated tree contain the actual complete filenames) But imho the only real use of an output with --format=dir is either to chroot to it, or to create a tarball of it myself. In both cases, the absolute symlinks point to the wrong location.
josch commented 2021-10-28 12:24:35 +00:00
Owner
Copy link

No. This is not a bug but just how fakechroot works. If you don't want it, then don't use fakechroot.

Suppose mmdebstrap would convert all symlinks to not have the full path. Then anybody who wants to create a tarball of it later (as you intend to) would have broken symlinks inside the chroot. So this is not an option.

If you disagree, please explain further why this would be useful.

No. This is not a bug but just how fakechroot works. If you don't want it, then don't use fakechroot. Suppose mmdebstrap would convert all symlinks to not have the full path. Then anybody who wants to create a tarball of it later (as you intend to) would have broken symlinks inside the chroot. So this is not an option. If you disagree, please explain further why this would be useful.
josch commented 2021-11-07 09:06:59 +00:00
Owner
Copy link

If you don't have any further input, I'll close this bug.

If you don't have any further input, I'll close this bug.
josch closed this issue 2021-12-06 10:24:52 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.3
1.4.2
1.4.1
1.4.0
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.0
1.0.1
1.0.0
0.8.6
0.8.5
0.8.4
0.8.3
0.8.2
0.8.1
0.8.0
0.7.5
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
0.6.1
0.6.0
0.5.1
0.5.0
0.4.1
0.4.0
0.3.0
0.2.0
0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: josch/mmdebstrap#16
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?