[04:30]  * micahg kicks off a few haskell rebuilds
[04:33]  * ScottK uploads haskell so micahg  can start over.
[04:36]  * micahg grumbles over the default suite being precise on precise
[05:53] <bkerensa> micahg: might you know whats causing this bzr error? http://paste.ubuntu.com/1135538/
[05:55] <bkerensa> nvm I forget to add my ssh key back
=== vorian is now known as v
[09:53] <bdrung> micahg: that's for getting you using quantal! :p
[13:14] <dupondje> Best way to setup a local apt repo is mini-dinstall ?
[13:14] <dupondje> but then you need to build the packages localle with pbuilder? And then dput them?
[13:15] <Lasall> don't use mini-dinstall, reprepro is much better, dupondje
[13:15] <Zhenech> reprepro
[13:16] <Lasall> and you are not restricted to use pbuilder. just create your package with -sa and then upload it with dput
[13:16] <Lasall> (if you missed that -sa you can use changestool provided by reprepro)
[13:17] <dupondje> the package gets builded on the server then?
[13:17] <paultag> no :)
[13:18] <Lasall> no, first build it. either with dpkg-buildpackage/debuild/pbuilder/... then upload it
[13:18] <paultag> remember, you could host an arch:ppc on an arch:i386 machine
[13:18] <dupondje> true :)
[13:19] <dupondje> then I need a build machine & repo machine :d
[13:19] <paultag> (rather then doing a sourceful upload *source*changes, you can do a binary upload, like Debian, and stich together more then one build -- like *amd64*changes
[13:19] <paultag> )
[13:19] <paultag> dupondje: you can build them locally before a dput
[13:19] <paultag> via sbuild, pbuild or any other exoctic what-have you
[13:23] <dupondje> need to check that :)
[13:23] <dupondje> thx
[13:23] <paultag> yarp.
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== Zic is now known as Guest81042
=== vibhav is now known as Guest78758
=== Quintasan_ is now known as Quintasan
[20:07] <elgaton> Hi everyone, stumbled across ITP in bug #328324, decided to fix it. Seems the package was in Debian up to Etch, then it got removed due to lack of maintainers. Should I get the old, original changelogs and debian/ files or start with a fresh packaging?
[20:07] <ubottu> Launchpad bug 328324 in Ubuntu "[needs-packaging] webmin" [Wishlist,Confirmed] https://launchpad.net/bugs/328324
[20:09] <arand> elgaton: It might need quite a bit of work, since I've normally heard it being discouraged on the basis of it being incompatible with the debian/ubuntu administration model...
[20:10] <elgaton> arand: What kind of work, more precisely?
[20:10] <arand> I have no idea...
[20:12] <elgaton> OK, I'll just have a look at it and see
[20:12] <elgaton> Thanks anyway
[20:16] <arand> elgaton: The only thing I've heard is what you get from ubottu: "/msg ubottu !webmin"
[20:19] <elgaton> arand: OK, I think I got a rough idea. Configuration files in Debian/Ubuntu are usually created from templates in /etc/default or the like (then actual configuration files are generated from them using a script). On the contrary, Webmin directly edits the final configuration files, so, when they are regenerated from the templates (e.g. because a new package version is installed), all edits are lost.
=== mfisch` is now known as mfisch
=== mfisch is now known as Guest6140