[05:40] <pitti> Good morning
[05:41] <ajmitch> morning pitti
[05:44]  * pitti starts upgrade to oneiric and holds breath
[07:54] <didrocks> good morning
[07:58] <nigelb> bonjour didrocks :)
[07:59] <didrocks> hey nigelb ;)
[09:02] <dholbach> good morning
[09:04] <didrocks> good morning dholbach
[09:04] <dholbach> hey didrocks
[09:04]  * pitti hugs dholbach
[09:23]  * nigelb waves to pitti
[10:25] <cjwatson> now that UDS is over, could an MIR team member have a look at bug 780591, please?  it's blocking all kinds of things
[10:27] <seb128> didrocks, ^ you seem to be the only mir guy around, could you have a look to unblock that maybe? if you are busy we can probably wait a few hours for mterry to be there
[10:27] <didrocks> seb128: was just opening the launchpad page :)
[10:27] <didrocks> cjwatson: on it now
[10:27] <seb128> didrocks, thanks
[10:28] <cjwatson> didrocks: thanks
[11:17] <DasEi> paste
[11:17] <DasEi> sry, wrong tab
[11:41] <siretart> could some archive admin please process libav from binary NEW? it will cause a library transition that I would like have completed at least for main before the first alpha release…
[11:43] <StevenK> siretart: Looking.
[11:47]  * cjwatson syncs ibus-table-chinese into main to replace several previous ibus-table-* packages
[12:03] <StevenK> siretart: Done.
[12:15] <debfx> does raptor2 need a MIR to get into main? raptor is already in main
[12:16] <cjwatson> if it's a matter of switching out one for the other and raptor2 is indeed just a newer version of raptor, that doesn't require an MIR, but raptor doesn't seem to be due for demotion yet
[12:17] <cjwatson> also, raptor2 build-depends on yajl; unless that's just split-out code, that needs an MIR
[12:27] <debfx> raptor can probably be demoted once the packages waiting on raptor2 are built
[12:28] <cjwatson> OK, well if you get an MIR through for yajl we can then sort out the rest
[12:49] <siretart> StevenK: ty!
[12:53] <ion> :-D http://security.goatse.fr/compiz-denial-of-service-vulnerability
[12:55] <Take> Good day
[12:56] <Take> Hopefully I'm on the right channel, I'm building an custom lucid installation cd and I haven't found an tool which would include upgrades and go trough depencies automatically
[12:56] <Take> I tought that Simple-CDD would do the trick, but I can't figure out how to use it with ubuntu repositories
[12:57] <Take> So, should Simple-CDD do the trick or is there some other tool for ubuntu to maintain packages & download necessary files from the offical repository
[13:40] <hychen> kan/wi2
[13:54] <cjwatson> ogra_: (or anyone else ARMish) Debian has started to remove maemo/hildon packages from unstable.  Should we follow suit?
[13:55] <cjwatson> http://lists.alioth.debian.org/pipermail/pkg-maemo-maintainers/2011-February/001059.html
[13:56] <StevenK> I would sorely love to.
[13:59] <maxb> If the same update has been SRUed for maverick and is now to be SRUed for lucid, do I just clear the verification-done tag and restart the process?
[13:59] <maxb> On the same bug, that is
[14:33] <ev> do we know when the audio recordings from the sessions will start to land, and where? Incidentally, the old http://uds.ubuntu.com/audio/uds-m is broken.
[14:47] <smb> slangasek, So the oneiric version of ifenslave is an improvement. I added my comments to bug 714904. What would be the next steps? Is it enough to add nominations to the report?
[15:15] <stgraber> smoser: hey! for foundations-o-weblive-integration, can I give you a generic workitem to investigate the work needed for x2go web browser integration ?
[15:21] <stgraber> smoser: I assigned it to you for now (last work item at https://blueprints.launchpad.net/ubuntu/+spec/foundations-o-weblive-integration). Feel free to move it to the "Unassigned" list or re-assign to someone else.
[15:38] <tkamppeter> pitti, hi
[15:38] <pitti> hey tkamppeter, how are you?
[15:39] <tkamppeter> pitti, fine. Did you do the annotations for the s-c-p session?
[15:39] <pitti> tkamppeter: I haven't been in that one
[15:43] <tkamppeter> pitti, sorry, where do I find the session notes in general?
[15:43] <pitti> tkamppeter: ideally they were copied to the whiteboard; if not, check the etherpad
[15:43] <pitti> tkamppeter: find the session on http://summit.ubuntu.com
[15:44] <pitti> tkamppeter: there is a small icon on the top left in the session box which links to the pad
[15:44] <tkamppeter> pitti, thanks.
[15:47] <tkamppeter> pitti, I have also done a session about color management for Ubuntu. This has no drafter yet and it is something where the work items get distributed over several people of the Desktop team. Who should take the drafter roll there.
[15:48] <pitti> tkamppeter: at this point I think you are the person who knows about it most
[16:03] <sladen> tkamppeter: you should probably own the colourd session;  but I was in it and can add some input if you want
[16:04] <smoser> stgraber, thats fine.
[16:19] <micahg> is there an archive admin around that can copy chromium from the ubuntu-security-proposed PPA to $RELEASE-proposed?
[16:25] <slangasek> smb: unless the workflow has changed significantly, no one is looking at release-nominated bugs; so good that you've pinged me here.  Nominations accepted.  Do you want to prepare SRU uploads?
[16:28] <smb> slangasek, might be good training I guess...
[16:31] <tkamppeter> sladen, it would be great if you could help me on this Blueprint. I have added the notes now.
[16:35] <smb> slangasek, Naively I would take the current natty/maverick source slap in the new code while preserving the changelog where I add some comment about pulling in a new version...
[16:36] <slangasek> smb: the changelog should be based on the one for the package in natty/maverick and documenting what's being changed to fix this bug
[16:37] <slangasek> smb: since maverick and natty include the same version of the package, you'll want to pay attention to https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update%20the%20packaging
[16:41] <smb> slangasek, Ok, thanks. Not sure there is but the changes include documentation/examples changes the not directly are part of this bug report. Would I need to open en extra bug for that or are those kind of changes ok without a bug reference?
[16:43] <slangasek> smb: I would not expect those changes to be included in an SRU upload - only the changes directly related to fixing the bug
[16:43] <smb> ok, makes sense
[16:47] <bigon> seb128: could you have a look at https://bugs.launchpad.net/ubuntu/+source/telepathy-logger/+bug/745803 ?
[16:48] <seb128> what about it?
[16:48] <bigon> damm I post my comment in double
[16:48] <bigon> seb128: well see https://bugs.launchpad.net/ubuntu/+source/telepathy-logger/+bug/745803/comments/17 and /20 /o\
[16:49] <seb128> bigon, seems somebody is on it
[16:50] <bigon> ah right
[16:51] <tkamppeter> pitti, still there?
[17:14] <pitti> tkamppeter: will be back in ~ 30 mins
[17:28] <dholbach> pitti, good work on fixing the -no bug!
[17:28] <smb> slangasek, argh, so the latest ifenslave package has also a fix for two bugs in preinst to forget to check "$2"=="" and to look at if-up/down.d/wireless-tools instead of ifenslave. Lucky that a) those are not in the ifenslave package, so there is no checksum and b) there is a third bug that the package name is ifenslave-2.6 not ifenslave anyway. Since all of that is not related to the bug I skip that, and will file a debian bug
[17:29] <slangasek> smb: sounds good :)
[17:37] <apw> slangasek, these changes to linux-libc-dev for multi-arch, did we test the result at all ?
[17:42] <apw> someone last week mentioned that video for linux packages were breaking, to do with kernel headers, can anyone point me in the right direction
[17:42] <apw> to a bug or a person :)
[17:45] <cjwatson> apw: v4l1 was dropped and packages need to cope - it might just be that?
[17:46] <cjwatson> perhaps your interlocutor didn't realise it was deliberate
[17:46] <apw> heh that is entirly possible
[17:46] <cjwatson> if it's v4l2, that would be a different matter
[17:46] <apw> cjwatson, do we have a definatiive ftbs list
[17:47] <cjwatson> http://qa.ubuntuwire.com/ftbfs/
[17:50] <ev> mdz: Is this what you were referring to when you said there may already be a tech board decision on recording success/failure: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-August/000601.html
[17:51] <mdz> ev, no, that's not the bit I was thinking of. thanks for the reminder, i'll dig it up
[17:51] <ev> mdz: thanks
[17:53] <slangasek> apw: right - linux-libc-dev multiarch was tested, from the rest of your comments it sounds like you're probably running into the v4l1 deprecation issue instead
[17:53] <apw> slangasek, sounds good thanks
[17:55] <micahg> slangasek: can you please copy chromium-browser from the ubuntu-security-proposed PPA to $RELEASE-proposed for lucid, maverick, and natty and apply overrides to put the binaries/source in universe?
[17:56] <slangasek> micahg: you have the command handy for that?
[17:56] <micahg> slangasek: I'll check
[18:01] <mdz> ev, I'm not having much luck finding it. I don't think it was a tech board decision or meeting, just a technical discussion about the installer and whether it was a good idea to try to capture information from successful installs
[18:01] <ev> okay
[18:01] <mdz> it was years ago, and maybe not helpful enough to warrant a lengthy search
[18:01] <ev> thanks just the same
[18:02] <ev> I've already started drafting the mail to ubuntu-devel, so I'll have that out for tomorrow.
[18:02] <micahg> slangasek: can you give this a sanity look, I've never prepared this before: http://pastebin.ubuntu.com/608521/
[18:06] <htorque> hello, everyone! can you tell me, how long it will take for this fix to go into -updates: https://launchpad.net/ubuntu/+source/pygobject/2.28.3-1ubuntu1.1 ?
[18:06] <micahg> htorque: should be sometime this week, there's usually a backlog after UDS
[18:07] <htorque> micahg: thanks, that's good. i just don't want to advise someone to enable -proposed.
[18:12] <smb> slangasek, I have copied proposed ifenslave packages to chinstrap:~smb/4review for review and sponsoring in case things look ok to you. Install fresh/upgrade (just not from that very old version) tested on 64bit builds for Maverick and Natty
[18:17] <slangasek> micahg: copied
[18:17] <slangasek> smb: chinstrap> very much not best practice for sponsorship :)  Could you please push a debdiff to the bug report?
[18:21] <slangasek> smb: debdiff howto: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff#Method
[18:22] <smb> slangasek, Sorry just got distracted on other channel. I would have done debdiff with debdiff, but I look at that page
[18:22] <slangasek> smb: right, if you're already familiar with the 'debdiff' command, then there's nothing new and interesting there ;)
[18:22] <smb> slangasek, We just normally did that for kernel packages for the sponsor to be just able to copy and sign
[18:22] <micahg> slangasek: thanks!
[18:23] <slangasek> micahg: n/p
[18:23] <slangasek> smb: that makes sense for kernels for various reasons, but kernels are a special case
[18:24] <smb> slangasek, Agreed, just happen to fall easily back to the "bad" habits. ;)
[18:24] <slangasek> :)
[18:25] <kotique> how much is this devel channel devel?
[18:25] <kotique> i'd like to disable any graphical setting on grub2. ANY
[18:25] <kotique> want a plain text line with bootstring prompt
[18:25] <slangasek> that seems like a user support question rather than a development question
[18:30] <kotique> yeah
[18:30] <kotique> grub2 wiki is dead, second link points to ubuntu's grub tutorial
[18:31] <slangasek> wgrant: should I assign https://blueprints.launchpad.net/ubuntu/+spec/foundations-o-lp-archive-access-update to someone with LP mojo?
[18:31] <kotique> thx anywayz
[18:31] <smb> slangasek, debdiffs attached to bug 714904
[18:31] <slangasek> smb: thanks! :)
[18:32] <smb> Dammit, those replies seem to come nearly at the same time I press enter.. ;)
[20:48] <bcurtiswx> Natty SRU request for Telepathy-logger https://code.launchpad.net/~bcurtiswx/ubuntu/natty/telepathy-logger/lp_745803_fix/+merge/60964
[20:50] <bcurtiswx> Thanks :)
[20:52] <stgraber> bcurtiswx: hmm, your changelog entry says "Add series file" but the diff doesn't touch debian/series and instead modifies debian/patches/git_eat_cpu.patch
[20:52] <bcurtiswx> stgraber, yeah i just noticed that.. im fixing that as we type :)
[20:52] <bcurtiswx> forgot the bzr add .. doh
[21:06] <slangasek> huh, where did the summit etherpad go
[21:11] <bcurtiswx> stgraber, thanks and I have fixed the problem :)
[21:13] <geser> cjwatson: is MoM having issues again? main.html    09-May-2011 00:41 362K
[21:14] <stgraber> bcurtiswx: as it's an SRU, you want ubuntu1.2 instead of ubuntu2 and you need to target it to natty-proposed instead of natty
[21:15] <bcurtiswx> stgraber, ah this i didn't know.  Thanks for that info
[21:21] <bcurtiswx> stgraber, done :)
[21:23] <maco> to get onto http://reports.qa.ubuntu.com/reports/sponsoring/ with a merge proposal... do you subscribe sponsors to the bug or the proposal?
[21:23] <maco> oh hey akk joined. tell her the answer too
[21:23] <stgraber> bcurtiswx: version number is good but debian/changelog still says "natty" instead of "natty-proposed" :)
[21:24] <bcurtiswx> stgraber, hahaha im such a fool..
[21:26] <bcurtiswx> stgraber, <crosses fingers> this time
[21:27] <micahg> maco: akk merge proposals against the UDD branch (lp:ubuntu/foo) are automatically added, for bugs, you subscribe ubuntu-sponsors
[21:28] <micahg> geser: yeah, I was going to ping cjwatson about it tomorrow, figured at least give him a day to catch up
[21:28] <maco> micahg: thanks
[21:29] <stgraber> bcurtiswx: looks good
[21:29] <bcurtiswx> stgraber, thanks :)
[21:29] <stgraber> I'll upload in a few minutes
[21:31] <vish> micahg: isnt the default for merges "ubuntu-branches" (or has that changed now?)
[21:32] <micahg> vish: that's the long form
[21:32] <maco> long form?
[21:34] <stgraber> bcurtiswx: uploaded to -proposed (you now have to wait for someone to accept it in -proposed, then test it and give feedback in the bug report, if succesful it'll be copied to -updates)
[21:35] <maco> i have been surprised at the speed of -proposed testing lately!
[21:35] <bcurtiswx> stgraber, much appreciated :)
[21:35] <micahg> maco: as opposed to using the lp:ubuntu shortcuts, you can specify the full path, lp:~ubuntu-branches/ubuntu/package/suite/branch-name
[21:36] <maco> the SRUs i did on release day had fix-verified within like 2 hours of being uploaded to proposed
[21:37] <stgraber> yep, SRUs go through a lot faster than they used to. Seems like we have more testers closely following what hits -proposed (also, the delay to get stuff into -proposed seems to be a lot shorter than it used to be)
[21:38] <maco> thats because they read the SRU checklist in teh bug *after* upload now
[21:38] <maco> instead of *wait for people to read stuff*  *wait for sponsor to upload* *wait for thing to be accepted*
[21:39] <maco> reading got rolled into accepting and now they cant really forget to accept after reading
[21:41] <vish> micahg: i meant, the reviewer is set to "Ubuntu branches" by default... just tried with a branch lp:~vish/ubuntu/... and if i dont specify a reviewer it sets "~ubuntu-branches" as the reviewer
[21:44] <micahg> vish: ok?
[21:44] <vish> but i think those might show up in the sponsor list as well..
[21:44] <micahg> vish: right
[21:44] <maco> vish: im guessing micah means that the sponsors webpage looks for that
[21:45] <vish> ah!
[21:45] <maco> akk: your fix is now showing up there
[21:46] <akk> Yay!
[21:47] <maco> akk: for future reference, on SRU's it should be natty-proposed instead of just natty
[21:47] <broder> i think the sponsors page looks for any mp against any branch owned by ~ubuntu-branches, but i don't remember
[21:47] <akk> maco: sorry, noted for future reference
[21:48] <akk> though I think it chose that by default when I ran bzr lp-open -- at what point should I have specified it?
[21:49] <broder> vish, maco: ah, yeah - the queue looks for merges where a review was requested by any of ~ubuntu-branches, ~ubuntu-sponsors, ~ubuntu-dev, or ~ubuntu-core-dev
[21:49] <akk> oh, in the bzr push path?
[21:49] <maco> akk: at the dch -i step, the top line in debian/changelog has the package version number and release name
[21:50] <vish> broder: yay, cool! thx! i always wondered why -branches and used to change it to -sponsors.. :)
[21:50] <broder> vish: there are other reasons to change it to sponsors-  in particular, it means that people on sponsors can properly reject merges, which they can't do for -branches
[21:51] <broder> (they can just change the status, which is mostly an ugly work around for not being able to claim the review)
[21:51]  * vish nods..
[21:53] <maco> broder: what does "Review type: _____" mean?
[21:53] <broder> maco: i think the intent is to indicate if, say, you're only doing a "design" review or something like that, but in practice i just always leave it blank
[21:54] <cjwatson> geser: thanks, I'll have a look
[21:54] <cjwatson> ValueError: process failed 9: dpkg-source -x libtrace3_3.0.10-1.dsc /srv/patches.ubuntu.com/unpacked/libt/libtrace3/3.0.10-1
[21:55] <cjwatson> dpkg-source: error: none of the filenames in ---/+++ are relative in diff `libtrace3-3.0.10/debian/patches/fix-shlib-depends' (line 6)
[21:55] <cjwatson> *blink* that's a rather special quilt patch
[21:57] <cjwatson> current dpkg can cope though
[22:03] <cjwatson> geser: hacked around for now; next run should hopefully do better
[22:04] <geser> thanks
[22:04] <micahg> thanks cjwatson
[22:05] <geser> does MoM also process packages that are unchanged in Ubuntu?
[22:05] <cjwatson> (I stuck a dpkg-source wrapper script into the front of $PATH which points to an unpacked current dpkg)
[22:07] <cjwatson> geser: it shouldn't normally, no
[22:08] <cjwatson> at least not non-trivially
[22:14] <broder> stgraber: it looks like caff is misencoding your name, fwiw
[22:14] <stgraber> broder: as long as the signature is fine, I don't really care :) I'm used to seeing encoding issues with my name ;)
[22:15] <broder> fair enough :)