[09:02] <didrocks> hello there
[09:03] <seb128> hey didrocks
[09:17] <robert_ancell> seb128: hey seb
[09:18]  * mpt discovers Gnome Do's "Bug Number" plug-in
[09:18] <seb128> hey robert_ancell
[09:19] <seb128> robert_ancell: how was your day? what did you work on today?
[09:19] <robert_ancell> seb128: trying to manage compiz bugs - there are so many!!  And so vague...
[09:19] <mpt> mvo, about bug 356152, I think in future we will offer to install any pending updates whenever you make any other changes
[09:19] <seb128> oh yeah, it's a beast
[09:20] <mpt> mvo, but that doesn't particularly help now, I guess
[09:20] <mvo> mpt: so it will just check when update-manager wsa last run?
[09:21] <mvo> mpt: hm, code-wise it can still be changed relatively easily, but we are pretty late
[09:21] <mpt> yeah
[09:22] <didrocks> seb128: oh, you gave compiz to robert_ancell :)
[09:23] <seb128> mvo: it seems that mpt want to bring the bug I was having as an official feature now? ;-)
[09:23] <seb128> didrocks: I didn't have to, somebody else pushed him this way apparently, I've just been careful to not stop him on the way ;-)
[09:23] <didrocks> :)
[09:24] <mpt> Opening Update Manager yourself and closing it without making any changes -> resets the timer
[09:24] <mpt> Installing updates from the terminal -> resets the timer
[09:24] <robert_ancell> well I'm having a go at it but a lot of the bugs I can only shrug my shoulders at
[09:25] <mpt> Installing stuff other than updates -> ...?
[09:25] <mvo> I guess the problem is currently "using add/remove -> resets the timer"
[09:25] <mpt> yeah
[09:25] <seb128> mpt: "we will offer to install any pending updates whenever you make any other changes" ... what does "any other change" means?
[09:26] <mvo> on the commandline we can not distinguish between installed updates or installed new stuff easily, I mean, we could try, but I'm not sure if that would not make things easier to understand for the user
[09:26] <mpt> seb128, installing or uninstalling anything manually
[09:26] <mvo> add/remove> different matter
[09:26] <mpt> mvo, well if it's easy to exclude Add/Remove for 9.04, and you have time to fix it for 9.04, I have no objection :-)
[09:27] <seb128> mpt: do you count update as installing?
[09:28] <seb128> mpt: I was complaining some days ago to mvo that I got that bug, update-manager autoopening after every install I did in synaptic
[09:28] <seb128> *really annoying*
[09:28] <seb128> I usually select the updates for bandwith reasons
[09:28] <mpt> seb128, sorry, I was imprecise. I meant installing anything other than updates.
[09:28] <seb128> ie I don't want to download 300 megas every day
[09:29] <mvo> mpt: I will meditate about  add/remove for 9.04, but chances are not that great :/
[09:29] <mpt> seb128, that shouldn't happen unless they're security updates
[09:29] <seb128> hum ok, I'm not convinced that we should nag users too much
[09:29] <seb128> there is a limit between being helpful and annoying that we should try to not cross
[09:29] <mpt> seb128, that's a bug then.
[09:29] <seb128> right, that one was
[09:29] <seb128> I though you suggested increasing the nagging cases ;-)
[09:30] <seb128> sorry for the noise
[09:31] <robert_ancell> does anyone know what package bug 284124 should be against?  It's a keyboard shortcut issue (not compiz specific)
[09:34] <mpt> mvo, I commented in the bug report
[09:34] <mvo> thanks mpt
[09:35] <mpt> seb128, ideally it would reduce the nagging, by making it easier to install updates at the same time as you're doing other package management
[09:35] <seb128> robert_ancell: not sure but xorg would be a better bet, I get the issue in kvm or virt-manager on current jaunty I think
[09:36] <seb128> mpt: I don't want to install all the updates, it's just too much to download but maybe I'm a special case and I should get faster internet or something ;-)
[09:37] <seb128> mpt: ie, I know I've pending updates, they are pending for a good reason and I would find extra nagging annoying rather than helpful there
[09:38] <mpt> seb128, it wouldn't be nagging.
[09:38] <seb128> well, auto-opening the update list just because I install a new software in synaptic would be nagging
[09:38] <seb128> no?
[09:38] <mpt> Yes, but that bears little resemblance to what I'm suggesting
[09:39] <seb128> ok, I didn't get what you are suggesting though
[09:39] <seb128> though -> then
[09:39] <seb128> I will just wait for mvo to do the change and see how it works ;-)
[09:40] <mvo> mpt: thanks for the update to bug 351484 -- I don't think this can be done for jaunty, it requires that we make bigger changes to software-propoerties
[09:40]  * robert_ancell is loving the random compiz crashes...
[09:40] <seb128> re robert_ancell
[09:40] <mpt> Imagine, you go into the AppCenter thingy to install a program. Whatever updates are available are pre-selected. You select the program you want to install, and click "Install". The updates are installed along with whatever you're installing.
[09:40] <seb128> robert_ancell: did you read my reply before?
[09:40] <robert_ancell> seb128: no, I just crashed
[09:40] <mvo> mpt: currently s-p runs as root and the options you mention are user options, so we need a proper policykit/dbus backend for s-p
[09:40] <mpt> seb128, I guess for you we'd need to make it easy to unselect all updates at once, for if you really wanted to *just* install the new program and no updates.
[09:40] <mvo> mpt: not a big deal, just work (and too invasive at this point :/
[09:40] <seb128> mpt: right, which is exactly what I don't want, because as said download make my internet too slow to work
[09:40] <mpt> mvo, ok
[09:41] <robert_ancell> seb128: last I heard was ""mpt: thanks for the update to bug 351484 -- I don't think this can be done for jaunty, it requires that we make bigger changes to software-propoerties
[09:41] <seb128> mpt: right
[09:41] <seb128> robert_ancell: not sure but xorg would be a better bet, I get the issue in kvm or virt-manager on current jaunty I think
[09:41] <robert_ancell> seb128: thanks
[09:41] <seb128> I've been annoyed by that so I might have a look
[09:42] <seb128> that was in some test environment though, either xephyr or kvm I think
[09:56] <chrisccoulson> robert_ancell - i had that key mapping issue in a vmware guest for some time. vmware recommend a workaround, and reading their workaround might help to understand what the problem is
[09:56] <chrisccoulson> http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1007439
[09:57] <huats> morning everyone
[09:57] <huats> (or afternoon for some of you)
[09:59] <seb128> lut huats
[09:59] <huats> hey seb128
[10:00] <robert_ancell> chrisccoulson: is this only applicable when running in vmware?  I'm guessing the reporters in the bug are just running Ubuntu on the metal
[10:01] <chrisccoulson> i'm not sure. the only reason i bought that up was because seb128 mentioned about running in kvm. i wasn't sure whether the underlying issue could be the same
[10:01] <crevette> good morning
[10:01] <chrisccoulson> i don't think that issue is specific to vmware
[10:02] <seb128> lut crevette
[10:02] <huats> hello crevette
[10:02] <crevette> hey gentlemen
[10:21] <robert_ancell> night all
[10:21] <mvo> night robert_ancell
[12:50] <didrocks> seb128: I think we can still sponsor my package for this release in gtk2-engines-murrine and sync in next cycle on Debian (bug #357543)
[13:00] <seb128> didrocks: looking
[13:01] <seb128> didrocks: can you work on an update? your version has a lower number and can't be used now
[13:07] <didrocks> seb128: hum, what's the convention for versionning in this case?
[13:07] <seb128> didrocks: 1ubuntu1
[13:07] <seb128> and do the changes you need
[13:07] <didrocks> seb128: even if I don't merge against debian (not using debhelper 7 for this release)?
[13:08] <seb128> well; do an update 1ubuntu1
[13:08] <seb128> copy your rules
[13:08] <seb128> and write "don't use debhelper7 yet"
[13:09] <seb128> ie take the current jaunty version
[13:09] <seb128> undo the debhelper7 use
[13:09] <seb128> call it 1ubuntu1
[13:09] <didrocks> seb128: ok, doing it this evening
[13:09] <seb128> thanks
[13:41] <seb128> chrisccoulson: hey, did you look at the fusa gnome-session use since we discussed it?
[13:42] <seb128> chrisccoulson: gnome-session in jaunty has session storing for restart, etc now
[13:42] <seb128> chrisccoulson: will that work in fusa or not?
[13:50] <chrisccoulson> seb128 - i can do some work to make it work with fusa
[13:50] <chrisccoulson> the changes required to gnome-session to do that are fairly trivial
[13:51] <seb128> chrisccoulson: please do, would be a shame to have session working but not with fusa now ;-)
[13:51] <chrisccoulson> no probs - i'll work on that:)
[13:52] <seb128> thanks!
[14:04] <didrocks> seb128: I assume the "Recommends" of a seeded packages in the CD are seeded too, right?
[14:06] <seb128> didrocks: yes
[14:06] <didrocks> seb128: gtk2-engines-murrine recommends in debian murrine-themes. how to know if this one is already seeded?
[14:07] <didrocks> or if this raise an issue concerning CD space
[14:07] <seb128> we don't want to add any change now
[14:07] <seb128> easy way
[14:07] <seb128> take your 0ubuntu1 version
[14:07] <seb128> dch -v 1ubuntu1
[14:07] <seb128> add "use ubuntu version again for jaunty"
[14:08] <seb128> and upload
[14:08] <didrocks> seb128: I can merge without this recommends, there are really few changes
[14:08] <seb128> as you want
[14:08] <seb128> but no depends or recommends change over what we have now
[14:08] <seb128> and it needs to build ;-)
[14:08] <didrocks> ok, that's why I asked you :)
[14:13] <Ng> seb128: haha, damn. I just dug through my "todo" folder in thunderbird and confirmed the fix for g-k-d, only to get your mail saying the fix has been backed out ;)
[14:13] <Ng> 3 minutes apart. bah.
[14:14] <seb128> Ng: sorry about that but the change turned gnome-keyring to crashland there
[14:14] <seb128> where your crash is a not-so-common one
[14:14] <seb128> still looking to a clean solution and it's on my jaunty list
[14:14] <Ng> seb128: np, I'd rather that I trash my keyring than everyone else's explode :)
[14:15] <Ng> although obviously it'd be great if we can fix all of them ;)
[14:16] <seb128> indeed
[14:42] <seb128> didrocks: how busy do you think you will be tonight?
[14:44] <seb128> didrocks: do you think you could update gst-plugins-bad0.10 to the current debian version?
[14:45] <seb128> didrocks: there is only a small ubuntu change and we have a stable candidate version where they have the stable one
[14:56] <didrocks> seb128: I have finished gtk2-engines-murrines. Just want to test it tonight. I can handle gst-plugins-bad0.10 too (from 8PM, going to cinema first :))
[14:57] <seb128> ok
[14:57] <seb128> no hurry, thanks
[14:57] <didrocks> y/w :)
[14:57] <seb128> I can review and upload the engine update if you want
[14:57] <didrocks> ok, let me push it
[14:58] <kenvandine_wk> james_w: can you take a look at the changes i pushed for indicate-python?
[14:58] <james_w> kenvandine_wk: sure, just about to hop on a call, so it will have to wait 20 minutes I'm afraid
[14:58] <kenvandine_wk> james_w: pitti won't have time today and figured you already looked at it once, we need to get it uploaded :)
[14:59] <james_w> yeah, I forgot pitti was away
[14:59] <tedg> kenvandine_wk: Any issues with the 0.1.5 stuff?
[14:59] <kenvandine_wk> tedg: not that i know of
[15:00] <kenvandine_wk> tedg: anything i should be looking at?
[15:00] <tedg> kenvandine_wk: No, I was figuring that was what you were mentioning with the indicate-python talk :)
[15:00] <didrocks> seb128: done and linked to bug #357543 (see bzr branch)
[15:00] <seb128> didrocks: thanks
[15:01] <seb128> hey tedg
[15:01] <tedg> Good morning seb128
[15:01] <seb128> tedg: I've sponsored your uploads, the evolution indicator and pidgin libnotify need rebuilds now
[15:01] <seb128> tedg: do you plan to get changes for those today?
[15:01] <kenvandine_wk> tedg: just getting indicate-python uploaded today :)
[15:02] <tedg> seb128: Yes.  I do.  There was a positive ack on the translations for evolution-indicator.
[15:02] <tedg> seb128: Thank you for the sponsorships!
[15:02] <seb128> you're welcome
[15:02] <tedg> kenvandine_wk: Ah, cool.  Make sure it works with 0.1.5 then ;)
[15:02] <kenvandine_wk> hehe
[15:03] <kenvandine_wk> ok... /me really hopes it does
[15:12] <asac> james_w: last time i looked, one issue with python-indicate was missing license headers for the test scripts. should be shipped with license headers in examples imo
[15:12] <james_w> yeah
[15:12] <james_w> luckily upstream is co-operative :-)
[15:12] <asac> should be really easy to fix for tedg ;)
[15:13] <tedg> You Ubuntu folks.  Only pass up bugs but never contribute upstream ;)
[15:14] <asac> i take that personal.
[15:15] <seb128> tedg: bug reports are valuable contributions ;-)
[15:17] <vuntz> seb128: I released a 2.26.0.90 tarball for gnome-session. It's more or less the same than what you have with the patches, with one or two minor other fixes
[15:17] <seb128> vuntz: ok thanks
[15:18] <seb128> vuntz: you rock
[15:18] <seb128> everybody hugs vuntz who fixed session storing for good now
[15:18] <seb128> in time for GNOME 2.26.1 and jaunty
[15:18]  * seb128 hugs vuntz
[15:18]  * tedg hugs vuntz
[15:19] <mvo> vuntz vuntz vuntz
[15:19] <vuntz> (well, you still can't save during the session -- it only works during logout...)
[15:21] <seb128> I don't care so much about session storing
[15:21] <seb128> I care about asking if you want to save your work
[15:21] <seb128> which works ;-)
[15:23] <seb128> brb
[15:25] <seb128> Ng: another gnome-keyring update tentative to fix the issue, let me know how it will work when available
[15:25] <Ng> seb128: ooh, will do :)
[15:25] <seb128> thanks
[15:26] <seb128> you get the bug in a reliable way?
[15:37] <seb128> tedg: do you have anything pending sponsoring? I'm doing a sponsoring round between some bug fixes which are on my todolist
[15:37] <tedg> seb128: I don't think so, I hope to in about 20 minutes :)
[15:37] <seb128> ok
[15:38] <seb128> the evolution indicator translation fix is not ready yet?
[15:39] <kenvandine_wk> seb128: the dx team will have new tarballs tonight too
[15:39] <kenvandine_wk> or in the morning if things go very badly today
[15:40] <seb128> right
[15:40] <seb128> I expect my day to be long again
[15:40] <kenvandine_wk> yup :)
[15:40] <seb128> but soon freeze and long weekend to catch up with sleep again ;-)
[15:40] <kenvandine_wk> but hopefully a quiet friday
[15:40] <seb128> it's a holiday there
[15:40] <seb128> so for sure it will be quiet ;-)
[15:41] <kenvandine_wk> ah... true
[15:41] <kenvandine_wk> the day after the beta freeze it was a ghost town
[15:41] <tedg> seb128: Yes, sorry, I'm making a tarball.  I'm at a coffee shop as my car is being repaired an the Internet is slow... like IRC delays slow.
[15:42] <seb128> tedg: no hurry you can do that later
[15:42] <seb128> tedg: I'll do an another round of sponsoring tonight european time
[15:52] <james_w> kenvandine_wk: bye-eye checking shows it to be pretty good
[15:52] <james_w> checking by computer now
[15:53] <kenvandine_wk> :)
[15:53] <james_w> there are two issues
[15:53] <james_w> firstly, the description sucks :-)
[15:53] <kenvandine_wk> hehe
[15:53] <kenvandine_wk> well... got suggestions?
[15:53] <james_w> usually you do something like
[15:53] <james_w> Description: python bindings for libindicate
[15:54] <james_w> <excerpt of libindicate description>
[15:54] <kenvandine_wk> i would usually get it from upstream :)
[15:54] <james_w> This package provides python bindings so that you can use libindicate from a python program
[15:55] <james_w> the other issue is licensing
[15:56] <james_w> there are some things it would be nice to change upstream, but there are some packaging ones too
[15:56] <james_w> the biggest problem being that debian/copyright declares that it is LGPL 3+, when it is LGPL 2.1 or LGPL 3
[15:57] <kenvandine_wk> oh
[15:57] <kenvandine_wk> so it should be LGPL 2.1+
[15:57] <james_w> my minor gripe is that your license for the packaging is more restrictive than the license for the code
[15:57] <james_w> no, it should be LGPL 2.1 or LGPL 3, there is no "or later" clause
[15:57] <james_w> assuming the headers are correct
[15:58] <kenvandine_wk> ok
[15:58] <kenvandine_wk> what do you mean by my packaging license?
[15:58] <james_w> 34 		
[15:58] <james_w> The Debian packaging is copyright 2009, Ken VanDine <ken.vandine@canonical.com> and
[15:58] <james_w> 35 	24 	
[15:58] <james_w> is licensed under the GPL-3, see '/usr/share/common-licenses/GPL-3'.
[15:59] <kenvandine_wk> what would you suggest?
[15:59] <kenvandine_wk> that is just from the template
[15:59] <kenvandine_wk> i don't think i changed that
[15:59]  * kenvandine_wk needs to stop using those templates
[15:59] <james_w> I always use the same license as the code itself
[16:00] <kenvandine_wk> ok
[16:00] <james_w> consider something in debian/patches/, you could consider it part of the packaging, and so making the packaging the same license means there are no issues in moving that patch upstream
[16:00] <kenvandine_wk> makes sense
[16:00] <kenvandine_wk> ok
[16:00] <james_w> and issues are usually theoretical of course
[16:01] <kenvandine_wk> back to the license of the code
[16:01] <kenvandine_wk> what is the appropriate way for me to handle that?
[16:01] <james_w> you just need to make the declaration in debian/copyright match the code
[16:02] <james_w> so take the header that is copied and overwrite it with one from a file in src/
[16:03] <kenvandine_wk> and for the packaging license, should i reflect both versions of the LGPL there?
[16:04] <james_w> it's up to you really, it's your work to license, but I would suggest that you do
[16:04] <james_w> you can say "same licenses as above" if you like
[16:04] <seb128> mclasen: hi, for your gnome-keyring assertion issue, your change is no the version which has been commited to svn but the one added to the bugzilla bug
[16:04] <mclasen> that may be
[16:04] <seb128> mclasen: try using http://svn.gnome.org/viewvc/gnome-keyring/trunk/egg/egg-secure-memory.c?r1=1706&r2=1705&pathrev=1706 instead rather
[16:04] <mclasen> in which case its all Richards fault...
[16:06] <kenvandine_wk> james_w: so you think it is best to dual license the packaging too?
[16:06] <james_w> kenvandine_wk: for simplicity, yes, but if you would prefer not to then that's fine.
[16:07] <asac> packaging license is usually different from upstream license, so no need to imp
[16:07] <asac> imo
[16:08] <kenvandine_wk> james_w: pull again, how is that?
[16:12] <james_w> kenvandine_wk: wrap the final line, but otherwise fine
[16:12] <kenvandine_wk> ok
[16:12] <kenvandine_wk> one sec
[16:12] <asac> sigh ... amd64 builder just never picks up my tiny build
[16:13] <asac> did someone force build score on all the builds that go in fast there?
[16:13] <kenvandine_wk> james_w: done
[16:15] <james_w> kenvandine_wk: looks pretty good
[16:16] <kenvandine_wk> :)
[16:16] <james_w> the last issue is that upstream should really be shipping two COPYING files I think, and should put license headers in tests/*
[16:16] <kenvandine_wk> james_w: ok, can you get it uploaded?
[16:16] <james_w> do you have a freeze exception?
[16:16] <kenvandine_wk> yeah... i will work with them on that
[16:17] <kenvandine_wk> well... not sure if there is anything official :/
[16:17] <kenvandine_wk> just we know we need to get it in...
[16:17] <james_w> an archive admin would be able to confirm whether the COPYING thing was blocking
[16:17] <kenvandine_wk> should i subscribe ubuntu-release and get an ack?
[16:17] <james_w> motu-release for universe
[16:17] <kenvandine_wk> ok
[16:18] <james_w> and I think we are supposed to get a second ~ubuntu-dev to review
[16:18] <james_w> pretty annoying
[16:19] <kenvandine_wk> does pitti's review count for that?
[16:19] <asac> yes
[16:19] <asac> i also reviewed it
[16:19] <kenvandine_wk> ok
[16:19] <kenvandine_wk> i subscribe motu-release
[16:19] <asac> what bug is that?
[16:19] <kenvandine_wk> bug 344936
[16:20] <asac> so still no license headers in tests?
[16:20] <asac> why cant we just fix that ;)?
[16:21] <asac> i mean once we let it in, it will take even longer to fix.
[16:21] <asac> because there is no need to
[16:21] <asac> if its already committed upstream branch then its fine
[16:21] <kenvandine_wk> it isn't... and they would need to make a new release
[16:22] <asac> kenvandine_wk: i would like ot see it getting committed there.
[16:22] <asac> if thats done we can let it in as it is imo
[16:22] <asac> e.g. no need to wait for new upstream release
[16:22] <asac> tedg: cant you just commit those license header changes for the tests?
[16:23] <kenvandine_wk> i am just working on the packaging branch, we are still building from the tarball... i think
[16:23] <kenvandine_wk> i am adding those headers and the second COPYING file
[16:23] <asac> thats not my point.
[16:23] <kenvandine_wk> will propose a branch merge
[16:23] <asac> yeah thanks.
[16:23] <kenvandine_wk> but.... those tests aren't getting installed either
[16:24] <tedg> asac: Sure.  Sorry, I was going and doing a couple of other things.
[16:24] <tedg> kenvandine_wk: Does it build and work against 0.1.5?
[16:24]  * tedg wants to be really sure there :)
[16:24] <asac> tedg: great thanks
[16:25] <kenvandine_wk> i don't have 0.1.5 yet
[16:25] <asac> ok i am travelling now for 2 hours ... will be back later and will ack the upload then (if nobody else came around)
[16:25] <tedg> kenvandine_wk: I think it was uploaded?  I got bug notifications of it.
[16:26] <kenvandine_wk> what is the preferred method for shipping 2 COPYING files?
[16:26] <kenvandine_wk> COPYING.LGPL-3 and COPYING.LGPL-2.1
[16:26] <kenvandine_wk> ?
[16:26] <seb128> tedg: it has been uploading this morning but only NEW-ed one hour ago
[16:26] <seb128> tedg: it was in new due to the soname change
[16:27] <tedg> seb128: Ah, okay.
[16:27] <tedg> kenvandine_wk: I dont' know the preferred way, but I did that in indicator applet :)
[16:30] <seb128> does anybody else has some sponsoring items waiting?
[16:30] <seb128> james_w: I've no watched that closely but is there anything to do for that nautilus patch you sent out of waiting for next tarballs?
[16:31] <james_w> seb128: ah, I forgot it would be in the next round of tarballs
[16:31] <seb128> james_w: tarballs are due next week and will be in jaunty
[16:31] <james_w> seb128: it wasn't until I fixed it that I realised that the functionality doesn't work with the version of packagekit that we have
[16:32] <seb128> I don't think there is any hurry to backport that now
[16:32] <james_w> it shouldn't be hard to fix that, but I wasn't sure if it was worth the effort/worth changing that at this point
[16:32] <james_w> or to just disable the feature in gconf/with --disable-packagekit
[16:34]  * didrocks hugs vuntz (lately, but I have so many times bothered you with gnome-session at SL :) I can live without gnome-session --save :p)
[16:35] <seb128> james_w: the patch doesn't fix it for the jaunty version so we need to disable the option, that's what you say?
[16:35] <james_w> the problem was not with using packagekit, but not with using it
[16:35] <james_w> that patch will make it acceptable to leave packagekit support enabled
[16:35] <seb128> what does the svn change fix exactly?
[16:35] <james_w> however, there's not a lot of point at this moment though, as packagekit support is broken
[16:35] <seb128> it what happens with next tarball and no packagekit installed
[16:36] <seb128> it -> ie
[16:36] <james_w> at the moment on a default install you get "Would you like to search for applications?", you click yes, and you will always get "obscure <dbus error because packagekit isn't running>"
[16:37] <james_w> the change in SVN means you don't get the question if packagekit isn't running
[16:37] <seb128> ok, good enough for jaunty then
[16:37] <seb128> thanks
[16:37] <vuntz> didrocks: hola
[16:38] <james_w> seb128: but if packagkit is running you get "<other obscure dbus error because of version mismatch>"
[16:38] <didrocks> vuntz: hey ;)
[16:38] <james_w> seb128: so, we can either add what I assume is a small patch to nautilus to make it work with the older packagekit we have, or disable the feature
[16:40] <seb128> james_w: or do nothing and let it this way, it will break for people installing the jaunty version but work if there is a backport or a ppa update somewhere
[16:40] <james_w> true
[16:40] <seb128> james_w: I think it's too much of a corner case to bother now
[16:40] <james_w> ok
[16:40] <seb128> we have other priorities for jaunty
[16:44] <kenvandine_wk> tedg: i just proposed a merge for indicate-python
[16:44] <seb128> ok btw
[16:45] <seb128> tedg: could you use normal sponsoring bugs rather than this weird launchpad thing you use to request updates? ;-)
[16:45] <seb128> tedg: this way your requests would be listed on the sponsoring list
[16:45] <tedg> kenvandine_wk: Cool, I'll look at it.
[16:46] <kenvandine_wk> thx
[16:46] <kenvandine_wk> it still doesn't install the tests :)
[16:46] <tedg> seb128: Heh, it's the way of the future man ;)  pitti isn't here, so I'll say that he forced me to do it that way :)
[16:46] <kenvandine_wk> which would be nice...
[16:46] <dobey> ugh. the gnome.mk in cdbs requires autotools.mk :(
[16:46] <seb128> tedg: I will force you to wait for pitti to get sponsoring maybe then ;-)
[16:46] <seb128> dobey: no it doesn't?
[16:47] <dobey> seb128: include $(_cdbs_class_path)/autotools.mk$(_cdbs_makefile_suffix)
[16:48] <seb128> dobey: I misread what you wrote I think, it doesn't force you to have this include in your rules
[16:48] <seb128> dobey: what is the issue with having it use by gnome.mk directly?
[16:48] <dobey> no, it forces me to include it indirectly, which doesn't work so well if you're python and using distutils/setuptools
[16:49] <seb128> hum maybe, all the GNOME things we package usually use autotools
[16:50] <dobey> sure
[16:50] <dobey> but i just want to use the icons stuff
[16:50] <seb128> add a dh_icons call in the rules
[16:50] <dobey> perhaps the different bits should be split out into icons.mk, scrollkeeper.mk, etc...
[16:51] <seb128> that wouldn't make sense, you can as well call dh_icons directly
[16:51] <dobey> and gnome/kde/xfce.mk could just include the individiual bits, and i could just include the icons bit
[16:51] <dobey> call it directly from where?
[16:51] <dobey> what rule?
[16:52] <seb128> binary-post-install/<binary>::
[16:52] <seb128>         dh_icons
[16:53] <seb128> or binary-install/<binary>:: could be enough
[16:53] <seb128> rather binary-install in fact I would say
[16:53] <seb128> try that
[16:53] <dobey> binary-isntall:: ?
[16:53] <seb128> yes
[16:53] <seb128> binary-install/whateverbinaryhasicons::
[16:54] <seb128>         dh_icons
[16:54] <seb128> in the rules
[16:54] <dobey> without a -pfoo for it?
[16:55] <seb128> do you have several binaries which have icons?
[16:55] <dobey> no
[16:55] <seb128> so that should not make a difference
[16:55] <dobey> ok
[16:56] <seb128> dobey: you can use "dh_icons -p$(cdbs_curpkg)" if you want
[16:56] <rickspencer3> kenvandine_wk: looks like tedg's patch for inhibiting exit was merged
[16:56] <tedg> rickspencer3: Just the libindicate changes.  Working on cleaning up the pidgin ones now.
[16:56] <seb128> rickspencer3: right, I sponsored those upload in the european morning today
[16:57] <rickspencer3> tedg: ktx
[16:57] <kenvandine_wk> rickspencer3: yup... looking forward to testing it :)
[16:58] <rickspencer3> kenvandine_wk: as tomorrow is final freeze, what can we do to help ensure that the tedg's pidgin changes are solid as a rock before he uploads?
[16:58] <rickspencer3> I'd be happy to help test if that would help
[17:02] <didrocks> seb128: do you know what's the file build-deps.in is used for? I see no reference in debian/control.in as I would expect to use it…
[17:02] <seb128> didrocks: grep for it in the debian directory, it used to have a rules target to update the control Build-Depends using it
[17:03] <seb128> didrocks: that could have changed, does it has a control.in?
[17:03] <didrocks> seb128: yes, it makes something with it in control.in
[17:04] <kenvandine_wk> tedg: can you get your pidgin stuff built into your ppa?
[17:04] <kenvandine_wk> or i can do it in mine
[17:04] <kenvandine_wk> so we can start testing asap :)
[17:04] <didrocks> seb128: or, maybe, I will wait for karmic to clean the multiverse version of gstreamer bad plugins which have diverged from the universe one (when I will have more time). People seems to usually just do an usual update to it, not syncing with debian
[17:05] <seb128> didrocks: see HACKING.Debian
[17:05] <didrocks> seb128: yep, I am looking at it right now
[17:05] <tedg> kenvandine_wk: rickspencer3: sure.
[17:06] <kenvandine_wk> tedg: feel free to toss that stuff to me to build in my ppa.. so you can get to work on other stuff :)
[17:07] <tedg> kenvandine_wk: No, I'm at the point of packaging -- so I'd rather get the build errors :)
[17:07] <didrocks> seb128: I think I will do that. I merged the universe version (only one ubuntu patch), and update the multiverse one. Just keep in mind to clean in for karmic :)
[17:07] <kenvandine_wk> ok :)
[17:07] <seb128> didrocks: ok looks good, thank you
[17:08]  * kenvandine_wk grabs lunch... back in 20m
[17:22] <tedg> kenvandine_wk: Watch this space :)  https://launchpad.net/~ted-gould/+archive/ppa/+build/941805
[17:43] <tedg> kenvandine_wk: rickspencer3: PPA version of pidgin-libnotify in my PPA if you want to play with it.
[17:44] <rickspencer3> kenvandine_wk: I'm at your service
[17:44] <rickspencer3> tedg: thanks dude!
[17:44]  * tedg really wishes rickspencer3 was at HIS service.  I'd really like a latte right now ;)
[17:45]  * rickspencer3 dons waiter uniform
[17:45] <kenvandine_wk> hehe
[17:48]  * kenvandine_wk updates system to get libindicate 1.1.5 first
[17:51] <Nafallo> kenvandine_wk: how's python-indicate progressing? :-)
[17:51] <kenvandine_wk> waiting for a freeze exception :)
[17:51] <Nafallo> kenvandine_wk: (and if it isn't, where can I find the source so I can PPA it? ;-))
[17:52] <kenvandine_wk> hehe... give it a little time
[17:52] <kenvandine_wk> it should be today... i hope
[17:57] <Nafallo> :-)
[18:00] <kenvandine_wk> tedg: closing the buddy list now exits pidgin
[18:01] <tedg> kenvandine_wk: ?  Did you restart indicator-applet after upgrading?
[18:01] <kenvandine_wk> yes
[18:02] <tedg> The old indicator-applet doesn't tell pidgin it's watching -- that's a feature :)
[18:02] <kenvandine_wk> i even rebooted to bes ure
[18:02] <kenvandine_wk> error in PM
[18:02] <tedg> Did you install indicator-applet 0.1.5 and not just libindicate1 0.1.5?
[18:02] <kenvandine_wk> Hmph :)
[18:02] <kenvandine_wk> i did a dist-upgrade
[18:02]  * kenvandine_wk checks
[18:03] <tedg> The error really looks like the indicator-applet isn't telling that it's watching.
[18:03] <kenvandine_wk> oh
[18:03] <kenvandine_wk> i have both libindicate0 and libindicate1
[18:04] <kenvandine_wk> oh... maybe evolution-indicator kept it around?
[18:04] <tedg> kenvandine_wk: It will until it gets rebuilt.  Which is okay.  I'm more worried about indicator-applet
[18:07] <kenvandine_wk> tedg: i also have indicate-messages 0.1.4
[18:07] <tedg> kenvandine_wk: Oh, don't have that.  It's like soooo old :)
[18:08] <kenvandine_wk> should it get erased?
[18:09] <kenvandine_wk> ok... found the problem... indicate-messages 0.1.5 needs building still
[18:12] <kenvandine_wk> ok seb128, you are right about upstream and pidgin... they have a patch :)
[18:12] <kenvandine_wk> it was actually a bug... evidently
[18:14] <kenvandine_wk> seb128: i will test the patch now
[18:52] <kenvandine_wk> how can i make bzr-buildpackage skip signatures?
[18:54] <james_w> add "-- -uc -us" to the end of the command line
[18:54] <kenvandine_wk> doesn't work
[18:54] <james_w> irritating, I know
[18:54] <james_w> oh
[18:54] <kenvandine_wk> works on debuild
[18:54] <kenvandine_wk> not bzr-buildpackage
[18:54] <james_w> you get an error, or it just still tries to sign?
[18:55] <kenvandine_wk> error
[18:55] <kenvandine_wk> no arg -u
[18:55] <james_w> ah
[18:55] <james_w> you need the "--" before
[18:56] <james_w> double irritating :-)
[18:56] <kenvandine_wk> oh
[18:56] <kenvandine_wk> thx
[18:57] <chrisccoulson> thanks james_w, i had always wondered why i could never get it to work
[18:57] <chrisccoulson> i always missed the "--"
[18:57] <james_w> because I suck :-)
[18:57] <james_w> you shouldn't have to, it's on my list for Karmic
[18:57] <chrisccoulson> :)
[18:57] <kenvandine_wk> good :)
[18:57] <james_w> but "--" is better than Intrepid :-)
[18:58] <kenvandine_wk> james_w: thx man!
[19:06] <kenvandine_wk> seb128: i updated bug 354298, new debdiff
[19:28] <seb128> kenvandine_wk: excellent
[19:29] <seb128> kenvandine_wk: see I was right on the upstream bug filing, they indeed got a quick reply saying that the wrapper was wrong and an easier fix to use ;-)
[19:29] <kenvandine_wk> seb128: yup... i already admitted you were right :)
[19:30] <kenvandine_wk> seb128: i never got such fast responses working on foresight or the gnome dev kit... but i guess for ubuntu folks jump a little faster :)
[19:30] <seb128> getting dinner now but I will sponsor that after dinner
[19:30] <seb128> lol
[19:30] <seb128> I think you have been lucky there
[19:30] <kenvandine_wk> maybe
[19:31] <kenvandine_wk> i have patches submitted places that are like 2 years old and ignored :/
[19:31] <seb128> but to win you have to play so opening a bug early is usually a good idea anyway ;-)
[19:38] <kenvandine_wk> tedg: bad news dude... indicate-python doesn't build with libindicate 0.1.5 :/
[19:38] <tedg> kenvandine_wk: Oh, fail.
[19:38] <kenvandine_wk> tedg: on the other hand... pidgin-libnotifiy is rocking!
[19:38] <tedg> eeejay: Have you looked at that any?
[19:39] <tedg> eeejay: I don't think that we need the new APIs, but having the old ones on the new lib would be nice.
[19:39] <tedg> kenvandine_wk: The queuing of messages is much better in the new plugin, isn't it :)
[19:39] <kenvandine_wk> yeah... i am much happier
[19:40] <kenvandine_wk> and of course it doesn't exit on close either :)
[19:42] <tedg> kenvandine_wk: Yeah, I hear that some people want that feature.
[19:42] <tedg> :)
[19:43] <kenvandine_wk> eeejay: can you look at indicate-python against 0.1.5?
[19:50] <rickspencer3> tedg: I'm rethinking the whole "exit on close thing"
[19:50] <rickspencer3> perhaps we were hasty?
[19:50] <rickspencer3> j/k
[19:50] <tedg>  /kick-with-a-vengence rickspencer3
[19:51] <tedg> :)
[19:51] <kenvandine_wk> haha
[20:06] <chrisccoulson> hey tedg - just looking at the fusa change at the moment. does your session-management branch contain only the patches up to 84_session_management?
[20:07] <tedg> chrisccoulson: Yes.
[20:07] <tedg> chrisccoulson: There's a fun little ripple through all of them there.
[20:08] <chrisccoulson> thanks. do you want me to merge my changes in to the session-management branch and the other branch too? (the changes will require updates to some of the other patches so they apply again)
[20:14] <tedg> chrisccoulson: I can do that, I have a small shell script for it.
[20:14] <tedg> chrisccoulson: It all uses bazaar magic :)
[20:14] <chrisccoulson> thanks tedg
[20:19] <mvo> kenvandine_wk: do you think you could give the ekiga held-back situation a go? slangasek was unhappy with my fix (rightfully so) and he suggested a different approach
[20:19] <kenvandine_wk> mvo: i actually don't even understand why it was held back
[20:20] <kenvandine_wk> mvo: what is the bug number?
[20:20] <mvo> kenvandine_wk: 353768
[20:20] <mvo> kenvandine_wk: bug #353768
[20:20] <mvo> kenvandine_wk: its apt being stupid really
[20:21] <kenvandine_wk> mvo: and what was slangasek's suggestion?
[20:23] <mvo> kenvandine_wk: we are discussing it on #ubuntu-release just now, he was of the opinion to either revert the plugin name or add dummy transitional package for them
[20:23] <mvo> kenvandine_wk: I would do it, but I'm rather busy with $stuff currently :/
[20:23] <kenvandine_wk> can you just paste the transcript to the bug or in a PM to me?
[20:23] <kenvandine_wk> and i will work on it
[20:37] <mvo> kenvandine_wk: will do
[20:39] <mvo> kenvandine_wk: added to the bugrpeort
[20:39] <mvo> kenvandine_wk: I think we need transitional packages for the plugin packages, give me a sec and I can prepare something
[20:44] <kenvandine_wk> mvo: thx
[20:48] <chrisccoulson> hi seb128 - i've done the gnome-session patch we spoke about earlier
[20:48] <seb128> hello chrisccoulson
[20:48] <seb128> chrisccoulson: ah, excellent, thanks
[20:48] <chrisccoulson> i've done it in bzr and proposed a merge in to ubuntu-desktop
[20:49] <seb128> chrisccoulson: ok, we don't receive email about those requests apparently, not sure where they are supposed to show
[20:49] <seb128> kenvandine_wk: you said you had 2 pidgin changes pending or only the focus one?
[20:50] <mvo> kenvandine_wk: I uploaded a version into my ppa - the descriptions for the transitional package need a bit of love, otherwise its hopefully ok
[20:50] <kenvandine_wk> seb128: only that one
[20:50] <mvo> kenvandine_wk: I guess you can not reproduce the held-back anymore, or can oyu?
[20:50] <kenvandine_wk> no :/
[20:52] <mvo> kenvandine_wk: rickspencer3-afk can still reproduce it, so we can ask him once the ppa is updated :)
[20:54] <kenvandine_wk> mvo: how can you repro it from a ppa?
[20:54] <kenvandine_wk> apt-get install ekiga just works...
[20:55] <kenvandine_wk> mvo: doesn't it just affect the dist-upgrade case?
[20:55] <mvo> kenvandine_wk: just, just please upgrade from beta
[20:55] <seb128> didrocks: there?
[20:56] <seb128> the gst-plugins-bad0.10 broken pidgin on jabber apparently, it crashes on start now
[20:56] <mvo> kenvandine_wk: I can not reproduce it myself here easily (but I will download a beta desktop cd, that should work to reproduce the upgrade with it)
[20:58] <didrocks> seb128: yes there, really?
[20:58] <seb128> didrocks: yes :-(
[20:58] <didrocks> seb128: I can revert it and open a bug upstream
[20:58] <seb128> didrocks: let's try to figure what is broken and fix it before reverting everything
[20:59] <seb128> didrocks: I asked you to do the update because it fixes some annoying bugs too
[20:59] <didrocks> seb128: ok, I will surely not have the time tonight but I can keep some time to fix this tomorrow
[21:00] <seb128> didrocks: ok thanks
[21:10] <kenvandine_wk> asac: can you ack the indicate-python branch?
[21:10] <kenvandine_wk> asac: i did have to make a change... added a patch to make it build/work against libindicate 0.1.5 which was just uploaded
[21:15] <seb128> didrocks: ok, not gst's fault, I'm on it
[21:15] <seb128> didrocks: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522669 for details
[21:28] <asac> kenvandine_wk: looking. let me get those latest bits
[21:28] <kenvandine_wk> asac: thx
[21:28] <asac> seb128: could you look/poke flashplugin-nonfree binary that sits in NEW?
[21:30] <seb128> didrocks: bug fix uploaded
[21:36] <asac> kenvandine_wk: what was the previous libindicate version?
[21:37] <kenvandine_wk> 0.1.4
[21:37] <kenvandine_wk> oh
[21:37] <seb128> asac: how come there is new binaries for it?
[21:38] <seb128> asac: is that targetted to multiverse now?
[21:38] <asac> seb128: its a rename to flashplugin-installer; has been requested multiple times from multiple sides
[21:38] <asac> seb128: yes its still multiverse
[21:38] <tedg> seb128: Could you please add bug 356147 to your sponsoring list :)
[21:39] <seb128> asac: accepted
[21:39] <asac> great
[21:39] <seb128> tedg: looking
[21:39]  * asac hugs seb128 
[21:39]  * seb128 hugs asac back
[21:40] <seb128> tedg: did you get an evolution-indicator update too? it needs a rebuild for soname change and to get evolution translations backs
[21:40] <didrocks> seb128: already ? I just uploaded my vm to reproduce the bug to take an eye on it
[21:40] <didrocks> seb128: was it easy to fix ? You used a stackstrace I guess
[21:40] <seb128> didrocks: yeah, pidgin crashing when connecting to jabber is not good ;-)
[21:40] <seb128> didrocks: it was a libxml bug
[21:41] <seb128> thanks to responsive upstream and valgrind I figured it quickly
[21:41] <didrocks> seb128: I have to get used to try valgrind and not only gdb :)
[21:41] <didrocks> seb128: great! Thanks ;)
[21:42] <tedg> seb128: Apparently I did everything but propose the merge... funny.  Anyway: https://code.launchpad.net/~indicator-applet-developers/evolution-indicator/packaging/+merge/5372
[21:42] <seb128> didrocks: no problem and sorry for the false alarm in your way, the gstreamer update just triggered the bug
[21:42] <seb128> tedg: thanks
[21:42] <didrocks> seb128: no problem :)
[21:43] <tedg> seb128: No thank you :)
[21:43] <seb128> I've the feeling I did a week worth of work in a day today
[21:43] <asac> kenvandine_wk: where is the orig?
[21:43] <asac> get-orig-source doesnt fetch it ;)
[21:44] <didrocks> seb128: hehe, you will enjoy next Monday, I'm sure :)
[21:44] <seb128> tedg: pidgin-notify uploaded
[21:44] <asac> oh its https
[21:44] <seb128> didrocks: next monday GNOME 2.26.1 tarballs are due so I will be working ;-)
[21:44] <tedg> seb128: Great!
[21:44] <seb128> didrocks: I will be enjoying friday to sunday for sure though ;-)
[21:44] <didrocks> seb128: vuntz told me it was on Wednesday, or I have misunderstood him :)
[21:45] <didrocks> seb128: ok, I will be there on Monday to give an hand :)
[21:45] <seb128> didrocks: tarballs are due on monday, GNOME on wednesday
[21:45] <asac> kenvandine_wk: seems your branch doesnt build for me. fails to apply that patch ;)
[21:45] <seb128> didrocks: excellent thanks
[21:45] <didrocks> seb128: oki ;)
[21:45] <asac> let me check again
[21:45] <didrocks> time to go to bed for me, see you tomorrow
[21:45] <asac> heh works. blind me
[21:46] <seb128> didrocks: 'night
[21:46] <asac> kenvandine_wk: set minimal version to build depend for libindicate-dev ... because the api/abi was changed
[21:46] <didrocks> seb128: thanks, you too in few hours ;) (few… I hope for you ^^)
[21:46] <seb128> didrocks: yeah, I will probably work for an another hour or 2 and crash to bed
[21:54] <rickspencer3> ArneGoetje: asac: bryce: calc: kenvandine_wk Riddell seb128 ...
[21:54] <rickspencer3> just wanted to point out that a couple of hours ago ...
[21:54] <rickspencer3> the desktop team had zero bugs on the RC list!!
[21:54] <seb128> waouh ;-)
[21:54] <bryce> \o/
[21:54] <seb128> "a couple of hours ago"
[21:54] <seb128> did we get new ones since? ;-)
[21:54] <rickspencer3> last time I checked
[21:54] <rickspencer3> I hope not, I'm afraid to look :)
[21:55] <asac> rock on ;)
[21:55]  * asac goes and opens a few late april joke bugs
[21:56] <rickspencer3> hehe
[21:56] <rickspencer3> someone should log a bug against notify-osd:
[21:56] <rickspencer3> "notify-osd does not support action buttons"
[21:56] <seb128> yeah
[21:57] <asac> heh. not that topic again ;)
[21:57] <seb128> ok, so we did transition to libindicate1 in jaunty
[21:57] <asac> lol
[21:57] <seb128> ie I cleaned the sponsoring requests from kenvandine_wk and tedg now
[21:57] <asac> yeah. i found that now ;)
[21:57] <kenvandine_wk> asac: doing it now
[21:57] <seb128> so everything should be using the new version soon
[21:57] <seb128> and the pidgin behaviour should be better
[21:58] <Nafallo> does that include the one in NEW? :-)
[21:58] <Nafallo> (python-indicate)
[21:58] <seb128> Nafallo: new was empty when I looked at it 15 minutes ago
[21:58] <Nafallo> I guess that sounds good :-)
[21:58] <asac> Nafallo: its not uploaded
[21:58] <asac> that will happen soon most likely
[21:59] <Nafallo> meh. oki.
[21:59] <kenvandine_wk> asac: done and pushed
[21:59] <seb128> in fact not it's not empty but that is not in the queue
[21:59] <kenvandine_wk> asac: oh... the patch doesn't apply for you?
[21:59] <kenvandine_wk> wtf
[21:59] <asac> kenvandine_wk: no it works
[21:59] <asac> all fine
[21:59] <kenvandine_wk> ok :)
[21:59] <kenvandine_wk> good
[22:04] <asac> i just try to get latest indicate to test.
[22:06] <kenvandine_wk> ok
[22:08] <mvo> kenvandine_wk: https://edge.launchpad.net/~mvo/+archive/ppa/+build/942108 :/ that looks like it will not finish before I go to bed. I have a day off tomorrow and then is easter. could you watch out for it and drive it? hopefully it just works and just needs someone to upload it
[22:09] <seb128> mvo: enjoy your well deserved weekend!
[22:09] <asac> mvo: enjoy
[22:09] <mvo> I will be here for a bit longer :(
[22:09] <mvo> but yeah, I look forward to it :)
[22:10] <seb128> still a pleasure to have you around there ;-)
[22:10] <seb128> still feel to join the club of those who don't sleep who is lead by asac
[22:10] <mvo> haha, thanks!
[22:10] <asac> ;)
[22:10] <mvo> asac never sleeps?
[22:10] <seb128> not during the night apparently
[22:11] <asac> mvo: why would i ... i dont drink tea ;)
[22:11] <mvo> and *how* did you find out ;) ?
[22:12] <kenvandine_wk> mvo: will do
[22:13] <mvo> kenvandine_wk: thanks a lot!
[22:13]  * mvo hugs kenvandine_wk
[22:13] <kenvandine_wk> mvo: enjoy some time off :)
[22:13] <kenvandine_wk> mvo: so how can i test this from your ppa?
[22:14] <mvo> kenvandine_wk: easiest is probably to ask rickspencer3 to add the ppa to his sources.list (deb http://ppa.launchpad.net/mvo/ubuntu jaunty main) and then run apt-get update ; apt-get dist-upgrade - if ekiga no longer displayed as held-back its solved
[22:14] <kenvandine_wk> ah
[22:14] <kenvandine_wk> so that would get it in a dist-upgrade
[22:14] <kenvandine_wk> ok
[22:15] <kenvandine_wk> great
[22:15] <kenvandine_wk> thx
[22:15] <kenvandine_wk> rickspencer3: i will be pinging you about that tomorrow :)
[22:15] <mvo> alternatively a jaunty beta desktop cd should work as well
[22:15] <kenvandine_wk> i have a VM i can rollback too
[22:15] <mvo> yeah, the problem currently is that its held back there
[22:15] <kenvandine_wk> asac: how is indicate-python looking?
[22:15] <mvo> and update-manager should show it not grayed out too :)
[22:15] <mvo> kenvandine_wk: vm> execllent!
[22:15] <kenvandine_wk> mvo: that is always a good thing :)
[22:16] <kenvandine_wk> mvo: thx again... enjoy your day off :)
[22:16] <mvo> :)
[22:19] <kenvandine_wk> asac: i have to run to get the kids ready for soccer... but will try to check-in before i leave to make sure there are no blockers :)
[22:19] <asac> kenvandine_wk: i think its ok. i have to find a archive admin who will take care of the NEWing though to check on the licensing
[22:19] <asac> would be bad if it gets rejected ;)
[22:20] <kenvandine_wk> yeah :/
[22:20] <kenvandine_wk> please let me know
[22:20] <asac> james_w: you available for the NEWing?
[22:22] <kenvandine_wk> asac: i have a patch that fixes the COPYING files
[22:23] <kenvandine_wk> asac:  http://bazaar.launchpad.net/~ken-vandine/indicator-applet/indicate-python/revision/22
[22:23] <asac> kenvandine_wk: that would be a good start. could you also make a patch for those test files ;)
[22:23] <kenvandine_wk> if that helps
[22:23] <kenvandine_wk> i have that too
[22:23] <kenvandine_wk> one sec
[22:24] <kenvandine_wk> http://bazaar.launchpad.net/~ken-vandine/indicator-applet/indicate-python/revision/23
[22:24] <kenvandine_wk> i really have to go
[22:24] <rickspencer3> hey all
[22:24] <djsiegel1> rickspencer3: hey
[22:25] <rickspencer3> djsiegel1 == gnomedo
[22:25] <asac> kenvandine_wk: lets see if i can get some archive admin input ;)
[22:25] <rickspencer3> now works at Canonical on Ux team
[22:26] <asac> welcome djsiegel1
[22:26] <eeejay> hey kenvandine_wk
[22:26] <asac> hope you enjoy #ubuntu-desktop ;)
[22:28] <seb128> hello djsiegel1
[22:29] <bryce> welcome aboard djsiegel1
[22:29] <djsiegel1> thank you, seb128, bryce
[22:31] <seb128> chrisccoulson: gnome-session uploaded, do you think you could send those changes upstream too?
[22:32] <seb128> chrisccoulson: there is also the 2.26.0.90 update to do if you want ;-)
[22:33] <chrisccoulson> i don't mind doing that:) perhaps tomorrow night if thats ok though - just working on the fusa changes now
[22:33] <seb128> chrisccoulson: right, really no hurry I did the snapshot today
[22:33] <seb128> chrisccoulson: vuntz just fixed some small bugs before rolling the tarball
[22:34] <seb128> chrisccoulson: there is really no hurry there
[22:34] <chrisccoulson> that's good. i'll sort that out tomorrow evening after work hopefully
[22:34] <seb128> ok thanks, you work is really appreciated ;-)
[22:34] <chrisccoulson> you're welcome:)
[22:51] <james_w> asac: I don't think I should as I reviewed the packaging
[22:52] <seb128> asac: try asking slangasek on the next channel ;-)
[22:52] <james_w> StevenK should be online soon and it is his day
[22:54] <asac> yeah lets poke stevenk
[22:56] <seb128> I appreciate that you don't try to make me review it ;-) I'm not the best person to ask for license review and I'm busy this week ;-)
[23:04] <asac> seb128: i left you out intentionally ;)
[23:16] <Ampelbein> james_w: ping about bug 338963 and bug 352653
[23:16] <james_w> hi Ampelbein
[23:16] <Ampelbein> hi.
[23:17] <Ampelbein> the thing is that python-coherence can't be shipped on the live-cd as seb128 pointed out.
[23:18] <asac> james_w: hmm ... where were those auto synched bzr branches for our packages again ;)?
[23:18] <Ampelbein> so this "ugly" error message by totem should be fixed by not-shipping the totem-plugin on the cd also.
[23:20] <Ampelbein> or at least have the error message changed to something more useful.
[23:22] <james_w> Ampelbein: ok, Charlie highlighted as something he wanted to fix for Jaunty, but it shouldn't block your fix
[23:22] <james_w> if you could have nailed both in one upload then it would have been great
[23:22] <Ampelbein> james_w: the plugin for totem is in totem-plugins, while the missing dbus-file is in python-coherence.
[23:23] <Ampelbein> james_w: we could split-out the coherence-plugin to a seperate totem-plugins-coherence package and have that depend on python-coherence, but i don't know if thats gonna be useful.
[23:24] <james_w> I'm not sure
[23:25] <seb128> I've missed the start of the discussion
[23:25] <seb128> what is the issue?
[23:25] <seb128> we have totem-plugins-extra for the purpose of "plugins which need universe depends to work"
[23:26] <Ampelbein> seb128: bug 338963 and bug 352653
[23:26] <Ampelbein> seb128: then i suggest to move the coherence-plugin to totem-plugins-extra.
[23:26] <seb128> seems a reasonable suggestion indeed
[23:26] <Ampelbein> since it needs python-coherence to function.
[23:26] <seb128> want to work on the change?
[23:26] <Ampelbein> sure.
[23:26] <seb128> thanks
[23:27] <seb128> you need to use a Replaces since you will move files between binaries
[23:27] <seb128> and don't forget to update the descriptions ;-)
[23:27] <Ampelbein> i'll try to be perfect ;-)
[23:28] <Ampelbein> james_w, seb128: i think the change to 352653 can be uploaded nonetheless.
[23:28] <seb128> I will let a MOTU review that
[23:28] <seb128> i've too much to do already
[23:29] <james_w> Ampelbein: I'm sure it can, thanks for investigating
[23:29] <james_w> Ampelbein: drop a note in the bug and it will appear in my Inbox to remind me to upload tomorrow
[23:29] <Ampelbein> will do.
[23:34] <Laney> are fakesyncs done by AAs?
[23:35] <Laney> hm, meant that for -motu
[23:36] <seb128> Laney: why not doing a real sync?
[23:36] <Laney> orig mismatch
[23:36] <seb128> yeah, so they are a normal upload
[23:36] <Laney> ok, thought so
[23:37] <seb128> use an ubuntu revision so there is no confusion and nobody tries to sync a new revision from debian next cycle
[23:39] <Ampelbein> seb128: should the replaces be (<< 2.26.1-0ubuntu3), as this is the version i'm building or rather (<= 2.26.1-0ubuntu2), the version currently in the archive?
[23:40] <seb128> either way
[23:41] <seb128> they are equivalent
[23:41] <Ampelbein> ok, so there is no standard way of doing it?
[23:42] <seb128> not that I know about
[23:44] <asac> Ampelbein: use << 3 ... in that way versions like ubuntu2.xxx would still be replaced (e.g. in ppas or downstreams)
[23:44] <Ampelbein> asac: ok, thanks.