busybox example no longer has permission to access files in home
Metadata
Current evaluation
Busybox example autopkgtest broke under new confinement default paths; fixed by ubuntu-core/snapcraft PR #487 updating the example tests, verified and released in snapcraft 2.8.8/2.8.8b (LP: #1574901 closed as verification-done).
Resolution: closed resolved
Reason: The reporter (~elopio) linked PR https://github.com/ubuntu-core/snapcraft/pull/487, merged as commit f5f7840ec adjusting the busybox example test to use the snap data path instead of $HOME. The fix shipped in snapcraft 2.8.8/2.8.8b and ~elopio marked verification-done on 2016-05-13 after testing in xenial-proposed, so SRU verification completed successfully.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Busybox example autopkgtest broke under new confinement default paths; fixed by ubuntu-core/snapcraft PR #487 updating the example tests, verified and released in snapcraft 2.8.8/2.8.8b (LP: #1574901 closed as verification-done). | |
| stealth/space-bunny-alpha | — | closed resolved | Busybox example test failed to access $HOME files after confinement default-path changes. Fixed by merged PR #487 (commit f5f7840ec) updating the test to use the snap data path; shipped in snapcraft 2.8.8/2.8.8b. | |
| stealth/space-bunny-alpha | — | closed resolved | Busybox example tests were fixed to use the snap data path, avoiding confinement-blocked access to $HOME and restoring the ls test (f5f7840ec). | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved the busybox example test failure caused by confinement and default path changes. The fix was verified and the issue closed, alongside autopackage test improvements. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed and verified. Confinement and path changes breaking busybox example tests were resolved. Autopackage tests improved. Verification label confirms successful resolution. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
ubuntu-core/snapcraft#487
(confidence 92%)
Upstream PR linked directly by the reporter in the fix comment; merged as f5f7840ec and included in the 2.8.8b release.
-
Related To:
snapcraft (launchpad)#1573349
(confidence 55%)
Same 2.8.8b SRU batch: 'Examples tests: Update the path to the snaps binaries' (#484), part of the same autopkgtest path-confinement cleanup.
-
Related To:
snapcraft (launchpad)#1573211
(confidence 45%)
Same SRU batch, examples autopkgtests adjustments (remove --allow-unauthenticated), indicating a coordinated fix for example test breakage.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #388 busybox example: update the expected results | snapcraft | merged | Merged in canonical/snapcraft#388 as c56bea031, updating BusyBox example expectations and using busybox.touch for Ubuntu Core's changed command directory. | |
| #1623621 busybox demo test fails in yakkety with x1/busybox.test: No such file or directory | snapcraft (launchpad) | closed | Fixed the Yakkety BusyBox demo test failure by using the last installed data directory; the change landed in snapcore/snapcraft PR #801 (commit 8d91b7758). | |
| #392 busybox example: update the expected results | snapcraft | closed | Superseded by snapcraft#388, merged as c56bea031 with updated BusyBox results for Ubuntu Core’s changed working directory. | |
| #1560255 test_busybox example fails because the /snaps/bin/busybox.ls now returns the cwd contents | snapcraft (launchpad) | closed | Updated the BusyBox example's expected output for Ubuntu Core's new ls behavior; PR #388 was merged as c56bea031. |