[05:26] <pitti> Good morning
[06:17] <slangasek> cjwatson: the debconf source points at a bzr branch with rich history that's been out of date since maverick; do you want me to fix that up when merging from unstable, or should I instead drop the Vcs-Bzr field?
[07:22] <pitti> poolie: meh, "bzr get" deprecated? is there some way or amount of beer that I could convince you to keep it?
[07:22] <dholbach> good morning
[07:22] <pitti> poolie: we have convenient shorter aliases for a lot of other stuff like "mu" or "up", can we keep "get" as an alias?
[07:22] <StevenK> bzr br ?
[07:22] <pitti> poolie: after so many years it's just on everyone's fingers, not to mention in documentation
[07:30] <didrocks> good morning
[07:42] <ok2cqr> Hi, I would like to rebuild existing package from devel version of Ubuntu to Lucit. I downloaded source package, extracted it, made changes and now I want to pack it again.
[07:42] <ok2cqr> But the package is signed by someone and I can't build it even when I have my own gpg signature.
[07:43] <ok2cqr> Could you help me please how to re-sign the package with my signature?
[07:45] <broder> ok2cqr: sounds like you might be looking for the backportpackage script in ubuntu-dev-tools
[07:50] <ok2cqr> broder, I already have ubuntu-dev-tools installed but didn't have this script. I use ubuntu 10.04
[07:54] <dholbach> @pilot in
[07:56] <dholbach> broder, chrisccoulson: do you have any idea where we're going with the "sleep" branches (upower, indicator-session, g-p-m)?
[07:58] <dholbach> jdstrand, are you on bug 723830?
[07:59] <dholbach> barry, mvo: do you think https://code.launchpad.net/~hodgestar/software-properties/configurable-key-server/+merge/57406 can go into oneiric?
[08:01] <dholbach> cjwatson, james_w: can somebody of you mark https://code.launchpad.net/~barry/ubuntu/natty/winpdb/bug-761131/+merge/57787 as irrelevant?
[08:02] <mvo> thanks dholbach, looking
[08:02]  * dholbach hugs mvo
[08:07] <dholbach> rbelem, ScottK, do you think https://code.launchpad.net/~rbelem/ubuntu/natty/kubuntu-mobile-default-settings/plasma-mobile-patches/+merge/58018 is SRU material or is it something we should just get into oneiric?
[08:09] <dholbach> james_w, cjwatson: can you also please mark https://code.launchpad.net/~benoitg/ubuntu/natty/libofx/libofx.new-upstream-fix-661809-629996/+merge/58207 as irrelevant?
[08:14] <dholbach> chrisccoulson, micahg, does the patch in bug 766559 look alright to you?
[08:20] <dholbach> james_w, cjwatson: can you also please mark lp:~hrw/ubuntu/natty/armel-cross-toolchain-base/1.63 and lp:~hrw/ubuntu/natty/gcc-4.4-armel-cross/1.40 as irrrelevant for natty?
[08:21] <ohsix> bug 57787
[08:30] <cjwatson> dholbach: I've done the first two.  For the last one, please add some kind of commentary to the merge requests explaining why
[08:41] <dholbach> cjwatson, hrw said that it's OK to just get them into oneiric, but yeah, let me add it
[08:42] <dholbach> done
[08:42] <mdke> pitti: hiya
[08:42] <pitti> hey mdke
[08:42] <cjwatson> slangasek: so I think something complicated went wrong with the upstream branch import; if you want to fix that all up, I certainly wouldn't object, but if that isn't straightforward (I don't remember it being so) then feel free to drop Vcs-Bzr
[08:43] <mdke> pitti: is that you looking at the gnome-user-docs uploads?
[08:43] <pitti> yes
[08:43] <pitti> had to reject maverick due to a version number conflict, see my bug followup
[08:44] <mdke> pitti: ah, I haven't got that email yet, will wait for that. Thanks for looking at them though
[08:44] <cjwatson> dholbach: OK, rejected
[08:44] <mdke> pitti: I guess the existing versions in lucid and maverick also have the same version number though? (because the lucid package was copied over to maverick)
[08:44] <dholbach> thanks cjwatson
[08:45] <pitti> mdke: the lucid SRU worked fine
[08:47] <mdke> pitti: if I use ~ubuntu2.1 as the version number, will that cause problems for people upgrading from lucid to maverick?
[08:47] <mdke> (because lucid users will already have ~ubuntu3)
[08:54] <pitti> mdke: ah, right; use 3.1 then
[08:54] <mdke> pitti: cool, thanks
[09:04] <mdke> pitti: uploaded. Thanks again for your help
[09:09] <poolie> pitti: sorry; we could re-add 'bzr'
[09:09] <poolie> i mean 'bzr br'
[09:56] <pitti> slangasek: I forwarded your libxklavier patch to https://bugs.freedesktop.org/show_bug.cgi?id=37278, but I only gave a vague description as I didn't see the build failures myself; there might be some further request for info there
[10:01] <cjwatson> zul: could you merge apache2, which will include rebuilding it against openssl 1.0.0?
[10:15] <seb128> cjwatson, hey, do you plan to do a syncs round today?
[10:23] <dholbach> cjwatson, james_w: can you please mark https://code.launchpad.net/~menesis/ubuntu/natty/wsgi-intercept/natty/+merge/58498 as irrelevant? it was superseded by https://code.launchpad.net/~menesis/ubuntu/natty/wsgi-intercept/natty/+merge/61212
[10:23] <cjwatson> seb128: it's in progress
[10:23] <seb128> cjwatson, thanks
[10:23] <cjwatson> seb128: (or do you mean manual syncs?)
[10:23] <seb128> cjwatson, both... ;-)
[10:24] <cjwatson> autosyncs are in progress - I do plan to get to manual syncs though
[10:24] <seb128> excellent, thanks
[10:24] <cjwatson> dholbach: done
[10:24] <dholbach> cjwatson, thanks!
[10:30] <cjwatson> slangasek: could you merge wget?  it's part of the openssl 1.0.0 transition
[10:31] <slangasek> pitti: thanks for the forward!  If in doubt, pkg-config upstream (i.e., Tollef) will be happy to explain
[10:31] <slangasek> cjwatson: ack, queuing
[10:31] <slangasek> queuing and going to bed, that is :)
[10:31] <dholbach> Daviey, do you think it's worth getting https://code.launchpad.net/~abone/ubuntu/natty/procps/fix-for-753124/+merge/58905 into natty still?
[10:32] <dholbach> (seems like -10ubuntu2 didn't solve the problem)
[10:50] <Daviey> dholbach, looking
[10:55] <Daviey> dholbach, Not entirely sure TBH... it does look kinda large... I'm missing what the impact of it is TBH.
[10:55] <dholbach> Daviey, it looks like a cleanup of the patches because in 10ubuntu2 the patch was not really applied
[10:56] <dholbach> Daviey, at least that's what I got from the description of the merge proposal
[11:00] <Daviey> dholbach, yeah, that makes sense - but i missed if it meet SRU criteria.
[11:00] <Daviey> dholbach, I have a call now - but will delve deeper after this.
[11:00] <dholbach> Daviey, maybe just get it into oneiric then
[11:00] <dholbach> Daviey, thanks muchly
[11:00] <Daviey> no worries.
[11:03] <dholbach> cjwatson, can you also mark this one as merged https://code.launchpad.net/~xaba/ubuntu/natty/pytrainer/bug-760885/+merge/58908? seems it got into natty-proposed and -updates already
[11:04] <cjwatson> dholbach: the new revision mentioned at the end of the comment thread too?
[11:06] <dholbach> cjwatson, hum, looks like not - I'll follow up on the merge proposal
[11:08] <dholbach> cjwatson, oh no, it's included - it's just not documented in d/changelog
[11:09] <lifeless> dholbach: oh hai; I've been meaning to let you know - we recently fixed searching for bugs w/ patches in lp
[11:09] <lifeless> dholbach: which I believe was something important to you :)
[11:10] <dholbach> lifeless, oh nice - what exactly did you change?
[11:10] <lifeless> added an index
[11:10] <lifeless> so that it works in non geologic time
[11:11] <dholbach> do you still have a bug number for that somewhere?
[11:11] <cjwatson> dholbach: generally, if you could add a comment to the merge before asking me, that would be good - I'd like to be able to operate mostly on autopilot for this kind of thing rather than needing to review
[11:11] <dholbach> I'd like to understand it a bit better :)
[11:11] <cjwatson> it won't scale otherwise
[11:11] <dholbach> cjwatson, will do - that's entirely reasonable
[11:11] <dholbach> thanks
[11:12] <cjwatson> (well it obviously doesn't scale particularly well as it is, but ...)
[11:12] <cjwatson> I'll just dump in the IRC conversation for this one
[11:13] <dholbach> cjwatson, added a comment
[11:13] <dholbach> and let's hope it's fixed soon :)
[11:13] <cjwatson> done
[11:13] <dholbach> thanks
[11:27] <mpt> mvo, good morning, who do you think should be Approver for <https://blueprints.launchpad.net/ubuntu/+spec/foundations-software-maturity-ratings>?
[11:27] <cjwatson> mdeslaur: you're touched-it-last for isc-dhcp - are you likely to have time to merge it?
[11:49] <ScottK> dholbach: Seems SRu worthy
[11:52] <nigelb> ev: I welcome the collection of ubiquity success/failure, if you need help building the public-facing website, I could possible pitch in and help
[11:59] <dholbach> mdke, mako: CC meeting?
[12:09] <ev> nigelb: wonderful. If you could post your support to the mailing list post, I'd greatly appreciate it, as it will otherwise get lost here
[12:10] <nigelb> ev: sure, will do :)
[12:11] <ev> @pilot in
[12:15] <nigelb> ev: done :)
[12:17] <ev> thanks
[12:26] <barry> dholbach, mvo: any thoughts on the software-propoerties merge proposal?  is it worth looking at ~hodgestar's update?
[12:28] <barry> lifeless: ping
[12:36] <mdeslaur> cjwatson: are you offering to do it?
[12:37] <seb128> could somebody from the security team review bug #782972
[12:37] <seb128> ?
[12:37] <seb128> some of the GNOME3 components are depwaiting on it
[12:39] <cjwatson> stgraber: bug 778655 - looks like the new version is in Debian now?
[12:39] <cjwatson> mdeslaur: only if necessary - I'm drowning in library transitions
[12:40] <mdeslaur> cjwatson: I'll try and get to it this week
[12:40] <mvo> hey apachelogger - nice work on the dbusworker branch for software-properties! how do you feel about it? is it ready for merging?
[12:41] <apachelogger> mvo: did I make that one? ^^
[12:41] <cjwatson> mdeslaur: *nod*, thanks
[12:41] <apachelogger> ah yeah
[12:42] <apachelogger> mvo: needs some work & QA I think
[12:42] <mdeslaur> seb128: I'll get kees to take a look when he arrives
[12:42] <apachelogger> mvo: do you want it for oneiric?
[12:42] <seb128> mdeslaur, thanks!
[12:42] <seb128> mdeslaur, no real hurry but we are eager to get those GNOME3 bits to build ;-)
[12:43] <seb128> (eog and gedit are the ones waiting on it)
[12:43] <mdeslaur> seb128: argh! I need gedit! :)
[12:43] <seb128> hehe
[12:44] <mdeslaur> of course, now I'm wondering why an image viewer and a text editor need a _javascript library_...where's the world going to? :)
[12:44] <mvo> apachelogger: that would rock, I would love to get the gtk version to no longer run as root
[12:45] <seb128> mdeslaur, they need libpeas which is used for loading python and js code and use seed for js
[12:46] <seb128> mdeslaur, in practice I don't think any .js code is in the archive or loaded but the loader is there
[12:46] <apachelogger> mvo: I'll try to find someone to finish the work, though apparently my supply of python minions is a bit compromised ^^
[12:49] <mdeslaur> seb128: I see...thanks
[12:49] <seb128> yw
[12:49] <mvo> apachelogger: haha, ok - I will also try to squeeze in a bit of time to help out
[12:49] <mvo> barry: I check the diff out now
[12:50] <barry> mvo: cool.  i did make a slew of comments in the mp, but haven't looked to see if he addressed them
[12:50] <apachelogger> mvo: I might have found someone, if he has time ... I'll report back once I know more
[12:51] <mvo> great, thanks apachelogger
[12:51] <dholbach> barry, mvo: I'll leave that to you 2 :)
[12:54] <debfx> pitti: I have added support for .svgz files to dh_scour. the patch is on bug #781810. could you have a look at it?
[12:55] <broder> dholbach: the sleep/upower branches should have been rejected. i think at this point they might be caught in the SRU/branch re-targeting bug
[12:55] <mpt> mvo, hi, did you see my question about who should be the Approver for <https://blueprints.launchpad.net/ubuntu/+spec/foundations-software-maturity-ratings>? (sorry I dropped off for a bit)
[12:55] <pitti> debfx: oh, thanks! will do ASAP
[12:55] <dholbach> broder, ok - can you add some kind of justification/explanation to the bug report?
[12:55] <dholbach> err merge proposal
[12:56] <broder> at least one of the patches already has an explanation from me as to why i don't think it should be merged
[12:56] <dholbach> then Colin or James can reject it :)
[12:56] <mvo> mpt: I'm happy to be the approver (if I'm not the assigne), otherwise probably slangasek
[12:56] <dholbach> @pilot out
[12:56] <dholbach> I'll continue piloting later on
[12:56] <dholbach> now it's lunch time
[12:56] <mpt> mvo, ok, made slangasek the Approver and you the Assignee :-)
[12:59] <lifeless> barry: hi?
[13:00] <barry> lifeless: hi.  this page times out for me all the time.  thought you might be able to blacklist it or something?   (i think you asked me about this?) https://bugs.launchpad.net/ubuntu/+bugs?field.tag=python27
[13:01] <lifeless> barry: sadly no, its really sick.
[13:01] <lifeless> dholbach: bug 618392
[13:02] <barry> lifeless: ah well.  it was worth a shot :)
[13:02] <lifeless> night
[13:05] <dholbach> thanks lifeless
[13:07] <mpt> mvo, is it intended that the UI for <https://blueprints.launchpad.net/ubuntu/+spec/foundations-o-update-manager-btrfs> is entirely in Grub? What if someone doesn't use Grub?
[13:13] <cjwatson> mpt,mvo: I thought the agreement in that session was to put any non-trivial UI in the real system, specifically not in the boot loader
[13:14] <mpt> cjwatson, ah, I see "GUI tool for selecting old snapshots (needs input from mpt what it looks like/where it should go)" in the session notes but not in the work items
[13:15] <cjwatson> although I think "because trying to do the UI in the boot loader would suck" is probably a better objection than "what if someone doesn't use GRUB" in the case of btrfs :-)
[13:21] <mvo> mpt: for oneiric we probably just go with a text ui in friendly-recovery
[13:21] <mpt> mvo, what's friendly-recovery and how does one run it?
[13:23] <cjwatson> it's the text menu you get if you select recovery mode from the boot menu
[13:23] <mvo> mpt: its in the grub menu, the "recovery" option. its a small text UI to help recovery from various aspects of breakage
[13:24] <rbelem> dholbach, ScottK, i think that patch was applyed already
[13:33] <zul> cjwatson: yep im just waiting for apr as well
[13:36] <cjwatson> zul: OK, I synced that a little while ago so it shouldn't be too long - thanks
[13:36] <zul> cjwatson: np
[13:41]  * pitti suspects cjwatson's upload karma can only be measured in powers of ten these days
[13:41] <micahg> dholbach: I should talk to chrisccoulson about that, I think there might have been a better solution
[13:41] <cjwatson> heh :)
[13:42] <cjwatson> pitti: I still only have about a quarter of your karma though
[13:42] <cjwatson> where does it all come from?  language packs?
[13:42] <cjwatson> or are you just awesome?
[13:43] <mpt> mvo, ok, it's up to you whether you add a work item for me to design something there
[13:43] <pitti> cjwatson: I think it still misattributes langpack uploads to me
[13:43] <pitti> cjwatson: presumably because it identifies the langpack-builders GPG key as being an alter ego of me (which it kind of is)
[13:44] <pitti> I filed a bug about it ages ago
[13:44] <cjwatson> ah yes
[13:49] <mvo> mpt: ok, I think for now it should be fine the text ui will be pretty borning
[13:54]  * Sweetshark is getting close to a real work environment: a) local git mirror -> check b) local tarball mirror -> check c) local CI builder for master -> running d) local CI builder for release branch -> tbd ...
[13:55] <andyrock> hi, i've a problem in transition from gtk2 to gtk3. Is it the right place for asking support?
[13:58] <ScottK> andyrock: No.  Support is in #ubuntu.
[13:59] <mpt> mvo: Sorry to keep bugging you. :-) Does <https://blueprints.launchpad.net/ubuntu/+spec/foundations-o-apt-mirror-method> require any design work for the "UI support [in] software-properties"?
[14:01] <jamespage> doko: are you looking at bug 779174? just noticed your comment...
[14:01] <mvo> mpt: yes, some UI selement that essentially says "pick the best one automatically"
[14:02] <doko> jamespage: yes
[14:02] <highvoltage> a bit off-topic, but the awesome scale makes it worth while posting here:
[14:02] <highvoltage> http://linux.slashdot.org/story/11/05/17/0242244/Boot-Linux-In-Your-Browser
[14:03] <jamespage> doko: so is the fix for that issue likely to be in openjdk?
[14:04] <doko> jamespage: yes, see my last comment for a work around
[14:05] <stgraber> cjwatson: it was on my post-UDS todolist. I'll have a look now. Thanks for the reminder.
[14:05] <jamespage> doko: right-oh; I'll stop digging....
[14:05] <doko> the main issue is that we'll see such breakage will probably occur with other multiarch conversions too
[14:06] <jamespage> doko: I suspect so
[14:07] <axp2> highvoltage: that's quite cool, probably has some interesting applications when it is more developed too
[14:09] <stgraber> cjwatson: bug updated
[14:15] <mvo> highvoltage: I have to say that I'm blown away by how fast it is
[14:18] <Satoris> Installing the Gnome 3 PPA makes my machine (or actually VirtualBox install) fail to boot. Is this a known issue?
[14:24] <highvoltage> mvo: yes, me too!
[14:25] <jamespage> hey - can anyone help me understand why I can find libjibx1.2-java in Debian but not in Ubuntu?  I can find a launchpad page in the Ubuntu project but its completely empty...
[14:34] <cjwatson> jamespage: it's in the list of new packages that haven't been processed yet.  I take it you want it?
[14:35] <jamespage> cjwatson: ultimately yes but it can wait; causing a FTBFS elsewhere at the mo
[14:35] <jamespage> cjwatson: thanks for looking :-)
[14:35] <cjwatson> jamespage: ah, yes, I see why we didn't process it - is this supposed to be replacing libjibx1.1-java, currently in main?
[14:36] <jamespage> cjwatson: hmmm - not sure - I'll take a look
[14:36] <cjwatson> (which also ships a libjibx-java binary)
[14:36] <cjwatson> E: libjibx-java is in main but its source (libjibx1.2-java) is not.
[14:37] <cjwatson> this is overridable, but preferably under instructions by somebody who knows about the packages in question
[14:43] <sconklin> cjwatson: do you have anything to add to https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/747090 ? I'm about to respin the Natty stable update and will be reverting some patches, not sure whether this should be among them
[14:43] <cjwatson> sconklin: I'll test it now - I couldn't do it at UDS because my ISO images were on the external disk for which I'd forgotten the power adapter
[14:44] <sconklin> cjwatson: thanks!
[14:47] <jdstrand> dholbach: I am not actively working on 723830 (I don't think I have the necessary expertise to ack the patch). I was just trying to make sure it was still a problem
[14:49] <matttbe> Hello,
[14:49] <matttbe> It seems that Cairo-Dock BZR branches on Ubuntu (lp:ubuntu/cairo-dock & lp:ubuntu/cairo-dock-plug-ins) are not up to date (and broken?).
[14:49] <matttbe> What can I do and/or who can I contact?
[14:49] <matttbe> Note that this bug has already been reported: https://bugs.launchpad.net/udd/+bug/704694
[14:52] <matttbe> I can see the problem there: http://package-import.ubuntu.com/status/#analysis
[14:52] <matttbe> but I don't know what can I do to resolve this problem
[14:52] <cjwatson> sconklin: verified now, so please keep that patch :-)
[14:53] <sconklin> cjwatson: great, thanks! I hate pulling them
[14:54] <cjwatson> (a whole half-hour before the Brad-stated deadline)
[15:00] <sconklin> pitti: I have a question about https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735171 - you wrote "Marking as verification-failed, but as this is not a regression, this doesn't block -updates migration.", does that mean that you don't think the patch should be reverted?
[15:03] <pitti> sconklin: if you are about to upload a followup kernel, then I'm fine with reverting it (it's safer, of course)
[15:04] <pitti> sconklin: it just means that if would have been the only problem, it wouldn't block -updates migration
[15:05] <sconklin> pitti: ok, thanks there is also this one which needs to be reverted, best I can tell - https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/700292
[15:10] <pitti> sconklin: *nod*
[15:17] <mvo> pitti: if you have a moment, could you please check the natty-proposed queue? there is a software-center 4.0.2 there, one is old, one from a couple of minutes ago, the old one can be rejected now. would be nice to get the new one reviewed because for new installs the review stats are currently not showing
[15:19] <qchn> Coi
[15:19] <pitti> mvo: there is just one software-center there
[15:19] <pitti> mvo: https://launchpad.net/ubuntu/natty/+queue?queue_state=1
[15:19] <cdbs> mvo: Looks like the new one superseeded the old one... ?
[15:20] <qchn> 22.  #kapy          │16:19:50  cdbs | mvo: Looks like the new one superseeded the old one... ?                                                                                                      │ bantu
[15:20] <qchn> Whoops, sorry.
[15:20] <qchn> emberassing.
[15:23] <mvo> pitti: oh, how odd. but in any case the new one is the right one :)
[15:25] <micahg> matttbe: the bug is sufficient to have someone look at it, the lack of branch update doesn't block further uploads
[15:27] <qchn> Does anyone know how to decrypt luks over the network and start this script with initramfs?
[15:28] <pitti> mvo: you didn't mean the aptdaemon which is in the queue? there's already an unverified aptdaemon in -proposed, I wanted to get that to -updates first
[15:28] <pitti> or you reupload with -v, if it's urgent
[15:28] <mvo> pitti: thanks, aptdaemon is not super urgent, fix is pretty small etc, but it should be fine to wait
[15:29] <dholbach> rbelem, you're right
[15:29] <dholbach> cjwatson, james_w: can one of you please mark https://code.launchpad.net/~rbelem/ubuntu/natty/kubuntu-mobile-default-settings/plasma-mobile-patches/+merge/58018 as merged?
[15:31] <broder> cjwatson or james_w: could you also reject https://code.launchpad.net/~psusi/ubuntu/natty/upower/sleep/+merge/54093 https://code.launchpad.net/~psusi/ubuntu/natty/indicator-session/sleep/+merge/54094 and https://code.launchpad.net/~psusi/ubuntu/natty/gnome-power-manager/sleep/+merge/54095 ?
[15:32] <james_w> broder, https://code.launchpad.net/~psusi/ubuntu/natty/indicator-session/sleep/+merge/54094 was approved, why reject it?
[15:41] <broder> james_w the 3 merges are tied together. it's only correct if the other two are accepted, and they weren't
[15:41] <james_w> ok
[15:41] <broder> thanks
[15:46] <dholbach> @pilot in
[16:07] <broder> are there any examples on how to migrate a sysv script that uses /etc/default to upstart? i.e. in terms of migrating the /etc/default settings
[16:10] <broder> (i'm trying to evaluate https://code.launchpad.net/~vanvugt/ubuntu/oneiric/mediatomb/fix-212441/+merge/60574 . i'm not particularly fond of the approach, but not sure if there's a better example i can point the submitter at)
[16:26] <micahg> broder: that /etc/default change should happen in Debian, not Ubuntu
[16:26] <broder> micahg: huh? he's trying to convert the package to upstart, and Keybuk says that upstart jobs shouldn't use /etc/default
[16:27] <micahg> broder: ugh
[16:27] <micahg> broder: do we normally carry a similar diff for other packages with upstart?
[16:28] <broder> honestly, i have no idea. but i think it could be a good idea in this particular case, since they're running into a race condition from networking devices not being up
[16:28] <micahg> broder: also, since there is upstart in Debian, just not the default, I'd like to try to get that into Debian first
[16:29] <broder> hmm...i bet that debian's not interested in Keybuk's belief that upstart jobs shouldn't use /etc/default...
[16:29] <broder> also, the policy to ship config jobs for multiple init systems isn't finalized, is it?
[16:29] <micahg> broder: not yet, but that can be worked around in debian/rules
[16:29] <broder> eww :)
[16:34] <matttbe> micahg: thank you :) . But if I want to propose a new version, I've to create a debdiff, join some files, etc. instead of simply launch bzr merge-upstream...
[16:40] <apw> cjwatson, do we have oneiric dailies yet ?
[16:40] <ogra_> lol
[16:41] <mdeslaur> slangasek: any objections to me killing the hurd compatibility patch in pam security updates?
[16:41] <ogra_> apw, we're (well, currently colin is)  switching the live builder tool, that will take a bit i guess
[16:41] <matttbe> james_w: Hello and sorry to ping you but is it possible to repair Cairo-Dock bzr branches? (lp:ubuntu/cairo-dock & lp:ubuntu/cairo-dock-plug-ins). My bug report has been marked as duplicated of this one: LP: #494481
[16:41] <apw> ogra_, oh ok, hrm
[16:43] <james_w> matttbe, hi, that's probably possible to fix
[16:44] <matttbe> james_w: great! and can I do something?
[16:45] <james_w> matttbe, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/cairo-dock/oneiric/revision/23 <- what did you do to create that revision?
[16:45] <poolie> ev: that's a great concept regardless of the various difficulties
[16:46] <matttbe> james_w, yes I guess I forgot to use bzr merge-upstream for this one...
[16:47] <james_w> matttbe, I'm not sure what the best way to recover from this is
[16:47] <james_w> matttbe, an easy one is to uncommit your revisions back to the last-good one, and have the importer take care of the new versions
[16:47] <james_w> that obviously loses your history
[16:48] <matttbe> james_w: I'm sorry but at this time I though I had to use uscan as before
[16:48] <rbelem> dholbach, :-)
[16:48] <james_w> the other solution is to decide where to put that missing tag, but as merge-upstream wasn't used there isn't a "correct" place to put it
[16:49] <matttbe> james_w: but I prefer to lose this history and use the branch. but yes, if we can simply add these missing tags, it's better
[16:51] <matttbe> james_w: note that if I add a upstream tag, the bzr merge-upstream command remove the debian directory. But it's not a problem if it removes this folder only this time
[16:52] <matttbe> james_w: this is what I said there: https://bugs.launchpad.net/udd/+bug/758032
[16:54] <broder> micahg: it looks like there are already a handful of packages in universe that ship upstart, though i suspect that most/all of them are ubuntu-native and not merged from debian
[17:00] <ev> poolie: thanks!
[17:04] <slangasek> mdeslaur: ah, I suppose not... :)
[17:04] <mdeslaur> slangasek: unless you're willing to rewrite it before I publish :)
[17:05] <mdeslaur> slangasek: I also gather you'd rather not turn off pam_env on user home directories?
[17:06] <slangasek> mdeslaur: is the security bug *in* the hurd patch, or is it just caught in the crossfire?  i.e., is another fix needed for Debian unstable?
[17:07] <slangasek> mdeslaur: turn off pam_env> it's not a behavior change I'd like in a security update, but we could change the default to not check user environment files going forward, to match upstream
[17:08] <mdeslaur> slangasek: ok, that's what I was going to do
[17:08] <mdeslaur> slangasek: the hurd patch is caught in the crossfire...the following commits have moved around all the privilege dropping code: http://paste.ubuntu.com/609063/
[17:08] <mdeslaur> slangasek: half of those commits went in after 1.1.2, so debian unstable needs them also
[17:09] <slangasek> ok
[17:10] <mdeslaur> slangasek: I'll let you know once I've done natty which ones are missing in unstable
[17:10] <broder> SpamapS: ping? what was the end result of the /etc/default discussion you had on ubuntu-devel a few months back? have you actually used that code anywhere yet?
[17:11] <slangasek> mdeslaur: thanks
[17:11] <broder> (no rush - feel free to wait until the end of your meeting)
[17:11] <SpamapS> broder: definitely not, there was no end result.. we kind of deferred the discussion. At UDS we all suggested that we actually measure the impact of sourcing default files before we abandon them completely.
[17:11] <SpamapS> s/we all/somebody/
[17:13] <dholbach> @pilot out
[17:14] <micahg> broder: so in light of what SpamapS said, I'd rather not make such a divergent change unless there's a decision
[17:21] <broder> SpamapS: ok. i can certainly make an argument that with ureadahead, there shouldn't actually be any sort of additional disk hit, which i think means that the /etc/default things is purely a philosophical and stylistic discussion
[17:22] <broder> but yeah, i think keeping the /etc/default file for now is fine
[17:27] <SpamapS> broder: certainly for new things that we create, use env .. but for sanity in syncing w/ debian, probably easier to just keep sourcing the default file.
[18:00] <bakarat> been an ubuntu user since dapper (if memory serves) and i just gotta say: so far (not been using it for very yet though), unity kicks ass
[18:00] <bakarat> great job!
[18:08] <hv> so, what's the deal with gnome-settings-daemon?
[18:08] <hv> it segfaults :(
[18:13] <seb128> hv, what distro version?
[18:13] <hv> oneiric
[18:16] <hv> apparently it has an issue with libgnomekbd7, as far as I can guess.
[18:17] <seb128> hv, don't use oneiric yet ;-)
[18:18] <seb128> but otherwise there is a known issue in the indicator code I think, check with rodrigo on #ubuntu-desktop maybe if you can
[18:18] <hv> heh, someone has to use it before release ;)
[18:18] <hv> ok, thanks.
[18:18] <seb128> well right now it's rather "it's broken and has no theme and we know about it"
[18:19] <seb128> it needs work, we don't really lack feedback, we basically know quite some things are broken ;-)
[18:20] <hv> but is it in the indicator? the segfault I get relates to xkb, xklavier, and libgnomekbd7.
[18:22] <seb128> hv, could be another one, the new libgnomekbd just landed today
[18:22] <seb128> hv, get a stacktrace if you can that would be useful
[18:23] <hv> well, the stacktrace (not mine, someone else's with similar issue) is already on launchpad.
[18:24] <seb128> hv, can you give the bug number?
[18:26] <hv> #649809, see comment #191 (3rd from the end)
[18:27] <hv> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/649809
[18:29] <hv> I suspect the latest comments are not exactly aligned with the title. maybe they need their own new bug report.
[18:29] <seb128> right, that should go to a new bug report
[19:03] <cr3> hi folks, what might cause someone upgrading from maverick to natty to have files under /usr/lib/python2.6/dist-packages/project.. but not /usr/lib/python2.7/dist-packages/project...?
[19:05] <tumbleweed> cr3: the package may (incorrectly or correctly) say that only supports 2.6 or <= 2.6. Or it may just need to be rebuilt (if it uses dh_python2)
[19:05] <tumbleweed> cr3: which package?
[19:05] <stgraber> slangasek: hey, I'm preparing a test setup for IPv6 so I can easily test it in Oneiric. I currently have the following networks setup (http://paste.ubuntu.com/609117/), anything I'm missing in there?
[19:06] <cr3> tumbleweed: checkbox
[19:07] <cr3> tumbleweed: XS-Python-Version: current, is that sensible?
[19:08] <slangasek> stgraber: I don't understand the shorthand.  What does each line represent?  A machine, a network interface?
[19:09] <tumbleweed> cr3: we try not to use that if possible, as that'll only build for one version, not all supported versions
[19:10] <stgraber> slangasek: each line is a bridge on my laptop to be used with libvirt. I have a single VM that's plugged on all of them and doing the dhcpv4/dhcpv6/radvd depending on what's supposed to be on the bridge
[19:10] <slangasek> stgraber: we probably need more test cases that are explicitly related to broken IPv6 - e.g., ipv6 advertised but no packets getting routed; ipv6 advertised but DNS server misbehaves when asked; that sort of thing
[19:10] <slangasek> stgraber: aha, got it
[19:11] <mpoirier> slangasek: aside from barry, who else can I ask a phyton question ?
[19:11] <stgraber> ah, interesting, I guess I can simulate the "broken network" relatively easily by writting a few scripts for my "router" VM, so one can simulate these qite easily
[19:11] <slangasek> stgraber: some of these cases require different static configurations of the VM, how do you plan to do this with only one VM?
[19:12] <slangasek> mpoirier: the channel is dense with python expertise, you could just ask the question here :)
[19:12] <stgraber> I currently have a bunch of .xml files for libvirt creating all of these bridges, will have the same for the router VM + at least documentation on how to setup the router so someone can easily replicate the setup
[19:12] <slangasek> (electrons : electric fields :: python : pythic field?)
[19:13] <slangasek> stgraber: but don't the static configs require changes to the *client* VM, not just the router VM?
[19:13] <tumbleweed> cr3: aah. it uses python-central. That shouldn't require a rebuild, it should just support whataver the current default python version is (pyversions -d). BTW: We are trying to get rid of python-central and replace it with dh_python2.
[19:14] <stgraber> slangasek: yep, the idea is to have a test network. The client part will have to be done with one VM being moved from a bridge to another and reinstalled/reconfigured depending on the configuration (at least for the static cases)
[19:14] <slangasek> ok
[19:14] <stgraber> slangasek: or have one VM per bridge (if you have enough resources)
[19:14] <cr3> tumbleweed: I could migrate to dh_python2 for oneiric. for natty, I suspect this is not the only package relying on python-central, is there something I should sru to improve user experience of people upgrading?
[19:16] <tumbleweed> cr3: no need to do anything for natty. Indeed it's not the only package. There's a goal to convert all the packages on the CD for oneiric (there was a UDS discussion). All python-central packages in debian will already have bugs filed against them, encouraging micration.
[19:18] <cr3> tumbleweed: by the way, if python-central "shouldn't require a rebuild", I'm not sure I understand why the package is failing to import some of its dynamic modules. very strange...
[19:20] <tumbleweed> cr3: trying a dist-upgrade from maverick -> natty with it installed...
[19:21] <cr3> tumbleweed: thanks!
[19:23] <tumbleweed> cr3: checkbox is importable for me in python2.7 after the upgrade
[19:33] <cr3> tumbleweed: can you try running this: for py in `pyversions -s`; do echo $py; echo '__import__("checkbox_gtk.gtk_interface", None, None, [""])' | $py; done
[19:41] <tumbleweed> cr3: aah, I was looking at checkbox not checkbox-gtk. Of course we don't expect it to be importable in 2.6
[19:43] <cr3> tumbleweed: so, if the python executable points to python2.6 for some reason, hell might break loose, right?
[19:45] <tumbleweed> cr3: but that wouldn't happen unless the user breaks their own system. The python package tells python-central to rebuild those symlink farms when the default python version changes
[19:45] <mterry> Does anyone know much about -Bsymbolic-functions?  It's causing the libpeas test suite to fail, but not entirely sure why yet
[19:48] <cr3> tumbleweed: heh, not always easy to troubleshoot what people do on their systems :)
[19:49] <tumbleweed> the usual hint for something like this is the appearence of /usr/local somewhere in their traceback
[20:38] <keks-n> sup
[20:38] <keks-n> Guys, I have some problems with uploading to ppa
[20:39] <keks-n> dput says "Successfully uploaded packages.", but I cann't see my package in the build queue
[20:39] <stgraber> keks-n: as it's a PPA and not the main archive, you probably want #launchpad
[20:40] <broder> keks-n: #launchpad is a better place to ask about ppa issues, but it takes a few minutes for packages to migrate from uploading into the build queue
[20:40] <keks-n> thanks
[21:32] <hallyn_> kirkland: jjohansen: regarding http://summit.ubuntu.com/uds-o/meeting/server-o-ecryptfs-testsuite/, the first block is about ecryptfs enhancements.  Should I write those up as actions in the ecryptfs-testsuite blueprint, or do you want to put it somewhere else?
[21:33] <jjohansen> hallyn_: I am fine with in the blueprint
[21:33] <hallyn_> jjohansen: ok, will put them there, thanks
[21:41] <maco> just saw unity in action for the first time. the user and i were both confused. why is there what looks like a "zoom" icon (magnifying glass with + sign) that opens up the application list?
[22:18]  * vish points maco in the direction of #ayatana
[23:13] <rootuser23> looking for a command so i can send mails trough ubuntu's terminal pls