=== avoine [n=avoine@modemcable060.221-200-24.mc.videotron.ca]  has joined #ubuntu-installer
=== blackskad [n=blackska@d54C1A48C.access.telenet.be]  has joined #ubuntu-installer
=== cjwatson [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk]  has joined #ubuntu-installer
=== cr3 [n=marc@pdpc/supporter/bronze/cr3]  has joined #ubuntu-installer
=== jetsaredim [n=jgreenwa@inet-netcache3-o.oracle.com]  has joined #ubuntu-installer
[03:30] <cjwatson> hah
=== cjwatson spots the source of some resizing problems in ubiquity
[03:30] <evand> eh?
[03:30] <evand> by the way, thoughts on hobsee's question?  I figured tag it and we'll deal with it when there's a mythbuntu source package, but I'm not entirely sure
=== mpt_ [n=mpt@121-72-128-43.dsl.telstraclear.net]  has joined #ubuntu-installer
[03:31] <evand> what was the source?
[03:33] <cjwatson> evand: tag/deal> fine by me
[03:37] <CIA-19> ubiquity: cjwatson * r2089 ubiquity/ (3 files in 2 dirs):
[03:37] <CIA-19> ubiquity: * Make sure that the bounds of the spin button in the partition edit
[03:37] <CIA-19> ubiquity:  dialog always include the current size of the partition, even if for
[03:37] <CIA-19> ubiquity:  some reason it is outside the minimum/maximum resize ranges reported by
[03:37] <CIA-19> ubiquity:  partman (part of #95619).
[03:37] <evand> ah
[03:38] <cjwatson> in fact, parted_server is reporting it properly, but then they get rounded by human_resize_range
=== avoine [n=avoine@69.70.0.36]  has joined #ubuntu-installer
[03:38] <cjwatson> so really ubiquity ought to be getting more accurate information from somewhere, but that's harder ...
[03:40] <CIA-19> ubiquity: cjwatson * r2090 ubiquity/debian/changelog: clarify changelog a bit
=== blackskad [n=blackska@d54C1A48C.access.telenet.be]  has joined #ubuntu-installer
[05:56] <evand> \o/ completely automated noninteractive install
[06:03] <cjwatson> ubiquity?
[06:04] <evand> ah yeah, whoops
[06:04] <evand> yes, ubiquity
[06:04] <cjwatson> nice!
[06:04] <cjwatson> well done
[06:05] <evand> I wouldn't say that until I've cleaned up the code a bit :)
[06:05] <cjwatson> I guess you still have some testing to do of individual component preseeding
[06:05] <evand> oh yeah
[06:05] <evand> running the gtk frontend with seen support is an interesting experience
=== avoine [n=avoine@69.70.0.36]  has joined #ubuntu-installer
[07:40] <saispo> win 4
=== ka1 [n=kaz@69.70.0.36]  has joined #ubuntu-installer
[08:06] <ka1> hello, are there a list of packages used after an installation with d-I ?
=== jetsaredim [n=jgreenwa@inet-nc01-o.oracle.com]  has joined #ubuntu-installer
=== blackskad [n=blackska@d54C1A48C.access.telenet.be]  has joined #ubuntu-installer
=== blackskad [n=blackska@d54C1A48C.access.telenet.be]  has joined #ubuntu-installer
=== avoine [n=avoine@69.70.0.36]  has joined #ubuntu-installer
[10:19] <cjwatson> ka1: some of it's done programmatically and varies depending on your hardware, so not quite exactly, but it's basically ubuntu-minimal + ubuntu-standard + ubuntu-desktop
[10:30] <ka1> ok thank but I would like to know what packages I need with d-I because I use d-I to restore my system with an archive  and I have removed base-installer and debootstrap and my problem is that I have the mirror of a debian install cdrom
[10:40] <btm_> ka1: you're aware that those ubuntu-* packages are meta packages that install most of the system, right? (dpkg -s ubuntu-standard)
[10:42] <ka1> ho you have not understand what I want say
[10:42] <ka1> do you speak french ?
[10:44] <cjwatson> the mirror of a Debian install CD will not help you to install Ubuntu
[10:51] <ka1> yes I know that but this chan is also development of d-I ?
[10:52] <evand> ka1: as it pertains to Ubuntu.  The official channel for d-i development is #debian-boot on oftc
[10:53] <ka1> ok thank you very much evand
=== ka1 [n=kaz@69.70.0.36]  has left #ubuntu-installer [] 
[11:01] <cjwatson> "d-I" is a capitalisation I've not seen before
[11:04] <evand> heh
=== avoine [n=avoine@69.70.0.36]  has left #ubuntu-installer []