phablet-flash needs a cleanup option to remove old images

[Alan Pope 🍺🐧🐱 🦄]

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-thought:~$ du -hs Downloads/phablet-flash/
9.0G Downloads/phablet-flash/

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.

[Oliver Grawert (ogra)]

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.

[Tim Peeters (tpeeters)]

now that we have ubuntu-device-flash where the images are in a hidden directory, I think this bug became a lot more relevant. We don't want the diskspace to fill and people to wonder where it went.

[Sergio Schvezov (sergiusens)]

On Mon, Mar 10, 2014 at 8:43 AM, Tim Peeters <email address hidden> wrote:
> now that we have ubuntu-device-flash where the images are in a hidden
> directory, I think this bug became a lot more relevant. We don't want
> the diskspace to fill and people to wonder where it went.

~/.cache/ubuntuimages/

[Sergio Schvezov (sergiusens)]

I've added a simple cleanup option; not sure yet how to get something that works for everyone in an automagic way as the files that are downloaded are not sequential in any way and different versions/revisions can refer to the same file;

Easy options seem to be to clean by age (but how old?)
By age and size if a certain size is passed (which size? How aggressively should we bump the age as the size is not met?)

The other option, which requires downloading all channels for all devices and seeing which files are unreferenced and clean those (useful for aggresive users of devel-proposed).

I would argue that an application developer would use a released version (channel stable) so I don't see why the sdk would need it per se in the future as the can just clean up everything (the few released images)

[Launchpad Janitor (janitor)]

This bug was fixed in the package goget-ubuntu-touch - 0.2+14.04.20140317-0ubuntu1

---------------
goget-ubuntu-touch (0.2+14.04.20140317-0ubuntu1) trusty; urgency=low

  [ Sergio Schvezov ]
  * Simple cleanup option for flashing. (LP: #1157710)
 -- Ubuntu daily release <email address hidden> Mon, 17 Mar 2014 21:37:05 +0000