/srv/irclogs.ubuntu.com/2008/10/08/#ubuntu-installer.txt

CarlFKalt installer too00:42
CarlFKit sees disks, but not the partitions00:42
CarlFKhttp://dpaste.com/83067/00:43
CarlFKthe cd errors might be relevant... let me reboot without that00:44
CarlFKhmm... partman found them: Guided - resize SCSI1 (0\,1\,0)\, partition #1 (sdb)00:46
CarlFKfdisk -l sees them now too.  guess something found them much later than I expected00:47
yannickmhi, anyone here that i could ask a few questions about the installer (tasksel in particular)01:11
CarlFKOct  8 00:14:39 grub-installer: You shouldn't call /sbin/grub-install. Please call /usr/sbin/grub-install instead!01:18
CarlFKdoes that apply to the installer?01:19
CarlFKOct  8 00:14:39 grub-installer: /dev/sdb1 does not have any corresponding BIOS drive.01:20
CarlFKthat's a problem.  off to lp I go...01:20
CarlFKhttps://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/262816 bug #26281601:27
CarlFK"grub-install failed: "/dev/sda1 does not have any corresponding BIOS drive"01:27
CarlFKcjwatson: I just got this too with alt - want logs? http://dev.personnelware.com/carl/a/dhcp91/01:28
Samahhello there, need help with ubuntu, anybody here?05:03
lukehasnonameHello, I had some trouble immediately after install. One is with the oem-config, and one with... something else. The full description of my problem is here: http://mibbit.com/pb/3ui0Ts06:57
evandlukehasnoname: please file a bug on Launchpad.  It's near-impossible to track bugs via IRC.07:04
persiaIn at least the case of the VBE issue, you may find the bug already filed, and some discussion.07:05
evandgood afternoon persia07:06
persiagood night evand07:06
persiaHmm.  Somehow that doesn't seem to be as much of a greeting when reread as when typed.07:06
evandheh07:06
evandodd that you cannot use night in a greeting though.07:07
persiaIt's the rampant hegemony of the diurnalists.07:08
StevenKIf mornings really exist, why are there only 12 hours on a clock?07:08
evandhaha07:09
persiaevand, while you're still up: I'm looking at allowing limitation of the requirement for passwords to not be blank.  The remaining spot seems to be a check in ubiquity to verify that username, password, verified_password, and hostname contain values.  Do you think it would be better to try to check the SEEN values for these, or change the logic to honor the preseeding hint I prepared for user-setup?07:16
* evand thinks07:18
* persia is around line 919 of gtk_ui.py if that helps07:18
evandI think we can remove that chunk of code07:20
persiaJust drop the check entirely, and rely on the interaction with user-setup?07:20
evandas user-setup/password-empty will be shown in ubiquity anyway, IIRC07:20
evandja07:20
* persia tries that07:20
evanddo let me know how that goes07:21
evandI suspect we should still leave it for username and hostname though.07:21
persiaIs that because there aren't such errors reported for those, or because double-checking is a good idea?  If the latter, I'd rather just split the check, and inspect the preseed value.07:23
evandbecause we save the user the trouble of clicking next and finding out that those values cannot ever be blank07:24
evandI'm not sure I understand what you mean by split the check07:24
persiaSomething like http://paste.ubuntu.com/55186/07:26
evandI don't think the latter half of that is necessary.  user-setup should take care of that for us.07:27
evandas it will ask an error question, which should show up next to the appropriate field and grey out the next button07:27
* evand pokes at the code to be sure07:27
persiaOh, the error question does show after clicking next, or if one tries to preseed blank in --automatic without telling user-setup that it's allowed.  I was thinking more about the avoidance of having the user click next and get the error.07:29
evanderr it doesn't grey the button, but loops back, meaning that you'll stay on the page until you fix the error07:29
evandpersonally I think it's best to leave that code in user-setup-ask, rather than duplicate it somewhat in ubiquity.07:30
persiaOK.  I like that, because it's easier for me :)  It's just a question of user experience of pressing Next and looping back.07:30
evandbut you're welcome to form a mob and overrule me :)07:30
evandindeed07:31
persiaJust removing the checks works for me for an --automatic install.  Once that completes, I'll try again interactively without allowing the password to be empty to verify.  Thanks for the guidance.07:36
evandanytime07:37
StevenKBit early isn't it, evand? :-)07:37
evandI'll call it late, as I do plan to go to bed at some point. :)07:37
persiaIs the distinction between "early" and "late" only in whether one has yet to sleep?  What about the poor folk at wedontsleep.org ?07:39
evandhahaha07:39
evandnoted07:39
CIA-52ubiquity: evand * r2875 ubiquity/ubiquity/frontend/noninteractive.py: Add missing initialization of self.auto_login in noninteractive.08:14
StevenKIs the evand the IRC nick, or just that the LP name and IRC nick are the same?08:15
CIA-52ubiquity: evand * r2876 ubiquity/ (configure configure.ac): Bump to 0.10.408:16
evandStevenK: latter08:17
evandwhoops, that should read 1.10.408:17
StevenKHaha. persia kept doing that.08:17
evandoh well, I got it right in the actual code.08:18
StevenKIt's contagious!08:18
evandhaha08:18
CIA-52ubiquity: evand * r2877 ubiquity/ (d-i/manifest debian/changelog):08:18
CIA-52ubiquity: Automatic update of included source packages: partman-ext308:18
CIA-52ubiquity: 52ubuntu3, partman-jfs 26ubuntu2, partman-reiserfs 41ubuntu3,08:18
CIA-52ubiquity: partman-xfs 41ubuntu2, user-setup 1.20ubuntu8.08:18
persiaevand, Please consider bug 280014 before you release.08:19
persiaevand, Also, you want to pull my partman-efi trunk, as 1.10.4 FTBFS on lpia with the current one.08:19
evandah, will do08:20
persiaOh, no partman-efi got merged.  It probably just needs an upload.08:20
evanduploading partman-efi now.08:22
persiaThank you.08:23
evandpersia: hrm, perhaps I'm just tired and screwing things up, but the debdiff of partman-efi 17ubuntu2 and partman-efi 18ubuntu1 doesn't show the changes you mention in the changelog.08:25
persiaWhat!08:26
* persia checks the branch08:26
persiaevand, Which change?  I intended to pull translations from Debian and to modify line 7 in commit.d/format_efi08:27
evandindeed, that's what it shows, but your changelog entry is as such:08:29
evand+partman-efi (18ubuntu1) intrepid; urgency=low08:29
evand+08:29
evand+  * Resynchronise with Debian. Remaining changes:08:29
evand+    - Automatically use existing EFI system partitions on Intel Macs as EFI08:29
evand+      boot partitions.08:29
evand+    - Create fat32 EFI partitions with the name "EFI System Partition" by08:29
evand+      default on Intel Macs.08:29
evand+    - choose_method/efi/do_option: Make sure no mountpoint is set.08:29
evand+    - Remove efi-modules dependency; it seems to be built into Ubuntu08:29
evand+      intrepid kernels now08:30
evand+08:30
evand+ -- Emmet Hikory <persia@ubuntu.com>  Tue, 07 Oct 2008 15:06:58 +090008:30
evandoh08:30
evandI'm just tired08:30
evandignore me08:30
evand:/08:30
persiaNo problems :)  You'd see those changes if you compared to 18 :)08:30
persiaBasically, I generated a lot of debdiffs, and then applied them in between commits to construct a bzr branch for the Ubuntu changes, which should be a sane basis for future updates using a bzr workflow.08:31
persiaI only started from 17, as I didn't think anyone was going to want to try to rebase from earlier versions.08:32
evandindeed08:33
evanduploaded08:36
persiaThank you.  I presume there's a wait for the buildd before it can be pulled into ubiquity?08:36
evandindeed08:38
persiaOh well.  Sorry about that.08:39
evandno worries08:40
persiaI'm fine with a push to address the auto-login issue for noninteractive, and the lpia FTBFS can be resolved on another day, if there's a reason things should happen that way.08:41
evandI should be able to get both in a build and new DVDs made before Dell can use them (US Central), I think08:43
persiaOK.  I just don't like to deprive anyone else of sleep just because I've not been pushy enough about uploads.08:43
evandoh no worries there, I had planned to be up anyway to tackle grub UUID issues, but KVM hates me so this is the best use of my time at the moment08:45
persiaAre you looking at something that would autodetect the installation medium, and not install grub there?08:45
evandthat's one of a few bugs that need to be fixed, yes.08:45
evandthat one is tricky as there's a request to not filter out disks entirely, but rather just partitions08:46
persiaOh cool.  I'd resigned to writing an installation note telling people to be careful about where they install grub when using KVM and USB images.08:46
evandhttps://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/276656 FWIW08:46
persiaSo if one has an installer on one partition of a disk, one can install to another partition of the same disk?  Interesting.08:47
evandwell, I'm not sure it will end that way08:47
evandI need input from cjwatson on it, as I believe it's not possible to have the installation medium on the same disk you're partitioning08:47
evandas then the kernel wont be able to re-read the partition table08:47
evandand if that's the case, my job is really easy as it's a simple matter of filtering out any disk with mounted partitions (the original patch specifically looked for /cdrom and /hd-media)08:48
persiaIt's at least tricky, but I can see the possible advantage for a "recovery partition" or the like.08:49
evandstill need to get update-grub writing UUIDs instead of root= though, and teach ubiquity/grub-installer to pick something a little more sane than (hd0) every time.08:49
persiaActually, that somewhat confused me : there's the opportunity to adjust with the Advanced... button at the end of the installation, but it doesn't seem to work when installing grub to ! hd008:50
persia(or maybe it's just the way I've used it)08:50
evandit works for me.  How did it fail for you?08:51
evandit should ensure you enter a sane value and give you a drop down of suggested sane values08:51
evandsomething like (hd[0-9]*,[0-9]) (slightly more complicated than that, iirc) or /dev/whatever08:52
persiaIt gave me a drop-down.  I just got a "grub couldn't install" error in the last stage.  As I know I've had this working with some changes to grub-installer itself, but which changes aren't preserved in my ubiquity branch, I suspect I got the error from incorrectly stacking versions of things.08:52
evandhrm, ok08:53
evanddo let me know if it persists08:53
lukehasnonamepersia: Under where will I file my report on oem-config and vbe_init?08:53
lukehasnonameWhat "project"?08:53
persialukehasnoname, For oem-config, I'd start from bugs.launchpad.net/ubuntu/+source/oem-config/+bugs  I'm not so sure for vbe_init08:54
persiaevand, Certainly.  It's not yet at the point where I consider it a bug.08:54
lukehasnonamemk, I'll do that tomorrow afternoon. It's 3am in Texas... I'm out. Thanks.08:55
cjwatsonFragadelic: copy directly from squashfs> evand's answer, plus we were very concerned about the support implications of installs not being pristine. No, we didn't actually try it the other way, but we had enough experience by then to be able to reason out the implications first09:27
cjwatsonTheMuso: I think the current behaviour has user-friendliness problems too - maybe we should detect the metadata and, if we find it, ask the user if they want to enable dmraid?09:28
cjwatsonCarlFK: the grub-install error is just noisy, it doesn't actually cause any problems09:29
cjwatsonevand,persia: I think I'd rather have ubiquity check passwd/allow-password-empty and continue to disable the next button if it's false09:30
cjwatsonif you don't know about the allow-password-empty change, it's a bit of a weird UI change, if my reasoning09:31
cjwatsonis my reasoning09:31
cjwatsonStevenK: in fact the CIA username is also independent; see bzr help cia09:32
cjwatsonevand: 276656> I'm happy for there to be some kind of "I know what I'm doing" override that Dell can set to have the installation medium on the disk being partitioned09:33
cjwatsonpersia: yeah, I suspect the reason that installing to non-first disk is broken is that grub fails to find its stage 1.5; all part of the same horrible ball of wax09:33
CIA-52debian-installer: cjwatson * r972 ubuntu/debian/changelog: releasing version 20080522ubuntu1809:39
=== nasrat_ is now known as nasrat
CIA-52ubiquity: cjwatson * r2878 ubiquity/ (debian/changelog scripts/install.py):11:58
CIA-52ubiquity: Check whether log files exist before copying them (thanks, Vitaly11:58
CIA-52ubiquity: Petrov; see LP #279003).11:58
CIA-52ubiquity: cjwatson * r2879 ubiquity/ (debian/changelog scripts/install.py):12:01
CIA-52ubiquity: Adjust live filesystem mounting for Debian (thanks, Vitaly Petrov; see12:01
CIA-52ubiquity: LP #279003).12:01
CIA-52ubiquity: cjwatson * r2880 ubiquity/ (debian/changelog scripts/install.py): Reconfigure splashy (thanks, Vitaly Petrov; see LP #279003).12:05
CIA-52user-setup: cjwatson * r120 ubuntu/debian/changelog: merge from lp:~persia/user-setup/ubuntu (changelog bug number only)12:36
=== davmor2 is now known as davmor2_away
evandcjwatson: noted, thanks14:36
persiacjwatson, OK.  I'll put together a UI check for that : probably be at least a few hours.14:45
=== davmor2_away is now known as davmor2
CarlFKcjwatson: you mean grub did get installed?  (box is still sitting with the installer error, haven't tried to boot it yet)15:08
Fragadelic-1cjwatson: did you take a look at my remastersys script?  http://pastebin.com/f78cff54b  - I don't think I'm doing anything to break popularity-contest or anything else really but I could be wrong and if I am I'd love to correct it.15:10
cjwatsonCarlFK: yes15:19
cjwatsonCarlFK: err, no, I mean that the /sbin/grub-install message did not change whether it was installed or not15:20
cjwatsonCarlFK: it's entirely possible that some later error broke it, it just wasn't the one you quoted15:20
cjwatsonFragadelic-1: no, sorry15:20
Fragadelic-1cjwatson: no problme - I know you are busy15:20
kirklandcjwatson: the daily server iso isn't detecting network or hard disks ... is this known?15:58
CarlFKkirkland: the installer, or the system that gets installed?15:59
kirklandCarlFK: installer16:00
cjwatsonkirkland: probably just kernel skew, fixed this morning16:00
cjwatsonkirkland: see if 'uname -a' matches the kernel udebs on the CDs16:00
kirklandcjwatson: uname says -4 ... looks like there's both a -4 and -5 kernel udeb16:01
cjwatsonyeah, it'll just be skew16:04
cjwatsonshould be sorted out tomorrow16:04
kirklandcjwatson: k, thanks.16:07
evandpersia: is it likely that you'll have time to update your ubiquity branch to relfect the suggestion cjwatson made in bug 28001416:15
evandI'd like to get an upload in soonish.16:15
evanderr, that you'll have time today*16:15
CarlFKcjwatson: sorry if I am missing something... installer syslog: Oct  8 00:14:39 grub-installer: error: Running 'grub-install  --no-floppy  "(hd0)"' failed.16:16
CarlFKshould I open a bug?16:16
persiaevand, I'm working on it now, but both tired and a little distracted.  If I don't finish in the next 3 hours, I'm happy to miss this next push.16:18
cjwatsonCarlFK: I'm in a meeting16:18
evandpersia: noted16:18
CarlFKk - I'll hold.16:19
cjwatsonCarlFK: ... and after that I'll be going out. Do whatever seems reasonable to you.16:20
TheMusocjwatson: A good idea, but we would have to ask the question for every array thats found, as a user may want one, but not another. We also would have to carry that through to the installed system. I think thats probably something for Jaunty.16:38
cjwatsonTheMuso: I'm really concerned that this is a regression on systems that used to work; I don't think we can defer it16:39
TheMusocjwatson: Ok, since disk-detect is what brings up the arrays, it needs to be done there. When I'm awake later today, i.e not for the meeting, I'll take a look at writing the debconf template for it. I'll also need help to figure out how to get such a setting for which arrays are wanted through to the installed system.16:41
TheMusocjwatson: This will need a UI freeze exception I'm assuming.16:41
cjwatsonfor intrepid we might be OK with just a global on/off switch16:42
cjwatsonthen it'd just be a matter of deciding whether to use dmraid or not, right?16:42
TheMusoYes, if the user says no, we don't activate.16:42
cjwatsonI think that would cover most of the affected users, and certainly 27928816:42
TheMusoSimple as that.16:42
cjwatsonerr, I mean "whether to install dmraid on the target system"16:42
cjwatsonthen you don't have to worry about any more complicated propagation16:42
TheMusoRight, but that toggle would also be askign if the user wants to use an array for the install.16:43
cjwatsonyes.16:43
TheMusoOk then that should be easy, by adding a new template to disk-detect.16:44
TheMusoWill look at it later today.16:44
cjwatsonjust "you seem to have dmraid stuff on your disks; do you want to use it?"16:44
TheMusoeah similar to what I was thinking.16:45
* ogra waves17:07
ograso i have some reports of users that end up with cdrom entries for a nnexistin /dev/sdb on their UMPC/MID after install ... do we use some kind of hardcoding there ? (that prevents usb keys that show up as sdb from being mounted)17:09
cjwatsonno, that just means it happened to be sdb during the install17:09
cjwatsonwe were just talking about this in the foundations meeting; it may be possible to strip that out at the end of USB installs17:09
cjwatsonor, if we're very lucky, to use /dev/disk/by-path/ or similar17:10
cjwatsonbut the real fix needs to be proper cdrom detection in apt, and is for jaunty17:10
ograudev should know if its really a cdrom, no ?17:10
ograso we should be able to look there17:10
cjwatsonapt's cdrom method needs to do it17:11
ograah, k17:11
cjwatsonright now, it doesn't, and the installer needs apt to work17:11
ograindeed17:11
cjwatson<cjwatson@sarantium ~>$ ls -l /dev/disk/by-path/17:11
cjwatsontotal 017:11
cjwatsonlrwxrwxrwx 1 root root 10 2008-10-08 09:59 pci-0000:00:1f.1-scsi-0:0:0:0 -> ../../scd017:11
cjwatson... would work on my system17:11
cjwatsonI think that's stable17:12
ograyeah17:12
ograwell, if thats addressed and known i wont bug further17:12
ograif you need testers, i have them in the community, wiling to help17:12
ogra*willing17:12
cjwatsonit's one of the oldest bugs in Ubuntu, actually :)17:12
cjwatsonyou're just running into it now ...17:12
ograwell, we didnt have USB installs before17:12
ograat least not in a sane manner :)17:13
cjwatsonthat's just one of the many possible scenarios17:14
persiaRemembering the issue with auto_login for noninteractive, if I want to use self.frontend.set_allow_password_empty, should this be defined in all frontends?18:13
evandincluding base.py, yes18:14
evandany time the components call a function in the frontend, that is18:14
persiaSo put it in base.py and each of the frontends?18:14
evandja18:14
persiaShould I be concerned that auto_login isn't defined in mythbuntu.py?18:16
persiaOr is that special in lots of ways.18:17
evandspecial.  It derives from the gtk_ui frontend.18:17
persiaOK.  That makes it easier.  Thanks.18:17
persiaRight.  Now to check if this works.18:25
persiaevand, Please don't wait for me on 280014 anymore.  I'm not going to get it quickly.  My first attempt was to set an attribute in components/usersetup.py based on a db_get of the preseed value, and then check that attribute, but I'm getting runtime errors, and will need to track them down (for which I'm probably too tired to be either quick or effective).  Maybe tomorrow, but that can wait for the 1.10.5 or so.18:47
evandok18:48
evandthanks for the heads up18:48
persiaNo problem.  Thanks for waiting for me to try to get it tonight.18:48
evandanyone else have changes they want to land before I upload ubiquity?18:51
evand(no need to respond with "no", I'll just wait a few minutes before kicking off the commits)18:52
persiaevand, Please do refresh the d-i components again, but that's it from me.18:52
evandwill do (it's part of the release process for ubiquity)18:55
persiaOK.  Sorry for the noise then :)18:56
evandno worries18:56
CIA-52ubiquity: evand * r2881 ubiquity/ (d-i/manifest debian/changelog): Automatic update of included source packages: partman-efi 18ubuntu1.19:01
CIA-52ubiquity: evand * r2882 ubiquity/debian/changelog: releasing version 1.10.419:06
evandyikes, i386 build took 47 minutes.19:53
persiaAnd amd64 41 minutes, and lpia 6 minutes.  Something seems wrong with this picture.19:59
evandhahaha20:01
persiaWell, if i386 took a long time, and everything else was quick, I'd blame arch: all stuff taking the extra time.  In this case, I can't explain it.  lpia is fast, but the buildd isn't actually lpia, and the discrepancy is just too big.20:03
pmatulis_t60pmatulis... http://groups.google.co.kr/group/linux.samba/browse_thread/thread/0f1526049ab53ac620:16
kirklandevand: hiya, are you around?23:06
kirklandcjwatson: hi, how much trouble would it be to spin off another set of intrepid server builds?23:11
kirklandcjwatson: the broken install iso is blocking some of my work, at the moment23:11
kirklandcjwatson: the daily builds have the kernel mismatch problem we discussed this morning, leading to network and hard disks not being detected23:12
cjwatsonyeah, I only just killed the stuck process on cdimage a few minutes ago, which is what was causing it23:12
kirklandcjwatson: i tried to fall back to the beta iso's, but those are failing looking for dmraid23:12
kirklandcjwatson: http://launchpadlibrarian.net/18298386/syslog23:12
kirklandcjwatson: i'm hoping thats been fixed in the daily iso's?23:13
cjwatsonI've kicked off Ubuntu server and alternate builds23:13
cjwatsonyes, that's fixed23:13
cjwatsonit was due to server-ship not depending on d-i-requirements in ubuntu.intrepid/STRUCTURE23:13
kirklandcjwatson: pfft, the nerve :-)23:16
cjwatson(d-i-requirements is the seed that contains random stuff that d-i might need depending on circumstances)23:17
kirklandcjwatson: k, thanks23:21

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!