[17:24] <brendand> pitti, what might 'W: No sandbox user '_apt' on the system, can not drop privileges' from adt-run mean? this is on xenial
[17:25] <teward> brendand: I saw that yesterday in my schroots...
[17:25] <teward> infinity had said that it's a harmless error, just that the sandbox user was missing, but that may be in my case due to package building in schroots
[17:25] <teward> and so far i haven't had any issues with that inside my Xenial VMs
[17:25] <brendand> teward, do your tests use dbus?
[17:26] <teward> brendand: not sure, the schroots do their own thing.  throw me a test to run, i'll run it :)
[17:26]  * teward is currently focused on the pending nginx merge since it's a month overdue, and additional packages are being uploaded after that for nginx which need the merge first
[17:27] <flocculant> nothing to do with tests or anything - but plagued by similar messages from synaptic in xenial since an apt update "Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"
[17:27] <teward> (yes, i'm here for QA and ISO testing, AND i'm on the server team xD)
[17:27] <teward> flocculant: so, basic apt-get update would trigger?
[17:27] <flocculant> perhaps the same root cause - pun intended
[17:27] <teward> or is that specifically with Synaptic or such
[17:28] <flocculant> seems synaptic specific
[17:29] <flocculant> though I did grab a new apt earlier I think
[17:29] <flocculant> 1.1.5
[17:30] <flocculant> yesterday - today was apt-xapian-index
[17:31] <flocculant> anyway - might be noise, might be connected :)
[17:31] <flocculant> balloons: is it possible to actually delete testcases from the tracker ? that is delete so not available for anything?
[17:31] <flocculant> obviously can from the branch
[17:45] <infinity> flocculant: Different bug.
[17:45] <infinity> flocculant: Yours is because synaptic is asking apt to read/write from an area that the _apt user can't access.
[17:46] <infinity> flocculant: brendand and teward are talking about chroots that don't have the _apt user at all.
[17:47] <infinity> flocculant: In either case, it's "harmless" in that apt will just run as root instead, as it always used to, but fixing the bugs so it can drop privs would be nice.
[17:54] <teward> thanks infinity for clarifying :)
[18:10] <flocculant> indeed infinity - thanks :)
[18:35] <balloons> flocculant, no
[18:35] <balloons> flocculant, it's there forever
[18:35] <flocculant> balloons: thanks - was pretty sure that was the case :)
[18:39] <flocculant> balloons: just double checking here - to enable tracker admin access someone just needs to be in a release team? https://launchpad.net/~ubuntustudio-release/+members#active
[18:39] <flocculant> talking about Ross
[18:39] <flocculant> I'm trying to help him sort his tracker stuff out
[18:40] <balloons> ohh right.. he mailed me
[18:40] <balloons> yes, it's controlled via LP teams (and the owner set properly in the tracker)
[18:41] <flocculant> as long as everything is set right - I've got to mail him about something else - so will send him screeny to make sure he is ticking the studio release box :)
[18:43] <balloons> ok, everything should be right on the tracker end
[18:44] <flocculant> ok - sent him that amongst other stuff
[18:44] <flocculant> I know when I first did it I wasn't seeing because I wasn't ticking the right box :)
[19:10] <pitti> brendand: this is the new apt  1.1; schroot does not really get along with that yet, so it prints the warning
[19:10] <pitti> brendand: should otherwise be harmless