[00:40] <KIAaze> hi
[00:40] <KIAaze> how can I build 32-bit packages on 64-bit?
[00:40] <KIAaze> (without using launchpad)
[00:47] <RAOF> KIAaze: pbuilder-dist from ubuntu-dev-tools is a quick and easy way; call it as “pbuilder-dist lucid i386 $OPERATION” and you'll get an i386 lucid chroot.  Symlink pbuilder-lucid-i386 to pbuilder-dist for added ease.
[00:50] <KIAaze> thanks :)
[00:51] <KIAaze> the distro specification is even better :)
[00:51] <KIAaze> well, just as useful at least
[00:52] <Nafai> I need to learn all of these tools
[00:52] <Nafai> Hopefully RAOF and others can school me at UDS :)
[00:53] <persia> Nafai: Actually, you'd do best to learn online: UDS is busy, and you'll want to follow along.  Join #ubuntu-packaging anytime and folks are happy to help (or ask here if it's quiet).
[00:53] <Nafai> thanks
[00:54] <RAOF> Or even #ubuntu-motu; we're more used to (and generally happy to field) beginner questions in there.
[00:54]  * persia thinks it's mostly the same folks answering questions in any of these places.
[00:55] <RAOF> Mostly, yeah.
[00:56] <YokoZar> Was Universe/Multiverse supposed to be disabled in apt by default?  (and then silently enabled by codec-install and software center when you install an appropriate package)?  I don't see the point other than breaking apt:// links
[00:56] <persia> #ubuntu-desktop might be handy as well, for the bits about how the Deskop packages work with bzr, etc.
[00:56] <persia> YokoZar: Not anymore.  Used to be that way.
[00:56]  * persia wishes multiverse was still disabled, but ...
[00:56]  * jdong giggles at http://jdong.mit.edu/~jdong/wtf.png
[00:56] <jdong> am I supposed to say yes or no?
[00:56] <YokoZar> persia: Apparently apt://ubuntu-restricted-extras  doesn't work if it's the very first thing you do after install
[00:57] <jdong>                    │ Default package if none is detected.  │
[00:58]  * YokoZar wonders why jdong is installing checkbox on a terminal session...
[00:58] <persia> jdong: ubuntu-bug to the rescue!
[00:58] <YokoZar> persia: By the way do you know if there's a sort of bzr-hg tool?  I know we have bzr-git and now there's git-hg too
[00:58] <jdong> YokoZar: I don't know what checkbox is and why it's on this system I'm do-release-upgrading.
[00:58] <YokoZar> jdong: it's a QA tool that's only graphical
[00:59] <jdong> YokoZar: oh.
[00:59] <jdong> well List of jobs to blacklist: Suites Blacklist: ____________
[00:59]  * jdong is gonna just assume blank....
[01:00] <persia> jdong: I have a suspicion there is because I've heard of folks doing hudson with bzr, but ask in #bzr
[01:00] <persia> YokoZar: It's not only graphical: the primary frontend is graphical.
[01:00] <YokoZar> Yes, true
[01:01] <YokoZar> I haven't run it on a headless setup in forever because all the tests I cared about were the ones that crashed X
[01:01] <persia> heh.
[01:02] <RAOF> YokoZar: I'm pretty sure that launchpad is now using bzr-hg to mirror mercurial branches, so I'd guess that it's out there *somewhere* :)
[01:02] <YokoZar> woop woop
[01:29] <KIAaze> RAOF: I'm having problems adding a PPA to the i386 base.tar.gz. Do you know how to do that?
[01:29] <KIAaze> (I switched to #ubuntu-packaging)
[01:42] <arand> Regarding
[01:45] <arand> Regarding https://bugs.launchpad.net/bugs/519541 I'm wondering if it's worth looking for a small diff here? Is the new package still not very appropriate for a SRU, and hence narrowing down the error is a worthwhile pastime?
[01:46] <psusi> well that's weird... why is #ubuntu+1 invite only?
[01:46] <JanC> psusi: because there is no ubuntu+1
[01:46] <arand> psusi: It's shut down, until 6th
[01:47] <psusi> odd to close the channel though...
[01:47] <JanC> #ubuntu-1 is to discuss the next version, and that has to be started still  ;)
[01:48] <persia> arand: Yeah, it would need a cherrypicked fix.
[01:48] <persia> psusi: That channel always goes away on release.  It usually opens again after the first milestone or so.
[01:48] <JanC> psusi: if you want to party, go to #ubuntu-release-party  ;)
[01:49] <arand> persia: Ok, then I'll carry on.
[01:49] <psusi> shame that dmraid support regressed at the last minute...
[01:49] <TerminX> is the 6th supposed to be when the maverick repo opens?
[01:49] <persia> arand: Good luck.  I recommend focusing on stacktraces, rather than on the upstream changes.  Use the upstream changes as reference when trying to find a fix once you find the interseting bit of the stacktrace.
[01:50] <persia> TerminX: It's usually mushier than that: in that the repo first needs to be defined, and then it needs to get toolchain uploads, and sometimes multiple revisions, and then it's open for general use.
[01:50] <JanC> on the 6th most developers will probably be in the middle of nowhere somewhat south of brussels  ;)
[01:51] <persia> TerminX: I'd say it's a safe bet that the repo will be open before the 9th, but wouldn't want to promise that it's definitely open on the 6th (although that's likely)
[01:51] <persia> JanC: Why, is there another event happening?
[01:51] <JanC> persia: UDS ?
[01:51] <TerminX> ah, okay.  I usually switch to the new repo within a couple of days after it opening
[01:52] <TerminX> I ran debian unstable for years until warty opened
[01:52] <persia> JanC: I didn't think that started until the 10th (and planned to arrive the 9th).  Will I be missing something?
[01:52] <TerminX> it was a no-brainer to switch since debian was moving extremely slowly at the time :p
[01:53] <persia> TerminX: Watch ubuntu-devel@ I'm sure it will be announced.
[01:53] <JanC> persia: you're right
[01:53] <persia> Oh good!
[01:53]  * persia was really not looking forward to that call to the travel agent
[01:54] <JanC> hehe
[02:19] <bthesorceror> does anyone have any suggestions for a newbie that wants to get involved in ubuntu development?
[02:28] <persia> bthesorceror: I've an entire collection, depending on the sort of thing you like to do.  What do you like to do?
[02:30] <bthesorceror> well my day job is a web developer for a university, but I am looking to get more hands on with the system and want to learn more about what makes it tick
[02:31] <bthesorceror> so I guess the real answer is I dont really know yet
[02:33] <persia> OK.  The way I usually recommend for folks that aren't sure is to get involved in bugsquad for some of the packages they use, and get to know any teams that work on packages that interest them.
[02:34] <persia> So, if you're interested in webservers, you'd want to hang out in #ubuntu-bugs and #ubuntu-server and see if you can track down (and maybe help fix) issues with the webserver.  If you get enough of that at work, and want to do something completely different in the evening, you might choose something different, like #ubuntu-bugs+#ubuntu-mythtv
[02:35] <bthesorceror> ok, that sounds like a good idea, thanks for the help
[02:35] <persia> bthesorceror: If you get lost, come back here, and ask for directions :)
[03:47] <ccheney> heh archive is so hammered i can't even use a cached approx to update, just apt-get update takes forever :-
[03:48] <micahg> ccheney: are you upgrading to lucid or just upgrading packages?
[03:48] <ccheney> micahg: trying to update karmic from my approx mirror then upgrade to lucid once that is done
[03:49] <ccheney> it might go a lot faster if i kill internet connection on the approx mirror box, heh
[03:49] <ccheney> it took 8 minutes to run apt-get update on a 12mbps connection
[03:49] <micahg> ccheney: ah, the trick I used is to update from a local mirror to lucid, then switch to main archive and update again before reboot
[03:50] <ccheney> well approx passes through to the real archive unless it think the connection is down so seems to be causing the slow down
[05:31] <pitti> Good morning
[05:34] <Hobbsee> morning pitti
[05:36] <ajmitch> morning pitti
[05:36] <StevenK> Hey pitti
[05:36] <StevenK> pitti: All ready for Maverick, or do you need another minute? :-P
[05:40] <pitti> StevenK: Look at https://bugs.edge.launchpad.net/~pitti/+assignedbugs?orderby=status and see how much I want to upload :-P
[05:40] <pitti> maverick! maverick! maverick!
[05:40] <StevenK> Haha
[05:41] <ajmitch> that's quite a pile of bugfixes to land
[05:42] <pitti> well, a lot are SRUs, too
[05:45] <Damascene> after I leave my system for along time I wake up in the morning on the sound of the fan
[05:46] <Damascene> not really but the sound is very high.
[05:46] <Damascene> and after I start using the system the fan calm down
[05:46] <Damascene> calms
[07:25]  * pitti ceremonially removes his intrepid chroot
[08:43] <dholbach> good morning
[08:46] <pitti> hey dholbach, happy TGIF!
[08:46] <dholbach> hola pitti
[08:46] <dholbach> TGIF indeed :)
[08:47] <pitti> TGIDAR, even
[08:47] <pitti> ("day after release")
[08:47] <m4t> hey, does anyone know if something changed with kernel-package in 10.04? initrd doesnt seem to be generated
[08:48] <pitti> m4t: is it supposed t  in the .deb? (note that Ubuntu doesn't use kernel-package)
[08:48] <pitti> m4t: the initramfs has been dynamically generated on kernel installation for ages
[08:49] <m4t> yea i think something is not in /etc/kernel/postinst.d
[08:49] <slangasek> highvoltage: thank you as well for your work coordinating on the release!  It was a pleasure working with you
[08:49] <slangasek> highvoltage: as for FFe's, I'm afraid you'll have to suck up to someone else next cycle :)
[08:50] <rickspencer3> no FFE's next cycle!
[08:50] <ogra> no next cycle ?
[08:50]  * ogra is scared
[08:51] <rickspencer3> ogra yes next cycle, no FFEs next cycle
[08:51] <ogra> haha
[08:52]  * pitti makes a note to push rickspencer3 to the FFEs from the artwork/design/etc teams :)
[08:52] <rickspencer3> pitti, we'll be talking on Tuesday
[08:52] <rickspencer3> of course, I'm not the sabdfl ;)
[08:53]  * pitti goes back to this great fun called "tzdata update"
[08:53] <pitti> go Argentina
[08:53] <rickspencer3> no rest for the weary
[08:53] <rickspencer3> thanks pitti
[08:57] <m4t> hrm i had to manually copy initramfs to /etc/kernel/postinst.d, but it made the initramfs
[08:58] <m4t> don't recall having to do that in 9.10
[09:15] <m4t> hah, my progress bar at boot is like 8bit ansi art...very low res. any idea why that might be?
[09:16] <m4t> prolly my vga mode i guess
[09:22] <hrw> vga mode... I hope that 10.10 will get more framebuffer drivers into alternate installer (or lvm/raid/crypto etc support into normal one)
[09:26] <m4t> for some reason update-initramfs isnt bringing the right modules into the initrd
[09:26] <m4t> its skipping radeonfb for example
[09:31] <m4t> i just specified it in /etc/initramfs-tools/modules...that worked
[09:33] <virtuald> that's because it's blacklisted because it doesn't work well
[09:40] <epochfail> hmm. wow.
[09:41] <epochfail> my boot up time improved to 30 seconds to give me a complete desktop on a crappy netbook
[09:41] <epochfail> good work :D
[09:53] <highvoltage> slangasek: heh :)
[10:13] <seb128> did somebody read any bug about fsck being stucked around 90% and use lot of cpu?
[10:13] <seb128> didrocks and I just got the same issue today
[10:14] <seb128> 88% to 91% take like twice the time usually full fsck takes
[10:14] <pitti> this rather doesn't sound like a plymouth problem, though (too specific on the percentages)
[10:14] <seb128> the cpu seems to be quite busy hearing the laptop noise
[10:15] <pitti> the total percentage is calculated from the fsck stage and progress within that stage
[10:15] <pitti> perhaps that particular one just took very long
[10:15] <seb128> it's weird that didrocks and I just got the same issue today
[10:15] <seb128> well if you skip a fsck it should trigger again on next boot?
[10:15] <didrocks> yeah, that was very weird. I was thinking I was an isolated case
[10:16] <seb128> because I stopped it and reboot and I didn't get it to trigger again
[10:16] <seb128> I'm wondering if fsck was done running but plymouth didn't notice
[10:16] <joaopinto> why did you both get a full system check at the same time in the first place :) ?
[10:17] <seb128> I think mine was just the normal "n uncheck mounts" one
[10:17] <didrocks> I guess it's the same for me. I saw that a lot of previous one was just ignored (as if I triggered C) IIRC
[10:17] <didrocks> but I didn't cancel them myself
[10:19] <joaopinto> you coud try to reproduce with /forcefsck
[10:21] <seb128> joaopinto, where do you specify that? grub?
[10:22] <joaopinto> there is an option on grub, but you can do it at the fs level: sudo touch /forcefsck
[10:23] <seb128> joaopinto, let's try that, thanks
[10:25] <joaopinto> I did have an issue with the fsck hanging for a long time on the 70%, but I had the idea that was identified and fixed during beta/rc
[10:30] <arand> I had a stuckage at 74% after a /forcefsck as seen by others: https://bugs.edge.launchpad.net/ubuntu/+source/plymouth/+bug/554737   New very similar bug? Or this one hanging around still?
[10:33] <sladen> actually, I think I may have been that a week ago
[10:33] <seb128> arand, thanks
[10:33] <seb128> didrocks, pitti: ^ seems similar
[10:33] <sladen> a reboot cured it (the fsck had finished sufficiently)
[10:34] <sladen> my dread was that a reboot in the middle of a half finished fsck would just fsck again, but that didn't happen
[10:34] <didrocks> seb128: right, seems similar. I'm rebooting to have a try there too…
[10:34] <pitti> sladen: ah, perhaps it did crash then
[10:34] <pitti> seb128 ^ I mean
[10:34] <arand> For me, I had to get rid of plymouth (I assume, booting without quiet and splash) to get past it... testing in a vbox as we speak..
[10:35] <Tm_T> oh, was about to ask why fsck leads to boot problems...
[10:36] <sladen> pitti: I think it hung, I left it 5 minutes, then grumbled and rebooted.  So either that was enough time to get fro 75% to 100% (without displaying any progress), or the display of the progress is badly calibrated in the first place
[10:36] <Tm_T> seems to me that after checks are finished, boot doesn't continue
[10:37] <Tm_T> been 15 mins after last partition checked and no proceeding
[10:39] <Tm_T> sladen: when I tried with plash, percentages crawled to 90 and then stopped, so for whatever reason it's not reliable at all
[10:39] <arand> Yes, When I turned of graphical boot the fsck just stated "clean" and it booted fine... However if I only booted in graphical it was stuck in a loop..
[10:39] <Tm_T> crawl = several minutes per percent with no disk activity
[10:41] <sladen> arand: if you leave it 10 minutes first, then reboot?
[10:42] <arand> sladen: I'll do that... It's a virtualbox.
[10:42] <didrocks> (the fsck after reboot is proceeding there)
[10:43] <arand> Hmm, it's ~5-10 min now since booted, it halted on 70% and has now crawled to 74%..
[10:44] <Tm_T> arand: might be ready already
[10:44] <Tm_T> if no apparent disk activity...
[10:46] <didrocks> arand: same here :)
[10:46] <didrocks> 74% too, let's see who will win
[10:47] <Tm_T> it'll crawl up from there while doing nothing
[10:47] <arand> Oh! This is interesting, if I jump out to a tty (ctrl+alt+left) wait a while, and the jump back, it has moved much faster, otherwise it takes almost a minute or so per percent, if at all.
[10:48] <Tm_T> OOH! I waited long enough, boot continues (:)
[10:48] <Tm_T> ~30 minutes doing nothing
[10:49] <arand> And when I jump to the tty I see the fsck... 0.3% non-contiguous... message, which should indicate that the fsck is in fact done, right? the fsck message is printed each time I jump out.
[10:50] <didrocks> I confirm there too (well, reprinting is maybe due to fb handling), but normally, that means it's done
[10:59] <arand> It sound a lot like 554737 revisited, or is it to be considered new? Bug #571707 doesn't seem to be this one..
[11:00] <hrw> fsck on start is a thing which needs improvements. I did not yet know how it is in ubuntu but in Debian I feel that strange (even as 11 years Debian user). I understand that when 'fsck -a' fails then user has to do something. but on my machines I usually do "fsck" and press enter key to get all "fix <y>" accepted. normal stndard users will probably do similar.
[11:00] <didrocks> arand: I pretty agree that should be part of it
[11:02] <didrocks> arand: there is already a bootchart asked by keybuck. It seems we are all struck by it and the importance is already high (I'm at 90% right now)
[11:03] <arand> didrocks: Yes, seems like a nasty one...
[11:07] <apw> pitti, yo ... maverick burn down ... i know its real early but as we use the WI db to visualise our commitments list wise i am interested in getting the maverick.db building ... wondering when you might be planning to start
[11:08] <pitti> apw: I'm happy to start ASAP, but for that to work we need to create maverick in LP first
[11:08] <pitti> otherwise you can't target specs to it, read milestone dates, and so on
[11:08] <apw> pitti, damn good point :)
[11:12] <arand> didrocks: Would you say it's probably the latter bug then? That one states that there is no output on the ttys...
[11:13] <Tm_T> seems like fsck does its job normally but plymouth doesn't act accordingly
[11:13] <arand> Yes, especially since if you jump out to a tty it proceeds properly and boots fine.
[11:13] <didrocks> arand: I would say the root cause should be the same. After printing or not on tty can be related to framebuffer handling on various graphic card… (maybe adding a comment on the bug report there ?)
[11:14] <Tm_T> without plymouth graphics, it spits out fsck results to tty and then wait 30 minutes here
[11:17] <Tm_T> this in physical hardware, with old grub
[11:24] <arand> Tm_T: For me the boot takes less than a minute if I disable splash & quiet along with /forcefsck
[11:25] <arand> (virtualbox)
[11:27] <didrocks> ok, partition 1 finished, partition 2 now
[11:29] <arand> didrocks: You really going to sit through it to the end?
[11:29] <didrocks> arand: well, I have my netbook, so, not that a big deal :)
[11:31] <arand> didrocks: Well, if you just jump out to tty it should finish much quicker, at least if it's the same thing... and unless you aim to get som full gory debug out of it...
[11:32] <didrocks> arand: right, just have to jump for more than 4 seconds apparently
[11:32] <didrocks> arand: if you jump and come back, it doesn't
[11:32] <joaopinto> uff, I am sure plymouth/mountall will be the show stopper winners on 10.04
[11:34] <didrocks> joaopinto: well, if it's fixed soon enough, people installing lucid won't have the time to reboot 30 times (there is still the issue with people upgrading though)
[11:34] <arand> The logs just posted on Bug #571707 is a nice display of plymouthd (presumably) doing the exact opposite of the intended...
[11:35] <slangasek> mvo: <Dave> I mark Lucid a Success. Even my ability to break things that should not be breakable was no match for the upgrade process!
[11:35] <slangasek> mvo: congrats :-)
[11:36] <arand> Well, it's (seemingly) easily worked around by switching to tty, but that's not a good consolidation for most... I discovered it completely by mistake when trying to switch host virtual desktops, which got picked up by vbox instead :S
[11:37] <joaopinto> didrocks, there were too many issues being fixed too late on the development cycle, not enough time for broader testing, anyway the change was a challenge, I don't want to sound negative
[11:38] <arand> Do you think we should add a plymouth task there as well?
[11:38] <didrocks> arand: I was swithing to a tty, but too quickly for seeing the benefit on the time. I guess it's not easily discoverable :/
[11:39] <didrocks> arand: I think keybuck is on it as he answered, so he will triage if it's mountall or plymouth himself, I would say
[11:39] <arand> didrocks: No, as seen by the orig reporter as well, who apparently just concluded that tty was empty.
[11:40] <didrocks> arand: maybe we should ping him directly when he'll be online to point him to the last debugging info
[11:40] <mvo> slangasek: yipiee
[11:44] <arand> didrocks: Likely a good idea, sooner the better..
[12:37]  * cjwatson starts pushing maverick seed branches
[12:38] <xnox> cjwatson, =)))))) horay
[13:18] <Damascene> if some one want to build a distribution based on ubuntu and if the some missing translation were fixed. will he get ubiquity updated with the translation?
[13:21] <cjwatson> Damascene: we'll do a translation update for 10.04.1
[13:27] <dmart> kees,asac: hi, do you have a moment to talk about https://blueprints.launchpad.net/ubuntu-arm/+spec/arm-m-missing-security-features
[13:28] <jdstrand> dmart: fyi, kees doesn't usually come online for about ~4 hours
[13:29] <dmart> jdstrand: thanks, I'll try to catch him later
[13:31] <dmart> asac__: I can probably draft that blueprint in consultation with relevant kernel guys, but I need input on what the missing features actually are... is there someone other than kees who knows?
[13:31] <asac__> dmart: security? kees posted stuff in the summary
[13:31] <asac__> he can elaborate on that
[13:32] <dmart> asac__: ah, it's on the whiteboard.  OK, I'll see where I can get to
[13:33] <jdstrand> dmart: actually, it is more like ~3 hours -- I forgot which timezone *I* was in
[13:33] <jdstrand> :)
[13:33] <dmart> jdstrand: OK! thanks... maybe I can catch him before I go home after all :)
[14:14] <mvo> cjwatson: hi, for bug #540579 I would like to add a workaround in update-manager
[14:15] <mvo> cjwatson: I just got a system where the bug happens (just fyi)
[14:20] <pitti> YokoZar: is there a bug for the dssi-vst upload? As an SRU it needs some place to collect testing feedback, and standard policy is to have a bug for that
[14:20] <pitti> YokoZar: mind reuploading with an LP: # reference?
[14:24] <cjwatson> mvo: oh, right, yeah, that one - I think I sent mail about that a while back?
[14:25] <cjwatson> yes, I think it probably does need a u-m workaround
[14:26] <mvo> cjwatson: right, I will prepare something and send to -proposed, should be easy. I kind of ignored it because of the idea of moving a fixed version to -updates, but thinking again its best to add a u-m fix too
[14:31] <zul> pitti: can you reject the php5 upload to lucid-proposed please?
[14:31] <Damascene> hi,
[14:31] <pitti> zul: I was gonna ask you about it -- a new binary in updates?
[14:32] <Damascene> I want to start main-inclusion-request for mlterm for this bug to be fixed, bug #562130
[14:32] <pitti> zul: (rejected)
[14:32] <zul> pitti: yeah...bad idea i know
[14:32] <Damascene> could any one help me on doing it
[14:32] <Damascene> please
[14:33] <zul> pitti: thanks
[14:42] <Ixan> is there any way to automate the confirmation of accepting the license for sun-java6-jdk? my company has a distribution agreement (or something like that)
[14:43] <lifeless> yes, its documented in the wiki
[14:43] <Ixan> oh, okay. I'll search better next time. thx
[14:45] <Damascene> so no help on main-inclusion-request. I should go ahead and do what I can.
[14:46] <Damascene> I've read this https://wiki.ubuntu.com/UbuntuMainInclusionRequirements
[14:47] <ScottK> Damascene: The best thing to do is find someone who is interested in this and going to be at UDS to proposed a spec about it.  If that's done and it gets approved it smoothes the way for the MIR later.
[14:47] <ScottK> (Note: I am not that person)
[14:47] <Damascene> that person should be ubuntu member?
[14:48] <joaopinto> Damascene, is that related to the RTL issue and mlterm ?
[14:48] <Damascene> yes
[14:48] <joaopinto> Damascene, It's not clear for me that including mlterm was the accepted solution
[14:49] <Damascene> joaopinto, are you talking about the person that doesn't want any RTL text in terminal and his friend?
[14:50] <joaopinto> Damascene, no, I am talking that it doesn't make much sense to propose mlterm to be included on main to workaround a bug, when it was not decided if that's the best course of action for the bug resolution
[14:51] <Damascene> so we should vote?
[14:51] <joaopinto> bug resolutions are not democratic :)
[14:52] <Damascene> np. what should I do
[14:53] <Damascene> in another word who should accept the solution
[14:55] <joaopinto> Damascene, there was a recent blog post on planet about someone with would like to fix VTE
[14:55] <joaopinto> I mean, more like asking for help on where to start to look at
[14:56] <Damascene> could you give me a link?
[14:58] <joaopinto> I don't have the link :\
[14:59] <Damascene> any way I was just trying to see ubutnu more suitable for rtl languages users
[15:03] <Damascene> joaopinto,  I've searched for rtl vte and terminal but no luck in http://planet.gnome.org/ are you sure it's gnome planet
[15:06] <joaopinto> ops sorry, I mean ubuntu planet
[15:06] <Damascene> you didn't say it's gnome planet :)
[15:11] <Damascene> google led me to a link but when I open the page nothing mention the problem
[15:11] <Damascene> http://planet.ubuntu.com/?PHPSESSID=c35868b27a18dab48732329d71912a5f
[15:11] <Damascene> search string: terminal right to left site:http://planet.ubuntu.com/
[15:12] <hyperair> crimsun: the 01Pulseaudio script seems rather.. broken on lucid.
[15:12] <hyperair> crimsun: seems like an invalid invocation of su
[15:13] <hyperair> crimsun: and a misplaced '
[15:13] <Damascene> so VTE is not going to be fixed. any one could help in having mlterm installed for RTL users?
[15:14] <joaopinto> Damascene, aren't there locoteams for the affected countries ?
[15:15] <Damascene> yeah. I've contacted some of them and even subscribed some of them
[15:15] <Damascene> what do you want them to do?
[15:23] <ScottK> You might talk to dpm since it seems to relate to language support.
[15:33] <dpm> thanks for the heads up, ScottK. Damascene, are you going to UDS or know someone who could bring up this subject there? I can add it as a topic to a session, but I lack the tecnical knowledge on vte/mlterm to be able to commit to making it available, and it'd be good to have someone to discuss it with
[15:33] <hyperair> crimsun: i'll take back what i said about "rather broken" and replace it with "broken in so many ways that I can't even begin to imagine what went wrong"
[15:34] <Damascene> dpm, thank you. I don't know what the UDS is and I don't know any one who can help.
[15:36] <dpm> Damascene, ah, sorry. UDS is the Ubuntu Developer Summit, where the discussion for the next Ubuntu release takes place. It happens every 6 months, at the beginning of a release cycle, and the next one is going to Be in Brussels in a couple of weeks time -> https://wiki.ubuntu.com/UDS
[15:37] <Damascene> I can't go there for sure :)
[15:37] <dpm> it's open to everyone interested in contributing to Ubuntu and working towards making it rock even arder, basically
[15:37] <dpm> harder, I meant
[15:38] <Damascene> could you make it a session topic
[15:38] <Damascene> lease
[15:38] <Damascene> please
[15:40] <dpm> Damascene, I'll add it as a topic for one of the translations roundtables. Remember you can also participate remotely at UDS via IRC and listening to the session's voice stream. There is a class next week on IRC where Jorge Castro will explain how to participate remotely, if you are interested -> https://wiki.ubuntu.com/UbuntuOpenWeek (on Friday)
[15:40] <Damascene> ok
[15:41] <Damascene> dpm, would it help if we brought one of mlterm developers?
[15:41] <Damascene> or it's just ubuntu who can decide?
[15:42] <ivanshih> hi~ all
[15:43] <ivanshih> i have one problem in ubuntu 10.04 + thinkpad x201
[15:43] <ivanshih> the battery is discharged
[15:44] <ivanshih> does anyone can help me ?
[15:44] <Damascene> hi ivanka
[15:45] <Damascene> read the topic please
[15:45] <ivanshih> hi
[15:45] <Damascene> I think it's better to ask in #ubuntu
[15:45] <ivanshih> sorry
[15:45] <ivanshih> ^^
[15:48] <Damascene> he probably will be lost in the channel jam
[15:49] <Damascene> 1782 user
[15:49] <Damascene> you should start to offer channel based on problem kind
[15:50] <Damascene> #ubuntu-boot-problem, #ubuntu-update-problem
[15:50] <Damascene> :)
[15:50] <joaopinto> Damascene, that would allow more specialized support, but would be a burden to manage
[15:52] <Damascene> I think it's better than users get lost in channel jam
[15:53] <dpm> Damascene, it would definitely help if one of the mlterm developers could assist, either in person or remotely
[15:53] <joaopinto> and it would also allow to have developers to be present on related channels
[15:54] <Damascene> joaopinto, exactly
[15:54] <Damascene> some one should work on this
[15:54] <Damascene> dpm, I'll try to contact the developer
[15:54] <joaopinto> Damascene, there is an ubuntu irc group I think, you could suggest to them
[16:00] <Damascene> bug 392799
[16:09] <crimsun> hyperair: um, how? I'd have expected such errors to show up during local testing and in suspend-failure reports.
[16:10] <hyperair> crimsun: i'd have expected your local testing to show you something >_>
[16:10] <crimsun> hyperair: where is it broken?
[16:10] <hyperair> crimsun: did you look in /var/run/pm-utils/pm-suspend/storage/state:user:{source,sink}*?
[16:10] <hyperair> all the su invocations
[16:10] <hyperair> every single one of them is broken
[16:10] <hyperair> -l causes them to no-op
[16:11] <hyperair> and then savestate and restorestate are part of the commands passed into su
[16:11] <hyperair> but savestate and restorestate are pm-utils functions, and don't exist within su's internal shell.
[16:11] <hyperair> i mean the shell launched by su
[16:12] <hyperair> crimsun: i've got a patch ready, and am pushing the branch
[16:12] <crimsun> hyperair: ok, make user to incorporate my latest changes
[16:13] <hyperair> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/572391
[16:13] <hyperair> crimsun: i just branched from ~ubuntu-core-dev/pulseaudio or something
[16:13] <hyperair>   parent branch: bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/pulseaudio/ubuntu/
[16:13] <hyperair> that
[16:16] <crimsun> I can't look at it now (work); ping TheMuso if it hasn't been acted on it 12 hours
[16:16] <hyperair> crimsun: sure.
[16:16] <hyperair> crimsun: for now i'll just file a merge requet
[16:16] <hyperair> request*
[16:16] <crimsun> thanks
[16:16] <hyperair> crimsun: oh and the script doesn't fail, it just no-ops
[16:17] <hyperair> crimsun: so suspend/resume still occurs, which is why you don't get a suspend-failure report
[16:53] <cjwatson> james_w,jml: please initialise source package branches for maverick
[16:53] <james_w> cjwatson: roger
[16:54]  * jml breathes a sigh of relief
[16:54] <jml> (just because I wrote large chunks of the code doesn't mean I know how to use it)
[16:56] <cjwatson> jml: feel free to instruct us to take your name off https://wiki.ubuntu.com/NewReleaseCycleProcess
[16:57] <cjwatson> starting initial maverick publication now
[16:57] <jml> cjwatson: will do.
[17:41] <YokoZar> pitti: There's currently no binary at all so I figured it would be simple but sure I can make a bug link
[17:45] <YokoZar> Regardless, reuploaded, bug linked https://bugs.edge.launchpad.net/ubuntu/+source/dssi-vst/+bug/572470
[17:57] <cjwatson> pitti: what was the outcome of the discussion on whether to sync from testing or unstable?  I confess I'm not up to date on the mail thread
[17:57] <b52> hey guys
[17:57] <cjwatson> pitti: I'm switching MoM over now, but I'll leave it at testing until I hear otherwise
[17:58] <cjwatson> (since that's the more conservative choice)
[17:58] <b52> i would like to use notify-osd with arch, but im not sure how to send a notify to get this nice brightness popup with the horizontal bar
[17:58] <b52> whats the trick?
[18:01] <hyperair> b52: patch gnome-power-manager.
[18:01] <b52> i dont use gnome
[18:01] <hyperair> oh whoops
[18:01] <hyperair> then i have no idea.
[18:02] <hyperair> i thought notify-osd was only for GNOME thugh
[18:02] <hyperair> though*
[18:04] <cjwatson> doko: chroots aren't ready yet, but lamont should have that going shortly (see #soyuz).  Please go ahead and start uploading toolchain packages
[18:05] <cjwatson> doko: I'll be away for a few days; any other archive admin can push them through, or indeed in this case I think it's fine for you to push your own uploads through unapproved.  Just get some other admin to approve anything that's NEW, please
[18:06] <cjwatson> slangasek: for the record, I have done everything up to and including step 21 on NewReleaseCycleProcess; handing off to whoever wants to continue now
[18:08] <cjwatson> (fed up of mistyping 'maverick' already, but I'm sure I'll get used to it ...)
[18:09] <arand> cjwatson: Are you in charge of approving non-developer messages on ubuntu-devel mailing list? I sent a request for re-visiting swap-on-file a few days ago, you know how long it normally takes to go through/get rejected?
[18:10] <cjwatson> arand: I'm one of the moderators, but I'm about to finish for the week
[18:10] <cjwatson> pretty sure we're already planning to revisit swap-on-file anyway
[18:11] <JanC> arand: I think mods will look at the queue every couple of days or so
[18:18] <maxb> What component of the system is in charge of assigning names to partition device nodes (specifically deciding whether they get a 1 or p1 style suffix) ?
[18:25] <arand> (Augh disconnects!) JanC: cjwatson: Ok, just wanted to make sure, since it'd probably be a good idea if it made it to uds... I was looking through the blueprints yesterday and didn't see any for it, and there wasn't much talk about it for lucid from what I saw....
[18:28] <ccheney> hmm maverick appeared but then disappeared again
[18:28] <kees> dang, I keep missing dmart.
[18:28] <kees> ccheney: just like a meerkat
[18:28] <ccheney> heh
[18:29] <ccheney> it was apparenty only there long enough for me to add it to my sources.list and then went away
[18:32] <cjwatson> ccheney: that's probably just differences between mirrors
[18:33] <cjwatson> it'll come back eventually
[18:33] <cjwatson> it's certainly still there on the master
[18:36] <mvo> YokoZar: could you have a look at bug #571999 when you have a moment?
[18:37] <YokoZar> mvo: it should both conflict and replace it...
[18:38] <YokoZar> mvo: actually nevermind it's the conflict line that's wrong, it's supposed to be << 1.1
[18:38] <mvo> thanks :)
[18:38] <mvo> just stumbled on it when looking at the upgrade reports
[18:38] <mvo> but I think I did enough of those for today
[18:38]  * mvo waves
[18:39] <YokoZar> mvo: wine is just a dummy package anyway at this point.  I suppose an SRU to Wine would fix that...
[18:39] <YokoZar> surprised this didn't come up earlier
[18:48] <mannyv> if i wanted to help with an SRU or two where would i look to find candidate packages?
[18:49] <ccheney> cjwatson: ah ok, yea i see it again now
[19:37] <Damascene> isn't it a problem with computer januiture that think it can delete everything not in a repository?
[19:37] <Damascene> if I installed google chrome it will show it ready to clean
[19:45] <b52> i would like to use notify-osd with arch, but im not sure how to send a notify to get this nice brightness popup with the horizontal bar
[20:06] <m4t> hi, im trying to debug plymouth; i modified any call to /bin/plymouth or plymouthd in /etc/init to use --debug or --debug-file=, but i don't see any messages or the output file
[20:07] <m4t> when plymouth comes up, even with radeonfb compiled into a custom kernel, i just get text-mode 'Ubuntu 10.04' and a similarly text-looking progress indicator, no background image. just text on black
[20:08] <m4t> is there a special boot image (eg. tux) that the ubuntu-generic kernel is using to provide the background? or is it something else i should be looking at
[20:10] <m4t> would it have to do with the rendering mode plymouth is using? i assumed it was using fb0 all the way, but maybe its using drm?
[21:07] <gartral> i have a serious question about he i7 CPUs and the way ubuntu handles sensors: why does a chip that only has 4 physical thermo-resistors show 8 seperate tempuratures? isnt this.. impossible..? also, how do i turn off detection of just the 4 HT threads while maintaining a real readout of the actual temps?
[21:52] <blistov> ubuntu 9.04 or 10.04.  running kernel matches installed headers.  building libipt_NETFLOW (from cvs) against running kernel/headers.  insmod results in "invalid module format".  Idea's?
[22:29] <crimsun> blistov: generally wrong config.
[22:30] <crimsun> hyperair: thanks, reviewing
[22:30] <hyperair> np
[23:09] <|shad0w|> sorry for crossposting from #ubuntu but I don't think I'll get much help there
[23:09] <|shad0w|> could i install kubuntu desktoop on ubuntu 9.04 and what size it need on har
 Fast booting in 10.04 seems to be affecting network initialization on one of my network interface. Putting a sleep in pre-up seems to work around the issue but this is a hack. Is there anyway to delay the boot process after udev/module loading?
[23:09] <|shad0w|> meh, bad copy/paste