phablet-flash needs a cleanup option to remove old images
Bug #1157710 reported by
Alan Pope 🍺🐧🐱 🦄
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Phablet Tools |
Invalid
|
Wishlist
|
Unassigned | ||
goget-ubuntu-touch (Ubuntu) |
Fix Released
|
Medium
|
Sergio Schvezov |
Bug Description
Developers are using a button in qtcreator to launch phablet-flash, probably not realising this is eating up their disk space in ~/Downloads.
alan@deep-
9.0G Downloads/
it would be useful for phablet-flash to have a "--cleanup" option which removes all but the most recent "N" images (default N=2?). A button could then be added to qtcreator ubuntu devices pane to 'clean up' which would simply run phablet-flash with the cleanup option.
Related branches
lp:~sergiusens/goget-ubuntu-touch/clean
- Alan Pope 🍺🐧🐱 🦄 (community): Approve
- Manuel de la Peña (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 34 lines (+8/-1)2 files modifiedubuntu-device-flash/args.go (+1/-0)
ubuntu-device-flash/main.go (+7/-1)
Changed in phablet-tools: | |
importance: | Undecided → Wishlist |
Changed in phablet-tools: | |
assignee: | nobody → Sergio Schvezov (sergiusens) |
Changed in phablet-tools: | |
status: | New → Confirmed |
status: | Confirmed → In Progress |
information type: | Public → Public Security |
Changed in goget-ubuntu-touch (Ubuntu): | |
assignee: | nobody → Sergio Schvezov (sergiusens) |
importance: | Undecided → Medium |
Changed in phablet-tools: | |
assignee: | Sergio Schvezov (sergiusens) → nobody |
Changed in phablet-tools: | |
status: | In Progress → Invalid |
To post a comment you must log in.
it should also have a better numbering scheme, while the jenkins build number can be reset which makes you end up with multiple downloads in one dir (i.e. the first raring build is "95" which is also the version of the first released image) which makes quite a mess and will occur again once the build number changes again ... like if jenkins moves to a new machine or something else happens that makes it start counting from zero ...
since cdimage numbering is guaranteed to increment with every build i would propose to instead use this numbering scheme for the download dirs.