[11:40] <sridhar> Hi, everybody
[11:44] <sridhar> Iam creating live-come-install for my own distro, so that iam using ubiquity in my CD, by using ubiquity, while creating new partition, iam getting the error like " No root file system is defined Please correct this from the partitioning menu" But i gave the / in the file system combo manually. How do i rectify that????  plz
[12:45] <sridhar> hi, while running that partman in shell, its showing "No root file system No root file system is defined Please correct this from partitioning menu" Plz tell me how to rectify that ??????
[12:46] <cjwatson> please (a) describe exactly what you are doing in the partitioner (b) put /var/log/syslog and /var/log/partman up for download somewhere
[12:47] <cjwatson> and please also use fewer question marks; six consecutive question marks are not necessary :)
[13:26] <sridhar> cjwatson: i posted my syslog and partman in "http://pastebin.ca/790510 ,http://pastebin.ca/790522"
[13:26] <sridhar> http://pastebin.ca/790522
[13:27] <cjwatson> #
[13:27] <cjwatson> Nov 20 16:00:52 live ubiquity: /lib/partman/definitions.sh: line 155: /lib/partman/choose_partition/>: No such file or directory
[13:27] <cjwatson> err
[13:28] <sridhar> cjwatson: but it is there in my system
[13:28] <cjwatson> #
[13:28] <cjwatson> /lib/partman/free_space/50new/do_option: IN: NEW_PARTITION =dev=sda ext2 142971816960-145069263359 Beginning
[13:29] <cjwatson> something is rather broken there
[13:29] <cjwatson> sridhar: I'm willing to bet that a file called "/lib/partman/choose_partition/>" (note the >) does not exist on your system
[13:30] <cjwatson> http://pastebin.ca/790522 is not a complete partman log
[13:31] <sridhar> yes, that site accepts only 15000 bytes, that why i put the final error
[13:31] <cjwatson> I cannot help without the full log
[13:31] <sridhar> can i send it to your mail?
[13:32] <cjwatson> it looks like something in the ubiquity<->partman interface has got out of step; it's inserted the disk name instead of the new partition type (primary/logical)
[13:32] <cjwatson> sridhar: no, but you can file a bug
[13:32] <cjwatson> (if you mail me personally, it will likely get lost in the huge volume of mail I get)
[13:34] <sridhar> it is installing without having any problem, if iam having a  ext3 filesystem. iam getting problem only, while creating a new partition
[13:35] <cjwatson> please file a bug and attach the files I requested
[13:35] <sridhar> ya, i will do
[17:16] <soren> If a d-i component (user-setup-apply in this case) does an exit 1, that will be very obvious in that installer, right?
[19:24] <cjwatson> soren: it'll show up in syslog, yes
[19:25] <cjwatson> and will result in a red-screen-of-death
[19:25] <cjwatson> (perhaps more visibly)
[19:25] <soren> I thought so.
[19:25] <cjwatson> let me guess what you're tracing
[19:25] <soren> :)
[19:26] <cjwatson> the user got created, so [ -n "$USER" ] must be true
[19:26] <cjwatson> so the only ways for this to happen are (a) cosmic rays (b) passwd/root-login is false
[19:27] <cjwatson> (or conceivably (c) bust sudo)
[19:27] <soren> It really doesn't add up.
[19:27] <cjwatson> but root-login defaults to true and is only asked at medium and this is where I got stuck
[19:28] <soren> The particularly odd thing is that not selecting the mail server task allegedly fixes it.
[19:28] <cjwatson> I think that's a red herring personally
[19:28] <soren> me too.
[19:28] <cjwatson> it wasn't at all clear that it wasn't simply "next time through the installer, it didn't happen"
[19:28] <soren> root-login defaults to false, though, doesn't it?
[19:28] <soren> cjwatson: Preceisly.
[19:28] <cjwatson> err, sorry, I transposed false and true above
[19:29] <cjwatson> I wonder if they were installing to an existing partition. The installer doesn't make that easy though
[19:29] <cjwatson> did the reviewer get back with syslog by any chance?
[19:29] <soren> cjwatson: No.
[19:29] <cjwatson> I think that might be the only way we'll trace this
[19:29] <soren> I found a new bug about this. Don't know if you noticed I assigned it to the installer-team a couple of hours ago.
[19:29] <cjwatson> but it needs somebody to contact us *before* they nuke the machine
[19:29] <cjwatson> I didn't
[19:30] <soren> It links to a different thread on the forums explaining the exact same problem, only slightly more details.
[19:30] <soren> https://bugs.edge.launchpad.net/ubuntu/+source/user-setup/+bug/162638
[19:30] <soren> ...sorry, I didn't reassign it to you, I reassigned it to user-setup, so you got subscribed.
[19:30] <cjwatson> now *that* guy said he repaired it in-place
[19:30] <cjwatson> I'll ask for details
[19:31] <soren> If he can log in in rescue mode...
[19:32] <soren> Er..
[19:32] <soren> I'm not sure how to finish that sentence :)
[19:32] <cjwatson> all he needs to have done is not trashed the install
[19:32] <soren> It drops you to a root shell if what?
[19:32] <soren> root has a disabled password?
[19:32] <cjwatson> what, rescue mode?
[19:32] <cjwatson> he means d-i's rescue mode
[19:33] <cjwatson> which ignores auth altogether
[19:33] <soren> Oh, I thought he meant recovery mode.
[19:33] <soren> I might(!) be making this up, but I seem to remember that someone said that that didn't work.
[19:33] <cjwatson> that drops you to a shell if root's password is disabled, yes
[19:33] <cjwatson> which it probably is here
[19:34] <soren> In which case a proper root account must have been created.
[19:35] <soren> I can't find any reference to that sort of thing, so I seem to have made that up. forget it. :)
[19:37] <cjwatson> I've posted a plea for help to the forums too
[19:37] <soren> Yes, I've seen it.
[19:38]  * cjwatson wgets the server CD
[19:38] <soren> I've tried to reproduce it 5-6 times, Rick and Nick have probably tried 20 times each. No luck.
[19:44] <cjwatson> the forums thread mentions postfix too ...
[19:44] <soren> Which one?
[19:45] <soren> Oh... So it does.
[19:45] <cjwatson> the one referred to in that bug
[19:45] <cjwatson> http://ubuntuforums.org/showthread.php?p=3807132
[19:46] <cjwatson> it's not that it's impossible for the mail-server task to break this
[19:46] <soren> cjwatson: well, that might just be because he chose to not configure postfix during installation. The failed sudo attempt will try to send an e-mail about it, but if postfix isn't configured at all, I suppose that's the error you'll see.
[19:46] <cjwatson> it's just that it'd be perverse
[19:46] <soren> Quite.
[19:47] <cjwatson> "NoodleSmythe" says 'When installing the mail server components, I can't "sudo". If I do an install just without the mail components, sudo works a treat.'
[19:47] <soren> As you said, it might just be a case of "next time through the installer, it didn't happen"
[19:47]  * soren is starving
[19:47] <soren> bbl. I need food.
[19:47] <cjwatson> yeah, I just stop believing that when lots of people say it
[19:48] <soren> ..and I made the mistake of introducing my wife to facebook, so she's.. Um.. busy.
[19:48] <soren> cjwatson: I thought of that, too, but the scenario might be: "Oh, it broke. I'll look on Google. Oh, this guys says to not install the mail stuff." and then everything works.
[19:48] <cjwatson> mm
[19:50]  * soren wanders off to the kitchen
[19:51] <cjwatson> also bug 158952
[19:51] <cjwatson> which has recent activity - I've asked for the logs there too
[19:52] <cjwatson> (googled for "ubuntu 7.10 server sudo syslog" and found that)
[20:29] <soren> Uh, interesting!
[20:32] <cjwatson> ?
[20:33] <soren> That bug report.
[20:33] <soren> It's got actual information in it.
[20:42] <cjwatson> ah, yes. though I don't think it's helpful as it happens
[20:43] <soren> Oh?
[20:43] <cjwatson> which bit do you think helps?
[20:44] <evand> yikes
[20:44] <soren> Well, he says it's 100% reproducable and shows a bit of syslog that suggests that the installer doesn't bail out at some point.
[20:44] <cjwatson> true
[20:44] <soren> ..and he was online 7 hours ago, so there's a good chance we can get a hold of him.
[20:45] <cjwatson> indeed
[20:49] <soren> user-setup is run after the tasksel bits, I presume?
[20:50] <soren> user-setup-apply, that is.
[20:56] <evand> yes, iirc
[20:56] <soren> Oh... Hang on.
[20:58] <soren> is it possible that one of the maintainer scripts for one of the packages in the mail server task manages to set a USER environment variable and that makes its way into user-setup-apply?
[20:58] <evand> to elaborate, my understanding is that finish-install comes after pkgsel
[20:58] <soren> No..
[20:58] <soren> evand: And finish-install calls user-setup-apply?
[20:58] <evand> no?
[20:58] <evand> finish-install calls everything in finish-install.d
[20:58] <soren> no to my crack-pot hypothesis.
[20:59] <evand> which user-setup-apply gets called from
[20:59] <evand> so yes
[20:59] <soren> Alright.
[20:59] <evand> cjwatson: can you confirm I'm not filling soren's head with lies
[21:00] <soren> evand: You seem to be correct.
[21:00] <evand> I'm 99% certain
[21:05] <soren> sudo is in ubuntu-minimal, so it'd get installed even if not from user-setup-apply.
[21:06] <cjwatson> that's correct, and environment variables can't propagate from underneath tasksel to user-setup-apply
[21:06] <cjwatson> main-menu
[21:06] <cjwatson>  \-- base-installer --- (...) --- sudo.postinst
[21:06] <cjwatson> \-- pkgsel --- tasksel
[21:06] <cjwatson> \-- user-setup --- user-setup-apply
[21:07] <cjwatson> err, except that's finish-install --- user-setup-apply, sorry
[21:07] <evand> heh, I was just going to say
[21:07] <soren> Yeah,but still separate processes, clearly.
[21:07] <cjwatson> evand: you are correct
[21:07] <cjwatson> soren: right
[21:07] <evand> thanks
[21:40]  * soren chuckles
[21:41] <soren> Have we ever gotten any bug reports about people wondering why their full name got mangled to either Frans Pop or Martin Michlmayr?
[21:44] <evand> haha
[23:18] <cjwatson> aha!
[23:18] <cjwatson> Nov 20 20:23:43 user-setup: newaliases: fatal: open /etc/postfix/main.cf: No such file or directory
[23:18] <cjwatson> Nov 20 20:23:43 finish-install: warning: /usr/lib/finish-install.d/06user-setup returned error code 75
[23:19] <cjwatson> evand: do you have a user-setup merge in progress already?
[23:39] <cjwatson> evand: can't find one on LP, so I'll just do it now
[23:43] <soren> cjwatson: Ah, so if the user chooses to not configure postfix..
[23:44] <soren> cjwatson: and user-setup checks if newaliases exists and is executable..
[23:44] <cjwatson> right
[23:44] <soren> Of course.
[23:44] <soren> How could I have missed that?
[23:44] <cjwatson> I missed it too
[23:44] <cjwatson> fix in progress
[23:44] <soren> \o/
[23:46] <soren> ...doesn't the installer give any feedback about it failing miserably?
[23:47] <cjwatson> I have just realised that of course finish-install.d scripts don't do that
[23:48] <cjwatson> it can be difficult for some of them because it might be after the point of no return
[23:49] <soren> I see.
[23:49] <soren> So if installing sudo at around line 166 fails, and sudoers doesn't get created at all, that won't give any feedback either?
[23:49] <cjwatson> I think it might be a good idea to change that but it's an API change and I'd like to think about it
[23:49] <soren> ..that was my originial hypothesis.
[23:50] <cjwatson> right, but as you observed that's impossible since it's part of ubuntu-minimal
[23:50] <cjwatson> (in our case)
[23:50] <soren> True.
[23:51] <cjwatson> I've made a note to follow up at some point
[23:52] <soren> Hmm... Well, I suppose we can conclude that most of the stuff called in finish-install is quite solid since we've never encountered this before :)