cleanbuild should support ignoring things in its tarball
Metadata
Current evaluation
Closed as obsolete after bases/build environments replaced the old LXD cleanbuild design; hardcoded .tox exclusion PR #1098 was closed unmerged.
Resolution: closed stale
Reason: The maintainer closed discussion by noting that bases and build environments introduced a different design. PR #1098 was rejected as hardcoding .tox, while commit 27ec9ba63 (#2335) subsequently removed LXD support for bases.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When tox runs, it creates virtualenvs in .tox. For projects that use multiple environments, these directories can end up being over 100MB in size, which makes the cleanbuild tar and transfer considerably slower.
Given that .tox is used for testing, and potentially contains compiled code which won't work in the cleanbuild container anyway, I believe it should be excluded.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as obsolete after bases/build environments replaced the old LXD cleanbuild design; hardcoded .tox exclusion PR #1098 was closed unmerged. | |
| stealth/space-bunny-alpha | — | closed stale | The .tox exclusion was not merged; PR #1098 was closed as an unscalable hardcoded approach, and the request later went stale after a 2019 redesign comment. | |
| stealth/space-bunny-alpha | — | closed stale | Proposed .tox exclusion for cleanbuild tarballs in #1098, but it was closed unmerged after maintainers deemed the hardcoded approach non-scalable. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The feature request to exclude directories from cleanbuild tarballs received no comments or activity over nine years, indicating the proposal was abandoned. No resolution or merge details were provided. | |
| qwen/qwen3.6-35b-a3b | — | — | cleanbuild tarball exclusion for .tox directories was closed without implementation. The request appears abandoned due to prolonged inactivity and zero comments. | |
| qwen/qwen3.6-35b-a3b | — | — | Request to exclude .tox from cleanbuild tarballs was closed without implementation or discussion. Lacking maintainer feedback, the feature request was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned without resolution. The proposal to exclude .tox directories from cleanbuild tarballs to reduce size and improve transfer speed was closed due to prolonged inactivity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/snapcraft#1098
(confidence 99%)
Proposed ignoring .tox in cleanbuild tarballs but was closed unmerged in favor of a broader design.
-
Superseded By:
canonical/snapcraft#2335
(confidence 88%)
Commit 27ec9ba63 removed LXD support for bases, consistent with the design transition cited on the issue.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1098 Ignore .tox directories when creating cleanbuild tar | snapcraft | closed | PR #1098 was closed unmerged: maintainers rejected hardcoding a .tox exclusion and redirected the broader ignore-file design to LP bug #1661064. | |
| #1775585 cleanbuild fails when source tree contains file with >65535 ownership(from LXD) | snapcraft (launchpad) | closed | Closed as obsolete after the separate cleanbuild command was removed; builds now clean-build transparently by default, so the old LXD failure path no longer applies. | |
| #1830371 Error message when using cleanbuild with bases could be improved | snapcraft (launchpad) | closed | Closed as obsolete: cleanbuild was removed and builds now transparently clean-build by default, confirmed by the maintainer on 17 Aug 2023. | |
| #1788774 cleanbuild should use host filesystem mapping (disk device) instead of packing source tarballs | snapcraft (launchpad) | closed | Expired without implementation after discussion about LXD remotes; Launchpad’s janitor closed it on 2018-11-11 for 60 days of inactivity. |