← Back to issue list

Fix for bug #1572664 had broken my snap package build

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1575188
Type
issue
State
open
Author
~townsend
Labels
—
Created
Updated
Closed
—

Current evaluation

Reporter's snap build with a chroot containing dead-from-host symlinks broke after a fix for Launchpad bug #1572664; requests a build option to tolerate dead symlinks. No labels, no comments, no maintainer response; ~10 years old.

Suggested action: needs triage

Reason: No labels, no comments, no assignee, and no maintainer interaction in ~10 years, so it has never been triaged. The referenced fix (bug #1572664) and the build pipeline have changed substantially since (snapcraft now delegates to craft-parts), so it's unclear whether the dead-symlink failure still reproduces on a current version before deciding to close.

Impact: 35 Quick Win: 19.25 Staleness: 95 Complexity: 45 Confidence: 55 Support Request: 30

Issue body

I'm trying to build a snap package that contains a chroot. In the chroot are many symlinks. Those symlinks point to dead links from the host's perspective, but when inside the chroot, the symlinks are fine. I could build the snap before the fix for bug #1572664, but now it fails due to dead symlinks. Here is the output: $ snapcraft snap Skipping pull puritine (already ran) Skipping pull libertine (already ran) Preparing to build puritine Building puritine [Errno 2] No such file or directory: '/home/townsend/puritine/puritine/parts/puritine/build/libertine-data/libertine-container/puritine/rootfs/etc/alternatives/policytool.1.gz' Is it possible to have some sort of build option to allow dead symlinks when building a snap package?

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19.25
Staleness: 95
Complexity: 45
Confidence: 55
Support Request: 30
needs triage Reporter's snap build with a chroot containing dead-from-host symlinks broke after a fix for Launchpad bug #1572664; requests a build option to tolerate dead symlinks. No labels, no comments, no maintainer response; ~10 years old.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 10
close stale Open issue from ~10 years ago reporting snapcraft build failures due to dead symlinks in chroots after a previous fix. No maintainer response or labels.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 45
Confidence: 95
Support Request: 25
close stale User reports snapcraft build failure due to dead symlinks in a chroot after a previous fix. Issue has no comments, labels, or activity for over 10 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 30
Confidence: 85
Support Request: 70
close stale Unassessed request for a snapcraft build option to handle dead symlinks in chroots. Reported over 10 years ago following a fix for bug #1572664, with no maintainer interaction or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 100
Complexity: 35
Confidence: 90
Support Request: 60
close stale Snapcraft build fails on chroot symlinks that appear dead on the host after bug #1572664 fix. Requests a flag to allow dead symlinks. Issue is open, untriaged, and inactive with zero comments.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft#5384 (confidence 60%)

    Also about snapcraft following/failing on broken symlinks during build; triaged with fix deferred upstream to craft-application#721, so the same underlying symlink-handling concern.

  • Related To: snapcraft#1650686 (confidence 40%)

    Launchpad bug about symlinks not properly fixed up during snap build; closed as abandoned, indicating the symlink-fixup area was historically unstable.

Related issues

Issue Project State Summary Similarity
#1650686 Some symlinks not properly fixed up snapcraft (launchpad) closed Abandoned. Closed without comments or resolution. The snapcraft build failure caused by unpatched absolute symlinks remains unresolved, with no fix implemented.
71%