[00:17] snow_ru: problems with 64-bit environments are not unheard of, but are rare in Ubuntu in general these days, and rarer still in main [00:20] cjwatson, yes, as soon as programmers are aware of the 32 and 64 [00:20] snow_ru: they are for the most part, people just get lazy. [00:20] snow_ru: The "new" still scares them even though it's not new tech by any means. [00:21] "new"? [00:21] I've been running 64bit since before most supported it. [00:21] snow_ru: all one has to do is abide by standards - you generally don't need to special-case them, and usually these days compiler warnings pick up the most common bugs [00:21] snow_ru: yeah, people fear change. [00:21] snow_ru: mostly large corporations. [00:22] xorl, many guys still assume they will run on 32 [00:22] anyway, amd64 (or x86-64, whatever you want to call it) has been a first-class supported architecture on Ubuntu since the project began, so "new" is not particularly relevant. [00:22] snow_ru: exactly. [00:22] and do crazy tricks [00:22] I program myself and have to modify all kinds of code. [00:22] working with apps that only support 32bit memory stacks is hell. [00:23] xorl, with the assumption of 32, they do very "clever" tricks and it's very hard to figure out [00:23] snow_ru: Oh I find em most of the time. [00:23] it doesn't seem like this conversation is directly about Ubuntu - please take general discussion of how programmers suck elsewhere. :-) [00:23] Not very hard to tell crappy math. [00:24] cjwatson: haha, sure deal :) [00:25] any statistics on the languages used in the main ? [00:25] not that I know of [00:28] vast majority will almost certainly be one of C, C++, Perl, Python, with a smattering of various others [01:01] * snow_ru wants to apply for ubuntu dev position [01:30] anyone here [01:30] ??? === dendro-afk is now known as dendrobates [01:49] wow... I found an old copy of dd I had modified to use aio and it does 242 MB/s reading my ssd compared to 230 from stock dd with same settings [01:50] iirc, the manufacturer specs only say it does 230 === rickspencer3_ is now known as rickspencer3 [01:52] ohh dear.. make that 247 when I turn ncq back on [02:27] vvsz- [02:41] nixternal, the fact that you have to ask implies a bug that they aren't voiced correctly to you as the user in jockey [02:42] well it says sta is preferred [02:42] the non-free one [02:42] it doesn't support scanning which sucks [02:48] sure it supports scanning [02:48] iwlist scan? [04:04] what is the syntax to do in place sed replacement? [04:04] doh i just need to read better [04:04] -i does it [06:24] Riddell, stgraber: any progress on the branding question? [06:36] Good morning [06:37] kees: python> mind to comment on bug 542372 then? [06:37] Launchpad bug 542372 in python3.1 "MIR for basic python3 stack" [Undecided,Fix committed] https://launchpad.net/bugs/542372 [07:18] good morning === tkamppeter_ is now known as tkamppeter [07:20] If I had a bug assigned to me + "In Progress" whilst working on it, am I supposed to unassign myself and put it to another status when I request sponsorship? [07:40] maxb: the sponsorship queue isn't based on bug status, so I don't think you need to [07:45] Hi all [07:46] If I have a general complaint about Canonical software/packages, where should I drop the complaint? [07:55] Jeeves_: Bug reports go on Launchpad of course; other comments may find a more appropriate venue, depending on what the actual package is. [07:57] RAOF: Well, it's more a observation about Canonical packages. So I guess it would be more efficient to drop the complaint than to file bugs against all packages. Don't you agree? [07:57] What packages are you talking actually about? [07:59] pyhton-software-properties, for example [07:59] Packages in the main archive, without manpages. [08:00] Jeeves_, thats definately a bug, file it [08:00] ogra: I have [08:00] Jeeves_: add-apt-repository lacks a man-page. that is correct and a bug. help is much appreciated in fixing it [08:00] great [08:02] mvo: I would expect the developer (you?) to be able to write a manpage in about five seconds. Instead of releasing it without a manpage and sat 'go ahead, fix it. You've got the source'. [08:02] I would expect Canonical to have a quality standard, which says 'We dont release software about which Lintian complains' [08:04] Jeeves_: its a valid complain, but its not always that easy, there are a lot of things to do and a lot of bugs to fix. [08:05] mvo: By creating new bugs, you don't make your work much easier, do you? [08:06] Jeeves_: sorry, I have no interesst in continue a conversation like this. please note that I understand that its a valid complain and I don't like it either, but its not that simple. I don't think its unfair to call in this cases for help from the community (and I'm certain someone will step up and help wit hthat task) [08:08] Ok, so back to my original question. Where can I drop complaints about this, other than at the developers which are to busy? [08:10] * pitti suggests /dev/null [08:10] complaints are just about the worst possible way to motivate people [08:11] pitti: Ok, let me rephrase. Whom should I talk to, to motivate Canonical to uphold a quality standard that gives them credit and prevents complaints, and useless bugreports? [08:12] Jeeves_: there are certainly much more pressing bugs which need attention first [08:12] so by putting more resources into things like writing manpages, we had to drop resources from fixing really nasty things [08:12] * pitti points to bug 445852 [08:13] Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/445852) [08:13] Jeeves_: but in general, ubuntu-devel-discuss@ is not a bad place to start discussions about the project's direction and workflow [08:14] Jeeves_: wow. that's some astouding arrogance there [08:14] may I suggest you take it elsewhere? [08:14] Chipzz: I don't recall being arrogant. Explain? [08:15] pitti: That's a nasty bug indeed. [08:15] For starters, you claim that workign on missing manpages should be the #1 priority, without apparently knowing what the project is working on [08:15] and overgeneralize this as if we wouldn't care about quality [08:15] "09:02 < Jeeves_> mvo: I would expect the developer (you?) to be able to write a manpage in about five seconds." [08:16] that, too [08:16] Jeeves_: and no offence, but maybe it's more important to have something FUNCTIONAL than to have something perfect to the tiniest detail [08:17] and yes, I call supplying a manpage a MINOR detail [08:18] Obviously, functionality is more important than documentation. What would you document if it doesn't work? [08:18] Jeeves_: you obviously did not consider the fact that canonical has a limited amount of manpower, and a certain amount of goals to reach. [08:18] pitti: I never stated manpages are a #1 priority. I did say that I expect a manpage for professionally written sofware. [08:19] Chipzz: Ofcourse I did. [08:19] you obviously did not [08:19] Chipzz: Are there other things I did or did not do without knowing about it myself? [08:21] I suspect there are :P [08:21] but [08:21] obvious troll is obvious [08:21] pitti: I also did not say that canonical doesn't care about quality. The existance of LTS releases proof the opposite, so why would I say that? [08:21] one for the /ignore list [08:22] Jeeves_: lol. I think you did [08:22] Chipzz: Where, how? [08:22] at least the tone of what you said and how you said it implied hat [08:22] *that [08:22] Jeeves_: "motivate Canonical to uphold a quality standard that gives them credit and prevents complaints, and useless bugreports" [08:23] we do what we can, and we know Ubuntu isn't perfect. we wouldn't have 50.000 open bugs otherwise [08:23] pitti: That's because you did not approve complaints because complaints are unmotivating. [08:23] so we have to prioritize :) [08:23] pitti: I know it's not perfect, but it is one of the better Linux distributions. And I'm happy with it. [08:24] that's great to hear [08:24] I'm just trying to make a point, that if you write a manpage in a few minutes, it save you a bugreport, it saves you replying to that bugreport etc etc etc [08:24] And, it makes your users even happier [08:25] I agree [08:25] Jeeves_: writing a manpage doesn't take 2 minutes [08:25] it takes a lot longer than that [08:25] but still, writing a good manpage is not a "5 s" job, it's more like 30 minutes.. [08:25] Jeeves_: I'm happy to receive manpage contributions from you ;) [08:25] Chipzz: That kinda depends on the piece of software you're documenting, don't you think? [08:26] and more people are able to write manpages, that's why FOSS projects use bug trackers, so that everyone can contribute [08:26] pitti: I would estimate that writing the manpage content would take that much. but obviously a manpage also needs layout elements (groff or whatever is used markup) [08:28] Jeeves_: I would consider your complaint more valid if canonical were to write closed source software. but most of it is open source, so you can read the source... [08:30] Chipzz: But it's allready released, so too late. And obviously everyone can write a manpage. But by then it allready costs more time and bugs than necessary. [08:31] Chipzz: honestly, I don't think your aggressive defensiveness is helping the tone of this conversation. [08:32] tone it down, please. [08:34] Ubuntu developers can look after themselves and don't need others to defend them from criticism [08:36] cjwatson: ok, noted. although I think that Jeeves_' attitude is inappropriate and was reacting to that [08:37] cjwatson: I appreciate the work the canonical employees do, which is why I'm "defending them from criticism" [08:39] I think Jeeves_ should just file bugs where appropriate; Canonical doesn't have separate quality standards from Ubuntu for Ubuntu development, so it doesn't make sense to make this about Canonical; there is plenty of Ubuntu software maintained by Canonical employees that does have man pages, though doubtless it has different problems instead, nobody's perfect [08:39] Chipzz: Who's says I don't appreciate them? If I would care about it, I wouldn't be critical. [08:39] Chipzz: I can't speak for everyone, but I know I would prefer it if you were a little less vigorous. :-) [08:41] Jeeves_: you can be critical in a constructive way. but you attitude is hardly constructive... [08:41] *your [08:43] like I hear often, "complaints are welcome, especially wrapped with patch" [08:45] Tm_T: :) [08:47] mvo: i'm curious. what are these more complex issues that prevent add-apt-repository from sprouting a manpage? i'm more than willing to spend 5 minutes to write one, but i don't fully understand what add-apt-repository, nor the options it provides. [08:47] hyperair: I'm happy to help you with that, there are no more complex issues really, just someone needs to sit down and do it. [08:48] hyperair: and I'm currenly busy with other fixes that are higher on my priority list [08:48] 09:30 < Jeeves_> Chipzz: But it's allready released, so too late. And obviously everyone can write a manpage. But by then it allready costs more time and bugs than necessary. -> bugs don [08:48] mvo: okay, for starters, what options does add-apt-repository provide? [08:48] ugh [08:49] bugs don't cost anything, and time... in case a bug is files it doesn't necessarily take up time of a canonical employee, like pitti pointed out, anyone can contribute a manpage [08:49] you got truncated at "bugs don" [08:49] ah [08:49] hyperair: accidently hit enter. hence the subsequent "ugh" ;) [08:50] hyperair: it takes a single line for the form "deb http://foo.bar.com/ubuntu main universe" [08:50] Chipzz: ah =p [08:50] Or it can do stuff with ppa: [08:50] hyperair: it also supports a shorthand synatax for PPAs (and possible others in the future) [08:50] hm, and also something like ppa:pitti/postgresql, no? [08:50] and now I'll stfu :) [08:50] pitti: yes, that. [08:50] hyperair: like the line that pitti pasted [08:51] mvo: options? are there any? [08:51] -h doesn't document any besides -h [08:51] hyperair: no other options [08:51] okay then [08:51] hyperair: it needs to run as root (obviously) [08:52] mvo: right. =p [08:52] Jeeves_: the main root problem, if you must make it about Canonical, is that our staff are often overloaded with feature development, and something often has to give. Personally I usually write man pages first, but then on the flip side I tend not to do enough regression testing, which creates more bugs than forgetting to write a man page [08:52] hyperair: PPAs end up in sources.list.d dir [08:52] our internal standards are biased towards regression testing [08:52] mvo: and other things? [08:53] could someone please give-back apr-util? Thanks. [08:53] hyperair: it will get/add keys for PPAs automatically too [08:53] hyperair: I think thats it :) [08:53] mvo: okay cool [08:54] hyperair: wonderful, thanks a lot! just mail it or attach it to the bugreport [08:54] mvo: okay, will do [08:54] cjwatson: It's not really about making it about Canonical. More about the 'main' archive, which iirc, is Canonical responsibility because Canonical officially supports it. [08:55] mvo: er for non-ppa external repositories, where is it put? sources.list or sources.list.d? [08:56] hyperair: to the main sources.list [08:56] mvo: okay cool [08:56] hyperair: I guess that is something where a "--file=" option would come handy in the future [08:56] mvo: that would be cool [08:57] * mvo adds a FIXME in the source [09:03] hyperair: Thanks [09:03] Jeeves_: main does have elevated standards (https://wiki.ubuntu.com/UbuntuMainInclusionRequirements), but currently manual pages are not among them [09:04] and, even as the man-db maintainer, I'm not sure that that would make sense in all cases [09:05] cjwatson: I'm ofter curious for a description of a running daemon. [09:05] There's no direct need for extensive texts about options and so on [09:05] I'm not saying they shouldn't have man pages - merely saying that I don't think it makes sense to make it a requirement for main [09:06] I've probably put more effort into man pages than most people here :) [09:06] cjwatson: I'm not sure if I should be happy with that. :P [09:07] but it's not the most important thing [09:07] No, and I never said that [09:07] so, in particular, I don't think it would be appropriate to adopt a standard saying that we don't release software about which lintian complains [09:08] lintian is a tool to help developers, but many of its messages are inappropriate in certain situations, and the importance of the messages that are appropriate varies [09:08] That's true. [09:08] ubiquity produces a stunning number of lintian messages because it's so weird - but very few of those messages relate to the actual bug problems that it has in practice [09:09] Anyways, thanks for your time. Have to go in a meeting. [09:09] ttyl! === MacSlow is now known as MacSlow|afk [10:29] pitti: let's defer the units policy fixes to lucid+1 (including nautilus). [10:29] bdrung: okay [10:30] pitti: great. changing half is worse than changing nothing. [10:30] bdrung: well, wrt. nautilus it's already "half" right now [10:30] but yes, we certainly have more pressing bugs right now [10:31] pitti: yes, but the German translation uses "MiB" for example. [10:32] Could someone please give-back apr-util? Thanks. [10:32] pitti: my current plan is to write a library that can be configured to the users preferences. then we can port all apps to this library. [10:32] geser: done [10:32] bdrung: hm, I'm not sure whether this should really be user configurable, but if the GNOME guys agree with it, fine for me [10:33] pitti: reading all user comment there should be an option for base-2 [10:33] bdrung: ok, so like a gconf key for "geek" mode? [10:34] pitti: yes, gconf or something similar. the library should work with GNOME, KDE, XFCE, LXDE apps. [10:35] you don't want to add a new library only for that do you? [10:35] using glib seems right there [10:36] seb128: i think a new library is better, because not every app uses glib. [10:37] a separate lib seems quite overkill to me, too, TBH [10:37] seb128: there are some glib dev that didn't liked the g_format_size_for_display function. i don't know if they like to have 10+ new functions. [10:38] bdrung, GNOME will not use yet another lib for that details [10:38] units don't need translations, etc. so apps could just do the formatting themselves [10:38] pitti: but how do you want to have one configuration key to change all apps (including the Qt+ apps you are using in GNOME) [10:39] well, I don't want a configuration key :) [10:39] neither do I [10:39] at most this could be locale specific [10:39] but many user want [10:39] if you need one get a common configuration and let glib and qt respect this one [10:39] so that "2 kg" becomes "4.1 lb" for our American friends, or so :) [10:42] seb128: common configuration? does something like this exists? [10:44] bdrung, write a file on disk, both glib and qt should be able to read a file on disk no? [10:45] pitti: locale specificity does not work. preferring base-2 or base-10 does not depend on the location. === MacSlow|afk is now known as MacSlow [11:02] hi guys, I'm trying to aply quiet patch for grub but in ubuntu wiki there is advice to change 'quietboot' option to 'quiet' in a patch but I can't find option like this just function called 'quietboot_func', any hints? === MacSlow is now known as MacSlow|lunch === doko__ is now known as doko [11:42] manpage for add-apt-repository: http://people.ubuntu.com/~hyperair/add-apt-repository.1 [11:42] mvo: what do you think? [11:42] jdstrand: do you have some time to catch up with https://edge.launchpad.net/~ubuntu-archive/+subscribedbugs during your archive day today? there's quite some backlog with approved FFE syncs, and the like [11:44] hyperair: newline after the end of each sentence (nearly everyone gets this wrong) [11:44] the NAME section is formatted wrongly [11:44] cjwatson: really? [11:45] er how should i format it? [11:45] .SH NAME [11:45] add-apt-repository \- Adds a repository into the /etc/apt/sources.list or /etc/apt/sources.list.d [11:45] drop the .B and the two bits on separate lines [11:45] "really" to which? [11:45] nevemrind [11:45] ok [11:45] it was to newline after ... [11:45] see lexgrog(1) for documentation of this [11:46] ah, that's in 'info groff' somewhere [11:46] hmm [11:46] info groff --index-search Sentences [11:46] other than those two issues? [11:47] those were the two I noticed, I didn't see other serious typesetting issues; not qualified to review the substance though [11:47] imo we should have a wiki page documenting how to write a proper man page [11:48] i picked my things up from numerous places [11:48] cjwatson: okay, updated. [11:51] hyperair: personally I recommend groff_mdoc(7) anyway :-) [11:51] although that's a different macro set [11:51] it's logical markup rather than physical markup [11:51] hmm i see [11:52] invented by the BSD people, so you'll find it in use for e.g. ssh(1) [11:52] its only downside at the moment is that it doesn't interact very well with making the man page translatable, or at least I haven't been able to get po4a to cooperate with it [11:52] I think that's probably more of a po4a bug though [11:53] hmm [11:55] oh hell, they shut down my campus's ubuntu mirror [11:58] hello everyone, i'm having a problem with nouveau not recognizing my CRT (bad EDID) - against which package would i file a bug or which channel should i join? [12:11] What package do I assign bugs to for the PowerPC Alternate installer, suffering SEG faults ? [12:13] IntuitiveNipple: default for the alternate installer is debian-installer [12:13] (seg is not an acronym, BTW, it's short for "segmentation") [12:14] yeah, I know, I was being economical with keystrokes [12:14] Would you happen to know of a resource that might help me catch and debug the segfault? As it's running from the alternate CD its a bit basic! [12:16] IntuitiveNipple: usually it's bloody hard :-) [12:17] IntuitiveNipple: the dmesg should at least say which process is segfaulting [12:17] sometimes situational analysis is enough, or if it's late enough in the installer then you can 'anna-install strace-udeb' and try to get a strace [12:18] on tty4 I can see the syslog output that just says "segmentation fault". I've just found https://wiki.ubuntu.com/Installer/FAQ#How%20do%20I%20debug%20the%20installer? which suggests using strace [12:18] It's during the base-install phase - and I've already verified the CD is free of errors [12:18] hyperair: thanks! I have a look now [12:19] it seems to repeatedly happen as packages are unpacked [12:20] cjwatson: dmesg doesn't report the faulting process. I'll have to figure out this strace method [12:22] pitti: yeah, I was planning that today [12:26] hyperair: looks good, many thanks. added to bzr [12:35] jdstrand: thank you [12:38] cjwatson: It's writing stack-traces of seg-faults to tty1; into the ncurses-style windows so its all over the screen. Is there any way to separate that so it can be captured? [12:40] IntuitiveNipple: the kernel is just writing that to the foreground console, I think. your best hope is probably to boot with DEBIAN_FRONTEND=text and hope it reproduces with that frontend [12:41] cjwatson: Thanks, I'll try that later. What is weird is, the installer does seem to be making progress beyond the base-install, it's now asked for user details and is fetching stuff from the mirrors *fingers crossed* [12:41] I'll capture the syslog into USB key so it can be added to a bug report [12:43] cjwatson: Interesting: just seen an "Illegal instruction" report in syslog whilst setting up language-selector-common. Can you recommend someone I can talk to who knows about the PPC port? [12:46] jdstrand: planning to do some syncs today ? i'd need bug 543443 to be covered soon [12:46] Launchpad bug 543443 in maven-repo-helper "Sync maven-repo-helper 1.0.4 (main) from Debian testing (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/543443 [12:46] ttx: yes I am [12:46] jdstrand: cool :) [12:47] ttx: can you or kirkland respond to my email regarding libvirt 0.7.7 (sent to kirkland, cc'd you and ubuntu-server so it might have gotten filtered somewhere) [12:48] jdstrand: yes, it's on my TODO list [12:48] cool, thanks [12:48] jdstrand: still catching up, been at a conference those last days [12:48] ttx: no worries, I just wanted to make sure people saw it :) [12:49] jdstrand: nothing can escape my GTD system, resistance is futile [12:49] hehe [12:49] IntuitiveNipple: it used to be me, but it's been years; it sounds like something is miscompiled, but I don't know who you'd talk to [12:50] cjwatson: OK, thanks, I'll poke about a bit. It's a G3 iMac I thought would be useful for testing! Runs OSX 10.4 nicely though [13:01] Just to confirm, Xubuntu 10.04 is *not* an LTS release, correct? [13:02] wrong [13:02] xubuntu 10.04 is an lts [13:02] charlie-tca: okay, thanks a bunch! [13:02] no problem [13:03] 8.04 was also an LTS for xubuntu [13:14] jdstrand: about libvirtn read and commented [13:14] s/n/,/ === dendrobates is now known as dendro-afk [13:22] ttx: thanks! :) [13:26] hi people know, does libsoup respects GNOME proxy settings? === dendro-afk is now known as dendrobates [13:26] jeesh that came out wrong === sconklin-gone is now known as sconklin === MacSlow|lunch is now known as MacSlow [13:43] crimsun: Hello, if you need help and info about bug 400682 just ask me. [13:43] Launchpad bug 400682 in linux "[Karmic stac9227 regression] No sound after upgrade from Jaunty to Karmic" [Medium,In progress] https://launchpad.net/bugs/400682 [13:43] crimsun: I mean on the Lucid side [13:51] mvo: Thanks for the fix [13:52] Jeeves_: cheers, credits go to hyperair for writing it [13:52] !hyperair++ [13:52] =) [13:52] dumb bot :) [13:52] it's only in #ubuntu-mirrors i think === jamie is now known as Guest48160 [14:26] bdrung: I think upstream is really the right place to be dealing with the units issues and so now is the time to work on it for 10.10. [14:31] ScottK: and what to do with not-glib applications? [14:32] I think KDE already complies (at least KDE4 apps). [14:32] It's a matter of evangelizing upstreams about the issue and choosing which are most important. === zul is now known as sorensbot === sorensbot is now known as zul [14:43] micahg: any luck finding the thing that causes middle-button-pastes to disappear from my config every time I start firefox? :) [14:44] ScottK: with a separate library we can go to XFCE, LXDE, and so on and ask them to use this library. [14:45] Presumably. I'm not sure what the best approach is, but I think Ubuntu carrying a permanent difference from upstream on this topic is bad on many levels. [14:45] kees: sorry, not yet...probably will not get to this cycle unless you think it's really pressing [14:47] micahg: that'll be a regression -- asac fixed it in earlier versions before. [14:47] kees: ok, do you have the bug handy, we should target for lucid then [14:53] yes [14:53] ScottK: i want upstream to use the library. carrying a permanent diff is not a solution [14:59] micahg: bug 548866 [14:59] Launchpad bug 548866 in firefox "forgets middlemouse.contentLoadURL on upgrade" [Undecided,New] https://launchpad.net/bugs/548866 [14:59] kees: I found bug 535465 [14:59] Launchpad bug 535465 in firefox "middlemouse.contentLoadURL config option gets reset on every upgrade" [Undecided,New] https://launchpad.net/bugs/535465 === sconklin is now known as sconklin-afk [15:00] micahg: ah-ha yes [15:00] I'm trying to find where it was fixed in teh past though... [15:01] Hello, Could combody take a look to this bug: https://bugs.launchpad.net/ubuntu/+source/gtk-doc/+bug/526794 [15:01] Ubuntu bug 526794 in gtk-doc "Please sync gtk-doc-tools from debian stable/unstable main" [Undecided,New] [15:01] gtk-doc version in lucid is 1.11, but seems that 1.13 is available [15:02] in launchpad [15:02] micahg: I assume it's related to the changes from 1.5.dfsg+1.5.0.1-1ubuntu1 "Change various preferences: middlebutton paste disabled" [15:03] micahg: but I can't find where asac fixed it. [15:03] in xulrunner iirc [15:04] asac: kees: found it [15:05] micahg: cool! [15:05] micahg: I duped the older bug to 548866 since mine has a "reproducer" [15:06] kees: great, I'll test the patch and commit as soon as we know that 3.6.2 is clear [15:07] micahg: i think to test you need to touch .autoreg and maybe change the version in application.ini [15:07] micahg: e.g. to simulate upgrade [15:07] doko: ping bug 417009 [15:07] Launchpad bug 417009 in openoffice.org "all openoffice apps die in 'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic" [High,In progress] https://launchpad.net/bugs/417009 [15:08] NCommander: is one of the buildds buggy? i heard 4ubuntu1 failed but didn't see how before it was retried and worked, now 4ubuntu2 fails as well, not sure if it is the same way [15:08] * kees hugs micahg [15:09] NCommander: and/or the same machine [15:10] ccheney: ? [15:11] doko: i can't find reference to the jaunty stuff in the copyright file, but maybe i am misreading it? [15:11] doko: also 4ubuntu2 which didn't change anything relevant is failing to build with segfault, should that just be retried? [15:11] doko: i think probably 4ubuntu1 did as well but it was retried before i saw what caused the failure [15:12] looks it is removed in 1:3.2.0-4ubuntu2 [15:13] it's the usual buildd failure on armel. these are not reproducible locally unfortunately [15:14] well i didn't remove it in 4ubuntu2 as you can see in the debdiff, not sure why it showed up for you under 4ubuntu1 :) [15:14] doko: ok [15:34] hello [15:34] cjwatson, urgent ping === jsalisbury_ is now known as jsalisbury [15:51] * iulian has tried to install Lucid Beta 1 on his laptop and failed. :-( [15:51] All I got on my screen was this http://people.ubuntu.com/~iulian/DSC05679.JPG. [15:53] pitti: got a few minutes to help out with that cheese hook? [15:53] It opens up, but the debug does not get saved [15:54] correction, the debug gets saved, but not attached [16:00] pitti: bug 432631 is on the foundations list for the release meeting, but AFAICS all the rest is either desktop or assigned to you. slangasek asked whether the remaining tasks still needed to be fixed for lucid. Could you comment? [16:00] Launchpad bug 432631 in apt "clean up system/per-user proxy handling" [High,Fix released] https://launchpad.net/bugs/432631 [16:07] crimsun: ping - I tested your fix to pulseaudio for dove HP select switch, and it doesn't work as expected. It only adds the switch to the mute button in the sound-applet. [16:07] cjwatson: right, that's on our list now [16:12] GrueMaster: hmm, make it a port [16:12] ??? === deryck is now known as deryck[lunch] [16:13] Before we release a new version of pulse for this issue, lets make sure we have a completely working solution. [16:14] GrueMaster: switch = select, then enumerate the options [16:15] Ok. [16:18] hello [16:18] cjwatson, up ? [16:18] seems that deboostrap have some turbles [16:19] emgent: I'm here, but it would help if you gave me all the detail up-front rather than saying "urgent ping" and then quitting [16:19] makes it rather hard to actually respond to you [16:20] deboostrap seems faild always (lenny && ubuntu 9.10) after the packages download, with error: W: Failure trying to run: chroot /home/chroots/1 mount -t proc proc /proc [16:21] if you try to mount chroot by hands, skipping the mount apt-get is not avail, and also if you try to install it via dpkg and /var/cache/apt/archives/, show some lib perl errors [16:22] debootstrap --arch amd64 lenny /home/chroots/1 http://debian.fastweb.it/debian [16:22] cjwatson, take a look. [16:23] no, I'm not going to debug it with that level of detail, sorry [16:23] "some lib perl errors" [16:24] I can't run that command myself, I'm on i386 here, and I'm certainly not going to run debootstrap off a random mirror I don't know [16:24] -.- === yofel_ is now known as yofel [16:25] cjwatson, what you prefer.. but anyway debootstrap is broken. [16:25] and you are the maintainer, np for me. [16:26] debootstrap is run thousands of times each day on thousands of different systems in dozens of different contexts and varieties. [16:27] I'm not saying you're lying, but you're clearly using it in a special way that makes it fail, so providing more detail on what exactly you're doing would probably be a good start. [16:27] emgent: ^ [16:28] actually debootstrap is broken on lenny for unstable, iirc due to Build-Essential flags, which results that apt is not available. maybe that's connected to the problem your seeing? [16:28] emgent: If debootstrap was just plain proken, noone (in their right mind) would be able to install Ubuntu. [16:28] sistpoty|work, yes i think so [16:29] sistpoty|work, i found the same problem in lanny and ubuntu 9.10, 8.04 [16:29] s/lanny/lenny/ [16:31] sistpoty|work can you provide the bug id in debian tracker ? [16:32] emgent: sorry, can't find it right now [16:32] ok np [16:32] emgent: feel free to file a bug with full logs. but if you just turn up, yell at me on IRC, and don't provide enough detail, I can't help you. sorry [16:34] will do. [16:39] cjwatson, [16:40] emgent: Your chroot failure could be caused by not running as root, or typing to bootstrap an arch which can't run natively on the machine running debootstrap (in which case you would need --foreign). I take it these aren't the problem/ [16:40] s/typing/trying/ [16:52] cjwatson, slangasek: there will be a slight delay to plymouth testing [16:52] I got an assertion error [16:52] dmart, stop to dream. [16:52] and hurled the netbook out of the window in fury [16:53] and some wild marmosets ate it === zul_ is now known as zul === MacSlow is now known as MacSlow|capoeira === korn_ is now known as c_korn === nikolam is now known as Guest57625 [17:18] hmm [17:18] here's one of those things I wish I knew [17:19] when you compile source with debugging, gdb prints the source as you trace [17:19] ... how does it know where the source code is? [17:22] hello === nikolam_ is now known as nikolam [17:27] Hello, Could combody take a look to this bug: https://bugs.launchpad.net/ubuntu/+source/gtk-doc/+bug/526794 [17:27] Ubuntu bug 526794 in gtk-doc "Please sync gtk-doc-tools from debian stable/unstable main" [Undecided,New] [17:27] gtk-doc version in lucid is 1.11, but seems that 1.13 is available too [17:27] does anyone know if alice paul uses IRC or is around here somewhere/ [17:27]