buildd admins cannot upload new chroot tarballs without shell access to the archive
Bug #158402 reported by
LaMont Jones
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Steve Kowalik | ||
Bug Description
Right now, publishing a chroot tarball for the buildd requires shell access to the archive.
There needs to be a way to upload a tarball that does not require such access.
| Changed in soyuz: | |
| assignee: | nobody → cprov |
| milestone: | none → 1.1.11 |
| Changed in soyuz: | |
| milestone: | 1.1.11 → 1.2.1 |
| Changed in soyuz: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in soyuz: | |
| milestone: | 1.2.1 → 1.2.2 |
| Changed in soyuz: | |
| milestone: | 1.2.2 → 1.2.3 |
| Changed in soyuz: | |
| milestone: | 1.2.3 → none |
| Changed in soyuz: | |
| assignee: | Celso Providelo (cprov) → nobody |
| Changed in soyuz: | |
| importance: | High → Medium |
| Changed in launchpad: | |
| importance: | Medium → High |
| description: | updated |
| summary: |
- there needs to be a way for a buildd admin to upload a new chroot - tarball + buildd admins cannot upload new tarballs without shell access to the + archive |
| summary: |
- buildd admins cannot upload new tarballs without shell access to the - archive + buildd admins cannot upload new chroot tarballs without shell access to + the archive |
| Changed in launchpad: | |
| assignee: | nobody → Steve Kowalik (stevenk) |
| status: | Triaged → Fix Released |
To post a comment you must log in.
