canonical / canonical/workshop
Should suppress or wait for unattended-upgrades
- Dominant language
- Go
- Stars
- 108
- Forks
- 17
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 40
Description
Tried launching a new workshop today and ended up with
```
$ workshop launch
error: cannot perform the following tasks:
- Run hook "setup-project" for "mir" SDK (command exit code 100)
"dev" launch aborted
$ workshop tasks
# ...
2026-09-08T11:26:29+02:00 INFO + sudo apt-get build-dep .
Note, using directory '.' to get the build dependencies
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 6047 (unattended-upgr)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
```
Lots of SDKs will be installing packages, Workshop should avoid the above by either waiting for `unattended-upgrades` before executing hooks, or suppress it.
Contributor guide
Research direction
Start with the `workshop launch` path and the `setup-project` hook shown in the task output; reproduce the failure while `unattended-upgrades` holds `/var/lib/dpkg/lock-frontend`. Determine whether launch should wait for or suppress that process, then verify that SDK package-install hooks no longer abort when the lock is held.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100