=== beisner- is now known as beisner
=== brainwash_ is now known as brainwash
[18:07] <israel> Hi I am trying to build a minimal Ubuntu in a chroot and tar it and then copy it to another machine as the OS.  I can do all that... however I am having a few issues.  One being that network-manager claims it isn't running.  I have similar issues using wicd.  I do install ubuntu-minimal and ubuntu-standard with its recommends.  Anyone have any suggestions where to get more help?
[20:36] <israel> Hi I am trying to build a minimal Ubuntu in a chroot and tar it and then copy it to another machine as the OS.  I can do all that... however I am having a few issues.  One being that network-manager claims it isn't running.  I have similar issues using wicd.  I do install ubuntu-minimal and ubuntu-standard with its recommends.  Anyone have any suggestions where to get more help?
[21:06] <Noskcaj> doko_, Is there any reason you maintain python-service-identity separately in debian and ubuntu?
[22:06] <soren> I have an amd64 server which attempts to fetch i386 Package lists from my mirror which is amd64 only. How do I disable that? Didn't there used to be a file in /etc/dpkg telling it to look for i386 so that I could just disable that?
[22:09] <Noskcaj> soren, What ubuntu release? It might be the arch: all packages, which are built on i386
[22:09] <soren> Noskcaj: No, this is about apt fetching the Package lists, not about specific packages.
[22:09] <Noskcaj> ok, ignore me then
[22:10] <soren> Hm. dpkg --remove-architecture i386
[22:10] <soren> ...solved it, apparently.
[22:11] <soren> I swear that didn't used to be how this was done.
[22:11] <teward> is there a way to nuke all sbuild schroots and rebuild them manually?
[22:11] <teward> (not sure where else to ask)
[22:11] <soren> teward: Assuming they're in the standard location, you can delete them from /var/lib/schroot/ and /etc/schroot.d/
[22:22] <teward> soren: thanks, that seems to have worked - ended up having to reboot into a root prompt (recovery mode) in order to burn them into dust, but that's not too difficult
[22:22] <teward> the shm-overlays apparently were breaking things so i had to nuke them AND the chroots, and start afresh...
[22:23] <soren> teward: Ah, yeah, if you had active sessions you should have nuked those first.
[22:23] <teward> soren: y'know what I had noticed?  They wouldn't shut off
[22:24] <soren> teward: Something like "schroot -e -a"
[22:24] <soren> teward: Maybe you were being too polite.
[22:24] <teward> soren: `sudo umount --force`, `sudo rm -rf /path/*`, `I will burn you unto dust!` was being too polite?
[22:25] <teward> soren: to be fair i would rather have nuked them BEFORE they're loaded at all, rather than messing with manual deactivation - root recovery prompt has its uses :P
[22:26] <teward> i think I'll just not use shm overlays this time and see what evils may happen
=== jono is now known as Guest292
[23:48] <doko_> Noskcaj, there was a packaging issue with some of the dependencies