[00:00] <slangasek> the ISO language list (ISO 639-3) mentions languages "Bisaya, Brunei" (code: bsb) and "Brunei" (code: kxd) as well as a lot of different "Malay" languages
[00:00] <slangasek> there is Malay support in Ubuntu, but I don't know if it's a dialect that's acceptable / understandable in Brunei
[00:02] <cjwatson> http://en.wikipedia.org/wiki/Brunei says "Bahasu Melayu" and following links says that's msa
[00:02] <cjwatson> (ISO 639-2T/3)
[00:02] <cjwatson> oh, or ISO 639-1 "ms"
[00:03] <cjwatson> eglibc has an ms_MY.UTF-8 locale
[00:03] <broder> that article also claims that the variant of Malay in Brunei and most other Malay dialects aren't mutually intelligible
[00:03] <cjwatson> however I gather that Malay as spoken in Malaysia vs. Brunei isn't ... what you said
[00:04] <cjwatson> there's no msa_* or *_BN in /usr/share/i18n/SUPPORTED so I conclude that there is very little if any support for this language right now
[00:04] <Juayz> who is the boss of this project?
[00:05] <cjwatson> looking for bosses of free software projects generally indicates some degree of confusion :-)
[00:05] <cjwatson> http://www.eglibc.org/ is the eglibc project
[00:06] <broder> cjwatson: would eglibc not use something like kxd_BN? (http://www.sil.org/iso639-3/documentation.asp?id=kxd)
[00:06] <Juayz> they are responsible for translations?
[00:06] <cjwatson> no, only for the base locale metadata
[00:06] <cjwatson> broder: ah, maybe - but they don't have that entry right now
[00:07] <Juayz> ok if someone is doing this project for malay i want to know because many people here want to see it
[00:07] <cjwatson> https://wiki.ubuntu.com/Translations has a bunch of information on how translations in Ubuntu work in general
[00:08] <cjwatson> e.g. https://wiki.ubuntu.com/Translations/KnowledgeBase/AddingNewLanguage
[00:08] <slangasek> Juayz: as a general rule, free software translations happen when people who speak the language and care about the software get involved and make it happen from the ground up
[00:08] <cjwatson> if there is anyone working on this project, then they have not got very far yet, so if I were you I would treat it as if you were the first and maybe you'll link up later
[00:09] <Juayz> ok cjwatson thank you mr.
[00:09] <slangasek> we can provide pointers to help you get started (as cjwatson is doing), but that's probably about all
[00:09] <Juayz> also slangasek
[00:09] <Juayz> how much is to translate?
[00:10] <Juayz> how many words?
[00:10] <cjwatson> an absolutely ginormous amount
[00:10] <Juayz> estimate?
[00:10] <broder> it looks like oneiric had something on the order of 380000 strings
[00:11] <Juayz> 380,000 lines?
[00:11] <broder> more like phrases
[00:11] <broder> some would be long and some would be quite short
[00:11] <Juayz> ok.
[00:11] <cjwatson> ideally sentences, although not all projects will keep to that
[00:12] <Juayz> is there statistics for this?
[00:12] <Juayz> how long it takes for how many people to make it
[00:12] <broder> there's no requirement that *everything* be translated for a language to be included at all, though
[00:12] <cjwatson> somebody on #ubuntu-translators might have more idea about that kind of detailed question
[00:13] <Juayz> ok thank you.
[00:13] <cjwatson> most developers would be aware of the basic infrastructure involved but not of the quantities
[00:15] <Juayz> this is important for investment calculations
[00:15] <cjwatson> I understand, but don't have the numbers you want
[00:17] <Juayz> Is there some country that uses linux in government and municipal office computers?
[00:17] <Juayz> in desktops
[00:26] <cjwatson> Juayz: http://en.wikipedia.org/wiki/List_of_Linux_adopters#Government has a number of examples
[01:21] <bdmurray> @pilot out
[03:18] <micahg> tumbleweed: seeded-in-ubuntu or ubuntu-seeded?
[04:14] <ScottK> lool: clamav built on armhf in Debian.  Thanks for the tip: https://buildd.debian.org/status/package.php?p=clamav
[04:36] <pitti_> good morning
[04:45] <psusi> good night ;)
[04:54] <micahg> pitti_: are the font renames done?  I was going to spin up a new xubuntu meta
[04:54] <pitti_> micahg: so far, yes
[04:55] <pitti_> eh? the -omap4 kernel went to -1402, and now back to -1401?
[04:58] <dr3mro> please I need to know something .. does ubuntu sync packages with debian stable ?? when they are released ?? or just keep the unstable snapshot it had and wait for the next sync with next ubuntu release ??
[04:59] <micahg> dr3mro: we normally sync with unstable until Debian Import freeze which is 7-11 weeks into the development cycle, for the LTS, we've been syncing from testing
[04:59] <pitti_> dr3mro: we don't sync with debian stable
[05:00] <pitti_> dr3mro: we stop auto-syncing as micahg says, but we often manually sync individual packages when checking that they don't break
[05:01] <dr3mro> I mean if app X for example is in unstable repo of debian .. when it reach the stable repo .. does all fixes ported to ubuntu ?
[05:01] <dr3mro> pitti_, what about fixed bugs upstream ?
[05:02] <pitti_> dr3mro: no, we don't update ubuntu stable versions with all fixes, just selected ones
[05:02] <pitti_> which are particularly urgent (data loss/security/regression), or particularly safe
[05:02] <dr3mro> pitti_, does this apply even for LTS ?
[05:02] <pitti_> yes
[05:03] <pitti_> dr3mro: we _sometimes_ update stables to new upstream microreleases
[05:03] <pitti_> e. g. we often upload new KDE 4.7.x or GNOME 3.2.x releases
[05:03] <dr3mro> excuse me but doesn't that mean ubuntu will always has bugs debian has fixed months ago ??
[05:03] <pitti_> dr3mro: https://wiki.ubuntu.com/StableReleaseUpdates has the details
[05:04] <pitti_> in essence, yes
[05:04] <pitti_> hundred known small and non-fatal bugs are much better than accidentally introducing just one regression
[05:05] <dr3mro> pitti_, but why just use a branch of unstable and do whatever we ahve to to create ubuntu then merge back and release ?? so we benefit from upstream work ??
[05:05] <pitti_> dr3mro: if someone actually _does_ this cherrypicking, it's fine
[05:06] <pitti_> dr3mro: we just don't have a thousand developers to do this for all 30K packages for all N supported releases :)
[05:06] <dr3mro> pitti_, so if i use LTS ? it has more bugs than lets say debian 6.0 ??
[05:06] <pitti_> so in practice it only happens for a small subset of packages
[05:06] <pitti_> same argument -- it needs someone to do it
[05:06] <micahg> the same package in Debian stable might behave differently in Ubuntu due to different library versions and toolchain feature
[05:06] <pitti_> dr3mro: is this a general question, or do you have a particular package in mind?
[05:07] <dr3mro> pitti_, general as I am experincing alot of crashes and lock downs since ubuntu 9.10
[05:08] <dr3mro> pitti_, these never happend when i installed slackware, arch ,, i googled and find out about this unstable thing
[05:15] <dr3mro> I Like ubuntu specific things .. like unity .. global menu .. PPAs , but I have another Q? are those apps avail to other distros ?
[05:16] <pitti_> DreamThief: yes, of course; Debian packages some
[05:16] <pitti_> they have upstream releases, project pages, upstream bug trackers, VCS, etc.
[05:16] <pitti_> and are GPL
[06:21] <pitti_> cjwatson: are the things in http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt generally important? i. e. should this really be zero, or is this more cosmetical for the optional <-> standard things, etc.? (I know that the required/essential bits are breaking bootstrapping)
[06:22] <pitti_> jibel_: I noticed the new https://jenkins.qa.ubuntu.com/view/Precise/job/precise-problems-check/, nice! I have some ideas what else we should add there; can this be extended or is it meant to look at just one report
[06:23] <pitti_> jibel_: in particular, it would be nice if this could yell if some reports few, if anyone ever looks at have something
[07:18] <rickspencer3> hey pitti_ love to see that beer mug each morning :)
[07:18] <pitti_> :)
[07:18] <pitti_> rickspencer3: we got a fixed kernel for the EINVAL bug now, so the image tests should be a lot more stable now
[07:18] <rickspencer3> yeah!!!!
[07:20] <pitti_> jibel_, jamespage: propsed addition for the precise-problems jenkins test: http://paste.ubuntu.com/763513/
[07:21] <pitti_>  it's in shell, if you need a script in a different language I'm happy to write one
[07:31] <smoser> it looks like http://cdimage.ubuntu.com/releases/ has some incorrect stuff for 8.04/hardy
[07:31] <smoser> ubuntu-8.04.1-dvd-amd64.iso
[07:31] <smoser> i would have expected ubuntu-8.04.4-dvd-amd64.iso
[07:32] <micahg> smoser: dvds aren't necessarily respun for point releases IIRC
[07:32] <smoser> ubuntu-10.04.3-dvd-amd64.iso
[07:33] <smoser> so they were for 10.04. maybe not for 8.04, but then we have the directories there, and there.
[07:33] <smoser> i'm off to bd.
[07:34] <micahg> smoser: no mention of DVDs here: https://lists.ubuntu.com/archives/ubuntu-announce/2010-January/000128.html
[07:34] <micahg> whereas here there is: https://lists.ubuntu.com/archives/ubuntu-announce/2011-July/000150.html
[07:34] <smoser> good enough.
[07:36] <micahg> smoser: although neither does this, so no proof there: https://lists.ubuntu.com/archives/ubuntu-announce/2008-July/000112.html
[07:39] <micahg> smoser: so I guess there could be something wrong :)
[07:39] <cjwatson> pitti_: things below priority: important are relatively cosmetic
[07:39] <pitti_> cjwatson: good morning
[07:40] <pitti_> cjwatson: so e. g. py3.2 should move to "important" now, because it's in teh default install
[07:40] <pitti_> cjwatson: I'm happy to make the adjustments
[07:40] <cjwatson> yes, lsb-release has started depending on it again
[07:40] <pitti_> cjwatson: I also proposed to include arch/prio-mismatches into the new precise-problems jenkins job, as usually few people look at it
[07:40] <pitti_> and they aren't obvious
[07:41] <cjwatson> jenkins seems a bit heavyweight, I don't want it showing up as failures
[07:41] <cjwatson> also it's actually impossible to get priority-mismatches to zero right now due to some differences across architectures
[07:42] <cjwatson> (anyway, I'm on holiday, I just looked in on the red window, so if you want to fix things up be my guest)
[07:43] <pitti_> cjwatson: yep, thanks
[07:43] <pitti_> jibel_, jamespage ^ ok, so let's skip the prio-mismatches addition
[08:05] <jibel_> pitti_, good morning
[08:05] <pitti_> jibel_: bonjour, ca va?
[08:05] <jibel_> pitti_, ça va et toi ?
[08:05] <pitti_> jibel_: je suis bien, merci!
[08:07] <jibel_> pitti_, I discovered this check this morning. patrickmw set it up, you should ask him for any change to this script.
[08:07] <pitti_> jibel_: so, I'm happy to fix the one entry at http://people.canonical.com/~ubuntu-archive/architecture-mismatches.txt, but I'll hold off if you want to/can integrete it into precise-problems
[08:07] <pitti_> jibel_: ah, will do; which timezone is he in?
[08:08] <pitti_> jibel_: (I pretty much depend on IRC these days, still no email)
[08:08] <jibel_> pitti_, he leaves in the middle of the desert, let me check
[08:08] <pitti_> anyway, I'll watch out for him
[08:08] <jibel_> pitti_, UTC-7
[08:09] <pitti_> jibel_: thanks; so will try to catch him next week then, as I'll have to leave in the late afternoon today/tomorrow
[08:09] <jibel_> pitti_, ok
[08:10] <pitti_> jibel_: do you know whether the alternate/server tests already look at the generated report.html?
[08:10] <pitti_> jibel_: e. g. http://cdimage.ubuntu.com/daily/current/report.html
[08:10] <pitti_> if these are non-empty, we should totally have a red light
[08:10] <pitti_> it's usually not even worth testing the images if there's anything in there
[08:14] <pitti_> jibel_: looking at the current desktop/alternates failure
[08:14] <pitti_> Dec  8 08:09:05 in-target: Error: update-openoffice-dicts not present or executable. Missing dependency on dictionaries-common?
[08:15] <pitti_> dictionaries-common is installed on teh images
[08:16] <pitti_> ok, it's due to https://launchpad.net/ubuntu/+source/dictionaries-common/1.12.0ubuntu1
[08:16] <pitti_> rickspencer3: ^ it dropped update-openoffice-dicts, I'll figure out where it should live now
[08:16] <pitti_> yay for catchign real issues
[08:17] <pitti_> I'll re-spin once that's fixed
[08:18] <rickspencer3> thanks pitti_ ... and well done, jibel_ and QA too!
[08:22] <pitti_> rickspencer3: excellent case for the "revert" procedure
[08:22]  * pitti_ grabs the fireman helmet and gets going
[08:23] <pitti_> rickspencer3: bug 901572 FYI
[08:23] <rickspencer3> thanks pitti_
[08:28] <micahg> pitti_: are we not able to remove the need for that script?
[08:28] <pitti_> micahg: yes
[08:28] <pitti_> micahg: I'll investigate which dictionary packages are affected
[08:28] <pitti_> micahg: I don't intend to permanently re-add update-openoffice-dicts
[08:29] <micahg> ah, ok :)
[08:29] <pitti_> question is now whether I should start fixing dictionaries first, or put back a no-op script first
[08:29] <pitti_> and I think the latter is quick, safe, and unbreaks the world
[08:29] <micahg> makes sense
[08:33] <pitti_> workaround uploaded
[08:33] <pitti_> takes the pressure out
[08:36] <pitti_> looks like we'll need to rebuild 47 dictionary packages
[08:42] <jibel> pitti_, is anyone working on bug 850264
[08:43] <jibel> ?
[08:43] <jibel> it's assigned to you but is a bug in apt
[08:46] <pitti_> jibel: I'll work on a reproducer, and I also talked about it with Michael
[08:46] <didrocks> @pilot in
[08:46] <pitti_> jibel: so yes, it's high-prio
[08:47] <jibel> pitti_, ok thanks
[09:39] <pitti_>  ppisati: hello Paolo
[09:39] <pitti_> ppisati: the omap4 kernel went to -1402 and now _back_ to -1401; did something go wrong there or is that really deliberate?
[09:40] <pitti_> ppisati: it's currently in binNEW and I didn't release it as it looks wrong
[09:41] <ppisati> 3.0.0-1402.3 -> 3.2.0-1401.1
[09:42] <ppisati> new kernel version, ABI reset
[09:42] <ppisati> pitti_: ^^
[09:42] <pitti_> ppisati: oh, that's not monotonous then
[09:42] <pitti_> ppisati: ok, I'll update seeds and rebuild d-i for it, thanks
[09:42] <pitti_> and binNEW it
[09:43] <ppisati> pitti_: it's the same for master kernels
[09:43] <ppisati> pitti_: it went to 3.1-[12345...].x -> 3.2-1.x
[09:43] <pitti_> ppisati: ok, so "1400" is just the general offset for omap4 then?
[09:43] <ppisati> yep
[09:43] <ppisati> righty right my friend :)
[09:44] <pitti_> ppisati: ok, thanks; that looked confusing at first :)
[09:44] <pitti_> alright, binNEWed
[09:44] <seb128> pitti_, did you talk to slangasek today?
[09:44] <pitti_> seb128: no, I didn't
[09:44] <seb128> pitti_, he was wondering about language packs and srus yesterday
[09:45] <seb128> he said only part of the sets were copied and that it created issues
[09:45] <pitti_> I thought I fixed all these
	ScottK, cjwatson: I'm not sure what pitti did the other day to fix the langpack problem, but I still see a lot of langpacks in oneiric-proposed that have not been copied to oneiric-updates, and they're *not* showing up as candidates on http://people.canonical.com/~ubuntu-archive/pending-sru.html
	seb128: right, well, the current problem is that only some packages were copied to -updates for each language, making some of them uninstallable
[09:46] <seb128>  <slangasek>	can't copy language-pack-$foo-$lang without also copying language-pack-$foo-$lang-base, etc
[09:46] <seb128>  
[09:46] <seb128> pitti_, that's basically the summary
[09:46] <seb128> he maybe sorted it, dunno
[09:46] <seb128> I figured I would mention it
[09:46] <pitti_> these are two different things
[09:46] <pitti_> we only move the stuff to -updates which actually has been tested
[09:47] <pitti_> but we forgot some -base packs from the previous run
[09:47] <seb128> right, that I told him
[09:47] <pitti_> that's a bit confusing
[09:47] <seb128> pitti_, I pointed him to https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA
[09:47] <seb128> pitti_, oh, he said "<slangasek>	SpamapS: there was an SRU regression alert a week ago because of resulting uninstallabilities, and I've just tracked down another 3 packages that had the same problem :/"
[09:48] <pitti_> hm, we really should have a britney run for stable and stable-proposed
[09:48] <seb128> pitti_, so yeah, he probably fixed them but he was unsure what is the process for those
[09:48] <pitti_> in that case, just copying the missing -base packs as well
[09:48] <seb128> pitti_, anyway I was just mentioning it for the record
[09:48] <pitti_> seb128: thanks
[09:48] <seb128> yw
[09:48] <seb128> pitti_, still no server btw?!
[09:48] <pitti_> ok, brb, switchign to IRC proxy
[09:48] <pitti_> seb128: it came back 5 mins ago
[09:49] <seb128> nice ;-)
[09:58] <micahg> pitti: for magyarispell, you could've switch to source format 3 instead of repacking
[09:58] <pitti> micahg: I actually tried merging with Debian's changes (whci also does that), but that package is such a mess that it'll take some time to actually finish this cleanly
[10:19] <jamespage> pitti: Jenkins job setup - publishes to here - https://jenkins.qa.ubuntu.com/view/Precise/job/precise-priority-mismatches-check/
[10:20] <jamespage> and notifies via email to ubuntu-testing-notifications of any mismatches!
[10:20] <pitti> jamespage: nice, thanks!
[10:20] <pitti> jamespage: can we get one for architectures-mismatches, too?
[10:20]  * jamespage gets out his copy/paste magic
[10:20] <jamespage> sure
[10:20] <pitti> (which is actually the more interesting one)
[10:20] <pitti> wget -q -O- http://people.canonical.com/~ubuntu-archive/architecture-mismatches.txt | grep -E '\[[[:alnum:]]+\]$'
[10:20] <pitti> jamespage: ^
[10:21] <pitti> if that succeeds, that's a FAIL
[10:21] <jamespage> great - on it now
[10:22] <pitti> ok, I think I nailed bug 901572 now
[10:22] <pitti> once it's all published, I'll re-spin images
[10:25] <pitti> rickspencer3: so, 3 mins for the workaround vs. 2 hours of fixing it properly, I'd say it was worth it
[10:27] <pitti> jamespage: remaining prios fixed, so that should go green in the next hour
[10:31] <pitti> jamespage, cjwatson: uploading d-i for new omap4 kernel FYI
[10:31] <pitti> (NBS)
[10:42] <jamespage> pitti: https://jenkins.qa.ubuntu.com/view/Precise/job/precise-architecture-mismatches-check/
[10:43] <pitti> jamespage: nice, thanks!
[10:43] <pitti> will upload the fix now
[10:44] <pitti> pretty funny game, this "introduce new red dots and then catch up with them"
[10:44] <jamespage> lol
[12:06] <didrocks> @pilot out
[12:17] <bkerensa> seb128: bug 805480
[12:18] <seb128> bkerensa, what about it?
[12:19] <bkerensa> interesting bug
[12:19] <bkerensa> :D
[12:19] <bkerensa> lots of dupes and most have been invalidated
[12:19] <bkerensa> :D
[12:20] <bkerensa> I was able to reproduce in Oneiric and Precise so I moved it to confirmed and linked
[12:20] <seb128> bkerensa, right, and what that has to do with me? seems like duplicates have been wrongly duplicated
[12:20] <seb128> like they are not the same errors not the same steps
[12:20] <seb128> somebody should open a proper bug for it
[12:22] <bkerensa> seb128: k I will crash it and report it here in a sec :D
[12:22] <seb128> thanks
[12:23] <seb128> bkerensa, is your issue happening when uninstalling gnome-utils?
[12:23] <seb128> bkerensa, urg, please undo what you did, you clearly dupped stuff which have nothing to do with that bugs and were valid bugs
[12:24] <seb128> like the invalid free, the abort in the log function and yours are 3 different issues
[12:39] <pitti> jibel, jamespage: rebuilding desktop/alternate/server images to pick up dictionaries-common fix
[13:25] <doko> pitti, seb128: MIR needed for libpst (evolution)
[13:25] <seb128> doko, it was in main until natty and demoted,stopped used by error in oneiric
[13:25] <seb128> doko, do we need a mir again for it?
[13:26] <seb128> like the build-depends was dropped by error which is why it got demoted, it seems like we should just promote it back?
[13:26] <doko> ok, promoting
[13:26] <seb128> doko, thanks
[13:26] <infinity> It pretty much hasn't changed since natty, even.
[13:26] <seb128> doko, did the glib update worked? i.e did it fix your build issues with the single include error?
[13:27] <doko> seb128, yes, see http://qa.ubuntuwire.org/ftbfs/primary-precise-armhf.html
[13:27] <seb128> doko, great ;-)
[13:29] <jibel> pitti, alternate is back to normal but there's something wrong with oem install
[13:30] <jibel> desktop and server are running/queued
[13:30] <pitti> back from lunch
[13:32] <jamespage> pitti: ack
[13:33] <pitti> jibel: ah, that's why they are yellow now? looking at logs..
[13:35] <pitti> jamespage: ok, so much for http://people.canonical.com/~ubuntu-archive/architecture-mismatches.txt, jenkins report is green now; thanks for adding this!
[13:35] <jibel> pitti, Dec  8 13:21:09 finish-install: warning: /usr/lib/finish-install.d/01oem-config-udeb returned error code 100
[13:35] <infinity> doko: Were you doing an upload for gnat* at some point, or should I?
[13:36] <infinity> doko: (Although, it'll need some actual bootstrapping anyway... *sigh*)
[13:36] <jamespage> pitti, np
[13:36] <doko> infinity, I don't doing you the bootstrapping =)
[13:37] <infinity> doko: You also don't Englishing the morning this.
[13:37] <ogra_> lol
[13:37] <doko> infinity, I'll get a coffe now, get a single malt yourself ;)
[13:38] <jibel> pitti, it's yellow because some post-install test failed
[13:38] <pitti> jibel: right
[13:38] <jibel> pitti, you can see the results of the tests in http://10.189.74.2:8080/job/precise-alternate-amd64_oem/105/artifact/105/test-results/TEST-oem.xml
[13:39] <pitti> jibel: right, the assertion error
[13:39] <jibel> pitti, in this case oem-config is not installed and there is no desktop link to prepare for shipping in the first stage of an oem installation
[13:39] <pitti> jibel: I'll investigate this more closely in a bit, just finishing up something else
[13:39] <cjwatson> oem looks broken due to hunspell-en-us, like everything else
[13:40] <pitti> cjwatson: no, I rebuilt images an hour ago for thsi
[13:40] <pitti> this
[13:40] <cjwatson> oh, I'm looking at out-of-date jenkins logs then
[13:40] <pitti> https://jenkins.qa.ubuntu.com/view/Precise/job/precise-alternate-i386_oem/lastSuccessfulBuild/
[13:40] <cjwatson> (anyway, SEP today)
[13:40] <pitti> ^ from 41 mins ago
[13:40] <pitti> cjwatson: whatever "SEP" is, I think you're on vac :)
[13:40] <infinity> pitti: Somebody Else's Problem.
[13:41] <pitti> aah
[13:41] <cjwatson> oh, it wants to remove python-gobject-cairo
[13:41] <cjwatson> that's easy, we just uploaded ubiquity to fix that
[13:41] <cjwatson> rebuild in an hour or two
[13:42] <cjwatson> hm, wait
[13:42] <pitti> that was yesterday already
[13:42] <cjwatson> I think perhaps something else with a python-gobject-cairo dep needs to be fixed
[13:42] <cjwatson> software-center maybe?
[13:42] <pitti> yes, that's in bzr, but not uploaded yet
[13:42] <cjwatson> that's what NBS says.  fix that and it should go away
[13:42]  * cjwatson vacs
[13:43] <pitti> mvo: ^ ok to upload current s-c bzr head?
[13:44] <pitti> mvo: the changes in http://bazaar.launchpad.net/~software-store-developers/software-center/trunk/view/head:/debian/changelog look both safe and exactly what we need
[13:44] <mvo> pitti: right, let me quickly look at a outstanding branch, ok? should also be safe and good and then I do the upload?
[13:44]  * pitti hugs mvo, danke
[13:45] <mvo> yw - I was slacking a bit with the recent merge requests, so I want to at least pick the easy ones into this upload
[14:06] <doko> does somebody want to merge isdnutils?
[14:09] <pitti> doko: hm, debian's version is even older than our's..
[14:09] <doko> pitti, right, but never merged
[14:10] <jibel> pitti, I can't install alternate, same update-openoffice-dicts error than this morning but on hyphen-en-us
[14:11] <pitti> jibel: argh, that too? looking
[14:11] <pitti> jibel: weird that the auto tests seemed ok?
[14:12] <pitti> jibel: confirmed; I'll check these packages, too, thanks for pointing out
[14:12] <jibel> pitti, indeed, I'll compare what's different from a manual install
[14:13] <pitti> jibel: oh, that's presumably one of the packages which is installed from the network through the check-language-support stuff
[14:13] <pitti> jibel: i. e. it's not in the live system
[14:14] <pitti> jibel: the tests might do a networkless install?
[14:14] <doko> barry, could you have a look at https://launchpad.net/ubuntu/+source/cython/0.15.1-1/+build/2961231
[14:14] <doko> I assume it's the same for other archs
[14:15] <barry> doko: sure, looking...
[14:15] <jibel> pitti, the tests are running with full network support. Do you know what pulls hyphen-* during install ?
[14:16] <pitti> jibel: if select English, it should be part of the extra language support for English
[14:16] <jibel> pitti, ok, I'll diff both installs and will see
[14:16] <pitti> jibel: I'm about to upload the fix, is that ok? or do you want to keep the current situation for examining this?
[14:17] <jibel> pitti, that's fine I saved the logs
[14:18] <pitti> uploaded
[14:18] <pitti> jibel: doing an archive grep now for finding similar issues
[14:30] <pitti> jibel: I added teh remaining affected packages to bug 901572, will go through them
[14:30] <pitti> jibel: but none of them are on the images or should be covered by the tests, so fixing them shouldn't block the next image test run
[14:50] <doko> pitti, Sweetshark: these SA dictionaries really should be updated
[14:55] <pitti> yeah, four years might be a bit outdated
[14:55] <pitti> although I figure only we Germans are crazy enough to try and officially change our language once a decade :) but there's certainly a lot of new words
[14:57] <doko> Riddell, qtmobility ftbfs on armel/armhf (symbols mismatch)
[15:23] <slangasek> pitti: right, cjwatson is already looking into a britney for SRUs; in the meantime I've copied over the missing -base packages, but I'm still left wondering what the actual process is for publishing langpack updates - is it you personally monitoring that wiki page for test results?
[15:24] <pitti> slangasek: when the official testing time is over, we copy the stuff that has been marked on the wiki page
[15:24] <slangasek> pitti: but who is this "we", because this all lies outside of any SRU process I'm familiar with :)
[15:24] <pitti> slangasek: but that process failed in that case, as the update _before_ the most recent one was a -base refresh
[15:25] <pitti> so I need to look more carefully when copying next time and watch out for missing -base updates
[15:25] <pitti> slangasek: ubuntu-translators are doing the actual verification, I'm just pushing the buttons for moving stuff between ppa, -proposed, and -updates
[15:26] <pitti> we have a plan which apps to test to call a language update "verified"
[15:26] <pitti> which is coordinated on https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA
[15:26] <pitti> sorry, need to run for today, have an appointment; will catch-up tomorrow
[15:26] <elmo> https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel/extension-list <-- I don't understand this - isn't it outdated by firefox's modern works-with-anyversion plugin stuff?
[15:27] <pitti> now that I actually have a server again, I'll have scrollback
[15:33] <elmo> chrisccoulson: ^--
[15:34] <chrisccoulson> elmo, that wiki is ancient and from a time when we had extensions in the archive
[15:35] <elmo> chrisccoulson: it's referenced from the sync blacklist
[15:35] <elmo> chrisccoulson: do we now not do extensions in the archive at all?
[15:35] <elmo> I started a top this rabbit hole wondering why foxyproxy was packaged in Debian but not ubuntu
[15:35] <slangasek> mvo: I've kicked bug #901638 in your general direction; if there's something I can do better in the tdsodbc metadata to make this upgrade work, please feel free to kick it back
[15:36] <chrisccoulson> elmo, only for very special cases, decided mostly by me (ie, lightning and enigmail)
[15:37] <chrisccoulson> and any extensions maintained by us
[15:37] <chrisccoulson> but that's it
[15:38] <elmo> chrisccoulson: ok - it'd be lovely if we could update sync-blacklist to say that
[15:38] <elmo> (if someone wants to point me at bzr, I can propose a merge - the file helpfully says it's under bzr, but not where the canonical repo is)
[15:38] <elmo> chrisccoulson: but umm, sorry, one other thing - why?
[15:39] <chrisccoulson> elmo, because there is a significant overhead with maintaining in-archive extensions, and we can never do a better job than addons.mozilla.org
[15:40] <chrisccoulson> eg, AMO provides updated compatibility metadata for addons hosted there, to prevent developers having to respin addons for new versions
[15:40] <chrisccoulson> extensions in the archive don't benefit from any of that, meaning they need manual uploads every 6 weeks
[15:40] <elmo> hmm, ok
[15:41] <chrisccoulson> in addition to that, addons are frequently updated upstream to fix stability / security issues, and the ones in the archive were always left to rot and ended up hopelessly outdated
[15:44] <elmo> chrisccoulson: well, that's not a firefox specific argument and just indicates packages that aren't well maintained
[15:51] <mvo> slangasek: thanks slangasek, I will have a look (unfortunately burried in $stuff currently)
[15:51] <slangasek> mvo: no hurry :)
[15:57] <bolo56> hail !
[15:57] <bolo56> o/
[15:57] <bolo56> i upgrade ubuntu 11.04 kernel from 2.6 to kernel 3.0
[15:57] <bolo56> but i can't mount the CD
[15:58] <bolo56> also when i try to start xconfig i get an error
[15:58] <bolo56> can anyone help me ?
[16:03] <soren> If I install a package for the first time, and it contains a conffile, but that file is already on the filesystem... What happens? Does it get overwritten?
[16:05] <barry> doko_: this is an interesting one.  package builds fine in an oneiric chroot for py2.6 and 2.7.  upstream tarball fails exactly the same way in a virtualenv w/2.7 on precise.  i'm testing upstream tarball in a virtualenv on oneiric in 2.6 and 2.7.  i wonder, could this possibly be a gcc issue?
[16:07] <barry> doko_: source tarball in 2.6 virtualenv on oneiric passes
[16:08] <doko_> barry, you could check with gcc-4.5 instead
[16:10] <barry> doko_: will do after my 2.7+upstream+oneiric completes.  otoh, i'm using gcc 4.6.1 on oneiric and 4.6.2 on precise.  i wouldn't *think* that would make a difference, but i guess you never know ;)
[16:16] <jamespage> doko_, do we have a icedtea-plugin package for openjdk-7? or is that superceeded by something else?
[16:17] <doko_> jamespage, no. we need to build it for both openjdk's
[16:41] <barry> doko_: is there a good way to change the default gcc?  i tried `export CC=gcc-4.5` and that builds source, but the tests fail with the following error
[16:41] <barry> gcc-4.5 -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c a.cpp -o build/temp.linux-x86_64-2.7/a.o
[16:41] <barry>  
[16:41] <barry> gcc-4.5: error trying to exec 'cc1plus': execvp: No such file or directory
[16:41] <barry>  
[17:01] <infinity> barry: cc1plus?  You have C++ hidden in there?
[17:02] <infinity> barry: If so, you want a CXX=g++-4.6 too.
[17:03] <infinity> barry: It also could just be that you don't *have* g++-4.6 installed, so when you ask gcc-4.6 to operate on that obviously-C++ file, it has a sad.
[17:04] <infinity> barry: s/4.6/4.5/
[17:10] <doko_> barry, install g++-4.5 too
[17:22] <barry> infinity, doko_ thanks, that looks like it did the trick
[17:57] <micahg> elmo: re addons in the archive> we don't have the people power to update extensions in the archive in the stable releases, Debian has a frozen Iceweasel version in their stable release which allows them to package extensions
[20:56] <barry> doko_: https://bugs.launchpad.net/ubuntu/+source/cython/+bug/901840
[21:11] <nigelb> kees: Did Nyan Cat help? ;)
[21:12] <nigelb> kees: unping. I was responding to something *ages* back.
[21:12] <kees> nigelb: hehe :)
[21:12] <nigelb> :D
[22:02] <hallyn> smoser: fwiw, nested containers just worked fine for me - just make sure you use different subnets and differnet names (for different cgroups) for both
[22:42] <Cheery> it's simple question and I know the answer, but I'm interested to hear if you've got something to add.
[22:42] <Cheery> if I'd like to write an opengl application for ubuntu, what could I do?
[22:44] <Cheery> my other information sources stay quiet
[22:44] <Cheery> so I guess there's nothing done by ubuntu for that..
[23:08] <hallyn> Cheery: maybe #ubuntu-desktop would have answers
[23:08] <Cheery> hallyn: thank you. I'll check that channel
[23:09] <hallyn> np
[23:09] <hallyn> (it's not that we don't want to help, opengl is just probably not our forte :)
[23:11] <Cheery> hallyn: there's large amount of 'you'. and ubuntu partially stands on a huge layer of other devs outside ubuntu.
[23:11] <hallyn> of course.
[23:12] <hallyn> that's how i can get away with not coding opengl myself :)
[23:12] <Cheery> I don't worry about not signal on the channel.. because it seems ubuntu as a channel seem to sink into questions. ^^
[23:15] <Cheery> still it's sort of funny I haven't seen widespread tools you use with ubuntu to develop content for it.
[23:16] <broder> Cheery: you mean like http://developer.ubuntu.com/ ?
[23:17] <Cheery> yeah. sort of like that
[23:18] <Cheery> broder: though it's quite late and you'd have lot of other domains to go through as well.
[23:21] <Cheery> of course, tools for just tools sake doesn't do much.
[23:32] <Cheery> in particular what bothers me is that you haven't taken concepts of css and brought them into desktop GUI
[23:32] <Cheery> yet in about every distupgrade you've had a new desktop style.
[23:37] <infinity> Cheery: Eh?  Have you actually seen a GNOME theme?
[23:37] <infinity> Cheery: "dpkg -L light-themes" and check out what comprises them.
[23:42] <Cheery> oh you've gotten there..
[23:51] <psusi> TheMuso, ping