[00:38] <persia> ScottK: crimsun: This hasn't beeen *the* place to ask packaging questions (but rather one of many) since community-lucid-motu was approved "Developer Training: distribute".  This is still *a* place for packaging questions.  #ubuntu-packaging is mostly for new packaging, PPA packaging, derivative packaging, etc. but similarly won't not answer questions about other things (although at least I'll redirect when soemthing is clearly about Ubuntu proc
[00:38] <persia> esses or working with an Ubuntu team, etc.)
[02:36] <lfaraone> We don't need FFes for RC bug syncs, right?
[02:38] <ScottK> persia: None of that would make directing people away from here for packaging questions for Ubuntu appropriate, would it?
[02:38] <ScottK> lfaraone: If they also bring new features you do.
[02:38] <persia> ScottK: Indeed, no.  People asking questions about working on Ubuntu (whether packaging-related or not) should be answered ehre.
[02:39] <ScottK> persia: OK.  I don't know if you changed it or not, but /topic in that channel was confusing people.
[02:39] <lfaraone> persia: how often is http://qa.ubuntuwire.com/bugs/rcbugs/ regenerated? half the listed packages have already been synced. (not that I'm complaining :P )
[02:40] <persia> lfaraone: Last updated Mon Mar 15 15:39:58 2010
[02:40] <freeflying> do you have any problem with dbus upgrade in lucid's schroot?
[02:40] <persia> Maybe it's targeting karmic stuff?
[02:43] <persia> lfaraone: See if http://qa.ubuntuwire.com/bugs/rcbugs/lucid/ more closely matches what you seek.
[02:43] <lfaraone> persia: aha.
[02:44] <persia> freeflying: I don't seem to have an old dbus installed in any of my lucid schroots.  I remember dbus being a prior problem because it starts a service that needs stopping prior to unmount.
[02:45] <lfaraone> ScottK: would any of http://packages.debian.org/changelogs/pool/main/m/mirage/mirage_0.9.3-5/changelog.html count as "new features"
[02:46] <ScottK> lfaraone: I'd say no.
[02:47] <lfaraone> ScottK: okay, just checking.
[03:09] <freeflying> persia: i don't remember we have had similar issue before
[03:10] <persia> freeflying: So, why do you have dbus (or any service, really) running inside the schroot?
[03:11] <freeflying> persia: I'm doing upgrade my lucid chroot
[03:11] <persia> I understand.  Why is dbus in there?
[03:11] <freeflying> persia: afaik, dbus has disabled to restart service inside chroot
[03:11]  * persia looks
[03:12] <freeflying> persia: due to build dependency
[03:13] <persia> Ah.  I understand.  I guess I don't encounter that by upgrading before installing build-deps.
[03:13] <persia> I didn't have any issues with the last upgrade on a running system.
[03:37] <lfaraone> nhandler: shouldn't the archive administrators be subscribed to bug 486807 since you ACK'd it?
[03:38] <nhandler> lfaraone: You need someone to ACK the actual sync request
[03:39] <lfaraone> persia: ^^, you told me to ping you once we got ~ubuntu-release approval on 486807
[03:39] <lfaraone> nhandler: so for a sync request with a FFe, you need ~ubuntu-release approval, ~ubuntu-*-sponsors approval, and then a manual push from an archive-admin?
[03:40] <nhandler> lfaraone: Basically, after FF, you need the release team's approval in addition to any other ack's that you would normally need
[03:41] <persia> lfaraone: Cool.  If nobody else does, I'll upload it as soon as I'm done with the thing I'm in the middle of doing.
[03:41] <nhandler> persia: It is a sync
[03:41] <persia> Oh, right.
[03:41]  * persia ACKs
[03:41] <micahg> nhandler: you want to take another look at pidgin0microblog?
[03:42] <nhandler> micahg: Yeah, I guess I can
[03:43] <nhandler> micahg: You will want to file a separate bug for the removal request
[03:43] <micahg> nhandler: k
[03:43] <micahg> nhandler: can I also ask you for Beta Freeze main upload exemtions?
[03:43] <micahg> *exemptions
[03:43] <nhandler> micahg: Once you do that, I'll ACK them both. You can get someone else to ACK the actual changes
[03:43] <nhandler> micahg: For what?
[03:44] <micahg> nhandler: Firefox, Thunderbird, Xulrunner
[03:46] <nhandler> micahg: Not until I review what the changes are.
[03:46] <micahg> nhandler: k, lets get this done, then I'll explain
[03:46] <micahg> bug 530660 bug 538914
[03:49] <nhandler> micahg: ACK'd
[03:49] <micahg> nhandler: so, subscribe ubuntu-archive now to the removal bug?
[03:50] <micahg> nhandler: you might want to remove u-u-s from the second bug
[03:50] <nhandler> micahg: See https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing%20Packages
[03:51] <micahg> nhandler: it doesn't make any sense
[03:51] <nhandler> micahg: Basically, it is the same process as a sync
[03:52] <micahg> nhandler: I thought only archive admins can remove?
[03:52] <nhandler> micahg: Yes, but the request to remove needs to be approved by a dev
[03:52] <micahg> nhandler: k
[03:52] <RAOF> micahg: How's gjs going?  Do you want me to prod at it again, or do you have it under control?
[03:52] <persia> More generally, the archive-admins typically perform most functions on behalf of developers, so need to have some developer on behalf of which they are doing things.
[03:53] <micahg> RAOF: I haven't been able to pin down asac to discuss it yet, so you can have a shot at it if you want
[03:53] <nhandler> That is true. Most of their tools require them to specify the name of the developer who requested the change
[03:53] <micahg> RAOF: otherwise, as soon as I know I'll update the bug
[03:53] <RAOF> “Want” is perhaps too strong a term. :)
[03:53] <RAOF> Ok.  I'll leave it with you.
[03:54] <micahg> RAOF: I figure you have more important stuff to work on :)
[03:54] <nhandler> Night
[03:54] <micahg> nhandler: you off?
[03:55] <nhandler> micahg: Yeah. Hilight me if you need me to look at anything more, or send me a message. I'll look at them tomorrow
[03:55] <micahg> nhandler: ok, thanks
[03:56] <nhandler> micahg: Keep up the great work
[03:56] <micahg> nhandler: thanks :)
[03:56]  * micahg needs to apply for MOTU when this cycle is over...
[03:58] <micahg> persia: I would only need 1 Beta freeze exception if we had a mozilla package set :)
[03:58] <persia> michas: Nothing stops you from applying for one.
[03:59] <micahg> persia: you said you were going to talk to asac about it
[03:59] <persia> micahg: And the number of freeze exceptions you need is entirely unrelated to how many packages you can upload.
[03:59] <persia> *every* developer is subject to the release team.
[03:59] <micahg> persia: no, I would have uploaded 2 of them before the freeze :D
[03:59] <persia> I did.  I explained the process, and pointed at the docs.  I don't know that he's done anything with this information.
[04:00] <micahg> persia: k, I'll follow up then
[07:20] <directhex> anyone feel it's worth chasing freeze exceptions for http://pinta-project.com/ ?
[07:21] <persia> directhex: Probably not.  There's lots more useful work to be done, and that can get dropped in next cycle with very little pain.
[08:11] <dholbach> good morning
[08:46] <abogani> http://launchpadlibrarian.net/40935125/buildlog_ubuntu-lucid-i386.avr-libc_1%3A1.6.7-1ubuntu1_FAILEDTOBUILD.txt.gz
[08:46]  * abogani waves
[08:47] <abogani> I have a problem: the avr-libc package build perfectly in my KVM Lucid VM but it failed on LP (above link)
[08:47] <abogani> Could anyone suggest me something?
[08:48] <geser> "sh: epstopdf: not found
[08:48] <geser> "
[08:49] <geser> the package is missing a build dependency on texlive-font-utils
[08:50] <Rhonda> Ah yes, I think pgadmin3 might be a good candidate to sync again. The new upstream release was just a bugfix release.
[08:50] <abogani> geser: I have totally missed it. Thanks a lot! Sorry for disturb!
[09:28] <\sh> zul: bug #531706 <- it's not a bug in zend-framework
[09:35] <bdrung> persia, TheMuso: my membership in u-u-s expires, can you renew it?
[09:36] <lifeless> should be able to renew that one yourself
[09:36] <TheMuso> bdrung: Afaik things are being changed atm, I am not sure what team has taken over. I have been meaning to withdraw my admin powers recently actually.
[09:37] <lifeless> but yeah there is only one sponsor team now AIUI
[09:38] <dholbach> yes
[09:38] <bdrung> renewing the membership by myself is not possible. according to the mail i have to contact one of you.
[09:38] <dholbach> bdrung: let me add you to ubuntu-sponsors
[09:39] <dholbach> I just updated the documentation
[09:41] <bdrung> dholbach: thanks
[09:43] <dholbach> if somebody could check out https://code.edge.launchpad.net/~dholbach/ubuntu-dev-tools/permissions-reorg/+merge/21355 - that'd be nice :)
[09:44] <geser> dholbach: is there a reason why you proposed a merge of your ubuntu-dev-tools branch instead of simply merging them?
[09:45] <dholbach> geser: oh, that's how I do it in other projects
[09:45] <dholbach> we peer-review everything there
[09:51] <geser> dholbach: the changes look good. It's unrelated to your changes but the paragraph about sponsorship could use some rewording as requestsync now checks upload permissions instead of simply team membership.
[09:52] <dholbach> geser: I just pushed my changes now - do you think it's worth filing a bug about the doc changes?
[09:52] <geser> yes please, so it doesn't get forgotten
[09:57] <dholbach> done
[09:58] <dholbach> bug 538990
[11:01] <dholbach> DktrKranz, lucas: I uploaded a new ubuntu-dev-tools - do you think you could get it into debian too?
[11:08] <DktrKranz> dholbach: sure thing
[11:09] <dholbach> DktrKranz: awesome - but it's still sitting in the queue
[11:09] <dholbach> https://launchpad.net/ubuntu/lucid/+queue?queue_state=1&queue_text=dev-tools
[11:09] <DktrKranz> oh, indeed. here it explains I haven't seen it :)
[11:09] <dholbach> :-)
[11:10] <DktrKranz> it's not a problem per-se, as I merge from bzr anyway
[11:10] <dholbach> ok, gotcha
[11:12] <persia> DktrKranz: Just FYI: none of my foreign-chroot stuff currently works in Debian.  I'm hoping it *will* work at some point in the future, but at that point it will need specific divergence in Debian from Ubuntu.  Any suggestions on where to push that if I can make it work?
[11:14] <DktrKranz> dholbach: I'll push it in a couple of days, I'd like to finish some dak coding first, does it sounds good?
[11:15] <DktrKranz> persia: u-d-t already has some divergences (basically for python-apt 0.8 API), we can probably add some specific checks (lsb_release based) as mvo and I did for gdebi
[11:16] <persia> DktrKranz: Oh, right.  lsb_release is probably the solution for the actual scripts.  I'll also want to add a substvar for Suggests:
[11:17] <persia> And with those bits it won't need divergence for my work.
[11:17] <persia> Thanks for the guidance.
[12:17] <Rhonda> I'd like to ask for a freeze exception for pgadmin3. The new upstream version is a bugfix release. How to proceed?
[12:23] <Riddell> Rhonda: if it's only a bugfix and there's no features, you don't need a feature freeze exception
[12:23] <persia> Rhonda: Does it build & run in lucid?
[13:00] <Rhonda> persia: I would expect so, yes.
[13:01] <Rhonda> Riddell: Well, it's still a new upstream version, so it might have to follow that process to make that clear.
[13:01] <persia> Rhonda: Really, you don't need an exception if it's bugfix only.  Also, the person who first said you didn't is one of the release managers, so even if you did, you just got an IRC ACK, which is considered acceptable.
[13:04] <Rhonda> Oh, didn't know that. :D
[13:04] <Rhonda> So … what's needed then? Regular sync request?
[13:05] <persia> Yep.
[13:05] <persia> Extra points for actually testing build/run on lucid :)
[13:31] <Rhonda> Bug #539061 - hope I did it right. :)
[13:32] <persia> Looks right to me
[13:33] <persia>  /s is arguably a minor feature, but not likely one that would affect any other software, or even most users by default.
[13:35] <Rhonda> It's in documentation parts only so it doesn't affect anything. I just put it in because lintian compl^Hhintend and I didn't notice it earlier. ;)
[13:36] <persia>  /s is only documentation : it actually worked before?
[13:36] <Rhonda> Yes.
[13:37] <persia> heh.  that's not clear from the upsteam changelog, but means it *definitely* didn't need FFe :)
[13:37] <Rhonda> Once in the manpage, twice in the changelog, twice in the NEWS file.
[13:37] <Rhonda> Erm, wait.
[13:38] <Rhonda> What are you refering to with /s?
[13:38] <Rhonda> Oh, that one.
[13:38] <persia> 2010-01-10 GL 1.10.2 Select the server choosen with the /s command-line argument.
[13:38] <Rhonda> Right, found it.
[13:40] <Rhonda> Darn year change, makes the diff from 1.10.1 to 1.10.2 unreadable with changes of "2002 - 2009" to "2002 - 2010"  %-(
[13:53] <duanedesign> persia: while reviewing patches i found a submitted patch that has already been applied upstream. i assume that bringing in the new revisioin is preferable to applying the patch downstream?
[13:54] <persia> duanedesign: Depends on the bug.  If it's critical, and the new upstream would break FF, and there's not enough reason for an FFe, then cherrypicking is fine.
[13:54] <nigelb> duanedesign: depends on the patch
[13:54] <nigelb> bah, too slow
[13:54] <persia> duanedesign: In most cases, we'd just wait for upstream to come naturally.
[13:54] <duanedesign> yeah its not a critical bug. Thank you
[14:27] <dupondje> somebody else also noticed the translation bugs in gnome-power-manager? Seems some items are not translated
[14:30] <dpm> dupondje, I haven't noticed any. It might be that the translation team for your language has not yet finished the translation. If the translation is complete and there are still untranslated strings, I'd recommend you to file a bug in the ubuntu-translations project (adding a bug task for gnome-power-manager) -> https://bugs.launchpad.net/ubuntu-translations/+filebug
[14:31] <dupondje> dpm: there was a translation bug that I fixed upstream, but everything in the po file was fine, seems like it just didn't got translated
[14:32] <dpm> dupondje, can you point me to the upstream bug? I can have a look if you like
[14:33] <dupondje> well it was just a translation error I fixed, this got into 10.04 already, the translation was correct for the rest. But seems still some untranslated items
[14:34] <dupondje> like when you click on the icon, it tells me 'laptop-accu is charged'
[14:34] <dupondje> while it should be translated :p
[14:34] <dupondje> in the overview: Status: fully-charged
[14:34] <dupondje> Tijd tot vol: xx seconds => seconds = english imo :D
[14:39] <Rhonda> BlackZ: You confuse me. :)
[14:39] <BlackZ> Rhonda: ?
[14:40] <Rhonda> BlackZ: pgadmin3, we discussed it in here and I was told that sync request is appropriate. :)
[14:42] <BlackZ> Rhonda: u-p-a was not subscribed, btw it's ok now
[14:43] <Rhonda> What's u-p-a? The website says u-s
[14:44]  * Rhonda starts to wonder if BlackZ is the confused person here or me. :)
[14:46]  * persia is curious about u-p-a as well, never having heard that term.
[14:47] <BlackZ> Rhonda: I mean ubuntu package archive - btw, it was just an misunderstanding
[14:47] <Rhonda> I'm not a ubuntu developer, even when Mark says that from time to time, so I need to use u-s.  :)
[14:51] <nigelb> If a packages does not build properly in karmic (broken dependencies) and fixed in Lucid with a new package, worth an SRU?
[14:51] <nigelb> or should it go into backports?
[14:52] <nigelb> bug 452845 - this issue is fixed with the new epiphany-extensions-more that was synced in Lucid
[14:53] <persia> nigelb: It's worth an SRU if (and only if) the patch can be cherrypicked.
[14:53] <persia> nigelb: And backports are not for bugfixes.
[14:54] <nigelb> persia: nope.  Its a completely new package
[14:54] <persia> Yeah, that's not good for SRU.
[14:54] <nigelb> epiphany stopped using python based extensions in favor of javascript based ones
[14:55] <nigelb> so the new package is entirely new
[14:55] <dupondje> "ngettext minute minutes 10"
[14:55] <dupondje> this should give translated output right ?
[14:57] <nigelb> so this package can have a backport to karmic?
[14:57] <BlackZ> Rhonda: sorry btw for the bug, just a mistake - and yes, you're right, if you aren't an ubuntu developer you must subscribe u-u-s. I had marked it as "Incomplete" because I tought it hasn't an FFE
[14:59] <Rhonda> BlackZ: No big deal, and don't take it anywhere personally, it just considered funny. :)
[14:59] <dpm> dupondje, I can see the "is charged" untranslated string, yes. It might be that we have to wait for the next language pack after the beta. If they still appear untranslated, I'd recommend you to comment it on the ubuntu-translators mailing list or file a bug
[15:00] <dupondje> dpm: I'm checking the code atm, like the '10 minutes' is translated with ngettext, but if I run 'ngettext minute minutes 10' in console, it doesn't get translated ...
[15:02] <Rhonda> BlackZ: I am just trying to find my way into it, and even though I might sound like I know quite a bit I'm still new. :)
[15:02] <Rhonda> … on this side of the sea, that is.
[15:03] <dpm> dupondje, 'ngettext -d gnome-power-manager minute minutes 2' works for me (I get «minuts»)
[15:03] <BlackZ> Rhonda: all can make a mistake. Aren't you agree?
[15:05] <Rhonda> BlackZ: Of course, in the meantime it is even allowed to think that the sabdfl can make a mistake. :)
[15:06] <dupondje> dpm: indeed, seems to work here also with domain set
[15:06] <BlackZ> Rhonda: I'm saying I'm wrong, not sabdfl ;)
[15:06] <BlackZ> however, I think we can stop this discussion.
[15:07] <dupondje> but where is the 'domain' set in the code ?
[15:07] <persia> BlackZ: Also, FF isn't about version numbers: it's about features.  Depending on upstream's release policies and procedures, it's possible to have new upstream without new features, and depending on the nature of random patches, it's possible to have feature changes without new upstreams.
[15:09] <dpm> dupondje, in C apps using autotools, like g-p-m, it is generally set in the build system in configure.ac or Makefile.am (can't remember which one right now), as GETTEXT_PACKAGE. Then this gets substituted in the code, generally in the initialisation code, as a parameter to bindtextdomain or a similar gettext function
[15:10] <duanedesign> persia: havent had much luck reviewing patches. do you have a minute to help me?
[15:11] <persia> duanedesign: Sure.
[15:11] <dpm> dupondje, here it is -> http://bazaar.launchpad.net/%7Eubuntu-branches/ubuntu/lucid/gnome-power-manager/lucid/annotate/head%3A/src/gpm-main.c#L182
[15:11] <dpm> defined here -> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/gnome-power-manager/lucid/annotate/head%3A/configure.ac#L103
[15:12] <duanedesign> persia: i found a couple new reports that are fails to build that have patches attached. But the op already made a debdif as well. Not sure what more i could do on those.
[15:13] <persia> duanedesign: Were the patch posters also following other Ubuntu Development guidelines, or were they folks you often see about?
[15:14] <duanedesign> persia: the poster has submitted 3 in the last few days. 1 has been 'uploaded'
[15:14] <duanedesign> bug 538386
[15:15] <Rhonda> persia: Especially the postgres people are extremely good examples with respect to good release management in that respect, and pgadmin3 isn't too far off from that. :)
[15:15] <hyperair> hmmm unified ubuntu-sponsors team eh? so how do i know what i can sponsor and what i can't?
[15:15] <dupondje> dpm: thx, the function to get the translation is here: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/gnome-power-manager/lucid/annotate/head%3A/src/gpm-common.c
[15:16] <dupondje> but it doesn't seem to translate it somehow
[15:16] <persia> Rhonda: Indeed.  There's a few bugs against pgadmin I've noticed marked as "Fixed in 1.12" which I find especially nice.
[15:16] <directhex> duanedesign, FWIW, the patch looks correct to my eye
[15:17] <persia> hyperair: http://qa.ubuntu.com/reports/sponsoring
[15:17] <persia> hyperair: Please file bugs to make that better (submitting branches speeds the process)
[15:17] <dpm> dupondje, I still don't know what the issue is, though. What's the exact problem? Which particular string is not getting translated? Is there a bug for it somewhere?
[15:18] <persia> duanedesign: Since those are all getting subscribed to sponsors, etc., I'd recommend just unsubscribing the review team.
[15:18] <nigelb> persia: a documentation fail perhaps?
[15:18] <persia> duanedesign: Essentially, we walk a thin line between helping make sure we don't lose patches and not getting in the way of developers using launchpad for workflow support.
[15:18] <nigelb> persia: ah, the script is causing a slight havoc
[15:19] <persia> nigelb: overanxious script, I think.
[15:19] <Rhonda> persia: 1.12??  *goestocheck*
[15:19] <nigelb> persia: this is when people force lp to accept debdiffs as patch, IMHO that is not needed
[15:19] <dupondje> dpm: in the overview you have 'Time to full: xxx seconds' translated it should be 'Tijd tot vol: xxx seconden' but it shows 'Tijd tot vol: xxx seconds' the 'seconds' aren't translated
[15:19] <duanedesign> persia: kk
[15:20] <persia> nigelb: But it *is* a patch.  Works with `patch`, `bzr patch`, etc.
[15:20] <persia> nigelb: So for any sane file management tool, it is indistinguishable from any other patch (run file against one sometime).
[15:21] <persia> nigelb: That LP happens to be currently broken is a different issue.  I'm not convinced that these deserve the "patch" tag though.
[15:21] <nigelb> persia: it is, it is, but this is only a workaround until the script it fixed
[15:21] <Rhonda> persia: Ah, the ipv6 part, found it. :)
[15:21] <nigelb> persia: you mean debdiffs should also come under the purview of reviewers?
[15:23] <dpm> dupondje, I cannot see any reference to seconds in that file. Do you mind the "%i minutes" and hours in http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/gnome-power-manager/lucid/annotate/head%3A/src/gpm-common.c#L57, for example?
[15:23] <dpm> Do you _mean_, I meant
[15:24] <persia> nigelb: Whether a patch is a debdiff is irrelevant.  Whether the patch submitter is participating in Ubuntu Development is relevant.  Random patches, even in debdiff format, not being tracked by developers need patch review.  Stuff in the sponsors queue doesn't.
[15:24] <abogani> The workflow for build PPA packages is the same for official packages, right? Sorry for stupid question but I have a package that build perfectly in PPA but not in my pbuilder env.
[15:24] <nigelb> persia: bah, forget earlier comment.  I misread what you wrote
[15:25] <dupondje> dpm: now thats weird, it really outputs for example 0 seconds ...
[15:26] <dpm> dupondje, then perhaps it is a bug and it is not marked for translation in the code...
[15:27] <james_w> abogani: hi, are you looking at the avr-libc build failure?
[15:27] <abogani> james_w: Exactly.
[15:28] <persia> abogani: The chroots in the PPAs should be similar to the chroots in the Ubuntu environment, I believe.  pbuilder can be very different.  The most common cause of issues is a requirement for network access during build.
[15:28] <james_w> abogani: heh, sorry, didn't notice you had just asked a question :-)
[15:29] <dupondje> its just weird where it gets the seconds from :)
[15:29] <dupondje> heh
[15:29] <abogani> james_w: I should fill a new bug report or it is a  "bzr push" enough?
[15:29] <james_w> it's an odd error
[15:29] <james_w> abogani: push it and request a merge again please
[15:32] <dpm> dupondje, might be somewhere else in the code, I've tried "ngettext -d gnome-power-manager "%d second" "%d seconds" 1" and that gives me translated output
[15:35] <dupondje> dpm: found
[15:35] <dupondje> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/gnome-power-manager/lucid/annotate/head%3A/src/gpm-statistics.c
[15:35] <dupondje> function gpm_stats_time_to_text
[15:35] <abogani> james_w: done. Sorry for my mistake.
[15:35] <james_w> abogani: no problem, it happens
[15:39] <dpm> dupondje, ok, does 'ngettext -d gnome-power-manager "%d second" "%d seconds" 1' give you localized output?
[15:40] <dupondje> yes :)
[15:44] <dupondje> return g_strdup_printf ("%.0f seconds", value); => return g_strdup_printf ( ngettext ("%.0f second","%.0f seconds",value), value);
[15:44] <dupondje> something like that ? :)
[16:03] <dupondje> dpm: made upstream bug, gnome is still synced from upstream atm ?
[16:08] <dpm> dupondje, if I'm not mistaken, yes, until 2.30.1 and sometimes .2
[16:08] <dpm> dupondje, could you point me to the bug? I'd be interested to subscribe and follow it
[16:09] <dupondje> https://bugzilla.gnome.org/show_bug.cgi?id=612950
[16:11] <dpm> dupondje, awesome, thanks
[16:14] <directhex> hyperair, did you 0ubuntu1 b-c-e? i spy a james_w and we could smile sweetly at him to do some archive-adminning
[16:16] <dupondje> dpm: the other translation issue is related to DeviceKit-Power
[16:16] <dupondje> seems there are no translations there ?!
[16:20] <dpm> dupondje, hmm, I'd have to check, I don't remember any of our team has translated DeviceKit-Power upstream, perhaps it is not yet set up for translations?
[16:36] <ryanakca> Could someone take a look at bug 538283 please?
[17:45] <dupondje> dpm: seems they 'fixed' it, but not correctly :p
[17:59] <dpm> dupondje, oh, they were quick!
[20:14] <hyperair> directhex: sorry my hands are tied.
[20:14] <hyperair> directhex: if you feel like handling it, please do so.
[20:15] <hyperair> directhex: oh yeah, could you clarify the copyright of the icon, please?
[20:15] <hyperair> directhex: the ubuntuone.png icon
[22:33] <Spirits-Sight> anyone in here that good with connecting CE device to Ubuntu to see it as a storage device?
[22:49] <bobbbo> hello everyone!
[23:05] <crimsun> thank goodness for tmpfs-mounted /var/cache/pbuilder/build
[23:09] <RAOF> crimsun: *Yes*
[23:58] <ramiro> hi
[23:58] <psusi> dang it, what was the program to install build dependencies needed to build a package?