[04:42] <ScottK> jelmer: When do we get Samba 4.0 packages.  Congratulations on the release.
[05:17] <ScottK> pitti: I went through and accepted the postgresql SRUs, but I didn't see 9.1.7 updates for precise/quantal.  Is that intentional?
[05:40] <achiang> when merging a package from debian, do people have a favorite strategy?
[05:40] <achiang> about to tackle merging valgrind from experimental
[05:40] <achiang> and it's been a while since we synced
[05:45] <achiang> ah, wisdom - https://wiki.ubuntu.com/UbuntuDevelopment/Merging
[05:48] <ScottK> For a merge from experimental, pay particular care to why the package is in experimental and not unstable.
[05:48] <ScottK> We may not want it at all.
[05:49] <infinity> achiang: Take the base debian version we're based on (pull-debian-source valgrind 1.2.3-4), debdiff against ours, then attempt to apply said diff to new version, resolve conflicts, make sure it all makes some sort of sense, drop useless patches we don't need anymore, profit.
[05:49] <infinity> ScottK: I think case, I think it's just staging a new upstream due to the freeze, but I haven't looked closely yet, since achiang wanted to cut his teeth on it.
[05:50] <infinity> s/I think case/In this case/
[05:50] <infinity> Typing's not my strong suit tonight.
[05:50] <ScottK> Right.  I didn't look at this case either.
[05:50] <StevenK> s/ tonight//
[05:50] <infinity> StevenK: Shut it, vegemite boy.
[05:53] <achiang> infinity: "attempt to apply diff to new version", you mean apply diff to *old* version, right? (since you have a diff of old vs. new...)
[05:56] <infinity> achiang: No, you diff old_debian and ubuntu_current to get our delta, then apply to new_debian[C.
[05:57] <achiang> oic
[05:57] <infinity> achiang: Which is, essentially, what merge-o-matic does, but it doesn't track experimental.
[06:01] <achiang> hm, i actually don't see valgrind in experimental, just unstable
[06:01] <achiang> http://packages.debian.org/search?keywords=valgrind
[06:02] <achiang> and that explains why we have m-o-m output https://merges.ubuntu.com/v/valgrind/REPORT
[06:24] <achiang> merging d/control and pondering the Architecture: line, shall i drop the archs we do not support in ubuntu, such as mips and s390x?
[06:25] <StevenK> No
[06:28] <achiang> interesting. ok
[06:35] <pitti> Good morning
[06:36] <pitti> ScottK: hm, they are supposed to be there, I uploaded them all; I'll check
[06:36] <snkt> hello
[06:36] <ScottK> pitti: I think I know what I did wrong.
[06:37] <snkt> can anyone help me how to install splash screen on ubuntu 11.10  for ARM .... I have used ubuntucore image for ARM...
[06:37] <pitti> arges: hello, what's up?
[06:37] <ScottK> I found quantal.
[06:37] <pitti> ScottK: what happened?
[06:37] <ScottK> I was looking in New, not Unapproved.
[06:38] <pitti> ah :)
[06:39] <ScottK> pitti: I still don't know where precise is though.
[06:40] <pitti> ScottK: right, I see accepts for hardy, lucid, oneiric, and precise/8.4, missing precise/9.1 and quantal
[06:40] <ScottK> That matches what I have.
[06:41] <pitti> odd; I don't see them in rejected either; I'll reupload them
[06:48] <ScottK> them/it, right?
[06:48] <ScottK> You should have gotten an accept for quantal just now.
[06:49] <pitti> ScottK: no, also 9.1 for precise
[06:49] <pitti> so "them"
[06:49] <pitti> https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=postgresql-9.1 -> there now, too
[06:50] <ScottK> Right.  That's the one I thought was missing.  Just accepted it.
[06:50] <pitti> ScottK: thanks!
[07:31]  * achiang tentatively tries to build valgrind after doing his merge
[07:44] <RAOF> didrocks: Sure.
[07:44] <didrocks> hey infinity! It seems that -dbgsym packages for daily-build didn't migrate to the dbgsym repo in the end
[07:44] <didrocks> thanks RAOF for noticing it
[07:44] <didrocks> so, if I remember correctly, we disabled -dbgsym publishing in the ppa so that they can migrate correctly?
[07:44] <didrocks> because when they were published, the copyPackages method failed
[07:45] <didrocks> it seems something is blocked in the pipe :)
[07:51] <RAOF> didrocks, infinity: Argh, false alarm. PEBKAC
[07:55] <dholbach> good morning
[08:28] <doko> xnox, you did the last python-defaults merge, any reason for keeping the diff in the tests?
[09:24] <xnox> doko: the other dmitry did last python-defaults merge =) >> mitya57 but he is not online.
[09:25] <doko> ahh, ok
[09:28]  * xnox knew the day will come of multiple dmitry. Back in school there were three in my class, so nothing new.
[09:55] <smb> Every "family" should have their Dmitry... Oh wait that was Igor...
[11:53] <pitti> would anyone know what "juju debug-log" is good for? It never shows anything for me, not even with -r
[11:53] <pitti> it would be useful to have it tail /var/lib/juju/charms/*/charm.log on all machines
[11:59] <rbasak> didrocks: hey, are you about? Do you remember sponsoring bug 1014732 for me around four weeks ago? It got trumped by a security update while sitting in the SRU queue. Would you mind re-uploading my rebased debdiff for me please? It's exactly the same patch with a bumped version number, and I've checked that it still build and works. I've been trying to land this since October :-(
[12:00] <didrocks> rbasak: not sure I've time to rebuild mysql today and sponsoring this before holidays :) maybe see with the security team as you got a bad luck due to them? micahg can help I guess :)
[12:01] <rbasak> OK, well thanks for sponsoring it last time, anyway!
[12:01] <didrocks> rbasak: no worry :) sorry for not being able to do it again, not sure who was supposed to be the patch pilot today :)
[13:03] <tkamppeter> pitti, hi
[13:23] <rbasak> ogra_: ping
[13:47] <pitti> hello tkamppeter
[14:28] <arges> pitti, hi. I was trying to figure out how to setup an sbuild environment that builds ddebs for a kernel build. not sure if there is an easy way to accomplish this
[14:29] <pitti> arges: I thought our kernel package would build the ddebs by itself, without any special magic?
[14:30] <arges> pitti, i'm also doing this with a precise host, and a lucid amd64 schroot
[14:30] <arges> pitti, no special magic is required. I tried the default method and no ddebs were found
[14:44] <ppisati> any cups/printer/scanner guy around?
[15:16] <micahg> rbasak: maybe mdeslaur_ will sponsor for you if you ask him nicely
[15:16] <hallyn> stgraber: is there a way to tell from https://launchpad.net/ubuntu/precise/+queue?queue_state=4&queue_text=lxc why )
[15:16] <hallyn> huh
[15:17] <hallyn> by whom 0.7.5-3ubuntu66 was rejected
[15:17] <hallyn> (sorry, bad cut)
[15:18] <rbasak> mdeslaur_: please would you consider sponsoring bug 1014732 for me? You've trumped me for a security update twice now :-/
[15:18] <mdeslaur_> rbasak: sure, I'll take a look a little later
[15:18] <rbasak> thank you!
[15:18] <mdeslaur_> rbasak: sorry about that :)
[15:18] <rbasak> It's OK, I understand. Just a bit frustrating when it happens after sitting in a queue for a month!
[15:19] <stgraber> hallyn: no, we're still missing the auditing feature in LP
[15:19]  * rbasak wonders when the next security update for mysql will arrive
[15:19] <stgraber> hallyn: though there appears to be a 9 days newer version of lxc in the unapproved queue, so that's probably why someone rejected the older one
[15:20] <hallyn> oh!  i thought i looked for on e there.  ok, makes sense then.
[15:20] <stgraber> hallyn: people with queue access fairly often go and reject the older of two duplicate entries
[15:22] <rbasak> infinity: I've not managed to reproduce 1079185 for SRU verification. The installer seems to set UUID= in fstab even though I had a label on the filesystem before, blkid listed that label and I reused the existing partition. The label remains after the install, too (and blkid still prints it). Thoughts? This is blocking bug 1084106 now :-(
[15:22] <rbasak> (I'm trying to reproduce on quantal and then verify that it's gone in quantal-proposed, but I can't reproduce on quantal)
[15:40] <barry> doko: is virtualenv still working for you on raring?
[15:41] <doko> barry, 2.7 or 3.3?
[15:41] <barry> doko: 2.7
[15:41] <barry> $ virtualenv /tmp/foo
[15:42] <doko> http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=python2.7
[15:42] <doko> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695707
[15:42] <barry> works w/3.3
[15:43] <barry> doko: that's it
[15:43]  * barry sees a yak needing a shave
[15:51] <tkamppeter> pitti, hi
[15:58] <ScottK> pitti: You're going to fix up your Hardy postgresql SRU, right?
[15:58] <pitti> ScottK: yes; a bit puzzled what went wrong there
[15:58] <ScottK> OK.  Thanks.
[16:05] <pitti> stgraber, cjwatson, xnox: I'm currently reviewing the top ten brainstorm items; two of them are installer issues: http://brainstorm.ubuntu.com/idea/29909/ and http://brainstorm.ubuntu.com/idea/29984/; would you like to respond to either of those?
[16:06] <cjwatson> I can take the former, although I don't know if I can commit to doing so in what remains of this year
[16:07] <cjwatson> Send me mail or I'll forget :)
[16:14] <zul> can someone help me out here, according to http://people.canonical.com/~ubuntu-archive/testing/raring-proposed_probs.html xen is blocked because xen-utils-common' has no installation candidate but im not sure why
[16:14] <pitti> cjwatson: yes, I was planning to, I just wanted to ask around who would like to respond to which
[16:14] <pitti> cjwatson: thanks!
[16:14] <pitti> cjwatson: mid-January is fine
[16:20] <pitti> stgraber, xnox: so would either of you like to respond to http://brainstorm.ubuntu.com/idea/29984/ ?
[16:21] <pitti> stgraber, xnox: target is a response mid-january, with a time commitment < 1 h
[16:21] <cjwatson> zul: note that that isn't the place to look for what's blocking migration from -proposed to release
[16:21] <zul> cjwatson: what is the place then?
[16:22] <cjwatson> zul: that error's because xen-utils-4.2 should be in universe rather than main - corrected that
[16:22] <zul> ah i understand
[16:22] <cjwatson> zul: http://people.canonical.com/~ubuntu-archive/proposed-migration/
[16:22] <zul> cjwatson: ok thanks
[16:23] <cjwatson>     * i386: nova-xcp-network, nova-xcp-plugins, xcp-guest-templates, xcp-squeezed, xcp-xapi, xcp-xapi-debug
[16:23] <cjwatson> i.e. trying to promote the new xen renders those packages uninstallable
[16:23] <tkamppeter> pitti, is http://brainstorm.ubuntu.com/ not included in the Ubuntu/Canonical/Launchpad SSO?
[16:23] <cjwatson> zul: at least some of this is because the new xen-api failed to build
[16:23] <zul> cjwatson: yeah im working on that
[16:24] <zul> cjwatson: xen-api hard codes xen-4.1 everywhere
[16:24] <pitti> tkamppeter: it seems not indeed; at least it has its own user/password field
[16:25] <cjwatson> zul: ok - well, proposed-migration won't let xen in until it's all ready at onc
[16:25] <cjwatson> e
[16:25] <zul> cjwatson: so fix xen-api first?
[16:26] <stgraber> pitti: this sounds like a xnox kind of thing as I've not looked at that part of ubiquity in a while and so can't remember exactly what the current behaviour is. However if xnox doesn't have time for the review, I guess I can do it.
[16:26] <cjwatson> if you want xen 4.2 in raring then you have to fix xen-api, yes
[16:27] <pitti> stgraber: ack, merci; I'll see whether xnox can
[16:27] <smb> cjwatson, The message about installation candidate sounds a bit weird. Though I may not understand the terms there. xen-utils-common is produced by xen...
[16:28] <cjwatson> smb: I've already debugged and fixed that, so you don't need to try to :)
[16:28] <xnox> pitti: stgraber: well I can respond, but it will be a decline. Inherently installer is there to wipe your data and install ubuntu. Adding extra warnings "warning we wipe your data to install ubuntu" will not help. And as stgraber found out many USB drives report as internal drives....
[16:28] <cjwatson> smb: testing/raring-proposed_probs.html only considers main
[16:28] <cjwatson> (well, and restricted, I think)
[16:29] <cjwatson> xnox: we don't necessarily have to respond to brainstorm requests as written; one approach would be to clarify the way in which drives are presented
[16:29] <pitti> xnox: fair enough; note that this is about responding by a qualified person, not an obligation to actually fix it in exactly the proposed manner; there are often better implementations which achieve the same result
[16:29] <cjwatson> which isn't necessarily in terms of their hardware interface
[16:29] <smb> cjwatson, Ah ok. Fair enough. :)
[16:30] <pitti> xnox: e. g. there coudl also be something like the device list showing an USB symbol, etc.
[16:30] <didrocks> barry: hey did you test with software-center that the python3 related-changes didn't clash? (we don't import everything, just 3 modules, but something to ensure)
[16:31] <barry> didrocks: i didn't.  what's a good test?  should i just try to install both in a chroot?  and then what? ;)
[16:31] <pitti> xnox: so, I'll send you an official question by mail with the details
[16:32] <didrocks> barry: oh no, just start software-center: File -> Sync between computers, set it up with your ubuntu one account
[16:32] <didrocks> barry: do the same with another computer, and you should see the diff view and all the data after 5 minutes
[16:32] <didrocks> barry: this is what oneconf is for btw ;)
[16:33] <barry> didrocks: :)  okay, i can try that in a little bit
[16:33] <didrocks> thanks!
[16:34] <xnox> pitti: cjwatson: sounds like mpt might actually be a better person to respond. It's more about usability than code.
[16:35] <pitti> mpt: ^ would you like to respond to http://brainstorm.ubuntu.com/idea/29984/ wrt. how to present internal vs. external drives in a better way?
[16:36] <pitti> mpt: target is mid-january with a time investment of < 1 h
[16:36] <tkamppeter> pitti, thanks. I created an account now, with the same user name as I have in LP.
[16:37] <achiang> infinity: hi, you awake yet? :)
[16:40] <infinity> achiang: In meetings.
[16:40] <infinity> (But yes)
[16:41] <achiang> infinity: ok, i'll stop bugging you. :)
[16:53] <tkamppeter> pitti, I have another quuestion: the cups-pk-helper MIR is ACKed now, how should we pull cups-pk-helper into Raring? Recommends from system-config-printer or direct call from ubuntu-meta?
[16:57] <seb128> tkamppeter, gnome-control-center already recommends it so nothing to do
[17:04] <tkamppeter> seb128, thanks.
[17:46] <mitya57> doko: do you know that your python3-defaults upload re-added python3.2 to supported versions?
[17:46] <mitya57> https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/python3-defaults/raring/revision/57/debian/debian_defaults
[17:57] <doko> $ apt-cache show python3-all
[17:58] <doko> Source: python3-defaults
[17:58] <doko> Version: 3.3.0-2ubuntu2
[17:58] <doko> Depends: python3 (= 3.3.0-2ubuntu2), python3.3
[17:58] <doko> mitya57, ^^^
[17:58] <mitya57> doko: but it still needs to be removed from debian/debian_defaults
[17:58] <mitya57> or it will cause FTBFSes like this one: https://launchpadlibrarian.net/125618205/buildlog_ubuntu-raring-i386.unity-mail_1.2.4~ppa1_FAILEDTOBUILD.txt.gz
[17:59] <doko> ohh crap
[18:14] <smoser> cjwatson, around ?
[18:14] <smoser> i'm wanting to mount a iamage, add proposed, apt-get update && apt-get upgrade.
[18:15] <cjwatson> Only slightly.  Dinnertime soon.
[18:15] <smoser> there is a grub update in proposed, and that is giving me grief.
[18:15] <cjwatson> Put it on hold then?
[18:15] <smoser> well, the gurb update and the linux-iage update together
[18:15] <smoser> that would work around
[18:16] <Riddell> is there a way to do a substitution variable for Depends: ${upstream-version} ?
[18:16] <cjwatson> ${source:Upstream-Version}
[18:16] <cjwatson> see 'man deb-substvars'
[18:16] <smoser> but is there a way i could tell it to just not worry about running grub-probe
[18:16] <cjwatson> I'm sorry, I don't have time to look into that now
[18:17] <Riddell> lovely thanks cjwatson
[18:18] <smoser> cjwatson, ok. it is something i'd like to have a solution for at some point though.  generally i'd like to be able to just 'apt-get dist-upgrade' and tell grub to just leave things as they are.
[18:19] <cjwatson> in general grub cannot just "leave things as they are" on upgrade without running grub-probe
[18:19] <cjwatson> any workarounds for that will have to be exceptions
[18:22] <smoser> cjwatson, i'm ok with needing to supply some  environment variable or something.
[19:11] <zul> mterry: so stevedore, the tests run fine when its not in a buildd
[19:12] <adam_g> how does the LP Janitor map new package releases containing bug fixes to bugs that get updated with to Fix Released? does it scrape the changelog? rely on some metadata in the source package? or on bzr branch metadata?
[19:16] <mterry> stev
[19:16] <mterry> whoops
[19:16] <bdmurray> adam_g: the changelog
[19:17] <mterry> zul, I don't remember the failures exactly, but are they not simply missing dependencies or something?
[19:18] <zul> mterry:  http://pastebin.ubuntu.com/1428165/
[19:23] <mterry> zul, when it works locally, do you have the package installed?  Maybe it's not looking in the build tree for what it needs
[19:24] <zul> mterry: yeah i think i need to set the PYTHONPATH
[19:36] <zul> mterry:  yeah that works
[19:44] <robru> adam_g, I believe it does scrape the changelog looking for something like (LP: #nnnnnnnn)
[19:48] <jono> stgraber, hey
[19:48] <stgraber> jono: hey
[19:48] <jono> stgraber, where can I find the current edubuntu logo?
[19:49] <jono> preferably as an svg?
[19:49] <stgraber> jono: http://www.edubuntu.org/edubuntu-text.svg
[19:50] <jono> thanks stgraber :-0
[19:50] <stgraber> np
[19:54] <highvoltage> stgraber: hmm, that doesn't seem to be the right logo
[19:54] <ScottK> Shhh.  You're spoiling stgraber's fun.
[19:54] <highvoltage> jono: could you use this one instead please? http://upload.wikimedia.org/wikipedia/commons/4/41/EdubuntuLogo.svg
[19:55] <jono> highvoltage, sure!
[19:55] <jono> just adding the logos to the ADK
[19:57] <highvoltage> okdk
[20:00] <stgraber> highvoltage: hmm, they look pretty much identical to me, besides the default size set in the svg :)
[20:01] <stgraber> though the actual .svg content is quite different
[20:04] <highvoltage> stgraber: the latter has the correct typeface colour
[20:05] <highvoltage> stgraber: (the circle of friends icon is also differently positioned, not that I care about that much, but might as well keep it consistant as we did so far)
[20:07] <stgraber> highvoltage: ok, updated the copy on humboldt to match that from wikipedia
[20:34] <bdmurray> @pilot in
[21:16] <cjwatson> adam_g: technically, it doesn't scrape the changelog.  dpkg-genchanges does that on the uploader side and puts the results into the Launchpad-Bugs-Fixed field of the .changes file.
[21:38] <tkamppeter> Someone of the Ubuntu SRU team here? For bug 1054495 cups 1.5.3-0ubuntu6 is waiting for approval in the -proposed queue and users are complaining that the package does not get available for testing.
[21:39] <bdmurray> tkamppeter: I'll look at it tomorrow
[21:39] <tkamppeter> bdmurray, thanks.
[22:15] <infinity> tkamppeter: Accepted (again).
[22:16] <tkamppeter> infinity, thank you very much.
[22:37] <bdmurray> stgraber: can you mark https://code.launchpad.net/~straemer/ubuntu/quantal/update-manager/fix-for-1058070/+merge/136551 as merged?
[22:37] <stgraber> bdmurray: done
[22:38] <bdmurray> thanks