Handle SOURCE_DATE_EPOCH for SquashFS

Metadata

Project: snapcraft (launchpad)
Number: #1890046
Type: issue
State: open
Author: ~abitrolly
Labels: —
Created: 2020-08-02 03:32 PM UTC
Updated: 2025-11-22 05:41 AM UTC
Closed: —

Current evaluation

Feature request to respect SOURCE_DATE_EPOCH when creating the SquashFS inside .snap archives for reproducible builds; open since 2020, unlabelled, no maintainer interaction.

Suggested action: needs triage

Reason: The issue is unlabelled with 0 comments and no maintainer acknowledgement (confirmed by the related-issue lookup: 'Currently unlabelled and unacknowledged by maintainers'), so it has not been assessed. It is a legitimate feature request (reproducible builds), not a support question, and the concern is still relevant, so it should be triaged rather than closed. Confidence is moderate because I could not inspect the current snapcraft source to confirm whether SOURCE_DATE_EPOCH handling has since been added.

Impact: 40 Quick Win: 20.0 Staleness: 72 Complexity: 50 Confidence: 55 Support Request: 15

Issue body

For reproducible snap builds is needed that if SOURCE_DATE_EPOCH is set, the timestamps inside of .snap archive were set from it. --- v2.snap +++ yakshaveinc_eternal_amd64.snap ├── unsquashfs -s {} │ @@ -1,9 +1,9 @@ │ Found a valid SQUASHFS 4:0 superblock │ -Creation or last append time Sat Aug 1 18:36:27 2020 │ +Creation or last append time Sun Aug 2 15:04:00 2020 │ Filesystem size 576 bytes (0.56 Kbytes / 0.00 Mbytes) │ Compression xz │ Block size 131072 │ Filesystem is exportable via NFS │ Inodes are compressed │ Data is compressed │ Uids/Gids (Id table) are compressed ├── unsquashfs -d -lls {} │ @@ -1,6 +1,6 @@ │ Parallel unsquashfs: Using 4 processors │ 1 inodes (1 blocks) to write │ │ drwxr-xr-x root/root 27 2020-05-26 13:34 │ drwxr-xr-x root/root 32 2020-05-26 13:34 /meta │ --rw-r--r-- root/root 275 2020-08-01 18:36 /meta/snap.yaml │ +-rw-r--r-- root/root 275 2020-08-02 15:04 /meta/snap.yaml

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 06:49 AM UTC	qwen/qwen3.8-27b	Impact: 40 Quick Win: 20.0 Staleness: 72 Complexity: 50 Confidence: 55 Support Request: 15	needs triage	Feature request to respect SOURCE_DATE_EPOCH when creating the SquashFS inside .snap archives for reproducible builds; open since 2020, unlabelled, no maintainer interaction.
2026-07-23 11:40 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 85 Complexity: 45 Confidence: 70 Support Request: 15	needs triage	Request to respect SOURCE_DATE_EPOCH environment variable for reproducible builds when generating SquashFS-based .snap archives. Currently unlabelled and unacknowledged by maintainers.
2026-07-22 01:25 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 92 Complexity: 35 Confidence: 85 Support Request: 15	needs triage	Request to respect SOURCE_DATE_EPOCH for reproducible builds when generating SquashFS-based .snap archives. Currently unlabelled and unacknowledged by maintainers after over six years.
2026-07-09 02:32 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 45 Confidence: 75 Support Request: 15	needs triage	Request to implement SOURCE_DATE_EPOCH support for SquashFS timestamps to enable reproducible snap builds. Currently unlabelled and awaiting maintainer assessment after nearly six years.
2026-06-20 07:06 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 30 Confidence: 60 Support Request: 10	needs triage	Implement SOURCE_DATE_EPOCH support to set consistent timestamps in SquashFS archives for reproducible snap builds. Open, untriaged, and awaiting review or assignment.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.