[10:07] <whereistimbo> Hi guys. I'm having trouble building pulseaudio deb from git branch remotes/pkg/applied/ubuntu/bionic, I'm using clean install of xubuntu 18.04.2 with virtualbox, any help with recommended setup?
[13:05] <raviola> 	Hi guys. I'm having trouble building pulseaudio deb from git branch remotes/pkg/applied/ubuntu/bionic, I'm using clean install of xubuntu 18.04.2 with virtualbox, any help with recommended setup?
[13:07] <raviola> I need build pulseaudio deb package from source so I can debug it. But I have trouble to build it even in clean install
[13:07] <cjwatson> this is not me offering to help, but you probably stand a better chance of finding somebody to help you if you put a transcript of exactly what you've done and the resulting error messages on a pastebin (e.g. paste.ubuntu.com)
[13:08] <cjwatson> (please don't highlight me in responses)
[13:08] <raviola> Thanks cjwatson, however I think the fault is my part so I'd like to just redo the clean install in virtualbox
[13:08] <cjwatson> 14:08 <cjwatson> (please don't highlight me in responses)
[13:09] <cjwatson> anyway, if you don't show what the errors are then probably nobody will be able to help
[13:09] <cjwatson> so that would be your best way forward
[15:30] <sil2100> Laney: hey! A quick question - do you know if the latest version of britney2-ubuntu is used in production right now? Since I was thinking of maybe switching off dry-run mode from the SRU ADT thingy this week, it looks like it works as expected but still doesn't save the state apparently
[15:30] <sil2100> Laney: I think I fixed that though
[15:31] <sil2100> Laney: is the latest master in production now? Or is it simply the broken version still?
[15:32] <Laney> sil2100: what broken version?
[15:32] <Laney> every run does a 'git pull' from the branch
[15:33] <Laney> I didn't merge anything further from you yet if that's what you mean
[15:38] <sil2100> Ah, hmmm, so it's basically using the latest master
[15:38] <sil2100> Since I pushed 2 fix commits there, but maybe there's something broken somewhere else
[15:39] <sil2100> Laney: thanks, will look into what's up then o/
[15:39] <Laney> you can go onto the machine and look at 'git log' in there
[15:39] <sil2100> Laney: but isn't that on snakefruit?
[15:40] <Laney> yeah
[15:40] <Laney> can confirm the head is 1cbc21d25851bf5652663a434d20a2c671c59e54
[15:41] <sil2100> Laney: thanks!
[15:42]  * sil2100 looks into that
[16:36] <sil2100> Laney: aaaah, ok, forgot that when it's run in dry-run mode, the state file is simply not saved
[16:37] <sil2100> Laney: duuuh
[16:37] <sil2100> Laney: so ok, it will most probably work once we switch to normal mode of operations
[16:38] <sil2100> Laney: do you think we could switch dry-run off tomorrow?
[16:45] <Laney> sil2100: yeah, I think that should just happen if you commit the appropriate change to b1
=== laptop27 is now known as laptop2
[18:45] <ahasenack> is there a specific log file ownership/permissions policy for when we want the logs to be restricted?
[18:45] <ahasenack> I've seen some 0640 root:adm
[18:46] <ahasenack> or root:root 0600
[18:46] <ahasenack> also syslog:adm 0640
[18:46] <ahasenack> apport.log: 0640 root:adm
[18:46] <ahasenack> auth.log: 0640 syslog:adm
[18:46] <ahasenack> boot.log: 0600 root:root
[18:47] <ahasenack> syslog: 0640 syslog:adm
[18:48] <sarnold> ahasenack: hmm, I thought the policy manual dictated adm group for most logs, but don't see it on https://www.debian.org/doc/debian-policy/ch-files#log-files
[18:48] <ahasenack> yeah, it talks about purging, but not ownership or permissions
[18:48] <ahasenack> even 10.9 just below
=== laptop20 is now known as laptop2