#ubuntu-installer 2007-08-01 <xivulon> superm1: yes but others helped to, I am ago on the forum <superm1> xivulon, well then perhaps i should speak to you after mythbuntu's first release regarding getting us in it <xivulon> superm1, at the moment what is required is a metalink file pointing to an alternate ISO <xivulon> you can reuse one of the metalink files we provide <superm1> xivulon, well we're not going to have an alternate iso unfortunately <superm1> at least not this release <xivulon> or use a metalink editor <xivulon> superm1 then you'll have to wait for cjwatson and evand to allow preseeding in ubiquity so that the livecd can be used, possibly should be done by 7.10 <superm1> right <evand> oh, it will be :) <superm1> well we have a variety of other options that would need to be preseeded as well <superm1> so i think wubi would need a few more pages for those options <xivulon> ps I sent a reply to cjwatson on the ml, I am interested in comments on the second part of the email <xivulon> superm1, the idea of wubi is to have a 1 click installer. and by 1 click I mean 1 click, not 2 or 3 <evand> ahhhhh, that explains the latter two changes <xivulon> evand yep <superm1> xivulon, i see. well the problem is that we account for options in hardware selection <superm1> during install <superm1> such as a remote and tuners <xivulon> sorry at the time I looked for malone in m-a, then I forgot to notify you <xivulon> superm1: what about having a reasonable config and have the rest at first boot? <evand> great! I'll fix that bug and apply the changes for dealing with already mounted filesystems, provided I can make the use case of previous partitions of a separate /home and / that are already mounted still work <superm1> xivulon, that's a possibility. one of our specs allows for it at least via our control centre <xivulon> evand thx <superm1> i'll get back to you after its implemented <superm1> and we can talk a little more about this <xivulon> superm1: quick OT question, why does not mythtv use mysql (at least some versions ago')? <xivulon> I mean sqlite <xivulon> I have always thought that lots of complications where due to the use of mysql as opposed to sqlite <superm1> xivulon, developers choice to originally use mysql, and there has been no effort towards sqlite at this point <xivulon> I think they should use sqlite ;P <superm1> a lot of the original complications on the ubuntu packages were mysql related, but i've massaged the packaging as much as i could to prevent users from messing things up with it <superm1> i agree though, i think there should be multiple options: sqllite, postgres, mysql, etc <superm1> just a matter of the effort involved to do so <xivulon> To be honest I think they should just use sqlite, there is little point in choosing a db in a media server, and most other dbs are probably an overkill. <xivulon> considering the tickets they had to answer because of mysql it is probably a worthy investment <superm1> does sqlite scale well to many machines, or only to a local app? <xivulon> used to be only local app, not sure if they managed to improve the locking system. But do you really need multiple backend servers? <superm1> well i use 2 <superm1> and i have remote frontends <superm1> i'm not sure how common that is though <xivulon> Yep but all the data could be in one backend anyway, even singlethreaded <xivulon> anyway that's ot <superm1> ya <xivulon> evand do you know if anyone plans to come on board and help with the wubi front-end? <superm1> i'd say bring it up in #mythtv, but i know what the result will be. "You want a feature, submit a patch, or put it on the wiki page, and maybe someone will do it" <xivulon> superm1: I wish I could help, but I have not much time for that, the little I have I am using on wubi <superm1> :) <evand> xivulon: I'm tempted to, provided I can find some free time. What needs to be done, exactly? <xivulon> improve the download manager, we need segmented downloads <xivulon> improve keyboard detection <superm1> xivulon, currently does it use bittorrent to do it? Or just http? <xivulon> http, but with a few features <xivulon> we used to have bittorrent, but it was clunky <xivulon> it required python and a few users had issues with it <cjwatson> as far as our use of wubi is concerned, I was imagining that we'd just ship it on the CD, which would mean that wouldn't be so much of an issue <xivulon> hi cjwatson <cjwatson> hi, going to bed soon so nothing complicated please :) <xivulon> np long day here, my brain is melting (more than usual) <xivulon> I sent you a reply, you already answered a bit <TheBigClash> hello <TheBigClash> i have a problem with installing ubuntu <TheBigClash> can anybody help me? <CIA-19> migration-assistant: evand * r56 migration-assistant/ (9 files in 2 dirs): <CIA-19> migration-assistant: * Close directories in ma-search-users. <CIA-19> migration-assistant: * Don't unmount devices when we can avoid having to. <CIA-19> migration-assistant: * Look for registry files case-insensitively. <CIA-19> migration-assistant: evand * r57 migration-assistant/ (import.c ma-ask search-items.c utils.c utils.h): Minor fixes in previous case-insensitive registry locations commit. Also make use of it in search items.c <glledo> cjwatson evand : I've been trying to get partman-crypto working with ubiquity, I've created a LP branch, if you want to take a look: https://code.launchpad.net/~glledo/ubiquity/ubiquity.crypto <cjwatson> glledo: I'd like to look, but http://geeksynapse.net/repo/ubiquity.crypto/ returns HTTP 404 so LP can't mirror the branch <dns_56> i have a bug with software raid and the ubuntu installer, i have fedora installed correctly and it has software raid 5 but ubuntu does not detect it <cjwatson> please file a bug, I think it's going to be too hard to diagnose on IRC <cjwatson> make sure to attach the /var/log/syslog and /var/log/partman files; you can go back to the installer main menu and use "save debug logs" to extract those <cjwatson> partman-md would be an appropriate package to file the bug on <cjwatson> I'm assuming you're using the alternate install CD and not the desktop CD <dns_56> tried both, the bug is in feisty as well but not in fedora <cjwatson> the desktop CD does not support RAID, so please don't bother trying that <cjwatson> I would welcome a report from the gutsy alternate install CD with the appropriate logs <dns_56> i do not know a huge ammount about raid, what info is going to be useful? <cjwatson> 11:25 <cjwatson> make sure to attach the /var/log/syslog and /var/log/partman files; you can go back to the installer main menu and use "save debug logs" to extract those <cjwatson> that information <dns_56> ok i will do that in a few minutes <glledo> cjwatson: I've changed the webserver to index, at least I can see the code now with the Browse Code LP thing <cr3> cjwatson: hi, would you have a minute to help diagnose an installation problem I'm encountering with a custom image generated by fabbione? <cjwatson> cr3: sure <cr3> cjwatson: if I get "No volume groups found", that means the hard drive is not detected right? <cjwatson> no, that means no LVM volume groups were found. Ignore it if you weren't expecting to have LVM; the log message is just a consequence of one of the commands run in the process of starting up partman <cjwatson> d-i is unfortunately noisier in the logs than it should be sometimes <cr3> cjwatson: hm, the installation is stopping with a blue screen (the usual blue background) and I'm trying to isolate the problem. I'll have a second look at syslog <cr3> cjwatson: the installation stops shortly after detecting hardware and the highest pid on the machine is running /lib/partman/automatically_partition/10resize <cjwatson> cr3: would like a copy of /var/log/partman then <cjwatson> it may have made an invalid parted_server request and got stuck <cjwatson> that can happen if e.g. one of the arguments is empty by accident <cjwatson> parted_server's protocol handling isn't too clever :( <glledo> cjwatson: I changed the branch so now it's hosted in LP: https://code.launchpad.net/~glledo/ubiquity/ubiquity-crypto <cjwatson> thanks, will try <cr3> cjwatson: I finally got networking up on the machine to grab partman but httpd is not there. where can I find that shell script to invoke nc with the proper arguments? <cjwatson> cr3: probably easier to just 'anna-install openssh-client-udeb' and scp it out <cr3> cjwatson: that outputs a bunch of blanks and returns 0, which might indicate the command completed successfully, but there's no ssh nor scp command <cjwatson> please check again, there really should be <cjwatson> unless you ran it very early on, before the "retrieving additional components" step of the installer (which is also before partman!) <cr3> cjwatson: yep, I didn't see that step go by <cr3> cjwatson: $bestpart is set to none in /lib/partman/automatically_partition/10resize_use_free/choices <cjwatson> yes ...? <cjwatson> 'nc -l -p RANDOMPORT >partman' should be enough on the server side <cr3> cjwatson: I still can't get /var/log/partman from the system, so I've been trying to diagnose the problem myself. the last line in the log file is: /lib/partman/automatically_partition/10resize_use_free/choices: IN: PARTITIONS parted_server: Read command: PARTITIONS <cjwatson> 'nc SERVERHOSTNAME SAMERANDOMPORT </var/log/partman' on the client side <cjwatson> also same with /var/log/syslog in case parted_server fell over and whined there <cr3> cjwatson: so, I looked at the script and tried running it manually. I get a bunch of blanks so I ran the script again with set -o xtrace. <cjwatson> check whether the parted_server process is still running <cjwatson> no no no no don't run it manually you'll break stuff <cjwatson> if you did that, please reboot and reproduce it cleanly <cr3> yes, the parted_server is still running <cr3> cjwatson: emailed both syslog and partman logfiles <cr3> I also sent the dmesg and lsmod output, in case it might be useful <cjwatson> thanks, but dmesg is included in syslog and lsmod usually isn't needed <cr3> cjwatson: I suspect that the problem is that no storage device is being detected, ie ls /dev/sd* /dev/hd* doesn't show anything <cjwatson> cr3: just how custom is this installer? <cr3> cjwatson: the installation process installs a base.sqfs, chroot-initrd and chroot-vmlinuz instead of installing a bunch of packages <cjwatson> cr3: sounds rather like: <cjwatson> partman-auto (54ubuntu2) edgy; urgency=low <cjwatson> * Fix hang on partman startup if no disks are present. <cjwatson> -- Colin Watson <douglassanchez@example.org> Tue, 18 Jul 2006 15:25:30 +0100 <cr3> cjwatson: ok, so now I need to figure out how to detect the disk considering the feisty live image detects it properly <cjwatson> yes, definitely <cjwatson> the PARTITIONS command is supposed to be followed by the id of the disk; parted_server is stuck waiting for that to arrive <cjwatson> r194 of bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/partman-auto/ubuntu/ fixes this <cjwatson> cr3: right, that would be a kernel question ... <cr3> cjwatson: I suspect the vmlinuz and initrd used for my installation is not up-to-date. so, I'm trying to make -d build_netboot from the debian-installer root <cjwatson> sourced from which release? <cr3> I should source it from gutsy because my target image is for gutsy <cjwatson> err, but the kernel is 2.6.15? <cjwatson> according to your log <cjwatson> I updated d-i for gutsy yesterday or so, so it should be bang up-to-date <cr3> cjwatson: that's just for the installer, but the system being installed is gutsy <cjwatson> blink, I wouldn't guarantee that gutsy d-i will work with the 2.6.15 kernel <cr3> cjwatson: I successfully did make -d build_netboot, so I'll try the generated initrd.gz and vmlinuz <cr3> cjwatson: where should the initrd.gz reside after running make build_monolithic in debian-installer? <cjwatson> cr3: dest/monolithic/initrd.gz I think <cr3> it seems to be generated under netboot directories so I'm wondering if that's normal or if that's a result of my previous runs of make_netboot <cr3> darn, no monolithic subdirectory under dest <cjwatson> the latter <cjwatson> then it probably failed <cr3> that's probably because of the pkg-lists I specified for monolithic, lets try removing that <cr3> hm, the dest directory isn't even created after running: apt-get source debian-installer; cd debian-installer-20070308ubuntu9/build; make build_monolithic <cr3> I wish make -d provide more readable output <cjwatson> why would you use make -d here? <cr3> because nothing is happening, so I'd like to enable debugging to understand why <cjwatson> it's only useful for relatively unusual makefile debugging. The regular output of the makefile is probably much more helpful if not obscured by insane amounts of -d <cjwatson> oh, you need to uncomment monolithic in build/config/i386.cfg or whatever it is <cjwatson> monolithic is only for installer developers (modulo fabbione being crazy and thinking it's a good idea to ship it) so it's not turned on by default <cr3> cjwatson: cheers! the problem was that I wasn't getting any output at all <cr3> cjwatson: ok, I'm getting close. I'm now getting: finish-install: Depends: installed-base but it is not installable <cr3> cjwatson: apt-cache search is not returning anything for finish-install, so where is that package coming from? * cr3 steps out for lunch <cjwatson> cr3: apt-cache search doesn't return anything for any udeb <cjwatson> cr3: that's due to the base-installer in gutsy being too old, anyway; I'll look at fixing that <phracker> help <phracker> hehhe <cjwatson> phracker: please ask your question rather than asking for general help <phracker> ok <phracker> here is my issue <phracker> when I attempt to dpkg -i webmin I get errors <phracker> jkennebe@Nix1:~$ sudo dpkg -i webmin_1.350_all.deb <evand> phracker: This is not a support channel. Please see #ubuntu. <cjwatson> this channel is just for matters relating to initial installation of Ubuntu; general package installation help is more appropriate for #ubuntu <phracker> well I just figured that you maybe have more information <phracker> I will try that chan thanks <cjwatson> no slight to individuals intended; while it's possible that we know the answer, I'd rather that this channel didn't turn into #ubuntu as then we won't be able to get anything done :-) <cjwatson> (I'm happy to do small bits of installer support as that often results in interesting bug-fixes) <evand> Is there anything special about Vietnamese as a locale? This bug doesn't occur when using any other language. <cjwatson> oh, have you reproduced it? <evand> oh yeah, it's simple <evand> just install with vietnamese :) <evand> you'll hit it every time <cjwatson> well, it's UTF-8 without having .UTF-8 on the end of its locale name, but it's not unique in that <cjwatson> (unusual, but not unique) <evand> I'm surprised we didn't hear about this sooner. <cjwatson> its legacy character encoding (TCVN5712-1) isn't used by anything else; perhaps it's ended up in the legacy encoding by accident? <evand> hrmm <cjwatson> that would be vi_VN.TCVN rather than vi_VN <phracker> how do you disable sudo <cjwatson> cf. also localechooser 0.27ubuntu17 <cjwatson> phracker: at install time? use expert mode and opt to create a root user <cjwatson> phracker: at any other time, just set a password for the root user <evand> cjwatson: indeed, thanks for reminding me. That was on the list of things to try in my head but had since slipped my mind. <evand> cjwatson: wait, why localechooser from dapper and not edgy? <cjwatson> evand: the changelog for that revision, I mean <evand> ahhh <cjwatson> interesting Vietnamese-related bug <phracker> thanks cjwatson <cr3> cjwatson: is there a workaround to the base-installer in gutsy being too old? <cjwatson> cr3: the workaround is the version of base-installer I'm about to upload ... <cjwatson> I'm surprised that actually broke anything though, as I'm not getting swarms of complaints about it being broken <cr3> cjwatson: I'm only getting that for monolithic though, netboot works fine. so maybe you didn't get any complaints because fabbione is on vacation :) <cjwatson> ah, could be that monolithic objects, yes <cjwatson> its dependency resolution is less permissive because it uses apt-get rather than anna to do the job <cjwatson> cr3: uploaded; try again in a few hours <evand> cjwatson: you're quite good at finding the cause of bugs without even looking at them: <evand> /target/etc/environment: LANG="vi_VN.TCVN" <cjwatson> ha! <cjwatson> just practice, you develop intuition after a while. you OK with tracking down the fix from there? <evand> indeed, thanks for the kick in the right direction <cjwatson> no worries <phracker> I have come to the conclusion that I am a moron <phracker> why didnt I know about aptitude <phracker> ugh <phracker> that made things alot easier <phracker> =| <phracker> and I dont have to get rid of sudo <phracker> do you guys know if there is a "tightvnc" application that I could use <phracker> oh nevermind <phracker> duh I am using ssh * phracker sits back to think for a change <cr3> when trying to build monolithic on feisty, I get: E: Couldn't find package acpi-modules-2.6.20-16-generic-di <cr3> I found that the pool was containing 2.6.20-15, so I downloaded that to the localudebs directory. however, now I'm getting errors about ext2-modules package <cr3> evand: would you happen to know where the packages for ext2-modules, ext3-modules, jfs-modules, etc. are located? <evand> cr3: http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.22/ ? <cr3> evand: partman-basicfilesystems seems to depend on ext2-modules, but it's nowwhere to be found even in that url <cr3> evand: that's weird, the linux-source-2.6.15 repository contains the ext2-modules but the later repositories don't <cr3> evand: I wonder if the module has been superceeded by something else and it's just the partman dependencies which haven't been updated <evand> hrm <evand> fs-core-modules <cr3> evand: do you think I could modify partman-basicfilesystems to depend on that instead of ext2-modules? <cr3> evand: I also changed pkg-list/standard-udebs to only require partman-basicfilesystems amongst the partman-* packages. seems to be running now, but this is feeling freaky hacky <cr3> Segmentation fault (core dumped) <cr3> Command failed with status 139 : mklibs-readelf --print-rpath ./tmp/monolithic/tree/bin/ld_static <cr3> that was on gutsy, trying on feisty now <evand> I may be wrong about the fs-core-modules thing, but I somewhat recall a changelog entry a while back about some sort of shuffle involving the base filesystems. Or it could be a false memory. <cr3> feisty seems to have generated something, now to see if it works #ubuntu-installer 2007-08-02 <tepsipakki> cjwatson, evand: I noticed that if universe/multiverse are enabled, the generated sources.list does not contain an -updates entry for them <tepsipakki> I'll make a patch for apt-setup to fix that <cjwatson> tepsipakki: I noticed the discussion in #ubuntu-devel and already fixed it in my tree <cjwatson> tepsipakki: did you file a bug? <tepsipakki> cjwatson: heh, no :) <tepsipakki> thanks <cjwatson> ok, sorry, beat you to it then ;) <cjwatson> (will leave it to you next time) <tepsipakki> haha <tepsipakki> the result is what matters ;) <glledo> uops, I've got ubiquity to install with partman-crypto, but obviously doesn't boot :P <cjwatson> if it needs to install tools not in the live filesystem then you need to make sure they're at least in the apt archive on the CD <glledo> Im checking that now <glledo> I think dmsetup is removed at the end of the installation, for instance <cjwatson> quite possible unless something apt-installs it <cjwatson> (apt-install is a d-i command to have packages installed in the target system; in ubiquity, there's a shim to have it arrange to keep packages from the live filesystem installed even if they aren't in desktop, or install them if they weren't in the live filesystem) <glledo> anyway, ill try now to chroot to the system, install the needed stuff and see if it can boot <glledo> ok, thanks for the info <tepsipakki> hmm, gutsy install fails with gnupg-doc claiming "can't read doc-base file 'gnu-privacy-handbook'" <cjwatson> silly gnupg-doc. <tepsipakki> so there's a bug in gnupg-doc postinst? <tepsipakki> or in doc-base <cjwatson> sounds like it, but haven't looked <tepsipakki> yep, debian bug 425351 <tepsipakki> seems like the files should generally have full paths now <tepsipakki> mind if I upload a new version? <tepsipakki> doesn't seem like it's going to be fixed in debian anytime soon :) <tepsipakki> uploaded <cr3> when making build_monolithic in the gutsy debian installer, I get a bunch of missing *-modules packages <cjwatson> if you're building against any set of kernel images other than gutsy, that's expected <cjwatson> the kernel udebs get rearranged every so often and I can only track whatever's current <cr3> cjwatson: I'm building against 2.6.22-9-generic <cr3> cjwatson: I suspect this is the directory where the packages should be retrieved from and *-modules aren't there: http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.22/ <cr3> cjwatson: evand mentionned that the *-modules might've been replaced by fs-core-modules <cr3> however, the partman-basicfilesystems package depends on ext2-modules which can't seem to be found anywhere <cjwatson> Provides <cjwatson> though you're right, it's not provided by anything right now, that's a bug <cjwatson> I'll send a patch for the next kernel release <cr3> cheers, I'll be using feisty in the meanwhile which has the same problem but which I hopefully fixed by creating my own partman-basicfilesystems udeb which depends on fs-core-modules <cjwatson> should be fine <cjwatson> rescue-mode too if monolithic uses that <cjwatson> (this is just one of the many reasons I recommend against monolithic though <cjwatson> ) <cr3> you'll now have to modulo fabbione and me on monolithic :) <cjwatson> anyway https://lists.ubuntu.com/archives/kernel-team/2007-August/001617.html should fix it when it gets applied <cjwatson> but only for filesystem modules; if there's anything else that's breaking then maybe d-i needs to be fixed <cr3> that's weird, I just modified the preseed file of the installer and now I'm getting 'cdrom-detect' failed. maybe a faulty burn <cr3> yep, faulty burn. hate it when that happens :( <cr3> I'm getting "No root file system is defined" for feisty even though I have this line in my preseed: d-i partman-auto/choose_recipe select All files in one partition (recommended for new users) <cr3> might a potential reason be that I don't have the right modules to format the partition since I removed partman-ext* packages to install fs-core-modules instead? <cr3> hm, I removed preseeding of the partitioning and manually selecting "All files in one partition" worked. something seems to be wrong with the preseed on feisty <evand> argh <evand> Disabiling m-a for the time being when using --automatic wont work as m-a mucks with FilteredCommand.cleanup() and that doesn't work with the graceful page skipping code. <evand> I'll start working on fixing m-a in a bit. I want to finish that Vietnamese bug first. <cr3> evand: do you happen to run debian-installer against gutsy repositories sometimes? <evand> cr3: what do you mean? I use the Gutsy alternate CD images often. <evand> which is d-i <cr3> evand: heh, nevermind, I'm confused in my own little world :) <evand> haha <cr3> turns out I was encountering problems building the install initrd.gz and vmlinuz because of the corruption in the gutsy repository <cr3> but the problem was that my apt-cacher was corrupted <cr3> I suspect the problem might be that the operations of apt-cacher aren't atomic so interrupting the process corrupts the cache <cr3> instead of wgeting directly to the cache, it might be safer to wget in a temporary directory and the mv to the cache <evand> hrm <cr3> I should contribute to the project just to get back into perl after a few years of deprivity <cr3> developing against gutsy is a pain :( <evand> nah, you just have to dogfood it. <cr3> fucking hell, the repository is consistently broken <cr3> ... and I don't have the bandwidth to make my own non-broken repository. this is insane, I'll have to work over the weekend <evand> yikes <cr3> W: http://669-615-7011/apt-cacher?/ubuntu-archive/dists/gutsy/main/binary-i386/Packages.gz was corrupt <cr3> and, a few minutes ago, the problem was with universe. so if it's not one archive, it's another. I'm reverting to feisty in the hope I'll get some work done <cr3> and in the hope the intel xorg driver and mesa library backports are sufficiently stable * cr3 apologizes for this venting <evand> no worries, it's amusing :) <cr3> evand: heh, makes me feel better there's a positive side to it :) thanks <cr3> evand: I'm actually running the build process for gutsy in parallel and I'm being amused myself at the different parts of the repository that spontaneously fail :) <evand> heh #ubuntu-installer 2007-08-03 * Starting logfile irclogs/ubuntu-installer.log <tepsipakki> cjwatson: I've hit some strange problem trying to install gutsy here. We start a sshd locally in the chroot with a temporary key, and then connect to it remotely to perform various things, but remote connections now fail. Downgrading the ssh-server in the chroot doesn't help either <tepsipakki> the client receives error 255 when trying to run some command remotely <cjwatson> tepsipakki: -vvv on the client and -ddd on the server are the places to start; also check /var/log/auth.log <cjwatson> (assuming you have a syslogd running in the chroot) <cjwatson> or bind-mount in /dev/log or something <tepsipakki> ok, when trying to open an interactive session, the server fails to open a pty ("openpty returhns device for which ttyname fails.") <tepsipakki> and when running commands remotely, I see write/read failures on channel 0 <tepsipakki> lunch, bbl -> <cjwatson> is /dev/pts mounted? <tepsipakki> umm, no :) <tepsipakki> ok.. bind-mounting /proc and /dev/pts made it all work <tepsipakki> remote commands and all <tepsipakki> now to figure out why this wasn't needed before :) <tepsipakki> umm, /proc was enough <tepsipakki> maybe some component used to bind-mount proc for me <shrug> <cr3> have you guys ever encountered this error when installing feisty: No common CD-ROM drive was detected <cjwatson> it means pretty much what it says on the tin. generally a kernel problem <cr3> darn, I was hoping something easier to fix <cr3> gutsy doesn't exhibit the same error, cool <cr3> when making build_monolithic on gutsy, I get a segmentation fault: Command failed with status 139 : mklibs-readelf --print-rpath ./tmp/monolithic/tree/bin/ld_static <cr3> oh wait, I'll upgrade and maybe mklibs-readelf will start working again <cr3> hm, still segfaulting at the same place <cjwatson> must kill mklibs <cr3> cjwatson: what do you mean by kill mklibs? remove it from the build process? <cjwatson> no, I mean "I must inflict pain upon mklibs" <cjwatson> it wasn't advice :P <evand> it was a call to arms * cr3 double donkey punches mklibs <cjwatson> eww <cjwatson> I rue the day I found out what that means #ubuntu-installer 2007-08-05 <CryptoMole> hi all <CryptoMole> i run feisty fawn currently <CryptoMole> and i was thinking about trying gusty tribes2 <CryptoMole> does anyone know what i might run into for problems? <cjwatson> firstly, the current release is Tribe 3, so use that instead (and it's "gutsy" :-)) <cjwatson> do you mean problems with the installer? <CryptoMole> yes and also after install <cjwatson> we only deal with the former here <CryptoMole> its on my thinkpad <cjwatson> AFAIK it's currently in pretty good shape <cjwatson> but really, you should upgrade rather than doing a fresh install <CryptoMole> aw <cjwatson> for after install, #ubuntu+1 is a better place <CryptoMole> thanks <CryptoMole> so anything on the installer <CryptoMole> i should know <cjwatson> not really <CryptoMole> ok <cjwatson> (at least not to my knowledge) <CryptoMole> so do upgrade, ill have to find out how to do that cause i have forgotten <superm1> CryptoMole, again, this isn't realy intended discussion for this channel, but this will get you started: http://www.ubuntu.com/testing/tribe3 <superm1> join into #ubuntu+1 :) <CryptoMole> thanks <tepsipakki> cjwatson: could I test the new debconf on dapper netboot by replacing some files on the fly while it's installing? <cjwatson> tepsipakki: yes, but I figured a modified ISO image would be a better test - why? <cjwatson> tepsipakki: the patch is in the bug - if you apply that after debconf is installed by base-installer but before pkgsel *starts*, then that would be a valid test <cjwatson> you either have to be quick, or edit pkgsel.postinst to put 'sleep 3600 || true' at the start and kill the sleep process when you're ready for it <cjwatson> oh, sorry, you said netboot <cjwatson> yeah, I guess that would be interesting. The problem is that it only shows up some of the time, so you might well have to run several times or on several machines to confirm that the hang had gone away or at least been ameliorated <cjwatson> but if you're prepared to patch on the fly maybe five or ten times over, or else set something up to automate it, sure <tepsipakki> cjwatson: I could reproduce it on some machines every time, so I'd test that first <tepsipakki> and then the fix <tepsipakki> but I'll try to come up with a way to test it several times <cjwatson> tepsipakki: ok, that would be great then <cjwatson> tepsipakki: the URL on cdimage.ubuntu.com I gave in the bug includes patches adjusted to apply to dapper, edgy, and feisty <cjwatson> you'll want to grab the dapper one as the original patch won't apply directly - a few other things were changed #ubuntu-installer 2007-08-06 <mpt> "Results 1 - 10 of about 64,900 for allintext:ubuntu gusty. (0.14 seconds)" <mpt> That's 4% of the pages that refer to Ubuntu Gutsy at all <mpt> wow <mpt> "Fiesty" is just over 3% of Ubuntu Feisty references <mpt> I wonder if the error rate increases or decreases over the release cycle <tepsipakki> cjwatson: patching debconf on dapper makes it reject parts of the patch <tepsipakki> only the first hunk applied <tepsipakki> oh wait <tepsipakki> duh <tepsipakki> wrong debconf :I <cjwatson> wrong in which way? <tepsipakki> version ;) <cjwatson> heh <tepsipakki> I had deb-src line for feisty.. <tepsipakki> too bad apt-get can't fetch the version I'd like if it's a source package <cjwatson> media-change handling was added to debconf-apt-progress after edgy <cjwatson> err <cjwatson> you're not installing feisty's debconf directly on dapper, are you? <tepsipakki> no, the deb-src was there for development <tepsipakki> hmm, I can of course build a new debconf package and put it on our repo, that way it should be a lot easier to test <cjwatson> tepsipakki: I can just give you the ones I built <tepsipakki> cjwatson: yeah, that works too :) <tepsipakki> I haven't seen that bug with feisty, so dapper is enough <cjwatson> http://people.ubuntu.com/~cjwatson/debconf-bug62986/ <tepsipakki> thanks, I'll try them out <tepsipakki> cjwatson: I've tried dapper-netboot on one machine three times now, and haven't been able to reproduce the hang, but this is without the fix.. I'll leave it looping, so maybe we'll hit the bug eventually ;) <cjwatson> tepsipakki: ok, thanks <tepsipakki> cjwatson: do you want me to test with the fix anyway? <cjwatson> yes please, would be useful to know that it hasn't regressed previously working systems <tepsipakki> ok I'll test that too <cjwatson> evand: bug 127365 got the information you asked for, but it looks rejectable - stuff like: <cjwatson> Aug 2 04:50:24 ubuntu kernel: [ 735.750836] SQUASHFS error: sb_bread failed reading block 0x282b <cjwatson> near the end <cjwatson> well, either reject, or reassign it over to linux-source-2.6.22 and remove the milestone <cjwatson> possibly the latter if you ping pkl to let him know <evand> will do, thanks <superm1> what would you guys think about adding an option in that last advanced dialog to not configure the bootloader if checked to resolve this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/130445 ? <cjwatson> I'm fine with a "don't install grub" checkbox in the advanced dialog <cjwatson> it should cause the grub device entry that's already there to be greyed out <superm1> great :). I'll work out a patch this week for that then <superm1> Ok. should be easy enough #ubuntu-installer 2007-08-07 <Erick> hi need some help with installing from HD (NOT CDROM). Is this the right channel? <Erick> to discuss? <tepsipakki> cjwatson: yay, gfxboot works now? <superm1> cjwatson, I wrote a patch for https://bugs.launchpad.net/mythbuntu/+bug/130445 in my branch at https://code.launchpad.net/~mythbuntu/ubiquity/mythbuntu-ubiquity if you would be able to look at it and possibly merge <tepsipakki> cjwatson: so it seems.. sleep well :) <cjwatson> tepsipakki: yeah. please check whether new gfxboot patches change APIs all over the place in future :) <cjwatson> it had interesting knock-on effects all the way into the theme font and stuff <cjwatson> superm1: looks great to me, more or less exactly how I'd have done it <CIA-20> ubiquity: cjwatson * r2169 ubiquity/ (9 files in 6 dirs): merge from Mario <tepsipakki> cjwatson: I'll be very careful even when thinking of starting to merge syslinux/gfxboot in the future :) <tepsipakki> cjwatson: by the way, dapper installation with the new debconf worked just fine <cjwatson> great <CIA-20> ubiquity: cjwatson * r2170 ubiquity/ (debian/changelog scripts/install.py): <CIA-20> ubiquity: * Run apt's DoInstall() method with stdin redirected from /dev/null, to <CIA-20> ubiquity: stop it hijacking the debconf protocol (LP: #130843). <CIA-20> ubiquity: cjwatson * r2161 tribe-4/ (debian/changelog scripts/install.py): cherry-pick r2170 from trunk <CIA-20> ubiquity: cjwatson * r2162 ubiquity/ (d-i/manifest debian/changelog): <CIA-20> ubiquity: * Automatic update of included source packages: apt-setup 1:0.21ubuntu2, <CIA-20> ubiquity: base-installer 1.81ubuntu1, partman-auto 69ubuntu5. <cjwatson> (that was really the tribe-4 branch) <CIA-20> ubiquity: cjwatson * r2163 tribe-4/debian/changelog: releasing version 1.5.7 <CIA-20> ubiquity: cjwatson * r2171 ubiquity/ (d-i/manifest debian/changelog): merge tribe-4 branch <superm1> i'm a bit confused, was this tribe-4 branch just made for doing the tribe 4 release? <evand> superm1: yes, there were changes to ubiquity that were in bzr but were not released as a version. As they were somewhat large, it was decided they should not be included for tribe-4. <evand> At least that's what my understanding was <superm1> i see <superm1> well that's sensible <cjwatson> correct <cjwatson> pitti told me to do it. :) <superm1> cjwatson, so is the plan to do some incremental testing releases with the bigger changes right after tribe-4 but before tribe-5 in the form of dailies? <evand> superm1: Can you clairfy that? Daily CD images are always built. Do you mean daily images tagged with specific features and announced to the community? <superm1> evand, i mean incremental testing releases of ubiquity in the dailies <superm1> for testing/showing those "bigger" changes to ubiquity <evand> I'm sorry, I'm having a really hard time understanding people today. If you mean additional releases of Ubiquity between now and Tribe-5 that include the changes that didn't make it into Tribe-4 as well as changes that have occurred since then, then yes, we will do that. <superm1> yea that's what i had meant :) <superm1> cjwatson, in the tribe 4 release, were any of the mythbuntu frontend changes added in? <cjwatson> no, I'm afraid not <cjwatson> I explicitly branched to avoid all the churn that hadn't been uploaded yet <cjwatson> they'll go in in the next upload, which will be well before tribe-4 <cjwatson> err <cjwatson> well before tribe-5 <superm1> oh ok. well i'll make sure to upload to our 3rd party repo then until then <superm1> we're lagging behind by about 2-3 weeks on our alphas anyhow, so that will work out well #ubuntu-installer 2007-08-08 <superm1> cjwatson_, you still here? <casperzshado> im having a problem booting my ubuntu on my brothers pc, anybody care to gimme a hand? <casperzshado> anyone here? <cr3> would it make sense for preseeding to automatically determine the disk device, assuming there is only one disk, instead of having to specify the disk explicitly: d-i partman-auto/disk string /dev/sda <cjwatson> cr3: it does, if you also preseed partman-auto/method. <cjwatson> partman-auto (62ubuntu3) feisty; urgency=low <cjwatson> partman-auto (62ubuntu3) feisty; urgency=l * auto.d/initial_auto: If partman-auto/method is preseeded and <cjwatson> partman-auto/disk is not but there is only one disk, act as though <cjwatson> partman-auto/disk had been preseeded to that disk. This simplifies a <cjwatson> number of preseeding scenarios that had been complicated by the removal <cjwatson> of devfs path support. <cjwatson> -- Colin Watson <douglassanchez@example.org> Tue, 23 Jan 2007 09:46:39 +0100 <cr3> cjwatson: cheers! how did you get that information into the channel? <cr3> if it's just a copy and paste, where did you copy from? <cjwatson> you've seen changelogs before, haven't you? <cr3> cjwatson: it looked like it but, for some reason, it looked more like a feature request. sorry for the stupid question :/ <cjwatson> no, it's <cjwatson> just the partman-auto changelog <cjwatson> (modulo irssi paste damage) <cr3> that is very cool, intel will be very pleased to hear about it <cjwatson> 'd-i partman-auto/method string regular' is the other piece of the puzzle for normal setups (as opposed to lvm or what-have-you). They probably have that already <cr3> cjwatson: how can I know the values supported by partman-auto/method? I remember having to specify "regular" during feisty, but I didn't quite understand why. <cjwatson> see the installation guide <cjwatson> except that crypto is not yet supported in Ubuntu <cr3> cjwatson: when I only specify "d-i partman-auto/method string regular" without "d-i partman-auto/disk string /dev/sda", I get prompted to partition disks. I guess I will read the installation guide more carefully <cjwatson> wow, the wubi build system runs on Unix with WINE <cjwatson> need to have NSIS installed though <evand> hahaha <cr3> cjwatson: so partman-auto-method string regular doesn't seem to be picking up the only disk on the system, I'm about to send you the syslog and partman files <evand> what even possessed you to try that? <cjwatson> cr3: ok <cjwatson> evand: I didn't try it, I was curious about where we would start with including wubi on the CDs and went to look ... <evand> ah <cjwatson> looks like it has a bunch of code for allocating disk images that can be replaced by partman-auto-loop now <evand> nice <cjwatson> well, once I get fuse and ntfs udebs done and such <cjwatson> cr3: that syslog shows four disks <cr3> cjwatson: but the installer doesn't prompt me to select on which disk I want to install, it only offers to partition sda <cjwatson> I never said there was UI for that :) <cjwatson> oh, er, wait * cjwatson rereads <cjwatson> cr3: what if you select "Guided - use entire disk"? you didn't in the logs you sent me <cjwatson> the auto-resize thing only ever offers freed space on one selected disk <cjwatson> you'll never get multiple "Guided - resize <blah> and use freed space" options <cjwatson> the partitioner has certainly noticed the existence of the other disks though <cr3> cjwatson: thanks for the explanation, I had assumed from the UI that there was only one disk but I should've paid more attention to the log file. that'll learn me * Starting logfile irclogs/ubuntu-installer.log #ubuntu-installer 2007-08-09 <cjwatson> btm: that's pretty much accurate, yes. different rather than additional. <CIA-20> oem-config: cjwatson * r321 oem-config/ (debian/changelog finish-install.d/07oem-config-user): <CIA-20> oem-config: * Chroot to test for existence of gdm-cdd.conf to avoid problems with <CIA-20> oem-config: broken symlinks; cf. casper 1.93. <CIA-20> ubiquity: cjwatson * r2172 ubiquity/ (debian/changelog scripts/install.py): <CIA-20> ubiquity: * Move oem-config post-user-creation hacks to the end of install_extras, <CIA-20> ubiquity: when oem-config-gtk/kde will have been installed in /target. <CIA-20> ubiquity: cjwatson * r2173 ubiquity/ (4 files in 3 dirs): <CIA-20> ubiquity: * Reimplement more of oem-config-udeb (ugh): disable the hwdb-client <CIA-20> ubiquity: notification for the created user; set up autologin for the oem user via <CIA-20> ubiquity: gdm/kdm. <CIA-20> ubiquity: cjwatson * r2174 ubiquity/ (debian/changelog ubiquity/frontend/base.py): * Disable migration-assistant if oem-config/enable=true. <CIA-20> ubiquity: cjwatson * r2175 ubiquity/ (9 files in 6 dirs): belatedly bump to 1.5.8 following tribe-4 merge; includes libtool 1.5.22-4 -> 1.5.24-1 <CIA-20> ubiquity: cjwatson * r2176 ubiquity/ (apport/ubiquity.py debian/changelog): * Adjust apport hook to attach /var/log/installer/debug too if available. <ion> will the installer implement FDE/full drive encryption option? <CIA-20> ubiquity: cjwatson * r2177 ubiquity/debian/changelog: r2172 closes LP: #131250 <cjwatson> evand: any objection to me releasing ubiquity bzr? <evand> cjwatson: not at all <CIA-20> oem-config: cjwatson * r322 oem-config/debian/changelog: releasing version 1.18 <CIA-20> ubiquity: cjwatson * r2178 ubiquity/debian/po/ (79 files): debconf-updatepo <CIA-20> ubiquity: cjwatson * r2179 ubiquity/d-i/manifest: add partman-auto-loop to manifest too <cjwatson> evand: I have to go for a while now, but I'll finish the upload later <evand> cjwatson: ok, no worries. You're not preventing me from committing atm as I'm tied up in other work. <cjwatson> nod #ubuntu-installer 2007-08-10 * Starting logfile irclogs/ubuntu-installer.log <CIA-20> ubiquity: cjwatson * r2182 ubiquity/ (doc/ubiquity.8 debian/changelog debian/rules): * Add a manual page for ubiquity. <superm1_> cjwatson, don't worry about the lirc bug, keescook uploaded it this morning <cjwatson> ok, just as well <cjwatson> about to go on vacation :) <superm1_> cjwatson, before you dissappear then, can you look over the email i sent to you regarding mythbuntu-meta? <superm1_> Riddell just wanted you to double check it before he uploaded <cjwatson> ok, checking out <cjwatson> superm1_: urgh, seed branches *must* be properly branched off the main ubuntu.gutsy seeds <cjwatson> I'm afraid that's a requirement <cjwatson> the one you gave me just starts at revision 1 <cjwatson> I haven't found it necessary to keep *-meta in bzr, to be honest <cjwatson> since it's generating all the data from bzr anyway <cjwatson> anyway, I'll send you a review by e-mail <superm1_> sorry stepped out for a few. Not too big a deal to branch off that branch instead, I'll watch for that mail and adjust accordingly. Thanks <cjwatson> you have mail now <superm1_> oh interesting, i was wondering how the apt archive was produced along side the CD. i've been doing it by hand currently.. Thanks for looking this over, i'll update everything accordingly later this evening <superm1_> one question would be regarding the -live metapackage, since we won't have tasks for a while, is it "ok" to do the -live for now, and then at a later time (gutsy +1) nuke it in the archive <cjwatson> sure <cjwatson> I only mentioned it because we found it to be a maintenance pain after a while, but that was more due to the repeated language pack dance than anything else <superm1_> ah i see #ubuntu-installer 2007-08-11 * Starting logfile irclogs/ubuntu-installer.log <axel_s> Hi, can I get help with Ubuntu installation here? #ubuntu-installer 2007-08-15 * Starting logfile irclogs/ubuntu-installer.log <xivulon> evand, cjwatson, how is the alternate/live iso supposed to be preseeded with respect to wubi? <evand> xivulon: I would image the same way as before, via initrd preseeding. I don't believe I fully understand your question. <thefloydfan> can anybody here help me troubleshoot my installation problems? <thefloydfan> I'm Getting the common can't access TTY and turning off job control. If I do a modprobe piix it takes FOREVER to get to the desktop. The installer frezzes while scanning disks. <xivulon> evand , my understanding of initrd preseeding is that the file has to be on the root directory of the initrd. But the initrd is on a CD and the preseed file is going to be on the HD, left there by the windows frontend... <xivulon> I'd need to be able to pass as a kernel argument the device and folder where to find the preseed file, something closer to hd-media preseeding. <xivulon> Did I miss anything? <evand> xivulon: Weren't you using initrd preseeding before? <evand> xivulon: my understanding is that initrd preseeding is the only way to entirely preseed during an alternate cd install. However, you can use file= or url= on the kernel cmdline to preseed ubiquity. <evand> on the livecd, obviously <bdmurray> evand: have you seen bug 128165? The use case seems interesting to me <evand> checking <xivulon> evand, the way it was done before, was to scan the HD for the wubi folder, mount the host folder, then copy the preseed in there to the initrd root (thus triggering an initrd preseed). <xivulon> So in a sense the initrd was similar to the hd-media initrd. The alternate/live CD initrd do not have HD scanning functionality as far as I am aware. Also in order to have initrd preseed, that functionality has to be in an early stage. <bdmurray> evand: I spoke with the reporter if you have any questions. It seems they manually setup IP configuration but did not have the cable connected. They were going to connect it to the network later. <evand> bdmurray: ahh, that makes it a little more clear. OK, I'll give that a shot and see what happens. No promises on it today as FF is tomorrow and I'm in a panic to get large amounts of code in. <bdmurray> evand: My question was more "is this a valid use case?" I don't think it is very high priority. <evand> bdmurray: ah, I'd wager not, as the installer should be able to assume that you're planning on using the network configuration right away if you're manually configuring it, but perhaps cjwatson would have a different opinion. <bdmurray> Okay, I think the original reporter was under the impression he was configuring the network for the installed system not the installling system. <bdmurray> And I was not sure of the relationship between the two. <evand> I believe they're assumed to be one in the same. Is there any reason why he couldn't have the network cable plugged in during the install? <bdmurray> I didn't ask that particular question. * Starting logfile irclogs/ubuntu-installer.log <cr3> how can I make the installation poweroff rather than reboot? <cr3> I tried adding poweroff to the late_command script but that exits 1. I also tried calling in-target poweroff and that exits 1. <cr3> just calling poweroff works though, so I'll just drop in-target <evand> cr3: from googling, no idea if it works: debian-installer/exit/halt and debian-installer/exit/always_halt #ubuntu-installer 2007-08-16 <xivulo1> evand do you have a working preseed with loop installation I can look at? <erika14212> hi all <erika14212> i have a install question <CIA-20> ubiquity: evand * r2184 ubiquity/ (5 files in 4 dirs): <CIA-20> ubiquity: * Use a migration-assistant script to continuously call m-a rather <CIA-20> ubiquity: than hacking cleanup(). <CIA-20> ubiquity: evand * r2185 ubiquity/ (8 files in 6 dirs): Update for release. <CIA-20> ubiquity: evand * r2186 ubiquity/debian/changelog: releasing version 1.5.9 <xivulon> evand, could you pls send me a working preseed with loop installation? For some reason it does not like my recipe (too large!) <evand> xivulon: I haven't had a chance to test loop installs yet. However, when I do I'll be sure to send you a recipe if I can get it working <CIA-20> ubiquity: evand * r2187 ubiquity/ (5 files in 3 dirs): * Fix intltool to fix FTBFS. Thanks Keybuk. <CIA-20> ubiquity: evand * r2188 ubiquity/ (configure configure.ac): Update for release. <xivulon> evand, maybe you can have a look at mine: http://wubi-installer.org/devel/test/preseed.cfg <xivulon> the error I get is: "partman-auto-loop/recipe too large (596>210) <CIA-20> ubiquity: evand * r2189 ubiquity/debian/changelog: releasing version 1.5.10 <evand> xivulon: I'll take a look when I get home tonight and see what I can come up with #ubuntu-installer 2007-08-17 <xivulon> evand, my understanding of that is that I have only 210MB free and I need a minimum of 596 according to the recipe. But I do have more than 210MB on sdb1 <xivulon> tried with another empty vm disk and it seems to be working <dariuskane> evening folks <xivulon> ls <xivulon> evand, cjwatson, I am glad to report that yesterday I managed to install and boot from a loopmounted file <xivulon> the filesystem is ro and as mentioned by colin grub is not setup yet but it works for me so far <xivulon> I used the alternate ISO, did not try the live ISO yet <xivulon> cjwatson, I tried the auto-loop and it worked well, one note on swap <xivulon> I noticed that fstab is setup to use swap as a loop device <xivulon> It was suggested to me by szaka to use a swap file directly without getting losetup involved, i.e. point it to /host/disks/swap.disk <superm1> evand, I just did a mythbuntu build using ubiquity 1.5.10, are things supposed to be working, or do you you have known issues with it? Both the mythbuntu and gtk ui's appear to run into issues <evand> yeah, there are issues <evand> I'm working on them today <superm1> evand, the current issues, should I expect them to be breaking the mythbuntu ui, or is that a undesired side effect I should look into? <evand> superm1: there are new changes that will break mythbuntu. I'll fix those as I fix the other bugs. <superm1> k, are you going to grab someone from core-dev to release once you do, or waiting until monday? <evand> superm1: it depends when I finish. It might be today, it might be over the weekend, or it might be monday. It will not be any later, however, as Tuesday morning the archive is frozen for Tribe and the installer needs to work by then. <superm1> evand, I'll stop pestering you and let you get back to fixing it then :-) <CIA-20> ubiquity: evand * r2190 ubiquity/ (configure configure.ac): Bump to 1.5.11. <evand> :) <evand> xivulon: \o/ nice on getting it working. Do you have a sample preseed file for this? <xivulon> evand, http://wubi-installer.org/devel/test/preseed.cfg <evand> thanks <xivulon> evand, was disconnected, did you get the link? <superm1> http://wubi-installer.org/devel/test/preseed.cfg xivulon ? <superm1> that came through, but nothing more <xivulon> superm1, y8ep <evand> indeed I did, thanks <xivulon> You'd need 3GB+ free, then you have to 1) extract kernel/initrd from root.disk, 2) use another grub installation <xivulon> 3) when you write menu.lst use the parameter loop=/disks/root.disk <xivulon> You end up with a ro system though. I tried to make it rw by remounting /host and then /, but it did not like the last step. <xivulon> evand, I plan to work on that a bit more this w/e are you going to be around? <evand> xivulon: I should be. There are a lot of ubiquity bugs I need to fix. <xivulon> evand, good, see if you can find some time to test the loop installation in vm so we can work in parallel <evand> xivulon: will do <|muelli|>
{'channel': 'ubuntu-installer', 'month': 8}