[01:15] [telegram] kc2bez: yep saw [01:15] [telegram] @The_LoudSpeaker i been dead all day sorry :P [01:16] [telegram] @The_LoudSpeaker you should be able to tell them to reg with their Debian address (debian.org) [01:16] [telegram] if they don't have one then they need to email the Council to request, and I'll process and add. [01:16] [telegram] the problem is that we got a maaaaaaaaaasive influx of spammers the past year so we did some security restrictions there xD === Linuxembourg_ is now known as Linuxembourg [14:14] Kaay. I will ask them to register using debian address [14:16] [telegram] The_LoudSpeaker: thank you kindly! [14:18] Also, can anyone share a script or list of commands that they are using for their sbuilder setups? [14:18] [telegram] from scratch? Yeah I can. [14:18] [telegram] from envbuild to execution of builds in the schroots from it, i can. [14:19] I didn't check earlier and moved to fedora as my main distro. Lxc doesn't work properly on Fedora. I gotta use sbuild or chroots now. Or docker images. [14:19] @teward001 yes please. Thanks! [14:20] I more or less follow the wiki https://wiki.ubuntu.com/SimpleSbuild [14:20] I only change the lintian stuff really. [14:21] [telegram] ^^ that [14:21] [telegram] but i have some extra stuff I toss into devscripts and the sbuild rc because of how I need to build envs. [14:22] [telegram] and i have a TON of extra stuff I toss in for when I'm testing against -proposed [14:22] I actually wrote a dockerfile for creating custom debian:sid images with required essential packages like nano debhelper, etc. I use that image to create and nuke containers. For creating impish dockerfile, there's a bug in docker currently. It will need some time. [14:23] [telegram] oh that reminds me... *tests Impish schrooting* [14:23] kc2bez[m]: yes. I used to follow that create my chroots earlier. But it's a long process. If someone has it all in a script then it would be nice. Else I gotta write one for myself. [14:24] @teward001 send your scripts. I will remove extra stuff I don't need. [14:24] [telegram] give me some time, i'm doing FT job stuff ;) [14:24] [telegram] and there's a lot of things in here so stdby [14:24] Yeah. At your convenience. [14:26] Also, is there a way to create small qemu ubuntu VMs using virsh ? [14:26] I found images here: http://cloud-images.ubuntu.com/ [14:27] Downloading and untarring a few now. [14:28] Sure but you might as well add Virtual Machine Manager so you don't need to remember all that. It doesn't really add any overhead. [14:57] The_LoudSpeaker: there's a lot of manual stuff you have to do for `sbuild` unless your environment is on the latest and greatest Ubuntu. Hence why there's no full-deployment script for building sbuild environments from scratch. I can try and concatenate everything into a single script but that'll take more time than providing what I've got. [14:58] [telegram] the inital sbuild setup on SimpleSbuild is only 9 steps (skip the optionals) [14:58] [telegram] the rest are more informative commands you can run if you need to [15:01] I think the mounting your home directory optional step is handy but certainly not required. [15:02] [telegram] @kc2bez it's required inside the schroot [15:02] [telegram] because everything writes to the scratch dir. [15:02] [telegram] which is *in* your home dir [15:03] [telegram] oh you mean the other hints one [15:03] [telegram] you're right [15:03] [telegram] but i meant the actual steps to get started [15:03] [telegram] not the extra hints [15:03] [telegram] i.e. https://wiki.ubuntu.com/SimpleSbuild#Creating_the_schroots specificlaly [15:03] yeah that [15:04] I didn't think it took too long for the whole thing really. [15:04] [telegram] it doesn't. [15:04] [telegram] that said, you *have* to mount your home directory if you have an *encrypted* home dir [15:04] [telegram] that's a different issue [15:04] [telegram] because that part says "If you use an encrypted home directory, your $HOME is mounted differently, so you will have to add" [15:04] [telegram] OTHERWISE it's pretty straightforward [15:05] Just LUKS encrypt the whole thing and then you don't need to worry about it. It unlocks on boot. [15:05] [telegram] lol [15:05] [telegram] the only thing not covered here is if you're NOT using the latest version of Ubuntu as your sbuild/dev env [15:05] [telegram] then you have to do some things for workarounds [19:15] I learned that I could install the daily and then use apt to update/upgrade as new dailies were released. So, I have an installation that is also testing this. It's not actually one of the mandatory tests, but could prove useful. Is there anywhere that I should be reporting that? (Also, I've had little free time in the past week.)