=== korn_ is now known as c_korn === mtx_init is now known as vinnythechin === dendrobates is now known as dendro-afk === bladernr_ is now known as bladernr-away === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk [01:20] Is it possible to have a package as of now that has build-depends on package versions not available in the repositories? [01:24] meaning "may I upload a source package that build-depends on packages that no longer exist?" No. [01:28] crimsun: No, meaning does it make sense that a package that was uploaded build-depends on a package version that was not? [01:28] quidnunc: if the source package in question hasn't been rebuilt in quite some time, yes, it's quite possible. [01:29] crimsun: THanks === Kai___ is now known as Kai_ [06:18] can anyone tell me where lernid is in the build queue? [06:21] jono, it appears to be in the NEW queue: https://edge.launchpad.net/ubuntu/lucid/+queue [06:21] an archive admin needs to release it [06:22] superm1, any archive admins around? [06:22] ideally we need it available for the kick off of some python sessions tomorrow [06:27] by my math its like 5am in the uk [06:28] pwnguin: fortunately they archive admins aren't UK people [06:28] pwnguin: only some are. [06:31] I didn't think any of today's archive admins were (for various values of "Today") [06:31] ive no clue who runs the archive [06:32] persia: james_w [06:32] lifeless: Is it not Thursday? [06:32] Well, I suppose it's also Wednesday [06:33] But it's *definitely* not Monday anymore. [06:33] persia: I wasn't aware that they lost access on non rota days [06:33] Personally, I think it's Wednesday in TX and Thursday in NSW, if one is hunting an archive admin right now. [06:34] lifeless: Well, no, but they tend to make themselves more available on rota days. [06:36] there must be a list archive admins somewhere [06:37] ~ubuntu-archive [06:37] https://edge.launchpad.net/~ubuntu-archive [06:37] heh [06:37] StevenK, around? [06:38] * StevenK prods jono [06:38] StevenK, :) [06:38] Lernid is in NEW - any chance you could move it along? [06:38] we need it for opp dev week starting tomorrow [06:38] Maybe. How much beer is on offer? [06:38] StevenK, two pints [06:39] * persia prefers https://wiki.ubuntu.com/ArchiveAdministration because it helps ping the right folk on the right days [06:40] thanks persia [06:40] jono: Accepted. [06:40] jono: Well, you've already spent the quart, so it doesn't matter so much to you, but maybe for the next person who needs one :) [06:40] thanks StevenK! [06:40] :) [06:40] sounds awesome, good to know, persia :) [06:41] Hi, can someone walk me through the process of submitting a patch that fixes a bug? I know which lines of code I want to change in the package "lirc" but I don't know how to generate a suitable patch against the package [06:41] lucent: Do you use bzr? [06:41] persia: I do not [06:42] https://wiki.ubuntu.com/Bugs/HowToFix [06:42] okay I will read [06:42] There used to be simpler instructions there :/ [06:43] https://wiki.ubuntu.com/Bugs/HowToFix?action=recall&rev=16 [06:43] persia: I get yelled at when I submit plain diff -uprN patches [06:44] it is kind of bewildering to me but I will try to learn more about this [06:44] Who yelled at you? [06:44] Which bug? [06:44] That should *never* happen. [06:44] The process for submitting patches is as follows: [06:45] A) If you use bzr, branch the package, change it, commit, push a branch, request a merge [06:45] B) If you don't use bzr, attach a perfectly normal patch to the bug, make sure the "this is a patch" checkbox is checked. [06:45] That's it. [06:45] oh, before I heard this I thought I was doing something wrong [06:45] Anything else is just extra messiness because someone thinks you're trying to learn how to be an Ubuntu Developer. [06:45] No, you weren't doing anything wrong. [06:46] We specifically have the Ubuntu Reviewers team (which more people should join! ) which reviews the patches. [06:46] thank you :) [06:46] Not all of them get uploaded right away. Sometimes they get pushed upstream first, etc. [06:46] Submitting a debdiff with all the correct tweaks to integrate to packaging, etc. makes it *harder* to get it upstream. [06:47] unrelated second question, there's no cdrtools in Ubuntu... is cdrtools a "not done here" for Ubuntu Karmic? [06:47] (although it's what we expect from developers who can't upload a given package) [06:47] * persia has no idea [06:48] I don't want to step on toes if I branch the existing PPA and fine tune it to work with Karmic [06:48] a little Google research had vague references to Mark Shuttleworth rumored to be saying no... it was all kind of unconfirmed [06:49] Nothing you do in a PPA affects Ubuntu. [06:50] lucent: however, debian and ubuntu both use cdrkit, not cdrtools [06:51] I am aware of that, in fact am helping to test code for the libburn and libcdio projects (yet a third iteration of burning software) [06:51] the devels for libburn and libcdio refer to cdrecord as the baseline [06:52] lucent: aah. yes, go wild in your ppa (never heard of libcdio, looks into it...) [06:52] the GNU project supports libcdio "in name only" (I'm sure you will be familiar with that concept?) [06:53] I think there's maybe 5 developers between the two projects libcdio and libburn [06:53] it is GPL license and actively developed [06:54] I guess the rumor was that cdrkit development is stalled [08:06] Good morning [08:07] Hey [08:08] slangasek: invalid-mta> well, FSVO "reasonable"; this was discussed to death with the LSB folks, and they are not willing to remove the sendmail requirement; so to finally fix pulling in postfix with every LSB package you isntall, this seems like a lesser evil to me; and it won't change a thing if you already have an MTA installed [08:08] there simply is no frigging way we can sensibly install a real MTA without any questions [08:08] pitti: +1 [08:08] nor is it sensible to install MTAs on nowaday's desktop boxes in teh first place [08:09] ... (says one who has running a local postfix, but with nicely configured SSL certificates for relaying to his server) [08:10] and ssmtp is even less useful; you don't have an MTA to relay to by default === tkamppeter_ is now known as tkamppeter === rainct_ is now known as RainCT [08:28] good morning [08:29] ccheney: can you go through the dups for bug #450569 and friends and demerge all the ones you just demerged. The Pre-Depends: loop is _not_ related to some random process running in the background. It should be possible to separate them again based on package number. 1:3.1.1-5ubuntu1 is where the Pre-Depends loop is (current), and 1:3.0.1 is where the process hang was (six months ago) [08:29] Launchpad bug 450569 in docvert "package openoffice.org-emailmerge 1:3.0.1-9ubuntu3.1 failed to install/upgrade: " [Undecided,In progress] https://launchpad.net/bugs/450569 [08:40] good morning #kernel [08:41] csurbhi: this is #ubuntu-devel ! :-) [08:41] hehe [08:47] hi there! i try to cross compile with arm-linux-gcc a sqlclient to arm720t and i need lib mysqlclient. Must i compile it from soucre with arm-linux-gcc? it would give me great pleasure for some tip. [10:10] pitti: we could have a package which provides m-t-a, and interfaces with UbuntuOne to send all your root mail there or something :P [10:11] hey slangasek! :) [10:11] * dholbach hugs slangasek! [10:11] dholbach: heyo. :) [10:13] Would it be terribly difficult to have an m-t-a that just delivered to /var/spool and had a config widget that let you set up the equivalent of postfix's sasl _passed and sender_relay maps to real smarthosts? [10:14] (and by default forward *all* mail to the first configured user on the machine) [10:14] persia: AIUI one of the concerns with that is that on a modern desktop, the user will never know they even have local mail in that case [10:16] slangasek: We could ship the mail clients with a default spool configuration? [10:16] maybe [10:16] Personally, I find lots of stuff I try to do ends up complaining that I don't have mail set up. [10:16] or we could turn every mail into a notification [10:16] :-) [10:16] As a result, I inevitably set up postfix without much confidence. [10:16] But I know I don't need that. === DrPepperKid is now known as MacSlow|afk [10:44] mvo: does https://wiki.ubuntu.com/LucidLynx/TechnicalOverview#Issue%20when%20upgrading%20from%20Lucid%20Alpha%202 seem like something you would want update-manager to do for us, and would you have time to implement it for Lucid? [10:51] TheMuso: do you know if anyone is planning to test UbuntuStudio so it can be included in alpha 3? [10:56] Hi all [10:56] why is libapache2-mod-wsgi in universe and not in main ? [11:00] sivang: Nothing in main either Depends or Build-Depends on it. [11:01] persia: this is going to be the next gen web gateway technology [11:01] persia: and is already used int he python web world [11:01] persia: ubuntu being a python in mind distro, should get it into main [11:01] persia: I can take care of it's maintainerhip if that's required [11:03] sivang: It's not about maintenance. It's about dependencies. If you think it's essential, get something to depend on it. [11:03] persia: what if I wanna use it under an ubuntu machine? do I need to switch to fedora where it is sort of officially supported? [11:03] persia: what's the dependency argument has to do with an emerging web technology [11:03] :) [11:04] sivang: How isn't it supported in Ubuntu? It's present, isn't it? === MacSlow|afk is now known as MacSlow [11:08] slangasek: yes, I can do that [11:08] persia: in univeser [11:08] mvo !! [11:08] mvo: How have you been you family man? [11:08] :) [11:09] persia: will libapache2-mod-wsgi get 5 years LTS support in universe? [11:09] Daviey++++++ [11:09] hey sivang - good, good (les sleep than before) [11:09] Daviey: Depends on people being interested, but there's nothing blocking it. [11:09] mvo: a child ? [11:10] persia: people interested == python web community worldwide [11:10] persia: Is that enough? ;) [11:10] sivang: Quite likely, as long as they care to keep the version we ship in Lucid in shape, and some people watch the status in Ubuntu. [11:11] sivang: But that's completely irrelevant to the universe/main distinction (which we're overdue abolishing anyway). [11:12] persia: whom do I need to talk to or do I need to create a wiki page for the promotion ? [11:12] pitti: ^^^ [11:12] sivang: What's your goal? Just having it work and getting regular security updates? [11:12] MainInclusionReport was the last time I checked [11:12] persia: security [11:12] persia: my only concern [11:13] sivang: OK. and are you willing to track the security status of it in Lucid and make sure any required patches are tested and made available in a timely manner? [11:13] persia: "I do." :) [11:13] but I need to get my membership fixed again [11:13] sivang: Whilt it shouldn't make any difference, there is certainly a difference in love packages in main recieve compared to universe. If you want to try and get it promoted, I would add it as a ubuntu-server agenda item for the next meeting. If you get the support of -server, then i think it's more likely. [11:14] Hmmm... red tape..... [11:14] ; [11:14] sivang: Great. So file "security" bugs whenever one is needed with the tested patches and ask folk in #ubuntu-hardened if they aren't getting uploaded in a timely manner. [11:14] ;) [11:14] Then you have a supported solution. [11:14] Only bother with the MIR if you need it as a dependency or build-dependency of something on the shipping images. [11:15] persia: not yet, that will come, but not yet. [11:15] Daviey: sure, because any time anyone loves a package in universe they push to have it in main, which isn't exactly scalable. :) [11:15] slangasek: true [11:15] but if I use ot now [11:15] now [11:15] who gurantees it won't screw my server? [11:15] Daviey: There really isn't any difference based on component. I've found *lots* of packages in main that were completely disfunctional and ignored (and tossed them out of main). The differnence is just that more people tend to care about more of the packages in main. [11:15] sivang: You? [11:16] sivang: and anyone you recruit to help you (Daviey seems like a good candidate) [11:16] persia: i entirely agree, but the server team seems to think diffently - based on posts such as http://ubuntumathiaz.wordpress.com/2009/11/30/rfp-packages-to-promote-to-main-and-demote-to-universe-for-lucid-lynx-lts/ [11:17] There's no warranty for the vast majority of software in Ubuntu (even in main), and most of it has a waiver for fitness for any particular purpose. That it works is because people care about it and because we trust each other, rather than because of any contractual arrangement. [11:17] Daviey: Some members of the server team are sadly benighted about the meaning of "support". Just do it :) [11:17] heh [11:18] persia: I hope no one of my customers ever hear that when I seel them Ubuntu Servers:) [11:18] sell [11:18] "sell" => offer them to use ubuntu server on their VDS [11:19] when they hear "no warranty" they run out and cry "RHEL, RHEL!!!" [11:19] ;) [11:19] anyway, to go back to a more fruitful discussion and less trolling :) [11:19] so, just file bugs and make sure someone cares aboiut it? [11:19] or cares "enough" about it [11:19] ? [11:20] sivang: Go read the licenses of RHEL software. It's the same software under the same licenses and comes with the same specific disclaimer of usefulness. [11:21] That doesn't mean it isn't useful, just that nobody guarantees it. If you, completely separately, decide to enter into a contract with a customer to provide support or warranty for some return, that's between you and your customer. [11:21] persia: sure, I try to explain that to them, however, you say that even if a [pacakge in main that's not gurantee for security, I don't think this is the right statement [11:21] one of the first tasks [11:21] charge them $10,000 and provide the guarantee yourself [11:21] I got from pitti as a mentor, was to do security review for warty [11:22] for everything we importedfrom debian [11:22] OK. Packages in main only get security support if someone either identifies the problem in a clear way to Ubuntu or if a CVE is published. [11:22] persia: that's what I want, is it so hard to achive ? [11:22] That's nice, but it's certainly not anything like a guarantee. [11:22] persia: it is *something* [11:22] better than *nothing* inuniverse [11:22] ahh I need a real latpo [11:22] aptop [11:23] right, I rest my case:) [11:23] this kbd is the worst ever [11:23] sivang: Like I said before, just do it, and provide the guarantee. You're effectively asking someone else to do something so that you can get paid. I'm unsure why they would want to do that. [11:23] no, I'm asking this so I could promote Ubuntu as a wsgi hosting platform [11:23] irrelavant to my pay [11:23] seriously [11:23] I've done so much for ubuntu without seeing a dime, so I don't think this request is out of place. [11:24] I am promoting ubuntu regardless of my commercial itnerest in it. [11:24] oh, and I've contributed with will :-) [11:24] sivang: I think you miss my essential point. If you want it to be supported, support it. That's all it takes. [11:25] If you want someone else to support it, then find some way to incentivise them. [11:25] so I don't feel like ubuntu is owning me something, to make straight [11:25] persia: okay, noted. [11:25] persia: I'll start with it and then find someone else to care for it. [11:25] sivang: your contribution _to_ Ubuntu would be _the support_ of $package [11:25] sladen: right, what's the comitte these days to get main upload right for a specific package? [11:25] sivang: I'd love to see the package well maintained. I think you're perfectly capable of doing it. I know that the universe/main distinction is meaningless and that we've been working to abolish it for the last two years. [11:26] sivang: either provided directly by yourself, or through pursuading somebody else to take on that support [11:26] sladen: you have main upload rights? [11:26] sladen: would you sponsor me? [11:26] sivang: I'd sponsor a sane-looking patch to a package that was already there [11:27] sivang: The security team would *love* to sponsor all your security updates. They are constantly looking for new people to submit tested patches. [11:27] okay cool [11:27] sivang: but I wouldn't _gaurantee_ to do so ('gaurantee' is a very strong word) [11:27] I'll start playing with mod-wsgi [11:27] sladen: I know, but you still have main upload rights yes? [11:27] sivang: last time I checked, yes [11:27] sladen: so once it's tested and working, we're good to go? [11:28] sivang: whether I use them as much as I should, is another question [11:28] sladen: good, cause I Have no interest in going throught the red tape for main right [11:28] sladen: :-) [11:28] sladen: I'm not entirely sure gaurantee is a word :) [11:28] Daviey: haha [11:28] in Israel surely it is not. [11:28] NOTHING is guranteed here. [11:28] ;) [11:29] what's the right omitte to file a universe upload rigths again? [11:29] sivang: If you care about the package as passionately as you seem to.. Just unoffically taking on burden of checking for security and bugs, submitting patches (either plain or debdiff), is enough to allow someone else to sponsor the package [11:30] sivang: This means that you can personally guarantee support, and everyone wins [11:30] And there's only a few people who can push to -security anyway (not everyone with main upload rights can do this). [11:46] lool, do you happen to have a working qemu lucid atm ? i cant get iso-codes to unpack here running rootstock, i wonder if you can in an interactive setup [11:47] ogra: You mean apt-get install iso-codes? [11:47] yeah [11:47] rootstok hangs forever in [11:47] Selecting previously deselected package iso-codes. [11:47] Unpacking iso-codes (from .../iso-codes_3.12.1-1_all.deb) ... [11:48] and i wonder if it has to do with the bz2 tarball or the 3.0 source format, though i would expect more packages to be in that format if i install the ubuntu-netbook task [11:49] neither the source tarball compression method nor the 3.0 source format can possibly have anything to do with whether the binary package installs successfully [11:49] ogra: it works in qemu-system-arm for me [11:49] Neither the source tarball nor the source format should have any impact on binary installation. [11:50] snap [11:50] Indeed. [11:50] lool, hmm, k, then it must be my VM setup i guess :/ [11:50] Schnipschnapschnappy das kleine Krokodil [11:50] LOL [11:50] ogra: it's you again and your bad karma [11:50] yeah, apparently :/ [11:51] I'll try in qemu-arm-static too [11:51] * ogra needs to do something about that karma thing [11:51] works with syscall emulation as well [11:52] cjwatson, well, repackaging in 3.0 was the only significant difference i found to the karmic package (which unpacks fine) ... apart from several new upstream releases [11:53] but i think lool has just proven it must be my VM ... and since we use the same kernel i suspect it can only be my setup ... either i'm missing something in the rootfs or in the qemu call [11:54] ogra: The key is that nothing in how the source package is packed or unpacked *can* affect the binary package, which is always constructed in accordance with debian/rules. [11:54] lool, do you use MALLOC_CHECK_=0 in yours ? [11:55] persia, indeed ... but as i said, it was the only significant changelog entry i found [11:57] ogra: no [11:57] aha [11:57] i should probably try without then [11:57] * ogra does that ... we'll see in 1h :) [11:57] But MALLOC_CHECK_=0 when the source package is built is not going to affect the binary packages! [11:58] i'm not building anything :) [11:58] i'm getting stuck installing a binary [11:58] I know, but I'm hungry, my jokes get worse every minute [11:59] ah, french humor :) get some lunch ! [11:59] If the chicken isn't ready in 10 minutes it's going to be awful [12:16] Can anyone suggest a better fragment than `while [ ! -f /var/lib/partman/persia ]; do sleep 5; done; tail -f /var/lib/partman/persia` to start viewing a low-volume file once it appears? I'm sure there's some cool fsnotify thing. [12:19] is there a timeout in the new lvm, for drive probing? [12:20] I haven't noticed one (and needed to press 'C' once to get the boot to finish when swap didn't want to come up) [12:20] persia: tail -F /var/lib/partman/persia [12:21] persia: hmm, I would quite like it to stop and drop me into busybox ;) [12:21] ion: Nifty. Is that smart, or does it poll like my snippet? [12:21] It probably just polls. [12:21] Yeah, it has an open-sleep loop, just straced it. [12:22] lifeless: What letters show up while it's waiting? Press them one at a time to see if you get a useful result. I *think* C is Cancel, but I'm kinda guessing (there's no docs I've found) [12:22] slangasek: I have a user who says that since upstart 0.6.3-11 landed, his ssh and apache servers don't start on boot. Does this sound familiar? [12:22] persia: letters? [12:22] ion: I'll probably use that next time because it's less typing, but it ought be done the smart way. [12:22] Yeah [12:22] persia: I'm talking about 'probing all drives, please pe patient this may take a while\n' [12:22] persia: C is cancel fsck [12:23] lifeless: So, you should have something like "Waiting for foo [CSM]" and that seems to mean you can press 'C' , 'S', or 'M' for different (undocumetned) effects. [12:23] soren: yes, his /etc/network/interfaces is broken and he should help verify the SRU for bug #497299 [12:23] Launchpad bug 497299 in ifupdown "upstart not starting init-scripts (event net-device-up IFACE=lo missing)" [High,Fix committed] https://launchpad.net/bugs/497299 [12:23] persia: only [SM] for that one ;-) [12:23] lifeless: mountall just stopping at that request instead of continuing until device appears or user hits a key is a known bug and will be fixed. [12:23] S = Skip this filesystem (pretend it's marked nowait in fstab) [12:23] M = Give me maintenance shell [12:24] persia: no prompt at all [12:24] ion: thanks [12:24] I = Ignore fsck errors (and try to mount anyway) [12:24] Keybuk: what needs to be installed to get that prompt? [12:24] F = Run fsck -y (after an fsck failure) [12:24] lifeless: nothing [12:25] lifeless: just mountall and plymouth [12:25] hmm, I suspect plymouth is missing. [12:25] you should get a message about that on boot [12:25] libplymouth is installed [12:25] A couple of small functions just need to be added to plymouth to make it integrate to other main loop than its own, and then mountall needs to be changed to be asynchronous with the boredom timeout query. [12:25] mountall will complain it cant connect to plymouth [12:26] Keybuk: Thanks for the summary of options. Is this already in /usr/share/doc/ somewhere, or would it be useful for me to put it in a text file and add it somewhere (and to which package?) [12:26] persia: no, and no [12:26] the fact you just see letters is very temporary [12:26] the idea is that the new theme will have a much nicer message [12:26] e.g. say "Press C to cancel" etc. [12:26] Ah, cool. Nevermind then. [12:26] Keybuk: aren't those strings verbatim from mountall? You intend the theme to fix them up? [12:26] I don't think anything in the kernel|initramfs dependency set drags in plythmouth itself [12:27] slangasek: the new theme will require changing the messages, yeah [12:27] lifeless: ubuntu-standard :P [12:27] slangasek: perhaps, but you really don't want to know what I'm up to :P [12:27] Keybuk: a little unnerving that this is considered tied to a theme [12:28] (and yes, I've been in the plymouth theme code) [12:29] slangasek: Great, thanks for the hint. I'll point him to that. [12:29] slangasek: we need the ability to put messages in different places on the screen [12:29] and also resolve the issues where the "Fsck in progress" messages are built into the theme, instead of from mountall [12:29] etc. [12:29] ah [12:33] and as ion says, mountall instead of just going into a "reading from plymouth" loop for each key press needs to work asynchronously [12:33] so if the volume arrives while waiting, it cancels the prompt and carries on with its work [12:35] Keybuk: Is there a way that one can provide hints to say "don't wait on this"? I never want to wait on swap for boot (although I'd like it mounted at some point). [12:36] persia: nobootwait in fstab is the hint [12:36] Nifty. I thought I'd get pointed at some code that needed fixing. Thanks! [12:40] slangasek: so, the new lvm doesn't want to find stuff at boot [12:40] slangasek: any pointers before I start climbing through hoops? [12:40] lifeless: WFM, worked for kees [12:40] I disavow all knowledge beyond that :-) [12:40] hah === thekorn_ is now known as thekorn [12:50] dpm: re bug 518718, bug 527052 implies that it should be just "Ubuntu Netbook", not "... Edition"? that's what current cdimage code says too [12:50] Launchpad bug 518718 in ubuntu-translations "Change "Ubuntu Netbook Remix" messages to "Ubuntu Netbook Edition"" [Low,In progress] https://launchpad.net/bugs/518718 [12:50] Launchpad bug 527052 in gfxboot-theme-ubuntu "live cd bootscreen has untranslated "Try Ubuntu * without installing" and "Install Ubuntu *"" [Undecided,New] https://launchpad.net/bugs/527052 [12:50] slangasek: FYI - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488332 [12:50] Debian bug 488332 in lvm2 "LVM sysfs_scan with newer 2.6.x kernels needs deprecated sysfs layout" [Normal,Open] [12:51] appears to be it; I haven't dug deep enough to know if there is more under the hood, but I can get pvscan happy with the sysfs setting [12:51] lifeless: ummm, I definitely don't have CONFIG_SYSFS_DEPRECATED_V2 set here (stock Lucid kernel), and WFM [12:51] slangasek: this is stock lucid kernel too [12:51] dpm: shall I just change the netbook strings in the obvious way here? [12:53] dpm: since it involves removing a word, I can probably just update all the translations myself [12:53] or most of them anyway [12:57] cjwatson: assuming you know the correct genitive->nominative conversion? :) [12:57] slangasek: should mountall depend on plymouth? [12:58] slangasek: oh, I can leave those fuzzy [12:58] lifeless: I defer to Keybuk; mountall /works/ without plymouth, it just doesn't /talk/ to you [13:00] how is it supposet to work on a serial terminal? [13:00] -sed [13:00] lifeless: udev doesn't work with deprecated sysfs layout anymore [13:00] I find it strange that a server install pulls plymouth.. [13:00] so you can't have it ;) [13:00] Keybuk: Oh, I don't want it. [13:01] tjaalton: why? we still need something to arbitrate password prompts and suchlike during boot [13:01] cjwatson, is debug-ubiquity supposed to send you in install only mode rather than livecd desktop? [13:01] I suspect that lvm in the initramfs is old, but I don't know why yet. [13:01] seb128: debug-ubiquity is orthogonal to the try/install mode [13:01] Keybuk: I'm not quite back into the system to fiddle; root is mounted but I suspect upstart is in lala land [13:01] Keybuk: no way to do that without plymouth? [13:01] oh, heh, maybe it isn't [13:01] tjaalton: plymouth works fine for doing that - there's no reason to invent a different way [13:01] cjwatson, weird, I picked livecd desktop and got installer only [13:02] cjwatson, I was wondering if that's due to me addign debug-ubiquity to the option, will try without === MacSlow is now known as MacSlow|lunch [13:02] seb128: yeah, bug I think, fixing now [13:02] cjwatson, thanks [13:02] well, that said [13:02] Keybuk: ok then. as long as it works on a serial terminal as well ;) [13:02] seb128: I think actually maybe it does make sense - the thing is that if you don't use install-only mode, then debug-ubiquity is a no-op [13:03] the way you get debug mode in "try ubuntu" mode is to run 'ubiquity -d' in a terminal [13:03] cjwatson, would it make sense to have debug-ubiquity in the f6 menu for unstable versions? [13:03] so I think I'll leave it as it is and retroactively declare that it's meant to be that way ;) [13:03] tjaalton: it does [13:03] cjwatson, ok, makes sense [13:03] seb128: hmm, the problem with debug-ubiquity is that it exposes your password in the logs [13:04] admittedly it does tell you that it's doing so, but still, I'd prefer it to just be when we ask for it [13:04] ok [13:04] unfortunately the only way to fix that is by some really messy hacking in debconf that made both joeyh and I feel ill [13:05] cjwatson, I don't get the crash in glib with today image btw, will make harder to report a bug about it, I delayed to have a version where the partition setup was working and now it's working all the way... [13:05] how annoying [13:05] yes [13:05] let's hope (?) it recurs [13:05] I will try again with yesterday's image later [13:06] it was not an image recording issue, I did write the key several times to clean hacks I did on the stick [13:12] seb128: yeah, I doubted it was [13:13] lool, ha ! seems qemu doesnt like the use of a swapfile [13:14] lool, running rootstock with --noswap makes iso-codes install [13:14] (that wasnt an issue in karmic though) [13:21] Riddell, in qt4-x11 4:4.6.0-1ubuntu2 you set -arch armv6, do you remember the reason for that ? [13:25] I did? [13:25] where? [13:26] ogra: I do, it was because there was a specific armv6 implementation of some bits [13:26] the default was arm, and wasn't good for armv7 [13:26] do you remember if it was assembler ? [13:27] the armv6 code doesn't handle multicore, but is otherwise much better than what was there before [13:27] yes [13:27] ah, k, thanks a lot [13:27] bah [13:27] I almost success to install a3 now [13:27] it's not moving from the "detecting other systems" now [13:27] ie grub install [13:28] * seb128 wonders if I should just power down the box [13:29] cjwatson, anything useful I can get from an installer only install blocking on grub os detection? [13:29] cjwatson, it's at 93% looking for other os for a while now [13:29] syslog, ps axf maybe [13:30] strace of whatever process it is that's looping [13:34] cjwatson, there is a "blkid -o value -s TYPE /dev/sda2" running for some 8 minutes now [13:34] can you strace it to see what it's doing? [13:34] Keybuk: 'mounted-dev main process (435) terminated with status 1 [13:34] Keybuk: would that throw upstart off? [13:35] wouldn't think so [13:35] cjwatson, nothing apparently, strace -p stays there [13:35] though it does mean something's wrong with your /dev ;-) [13:35] if you don't have anything in there - then you'd have bigger problems [13:35] eh [13:35] seb128: sounds like it's looping in internal logic then ... [13:35]