[00:12] cjwatson: Figured out bdrung's grub issue. The lua warning was a red herring. It was actually erroring out because older versions of grub can't handle if statements in menuentry blocks [00:14] ebroder: so it was an issue that multiple user will face. === sanchaz-away is now known as sanchaz [00:15] bdrung: Only if they, like you, clicked through the screen where cjwatson yelled at you for leaving grub-pc/install_devices blank [00:15] bdrung: I think we can work around it fairly easy and build a configuration that's backwards compatible [00:16] *easily [00:17] grub2 in natty is corrupteD? [00:17] I saw some messages there and I'm afraid to install upgrades [00:17] now I have grub2 1.98 and it going to be upgraded to 1.99 [00:17] If you upgraded from an older release and you agreed to the debconf prompt that warned you you were shooting yourself in the foot [00:19] ari-tczew: if "debconf-show grub-pc | grep 'grub-pc/install_devices:'" is not empty, you should be fine [00:20] But I'm going to send cjwatson a patch to fix the issue anyway [00:21] ebroder: * grub-pc/install_devices: /dev/disk/by-id/ata blah blah blah ;) [00:21] but what about upgrade to grub2 1.99? [00:21] ari-tczew: Then you are safe, at least from this issue [00:21] it will lost this file? [00:31] bdrung: You didn't find or open a bug about the GRUB thing, did you? [00:34] ebroder: nope, i didn't === Auv5 is now known as Auv5[Away] === thegodfather is now known as fabbione === yofel_ is now known as yofel === stalcup is now known as v === jamesh_ is now known as jamesh [04:39] @pilot in === udevbot changed the topic of #ubuntu-devel to: Archive: Open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: robert_ancell [04:41] I created a new project on launchpad which will use the pidgin code-base as it's base with a bunch of patches and rebranding. Do I want to "mirror" the pidgin bzr in lp or import it into my project? And after that, do I branch from there to apply my patches? [07:13] Good morning [07:16] Good morning pitti ! [07:16] pitti: And, thanks for that ureadahead upload! I had almost forgotten that I had worked on it [07:16] hey bilalakhtar, how are you? had a nice weekend? [07:17] pitti: Fine, you? How was your weekend? [07:21] bilalakhtar: quite nice! went to Munich with my wife (she's doing her final thesis here) [07:22] Munich! wow! I guess you live in berlin? [07:22] (or somewhere else in Germany) [07:22] in Dresden [07:22] hmm [07:24] cjwatson: can I just bzr commit in cdimage@antimony:~/cdimage ? I want to remove the ubuntu-netbook cronjob [07:37] pitti: good morning [07:39] is there any trick to not regenerate PO files if there's a clean rule to regenerate or do I just have to edit the .debian.tar.gz and resign? [07:45] micahg: the buildd cleans, as far as I know, so no [07:45] but updating po files on clean is pretty nasty anyway [07:45] this shouldn't ever be done automatically IMHO [07:46] pitti: should I bother editing the .diff.gz then? it makes a useless diff with Debian [07:46] I'll file a bug with Debian about the rule [07:46] micahg: and sending the fix to Debian? [07:46] micahg: does it actually cause a build failure? [07:47] if not, and it's just about the noise, then I would just ask Debian to fix that and not bother [07:47] pitti: well, I was just going to delete the PO stuff from the diff.gz and resign, no, it shouldn't it just updates the create date [07:47] they asked for it, they got it :) [07:47] good morning [07:47] that should work, too [07:47] hey didrocks [07:47] ok, thanks pitti [07:47] Guten Morgen pitti, did you have a good week-end? [07:49] * micahg forgot, there's not a diff in this case :( [07:53] didrocks: I disabled the ubuntu-netbook CD cron job now, FYI [07:54] pitti: oh, I was thinking it was done already (disabled for i386 and amd64/powerpc), will it still build armel? [07:54] cjwatson, didrocks: I'd like to remove the entire cdimage/www/full/ubuntu-netbook/ directory to avoid confusion, is that ok for you? [07:54] didrocks: oh, it's still supposed to build for armel? [07:55] didrocks: ah, that's daily-preinstalled, right? [07:55] not daily-live [07:55] pitti: yeah, hence my all headaches in transitionning for the seed/meta/netbook-default-settings [07:55] daily-live IIRC, but better to check with ogra [07:55] cjwatson: ok, so we should just remove daily-live, but keep daily-preinstalled and ports [07:56] good morning! [07:56] hey dholbach === hunger_ is now known as hunger === saispo_ is now known as saispo [09:26] hi all! [09:27] pitti, I've been working on scour for Debian, I cannot find any copyright/license information about debian/* files [09:27] (I mean: in Natty's package) [09:28] quadrispro: I don't like separate licenses for debian/* stuff, I usually want them to have the same license as the main source [09:28] quadrispro: so it's meant to fall under the "*" catch-all [09:28] quadrispro: but if you care, I can add a separate stanza for debian/*, with Canonical copyright and Apache license [09:30] pitti, I'm going to push the packaging to collab-maint's git area, so feel free so add whatever you want :) (including your name in the Uploaders field) [09:30] quadrispro: I'd like to be an uploader indeed; then I can upload to Debian and sync [09:30] quadrispro: cool, thank you! [09:35] pitti, you're welcome -> http://git.debian.org/?p=collab-maint/scour.git [09:39] quadrispro: pushed my "Uploaders:" addition [09:40] quadrispro: pushed debian/copyright update, too [09:41] quadrispro: hm, which version did you take? dh_scour is too old in the Debian version [09:41] quadrispro: and it seems it's missing the dh sequencer? [09:41] quadrispro: please don't upload this yet, I want to update these [09:42] oh yes, it is so, I've taken an old one [09:43] quadrispro: ok, all pushed, I'm happy now [09:44] quadrispro: thanks for bringing this to Debian [09:44] pitti, thanks for the great work! === almaisan-away is now known as al-maisan [09:49] fabbione: ping [09:58] pitti, we could grab new upstream releases by uscan --force-download --repack --rename so we don't need the current get-orig-source [09:59] bdrung, thanks a lot for making http://reqorts.qa.ubuntu.com/reports/sponsoring/ more readable! [09:59] pitti, maybe would be more useful a snippet to repack sources grab'd from bazaar [09:59] quadrispro: ah, nice; feel free to drop it === sanchaz is now known as sanchaz-away [10:01] dholbach, what changed? out of the weird alignment of stats? [10:02] like the title are on the right columns and the values on the left one? it's weird [10:03] seb128, the stats I don't know, but the rest is more compact and more readable [10:09] xxtjaxx: pong [10:12] fabbione: magnificent! Say you packaged corosync didnt you? [10:13] xxtjaxx: many many moons ago.... [10:13] xxtjaxx: haven't touched it in ages [10:13] xxtjaxx: I am fairly confident debian has newer packages than the ones I did [10:15] xxtjaxx: so what's the question? :) [10:16] fabbione: I try wrapping my head around it. seems different from a lot Im used to normally around debian. [10:16] its kinda hard to grasp. with the little documentation that is there. specially that the main goal is sheepdog. (for me) [10:18] xxtjaxx: are you referring to the package itself or the upstream? [10:19] xxtjaxx: the package is relatively straight forward IMHO. Understanding what corosync does no, it needs lots of reading about virtual syncrony and clusters === jjohansen is now known as jj-afk [10:19] xxtjaxx: and it's not something you learn from one day to another just because you wish to package somehting that uses it [10:20] xxtjaxx: your average application runs on one machine, done. corosync is cluster.. runs on multiple machines at the same time, interact in real time, etc. [10:20] xxtjaxx: it involves an extra level of complexity that's the whole cluster status/configuration/architecture/requirement/design/you_name_it [10:21] xxtjaxx: but if you need more upstream docs, www.corosync.org -> get the latest and greatest and the complain to upstream mailing list :) [10:21] xxtjaxx: upstream is also on #linux-cluster on freenode [10:23] fabbione: its eval...*ahem* [10:24] not packaging [10:24] xxtjaxx: also note, that recent versions of corosync (aka get the latest and greatest) have more docs [10:25] debian/ubuntu have been shipping ancient versions for sometime [10:25] at points I actually resorted to reading the code instead which made me cry at times :/ === cody-somerville_ is now known as cody-somerville [10:26] though that might have been sheepdog though. [10:26] xxtjaxx: just go to upstream and ask for more docs, also look at the openais mailing list. that's a very good start [10:26] upstream is not bad :) [10:26] just overloaded with work [10:26] <\sh> fabbione: corosync is only complicated when you run it with a Cisco ASA FW and the ASA runs in Multiple FW Context Setup...then you have problems with multicast, and you need to do some blackmagic on your switches to convert multicasts into broadcasts ;) [10:27] \sh: not anymore.. corosync 1.3.0 will support other transport methods than multicast (like point to point) [10:27] interesting \sh [10:27] \sh: plus.. corosync supports broadcast by default [10:28] \sh: but 1.3.0 will have normal udp connections between nodes, no need of either multicast or broadcast [10:28] alternatively go Infibarf^WInfiniband [10:28] <\sh> fabbione: yes...but not when you want multicast by default...but you bought very big cisco foo ;) and this is the problem...not corosync ;) [10:29] \sh: well multicast is problematic on many hw implementations. that's why we are adding also p2p [10:29] tho I agree with you, multicast performs the best [10:30] xxtjaxx: any more quick questions? gotta commute to the office :) [10:31] fabbione: go go Gonna poke them a'lil [10:32] xxtjaxx: ok :) [11:12] pitti: no, please don't ever commit in ~/cdimage - 'bzr co bzr+ssh://antimony/srv/cdimage.ubuntu.com/bzr/private/cdimage' on your local system and work on it there, then 'bzr pull' in ~/cdimage after committing [11:12] pitti: removing the daily-live directory is fine - not the whole of ubuntu-netbook, as you say [11:13] cjwatson: ah, thanks for the heads-up [11:16] cjwatson: bzr diff currently shows some stuff in cdimage/, is that expected? [11:17] for the moment, yes [11:17] ok, done [11:18] those will need some thought [11:20] (but no rush) [11:23] janimo1, hey === Mirv_ is now known as Mirv [11:28] dholbach: you're welcome. now the statistics at the bottom needs an optical facelift. [11:29] seb128, ^ [11:29] thanks bdrung [11:29] dholbach, right [11:29] the columns are weird [11:30] ogra_ac_: hello === Claudinu1_ is now known as Claudinux === doko__ is now known as doko [12:01] can some archive admin remove the linux-headers-omap binary (it should be NBS currently) [12:02] (it prevents omap4 images from being built) [12:02] ogra_ac_, can we tell what is pulling that package into the image? [12:03] as i suspect even if it is removed, they dep which is trying to pull it will just fail as badly [12:03] linux-omap very likely [12:03] which should be NBS too [12:03] and someone must be pulling that in for it to be an issue [12:04] i assume there is a like 'netbook-meta' package somewhere which has these kinds of things in it ? [12:04] http://people.canonical.com/~ubuntu-archive/NBS/linux-headers-omap [12:05] LIST="$LIST minimal^ standard^ ubuntu-netbook^" is what livecd-rootfs installs on armel [12:05] once all those dependencies go away, we'll remove it without you needing to ask [12:05] hum [12:05] I can reupload netbook-meta [12:06] I have no idea what's involved with powervr-omap3-dkms [12:06] why do we have -headers in such a high level seed at all ? [12:06] cjwatson, ogra_ac_, i suspect it is the linux-headers-omap in the netbook-meta which is pulling this in and causing ogra_ac_'s problem [12:06] cjwatson, can go until we have a decision about omap3 kernels [12:06] i suspect if we remove that then his issue will go away and we don't need to worry about the NBS [12:06] there are comments in the seed ... [12:07] I'll remove linux-headers-omap [12:07] apw: correct [12:07] from the seed, I mean [12:07] cjwatson, oh, i see [12:07] * ogra_ac_ only grepped instead of reading the seed file [12:07] cjwatson, powervr-omap3-dkms can go temporary too [12:08] i'll take care about re-adding either once we have a kernel decision (for A2 most likely) [12:08] can go what? [12:08] oh, where does that dep come from, that must be an rdep [12:09] if you mean removing the powervr-omap3 source package, please file a bug with rationale [12:09] however, as apw says, it's not relevant to your image build issues anyway [12:09] ogra_ac_, its in universe so it can't be in the seeds right? so it should be ok [12:09] so you can just ignore it if it's only going to be temporary [12:09] no, i dont want to remove it, i'll check with ricardo what to do about the dep [12:09] yep [12:09] apw, yep [12:11] netbook-meta uploaded [12:21] @pilot in === udevbot changed the topic of #ubuntu-devel to: Archive: Open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: robert_ancell, cjwatson [12:24] dholbach: what do you think about this column order: http://people.ubuntu.com/~bdrung/sponsoring/ === MacSlow is now known as MacSlow|lunch [12:52] cjwatson: Could you please look at bug #682644? (since you are patch pilot ATM) [12:52] Launchpad bug 682644 in ufw (Ubuntu) "Sync ufw 0.30.0-2 (main) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/682644 [12:52] bilalakhtar: why not just wait for sponsoring as normal? [12:53] Laney: of course I can wait [12:53] I don't think patch piloting is about pinging to have your stuff sponsored straight away [12:53] let us see his response, if he's busy then I will wait [12:54] Laney: Even if it isn't, I just asked: Can you look [12:56] https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews "patch pilots make themselves available on IRC" [12:57] bilalakhtar: sure, thanks! will look in a few minutes [12:57] thanks a lot cjwatson ! Take your time, even if you take a year its fine :) [12:59] alright, I just didn't think that it was supposed to be a programme to get your stuff sponsored immediately [12:59] but as you wish [12:59] Laney: it isn't for that [12:59] its just for confirmation [12:59] Reading that page, it says: [13:00] 'Patch pilots help make patches ready for inclusion' [13:00] Not necessarily sponsorship [13:04] bilalakhtar: acked [13:05] cjwatson: :o Thanks! [13:10] bdrung, I have no objections === alecu is now known as alecu-sprint === beuno_ is now known as beuno === drdanz_ is now known as drdanz === MacSlow|lunch is now known as MacSlow [13:40] FYI: I won't be doing any more autosyncs from Debian until after alpha-1 at this point. File bugs if you have syncs that are urgent for alpha-1, but otherwise they'll get picked up on Friday [13:42] doko, is there any chance we could get the workaround from the past comment for bug 675347 inot the archive before A1 ? [13:42] Launchpad bug 675347 in Linaro GCC "volatile int causes inline assembly build failure" [Medium,In progress] https://launchpad.net/bugs/675347 [13:43] (else i need to unseed a lot of stuff thats ftbfs due to it for alpha1) [13:46] I am seeing quite a number of cases where symbols on C++ packages change between i386 and amd64 such as http://launchpadlibrarian.net/59618185/buildlog_ubuntu-natty-amd64.phonon_4:4.7.0really4.4.3-0ubuntu2_FAILEDTOBUILD.txt.gz - Is this now intentional? IIRC, gcc-4.4 doesn't do this. [13:47] I think didrocks stumbled over that as well [13:47] if it's intentional, it's highly annoying [13:48] yeah, I got that in nux as well === NCommand1r is now known as NCommander [13:52] which encoding did change, the one for i386 or amd64? [14:00] didrocks: could you/desktop take care of the libgweather merge? === MacSlow is now known as MacSlow|afk [14:02] ogra_ac: it *is* fixed, please open your eyes on Monday mornings [14:03] doko, hmm [14:03] doko, didrocks: I can merge libgweather [14:03] cool, thanks [14:04] doko: pitti: thanks (sorry on mumble) [14:04] doko, the tasks on bug 675347 are "In progress" and "Confirmed" [14:04] Launchpad bug 675347 in Linaro GCC "volatile int causes inline assembly build failure" [Medium,In progress] https://launchpad.net/bugs/675347 [14:10] didrocks, hmm, why do you build nux with -Werror ? [14:13] Hi. I'm trying to fix LP #478392. My problem seems to be, that /tmp is on a seperate partition and also /usr. [14:13] Launchpad bug 478392 in mountall (Ubuntu) "/tmp is not cleaned when on a separate partition" [Medium,Confirmed] https://launchpad.net/bugs/478392 [14:13] For me /tmp is mounted before /usr, but the mounted-tmp script wants to use find to clean /tmp and fails. [14:13] I tried to "start on (mounted MOUNTPOINT=/tmp and mounted MOUNTPOINT=/usr), but this deadlocks the boot process. [14:14] Any idea what's going on here? [14:21] bug 523587 is possibly more directly accurate [14:21] Launchpad bug 523587 in mountall (Ubuntu) "/etc/init/mounted-tmp.conf uses find, which is in /usr/bin" [Medium,Triaged] https://launchpad.net/bugs/523587 [14:21] see particularly comment #8 in that bug === MacSlow|afk is now known as MacSlow [14:22] I suspect we need a dedicated C program to do this job [14:23] cjwatson: didn't find that one - thanks [14:25] SpamapS: did you see the upstream developer's comment on http://sourceforge.net/tracker/?func=detail&aid=3089978&group_id=65979&atid=512948 ? [14:26] cjwatson: you mentioned working to re-integrate casper/liveinitramfs. dunno what all that entails, but if i can help, please let me know. === akgraner` is now known as akgraner [14:28] hallyn_: it's somewhere on my queue, but not hugely far up :-/ [14:29] massive three-way merge exercise === ssweeny_ is now known as ssweeny [14:31] didrocks, oh, "configure: WARNING: unrecognized options: --disable-maintainer-mode" something is worng in nux, the option seems to be --enable-maintainer-flags=no [14:31] not sure why that is, but i suspect that causes the ftbfs on arm [14:34] a configure warning won't cause a build failure by itself [14:34] doko: The one for ad64, AFAIK, but it's happening on symbols that are new in the new upstream release so all I can really say is they are different. [14:40] cjwatson, it sets Werror [14:41] cjwatson, which i thoght we dont do on released tarballs [14:41] at least thats what seb128 always tells me [14:41] and i'm sure we have some warnings on armel [14:41] ogra_ac, we being? [14:42] usually GNOME doesn't set Werror in tarballs [14:42] but it's only GNOME [14:42] seb128, ah, i thought we do the same on tarballs where we are upstream [14:42] we being canonical [14:42] ogra_ac: oh, well, it depends [14:43] ogra_ac, dx has no rules as far as I know [14:43] hmm [14:43] depends of whoever is working on it [14:43] people are entitled to use -Werror and accept that they'll have to clean up more build failures, IMO [14:43] anyways we seem to hand over the wrong option for this configure [14:44] since it expects --enable-maintainer-flags=no (or --disable-maintainer-flags) [14:44] Werror doesn't apply to configure [14:44] it's a compiler thing [14:44] configure sets it in this case [14:45] configure: MAINTAINER_CFLAGS+="-Werror -Wall -Wcast-align -Wno-uninitialized -Wempty-body -Wformat-security -Winit-self" [14:45] well --enable-maintainer-flags=no is not what breaks [14:45] or was that just a side comment? [14:45] thats what is set if --enable-maintainer-flags=no isnt set [14:46] ogra_ac: gcc cflags don't cause configure failures [14:46] not even if configure sets them [14:46] no, what he's saying is that Werror is set because the maintainer mode is on [14:46] oh, right [14:46] yes [14:46] -Werror -Wall -Wcast-align -Wno-uninitialized -Wempty-body -Wformat-security -Winit-self [14:46] is what i see on the compiler line [14:47] well, trivial debian/rules change then. or just fix the compiler warning. :) [14:47] well, i wanted to know if we have a general rule here like gnome [14:47] since the warning is about alignment, it's possible that if you disregard it that the program will crash, is it not? [14:47] it would be nice to set one [14:47] I disagree [14:47] ogra_ac, dx-ers disagree [14:47] it depends very clearly on the package and on its upstream maintenance practices [14:48] they prefer to know about issues and fix those [14:48] i dont care if it crashes since we cant run it anyway on armel atm [14:48] currently the ftbfs just breaks my images [14:48] or at least some do [14:48] and tehre is no working GLES support in unity yet [14:48] but i dont want to useed all of unity [14:49] TBPH, if we set a rule, I'd prefer it to be on the side of enforcing warnings and making sure they get fixed (i.e. -Werror) [14:49] wouldn't it be quicker to fix the warning than to have this discussion, anyway? :) [14:49] well, dh seems to try to set one by default [14:49] ogra_ac, well send a patch to didrocks to fix the aligment bug [14:49] --disable-maintainer-mode" [14:50] ogra_ac: --disable-maintainer-mode has nothing to do with -Werror [14:50] didrocks or dx [14:50] see the autoconf documentation [14:50] MAINTAINER_CFLAGS="" [14:50] AS_IF([test "x$enable_maintainer_flags" = "xyes" && test "x$GCC" = "xyes"], [14:50] [ [14:50] MAINTAINER_CFLAGS+="-Werror -Wall -Wcast-align -Wno-uninitialized -Wempty-body -Wformat-security -Winit-self" [14:50] cjwatson, ^ nux does that [14:50] sorry, on the phone, fallbacking [14:50] backlogging rather :) [14:50] seb128: I know. but ogra_ac has the wrong end of the stick about dh. [14:50] cjwatson: well, we actually (mis?)use maintainer mode in udisks upstream to enable -Werror [14:50] hmm [14:50] sorry, the automake documentation, not the autoconf documentation [14:51] pitti: sure, but in general it has nothing to do with that [14:51] pitti, nux? [14:51] http://paste.ubuntu.com/537916/ [14:51] pitti, or you say udisks does the same? [14:51] seb128: nux what? [14:51] pitti, it fails to build [14:51] seb128: in udisks, we want people building git head to use -Werror, but we disable it for releases (i. e. for "make dist") [14:51] this seems to provide the best of both worlds [14:52] pitti, right, that seems sensible to me [14:52] but FWIW, if packages use -Werror, I applaud them in general [14:52] pitti, right, that's what GNOME do [14:53] cjwatson, hmm, so its Makefile.in vs configure ? [14:53] ogra_ac: no? [14:54] automake defines some macros which can be used by configure.ac [14:54] right [14:55] cjwatson, but the configure in nux doesnt know about maintainer-mode at all [14:55] it doestn know about maintainer-flags though [14:55] *does [14:55] so i dont get where i'm wrong here, configure uses some non-std stuff it seems [14:56] it does right [14:56] still not sure to get what you argue about [14:56] just fix the alignment issue and you are done [14:56] ogra_ac: maintainer-mode is a *complete red herring*. [14:56] there is a real bug there in the code [14:56] cjwatson, ah, now i get what you mean, ok [14:57] seb128, i know, i wasnt asking about the bug but about our policy for Werror ;) [14:57] there is no such policy [14:57] right, thats what i know now [14:57] thanks [14:57] the maintainers do what they want [14:58] yw ;-) [14:58] hi, not sure if this has already been reported; I just downloaded latest Ubuntu kernel from git (the maverick repository) and the last changelog entry seems borked [14:59] it says UBUNTU: Ubuntu-2.6.32-23.40 [14:59] Shouldn't it be Ubuntu-2.6.35-23.40? [14:59] I guess this breaks debian/rules insertchanges too [14:59] any thoughts? thanks in advance [15:00] ogra_ac, didrocks: there is a bug on the configure.ac there though [15:00] the intend reading it is to not set Werror on even versions [15:02] andreoli: #ubuntu-kernel is probably a better place to ask [15:02] ogra_ac: well, you have your own seed now, right? you can remove unity if it doesn't work there for armel, but agreed, I'll fix the right variable in configure [15:03] seb128: hum, let me check this [15:03] thx, sorry [15:04] seb128: ok, I'll fix configure.ac as well :) [15:05] didrocks, eval(nux_minor_version % 2), [1], [yes], [no])]) [15:05] didrocks, should be "micro" I think === bjf__ is now known as bjf [15:05] didrocks, not sure if the intend is to pikc 0.9 as an unstable serie? [15:05] or 0.9.5 unstable and 0.9.6 stable [15:06] didrocks, well, we aim to ship unity [15:06] seb128: yeah, it wasn't the case with the first versionning :) [15:06] ogra: right, but with alignment errors, you will ship a crashing unity [15:06] seb128: so, changing to micro and testing there, thanks! [15:06] didrocks, right, as long as GLES doesnt work i dont really care === mbarnett` is now known as mbarnett [15:08] ok :) [15:08] anyway, there will be a new nux release tonight, will ship the fixes with the new upload [15:17] ogra: where did you saw this maintainer-mode btw? debian/rules don't call it (only --enable-documentation) [15:18] didrocks, in the build log, dh sets it [15:18] ok, so it should be maintainer mode, not maintainer-flags in configure.ac [15:18] so, that + even/odd number handling [15:18] ok, fixing in nux upstream [15:18] thanks :) [15:19] ogra: apart from that, all is working fine regards to -settings package, metapackage and seed? (as I couldn't test on armel) [15:20] didrocks, well, its still failing to build images due to to many ftbfs [15:20] just trying to sort these [15:21] ogra: but not due to package I transitionned? [15:21] nope [15:21] phew :) [15:42] bdrung, micahg: please sponsor xiphos for xulrunner-2.0 and gtkhtml transitions: https://launchpad.net/bugs/682704 [15:42] or shall I ping patch pilots? === jam1 is now known as jam [15:47] kirkland- lp~andreserl/powernap/powernap-add-actions [15:52] xnox: if you already know whom to ask, you don't need a pilot to guide you :) === cjwatson changed the topic of #ubuntu-devel to: Archive: Open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: cjwatson [15:52] (don't believe that Robert has actually been on patch pilot duty for >11 hours) === txwikinger2 is now known as txwikinger [16:05] pitti,dpm: looks like one of you guys would need to deal with bug 632760 - can you? [16:05] Launchpad bug 632760 in language-pack-ta (Ubuntu) "Language variants don't work in Firefox because the language codes are separated with an underscore rather than a hyphen in chrome.manifest" [High,Triaged] https://launchpad.net/bugs/632760 [16:05] Arne's provided directions === dannf` is now known as dannf [16:15] thanks for the heads up cjwatson, I haven't got commit access to langpack-o-matic, and it also seems that upstream now packages xpi files differently, so I'm not sure if the fix will apply for natty. chrisccoulson, perhaps we could discuss this ^ on our call tomorrow? [16:16] i thought that one got fixed a while back [16:17] perhaps we still need to rebuild some language packs [16:17] now i'm confused [16:18] xnox: i would if BlackZ wouldn't be faster than me. :) [16:18] i supplied a patch to po2xpi, which pitti applied (with a small correction), which fixed what i thought the problem was [16:18] this process is too complex ;) [16:19] chrisccoulson, let me ask the Brazilian guys if that bug was fixed for them in the final language packs and see if they can provide some feedback in the bug [16:20] cjwatson, kk =) lol. [16:20] the patch pitti applied definately fixed the en-GB one, once they were rebuilt === beuno is now known as beuno-lunch [16:20] bdrung, =) Lol Thanks. [16:21] BlackZ, hello there =) thanks for xiphos sync ack. [16:22] xnox: the response time for sync requests is very short in most cases (countable in hours) [16:22] chrisccoulson, it might have been something else, as it seems po2xpi hasn't had any changes for a while: https://code.launchpad.net/~mozillateam/rosetta/po2xpi, and Arne's branch wasn't merged, either: http://bazaar.launchpad.net/~arnegoetje/rosetta/po2xpi-arne/changes. pitti might be able to tell us more [16:23] bdrung, hmm =) ok. It's just that it did take a while to propagate in debian experimental and to lp.net/debian/experimental. So I couldn'† get syncrequest straight after upload to debian. [16:23] ~ 1 day in total then ;-) === jj-afk is now known as jjohansen [16:24] this is why i'm so confused, it all seems to happen by magic atm ;) [16:26] cyphermox: I have a patch for a new feature on a specific project, but I'm lazy to create an account on their tracker and I think they don't care too much about it. [16:27] being lazy is no excuse ;) [16:27] and "i think" means that you aren't really all that sure that they don't care [16:27] living in the stone age of computing is [16:28] RenatoSilva, usually if the patch does something useful people will be happy to accept it.. but why don't you share a bit more... what did you patch? what does your patch do? :) [16:29] "I think" means I think, don't try guessing why I think that, thanks [16:29] RenatoSilva, we can certainly help you work on getting it upstream and in Ubuntu [16:32] cyphermox: I know people are usually happy, but it's purple/pidgin [16:34] they caused a regression in debian and ubuntu because their build doesn't fail if you tell configure to incude non-existing stuff in the build. They renamed a component and deb packages started to not include it anymore [16:35] RenatoSilva, ah, ok. is there a bug on launchpad about this? I would think it can be fixed by updating the way we call configure [16:36] yes there is, but the patch in not about it, it's just an example on how buggy pidgin /purple is [16:37] and mainly on how much they like to spend time calling their users idiots when they ask for fixing bugs and adding features [16:37] RenatoSilva, is there one for the bug you're fixing? -- also, I don't think it's very constructive to say a piece of software is buggy or complaining about the developers [16:38] well I just said "I think they don't care", someone instigated me to provide a reason [16:39] https://code.launchpad.net/~renatosilva/+junk/irchelper === dendrobates is now known as dendro-afk [16:40] http://bazaar.launchpad.net/~renatosilva/+junk/irchelper/revision/2 === dendro-afk is now known as dendrobates [16:41] they'll likely say I'm an idiot because I neither want to save my password nor type /msg nickserv identify, but just a password dialog [16:43] I just wanted to share this as I think it's *obvious* you should ask password with a dialog if not saved, and also for avoiding repatching on updates [16:47] cjwatson: re libdbi upstream bug. I did, and I had a discussion with Markus and Thomas Goirand (the debian libdbi-drivers maintainer) about the test suite. Its changing in 0.9, which is why I wrote it independent of that since 0.9 is unreleased. [16:47]