[Touch-packages] [Bug 1389357] Re: whoopsie reuses CRASH_DB_IDENTIFIER on next run

2014-11-05 Thread Evan Dandrea
This will mean that tests in CI will negligibly skew the results, but I think we can live with that for now. I agree that this is low priority. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.l

[Touch-packages] [Bug 1340604] Re: [phone] crash files are only uploaded on boot

2014-07-22 Thread Evan Dandrea
Stellar work, guys. I do find it odd that this is causing whoopsie to sit around doing nothing, given that online_state defaults to true, but let's assume for a minute that dbus is indeed the problem. The upstart job doesn't have any non-runlevel service dependencies, so it could conceivably come

[Touch-packages] [Bug 1307215] Re: destroy-environment fails to clear lxc containers

2014-07-17 Thread Evan Dandrea
Correct. Attached is a juju-deployer config that reproduces the issue when used with the juju local provider and /var/lib/lxc in the host backed onto btrfs. If you deploy it and run juju destroy-environment --force -y local, it should fail. This is because Ceph sees that /srv/ceph is on btrfs and

[Touch-packages] [Bug 1307215] Re: destroy-environment fails to clear lxc containers

2014-07-14 Thread Evan Dandrea
To further clarify, this isn't a juju bug. lxc should be smart enough to delete dependent subvolumes before it deletes the rootfs subvolume. I took a stab at this over the weekend, but ran out of time. btrfs_destroy(struct bdev *orig) is what you're after. ** Also affects: lxc (Ubuntu) Importan