[04:20] <Dmitrii-Sh> o/
[04:24] <jam> morning Dmitrii-Sh
[05:00] <Dmitrii-Sh> morning jam
[07:24] <niemeyer> Morning all
[07:49] <niemeyer> Today I'm running through the entire PR queue.. please don't merge anything as I go through it so we don't clash in the middle.
[08:15] <Dmitrii-Sh> jam: https://github.com/canonical/operator/pull/212#discussion_r404621103 addressed comments for 212
[08:16] <Chipaca> good and paperwork-flooded morning, all!
[08:16] <Dmitrii-Sh> o/
[08:18] <Dmitrii-Sh> jam: also: I think that emitting -changed events for remote_app_data if .begin() is called after a relation is added is an important use-case but probably belongs to a different PR
[08:19] <Dmitrii-Sh> we haven't discussed it in 212 but one test case I just added is related to that (it needs a counterpart where a unit is not a leader and a peer relation is tested)
[08:25] <niemeyer> Dmitrii-Sh: #216 is reviewed
[08:25] <Dmitrii-Sh> niemeyer: ty
[08:25] <niemeyer> np, glad to see this kind of component showing up
[08:26] <niemeyer> Hopefully the first of many
[08:26] <jam> Dmitrii-Sh, are you saying if you do add_relation_unit/add_relation after begin() ?
[08:27] <jam> Chipaca, no, please don't wish that upon me :)
[08:27] <jam> (hopefully you don't get too many papercuts from the paper flood)
[08:27] <jam> morning Gustavo
[08:28] <Chipaca> :)
[08:28] <niemeyer> jam: o/
[08:29] <Dmitrii-Sh> jam: not exactly. If somebody does `add_relation(... remote_app_data=some_dict)` or `set_leader(is_leader=False) ; add_relation(... initial_app_data=some_dict)` before calling .begin(), once they call begin, the charm object should get a relation_changed event
[08:30] <Dmitrii-Sh> it's the scenario where app data exists in the model but your unit hasn't come up yet
[08:30] <jam> Dmitrii-Sh, so we can certainly discuss that. My concern is mixing "setting up stuff as precondition" from "sending events during the lifetime"
[08:33] <Dmitrii-Sh> jam: ok, I'll switch to a different PR for now but just wanted to bring that up - in my view, it's a condition that might occur and that a conscious developer would want to test
[08:33] <Chipaca> whoa, 30 people. Feels like a celebration in here :)
[09:09] <niemeyer> facubatista: You got a review on #213
[09:41] <niemeyer> jam: #212 too.. this one feels like it might be better for you to think it through and take it over
[09:41] <niemeyer> jam: Let's catch up about it at some point today or tomorrow
[09:46] <jam> sure
[09:53] <Chipaca> jam: I had a note to talk with you about something similar, adding network_get support to the harness
[09:53] <Chipaca> as that's also going to be blocking Dmitrii-Sh soon (if not already)
[10:14] <Dmitrii-Sh> Might be useful to address https://github.com/canonical/operator/issues/175 along with adding relation-created https://github.com/canonical/operator/pull/218
[10:16] <Dmitrii-Sh> it feels like we'd need to change the signature of Relation.__init__ here https://github.com/canonical/operator/blob/17f4885b73d7b2bfb7445388e7e62b9fcd040859/ops/model.py#L368-L383 to be able to get the remote application based on JUJU_REMOTE_APP, instead of using units for that
[10:17] <Dmitrii-Sh> there is no such thing as `relation-list -r <id> --app` to list the remote app either
[10:18] <Dmitrii-Sh> happy to discuss this in more detail if anybody is interested
[10:45]  * Chipaca steps out for a bit
[10:49] <Dmitrii-Sh> FYI: there's an issue with Travis runs & aarch64: https://travis-ci.community/t/no-cache-support-on-arm64/5416/27 - that's why there were test failures in the tls-certificates PR which pulled the cryptography package
[10:50] <Dmitrii-Sh> I applied a workaround to .travis.yml in this PR. Giving it more visibility because it's hard to find online.
[11:00] <facubatista> Muy buenos días a todos!
[11:01] <niemeyer> facubatista: Good morning!
[11:03] <facubatista> niemeyer, hola :)
[11:12] <facubatista> niemeyer, ack, for the review
[11:13] <Dmitrii-Sh> facubatista: o/
[11:14] <facubatista> hola Dmitrii-Sh!
[11:30] <jam> hi facubatista, the patch has landed in edge and you can bootstrap again
[11:31] <facubatista> jam, yes! read the LP issue, thanks! (I put it to refresh, and then dived into a review
[11:31] <facubatista> )
[11:33] <facubatista> all: I don't know if this is more a github or a team convention, but I'm a little lost in this regard (never been involved in long multiperson reviews in GH before)... so: developer X does a PR, dev Y does a comment in the review; if X agrees with that (answers 'OK' or whatever, and pushes a commit with the proper change), WHO should "resolve" that conversation? X or Y?
[11:34] <jam> facubatista, the way *I* do reviews: If I mark it Approved with a comment, that is saying that if you agree with my comment and fix it, then I don't need to review it again for you to land it.
[11:35] <jam> If I mark it Comment then I want to see it again, but I'm not concerned, if I mark it Needs Fixing then I definitely don't want it to land without seeing it again.
[11:35] <facubatista> jam, not yet approved... you did a review, has 5 comments, I address 4 of those, answering each "ok", and pushing a commit... one conversation is still open! but those 4 are resolved, shall I close them or you?
[11:35] <jam> facubatista, but it is always on the developer to push to get their PR landed.
[11:36] <facubatista> jam, my question is not the PR as a whole, but each conversation
[11:38] <jam> good question. I'd generally say the person who raised the question should be the one who acknowledges it is resolved.
[11:39] <Dmitrii-Sh> jam: interesting comment https://github.com/canonical/operator/pull/210/files#r402267572 I responded but not sure if we should do something about it in this particular PR
[11:40] <jam> Dmitrii-Sh, that wasn't something for this patch, mostly something that we should think about.
[11:40] <Dmitrii-Sh> ok
[11:45] <jam> facubatista, though I think Dmitrii tends to use the comment list as the "things left to do" so he marks them resolved when he finishes them.
[11:53] <niemeyer> Good practice
[11:53]  * niemeyer => lunch
[12:37] <Dmitrii-Sh> jam, facubatista: I tend to resolve them referencing the commit where I address the issue/comment. With that I can at least sanely track the remaining items without looping over them and remember where I think I fixed things
[12:37] <Dmitrii-Sh> in short: jam is correct
[12:38] <jam> Dmitrii-Sh, I like the comment about "addressed", I'm just not sure whether it is on the response to resolve the thread, because that hides it when the reviewer comes back
[12:38] <jam> I often have to dig a bit to find your response to my comment.
[12:39] <Dmitrii-Sh> hmm, I could tag the responses somehow if that helps
[12:39] <Dmitrii-Sh> just need to agree on something easily searchable
[12:39] <facubatista> jam, that's my main point in favor of "all comments should be resolved by the person who initiated it"... (which has its downsides, of course)
[12:40] <jam> Dmitrii-Sh, my pattern is "I put it up for review, facu comments on it, I reply with 'done', facu gets to close it"
[12:41] <jam> that acks that I saw what he asked, and that I've done the work myself (including the git hash on top of that is great),
[12:41] <facubatista> jam, I prefer that; however, I need to pay attention to finally close all comments I initiated! (which IMO is my responsibility as a reviewer, anyway, UNLESS I already approved the PR)
[12:41] <jam> It does mean your list of 'things left to do' isn't the list of open questions, but the list of open questions that you haven't replied to.
[12:42] <jam> facubatista, yeah, I personally would probably only Resolve them if I was then asking for more, vs just an overall approval
[12:42] <jam> facubatista, I did have a comment on the Breakpoint pr. (213). It feels like we should be only printing the help text 1 time at startup, vs on each breakpoint. Thoughts?
[12:43] <jam> Dmitrii-Sh, given gustavo's comment. What do you think about letting update_relation_data set self values, but only prior to begin()
[12:43] <jam> that would let it be incremental
[12:44] <jam> but also avoid having the harness changing thing that the charm should be taking as its responsibility ?
[12:44]  * jam takes the dog out quickly, bbiab
[12:44] <facubatista> jam, I didn't see that question, sorry :( ... so, we should present the comment everytime the process is started, as juju would do that in a "clean tmux", right? but if we handle several breakpoints in the same run, one message should be enough
[12:49] <Dmitrii-Sh> jam: I can rework it as you suggested. Then I think we also need to remove the existing remote_app_data argument and handle everything via update_relation_data
[12:50] <Dmitrii-Sh> otherwise people will need to be educated that they can only add remote data like that but have to use update_relation_data before begin to set initial data for our unit and app
[12:50] <Dmitrii-Sh> before `.begin()` *
[12:52] <Dmitrii-Sh> I'll wait for feedback and then implement it if we all agree on the approach
[12:53] <Dmitrii-Sh> jam: also, if you have any thoughts on https://github.com/canonical/operator/pull/218#issuecomment-610364750, it would be good to hear
[12:53] <Dmitrii-Sh> either I don't see something obvious, or we need `relation-list -r <rid> --app`
[12:56] <narindergupta> Dmitrii-Sh, niemeyer hi
[12:56] <jam> facubatista, right. clean tmux per hook, but only 1 message when handling multiple breakpoints in a single exec
[12:57] <jam> Dmitrii-Sh, don't we have JUJU_REMOTE_APP ?
[12:57] <Dmitrii-Sh> jam: in a relation event context - yes. But not in "leader-elected" or "start"
[12:58] <jam> yeah, I hadn't finished going through your comment.
[12:58] <jam> hm
[12:58] <facubatista> jam, indeed, will improve that
[12:58] <narindergupta> Dmitrii-Sh, niemeyer in my case any change in pod sec  and calling set_spec is removing the juju unit and add a new unit.  So existing unit zookeeper/0 gets removed and zookeeper/1 gets added.
[12:59] <jam> narindergupta, changing a pod spec will update the pod spec with k8s, which causes k8s to spin up new pods and tear down old pods
[12:59] <jam> thus they show up as new Juju units.
[12:59] <jam> (eg, if you have n=3, at some point there will be a 4th k8s pod before it kills the 1st one)
[13:00] <jam> narindergupta, I'm not positive how it works if you have a StatefulSet that supports storage, because there the identifiers get to be reused.
[13:00] <narindergupta> jam, for persistent pods name is same so it tries to delete the volume and create it again and gets stuck
[13:00] <Dmitrii-Sh> jam: so if I want to write something to an app relation data bag in any non-relation event, I need to reference the app somehow. And currently we retrieve a remote app for a Relation object based on a remote unit
[13:00] <Dmitrii-Sh> before we have remote units .app is None
[13:01] <jam> Dmitrii-Sh, "reference the app", I don't quite follow. You don't get to write to the remote app's data.
[13:01] <jam> Dmitrii-Sh, are you saying to *read* the remote app's data ?
[13:02] <Dmitrii-Sh> jam: ok, sorry, read/write
[13:02] <Dmitrii-Sh> actually, "just read" because we have special handling for peer relations
[13:03] <narindergupta> jam, will it be an issue for any k8s charm update, upgrade etc if we change the pod spec. In other words we should not change the pod spec if using persistence volume. Is there a way to not to delete the persistence volume during pod stop?
[13:04] <jam> narindergupta, so you're past my knowledge for persistent volumes. I'd say ask in #juju from wallyworld or kelvinliu
[13:04] <narindergupta> jam, ok let me check with them.
[13:07] <jam> Dmitrii-Sh, seems ok to drop remote_app_data if we are dropping the rest. I prefer the single setup-step approach but obviously that isn't universal
[13:09] <Dmitrii-Sh> jam: ok, I think we can spend couple of minutes during the standup to go over that just to make sure everybody is on the same page and then I'll implement this.
[13:09] <jam> Dmitrii-Sh, I think we have a cross team sync during our standup
[13:10] <jam> Dmitrii-Sh, https://github.com/canonical/operator/pull/212/files#r404561805 . "if we make our unit a leader we should see it". Yes we should be able to read the data, but I don't think you get a relation-changed event for something the previous leader set.
[13:10] <Dmitrii-Sh> jam: indeed :^)
[13:12] <jam> Dmitrii-Sh, ok. I think it is just my confusion around the ordering of the checks. "if is_our_app_updated: " should return, but shouldn't return if it is a peer relation and we aren't the leader.
[13:12] <jam> Trying to figure out if there is a clearer way to convey that.
[13:12] <jam> I do see what you're checking.
[13:14] <Dmitrii-Sh> jam: ok
[13:15] <jam> Dmitrii-Sh, so you wanted this to handle the case of being promoted to leader?
[13:17] <jam> Dmitrii-Sh, I have a proposed spelling/comment. if it doesn't feel clearer I'm not stuck on it. But I think my confusion was because you were checking "not is_peer" first
[13:17] <Dmitrii-Sh> jam: "being promoted to leader?" - which line is that, sorry?
[13:17] <jam> Dmitrii-Sh, given that your unit doesn't get to see app data when it is updated, why did you want to update the app data for the remote?
[13:18] <jam> so that you could set it, and then promote the unit to leader and see that it sees the app data ?
[13:20] <pekkari> Hi guys, I'm having a charm that seems to be skipping the install hook, is there anything else required than declaring the observer on start, and defining the on_install function?
[13:25] <Dmitrii-Sh> pekkari: is that a k8s charm on Juju 2.7.x?
[13:26] <Dmitrii-Sh> in that case, this is expected per https://bugs.launchpad.net/juju/+bug/1854635 but will be fixed in 2.8.x
[13:27] <Dmitrii-Sh> you can use on_start though
[13:27] <pekkari> no k8s, Dmitrii-Sh, I'm just trying to write gsss charm using the op framework
[13:27] <Dmitrii-Sh> you need to have a symlink at hooks/install -> ../src/charm.py
[13:28] <pekkari> so in __init__ I add the line: self.framework.observe(self.on.install, self) , and then add the def on_install(self, event):
[13:28] <pekkari> that link is in place also
[13:28] <jam> Dmitrii-Sh, I just checked with Juju, that was released in a 2.7.? so it should be fixed in 2.7.5
[13:28] <Dmitrii-Sh> jam: thanks
[13:28] <jam> getting them to update the bug
[13:29] <Dmitrii-Sh> pekkari: could you paste your charm.py somewhere? Or at least the top and the bottom of it
[13:30] <Dmitrii-Sh> #!/usr/bin/env python3
[13:30] <Dmitrii-Sh> from ops.main import main
[13:30] <Dmitrii-Sh> # ...
[13:30] <Dmitrii-Sh> class MyCharm(ops.charm.CharmBase)
[13:30] <Dmitrii-Sh> # ...
[13:30] <Dmitrii-Sh> if __name__ == '__main__':
[13:30] <Dmitrii-Sh>     main(MyCharm)
[13:30] <Dmitrii-Sh> pekkari: you also need that ^
[13:32] <jam> Dmitrii-Sh, facubatista : there is a "Weekly K8s Charm Sync" that got a collision with our usual standup time.
[13:32] <Chipaca> Dmitrii-Sh: jam: standup?
[13:32] <Chipaca> jam: or are you going to that sync?
[13:32] <jam> Chipaca, going to that sync today at least
[13:33] <niemeyer> jam: If that was just booked, ideally it should deconflict
[13:33] <Dmitrii-Sh> Chipaca:  at this cross-team sync
[13:33] <niemeyer> Dmitrii-Sh: Same
[13:34] <niemeyer> We've moved the standup
[13:34] <pekkari> Dmitrii-Sh: let me try that and if I observe no change I'll paste it, to let you read, thanks!
[13:35] <narindergupta> jam, it seems to be juju bug and I have raised the bug and thanks for guidance. Also another question is there any event gets fired when pod/unit/app status gets changed? I am more interested in app status event as it would help me to determine whether all my pods are up or not? Instead of waiting for update status event after 5 minutes?
[13:35] <niemeyer> narindergupta: I'd like to have a call with you and jam to understand this behavior a bit better
[13:35] <Dmitrii-Sh> ok, sorry, I thought that sync conflict was agreed upon
[13:36] <narindergupta> niemeyer, I am available now
[13:36] <niemeyer> Okay, let's do it.. jam cannot join us but I'd like to understand at least what you're observing.
[13:37] <niemeyer> narindergupta: https://meet.google.com/gri-hkiq-itv
[13:53] <pekkari> hum, even moving the install code to start event doesn't seem to make it, can you please take a quick read here Dmitrii-Sh? https://pastebin.canonical.com/p/7TMVMG954c/
[13:55] <narindergupta> niemeyer, https://bugs.launchpad.net/juju/+bug/1871388
[13:55] <Dmitrii-Sh> pekkari: could you also share a pastebin with `tree <charm-source-dir>`?
[13:57] <pekkari> absolutely
[14:00] <pekkari> here it is, Dmitrii-Sh: https://pastebin.canonical.com/p/q5GVvb6rpw/
[14:04] <niemeyer> narindergupta: Can you please paste the pod spec for the example we've explored?
[14:04] <niemeyer> narindergupta: Just for completeness
[14:04] <narindergupta> niemeyer, sure
[14:06] <narindergupta> This is zookeeper pod spec http://paste.ubuntu.com/p/mqxjxZyBxh/
[14:08] <narindergupta> niemeyer, added in the bug comment also.
[14:14] <niemeyer> narindergupta: Thanks!
[14:15] <Dmitrii-Sh> pekkari: haven't found anything apparent yet. I'll have a look after meetings
[14:15] <Dmitrii-Sh> juju show-status-log <unit> might also help
[14:17] <pekkari> take your time Dmitrii-Sh, seems no trivial issue, I struggled for a big while with this, show-status-log here: https://pastebin.canonical.com/p/3rzGz3M93J/
[14:24] <jam> pekkari, install only happens once. it looks like you're long past install by the time you're doing these steps
[14:27] <pekkari> jam, that is what I expected, though after the creation of the unit I never see the packages I expect installed. install hook is nearly copy & paste of the former charm, and apt packages library works when running ocally
[14:28] <pekkari> so seems like the workflow never hit the on_start function when running the install hooks
[14:29] <pekkari> I'm going to remove the unit and add a new one though, perhaps with the changes will help
[14:40] <pekkari> no luck, it shows install status, goes forward to config-changed and errors there, the expected packages doesn't get installed
[14:43] <jam> pekkari, config-changed happens before start
[14:43] <jam> pekkari, install, relation-created, config-changed, start IIRC
[14:44] <jam> (relation-created is new in Juju 2.8)
[14:45] <pekkari> in that case, I'd need to consider to move back the code to the install event, and observe it as it was before
[14:46] <jam> pekkari, so if you need something before you can respond, I would, indeed, put it in install, and consider if it is the sort of thing that would change over time, putting it in upgrade-charm
[14:54] <pekkari> aha! now I see a traceback with my code, thanks for the hint jam and Dmitrii-Sh!
[15:00] <Dmitrii-Sh> pekkari: ok, so the "install" symlink needs to be in the hooks directory at the deployment time
[15:00] <Dmitrii-Sh> then all others will be created by the framework automatically
[15:00] <Chipaca> my canonical calendar is now suggesting personal contacts instead of canonical contacts for meetings
[15:00] <Chipaca> something's effed up o_o
[15:00] <niemeyer> Chipaca: It just knows you care personally about it
[15:00] <Dmitrii-Sh> Chipaca: maybe it's just the EOD time
[15:01] <Chipaca> :-)
[15:01] <niemeyer> Chipaca: "Hey, how about asking your son to fix that!?"
[15:01] <Chipaca> I mean, I can _ask_
[15:01] <niemeyer> I know *my* son would be super excited to get involved..
[15:01] <Dmitrii-Sh> pekkari: if you have any juju storage defined in metadata.yaml you also need to have storage event symlinks because they fire before "install" but it doesn't look like you have any
[15:02] <niemeyer> We might have some trouble handling that excitement, though
[15:05] <pekkari> Dmitrii-Sh: no, so far not yet, I took this charm because of being always broken, and seems to be little enough to let me learn properly the main points in operator framework, but thanks for the hint, I may hit that later
[15:13] <facubatista> niemeyer, jam, already addressed your comments on #213
[15:22]  * facubatista -> lunch
[15:24] <Dmitrii-Sh> pekkari: ok, have you managed to get to a proper state or can I still help?
[15:29] <pekkari> Dmitrii-Sh: yes, I got to the install code I wanted to reach, your hints about the ops.main import and the if __name__ clause, plus keeping the install code in the install event made it through, and now the problems around are problems for tomorrows José
[15:29] <pekkari> thanks man!
[15:30] <Dmitrii-Sh> pekkari: great, np!
[15:30] <Dmitrii-Sh> have a good evening
[15:30] <pekkari> you too!
[16:25] <niemeyer> facubatista: LGTM still
[16:30]  * facubatista is back
[16:34] <facubatista> niemeyer, thanks
[17:37]  * Chipaca goes off to make dinner
[17:37] <Chipaca> ttfn!
[17:47] <facubatista> Chipaca, have a nice cooking
[20:42]  * facubatista eods
[23:25]  * Chipaca eods


[02:22] <ojwb> http://www.localbd.co.nz/company/Chartered-Accountants_111275/ (the prefill of the directions "to")
[02:25] <ajmitch> classy
[03:06] <G> ojwb: I'm actually disappointed that there are no swim to Australia instructions there
[03:07] <ojwb> they seemed to have stopped trying to ring me after the second attempt at least
[03:07] <G> like I've had Kayak to mainland US via Japan & Hawaii on a trip 'just down the road'
[03:07] <ojwb> i couldn't understand who/what he was asking for, but I was fairly sure it wasn't me
[12:59] <chilts> hey everyone, I'm now MARRIED! :)
[13:00] <chilts> oh, and morning (though I haven't yet gone to bed, take in advance for tomorrow)
[13:00] <ojwb> congratualtions
[13:08] <chilts> thanks :)
[18:16] <ibeardslee> congrats
[18:16] <ibeardslee> good luck to you and your lovely lady
[19:22] <chilts> thanks again :)
[19:23] <mwhudson> morning
[19:26] <ajmitch> morning
[19:26] <ajmitch> congratulations chilts
[21:21] <ojwb> morning
[21:53] <G> morning
[21:53] <G> chilts: congrats


[22:19] <arcadellama> good evening, the official download mirror (for amd64 at least) seems to be down?
[22:20] <arcadellama> both bittorrent and direct download of iso
[22:20] <arcadellama> https://ubuntu-mate.org/download/amd64/jammy/
[22:20] <arcadellama> for 22.03
[22:20] <arcadellama> *22.04
[22:46] <sixwheeledbeast> https://cdimage.ubuntu.com/ubuntu-mate/releases/22.04.1/release/ubuntu-mate-22.04.1-desktop-amd64.iso
[22:48] <sixwheeledbeast> the link posted on UM website has now changed, if arcadellama comes back ^
[22:51] <sixwheeledbeast> probably could do with updating the link and new shasum, with the original 22.04 link being dead.


[03:43] <aringan> I just upgraded my ubuntu from 8.04 to 10.04, and its network is not working
[03:43] <aringan> it's on another Vm machine
[03:44] <aringan> I just upgraded my ubuntu from 8.04 to 10.04, and its network is not working
[03:44] <aringan> it's on another Vm machine
[05:52] <rigid_rexdrive> yo
[06:53] <dholbach> good morning
[08:45] <prawns> hi


[10:55] <Burgundavia> beuno: you up
[10:55] <beuno> Burgundavia: shouldn't be, but yes
[10:56] <Burgundavia> just finished speaking with Chris
[10:56] <Burgundavia> basically, all is rosy
[10:57] <Burgundavia> Canonical is very much interesting in not duplicating work and their marketing focus is very tight
[10:57] <Burgundavia> thoughts?
[10:58] <Burgundavia> beuno: we also spoke briefly about the dyi stuff
[10:58] <Ckenyon> beuno: Hi Martin
[10:58] <Ckenyon> Chris here
[10:58] <Burgundavia> if you need hosting for that, we should figure out the requirements for it now
[10:58] <beuno> ah, much better
[10:58] <beuno> hey
[10:58] <beuno> how are you?
[10:58] <Burgundavia> as poor elmo needs to make certain the relesae goes well
[10:59] <Ckenyon> As per Coreys comments:  For hosting  - Elmo is the lead and given the normal amount of work required for a release it is worth contacting him now
[10:59] <beuno> well, I'm glad to hear all is rosy!
[10:59] <beuno> and, well
[10:59] <Ckenyon> As for de-duplication of efforts we agreed to set up a web page with all community and canonical efforts laid out
[10:59] <Ckenyon> We can share resources
[10:59] <beuno> that sounds great
[10:59] <beuno> much more the we expected  :D
[11:00] <Ckenyon> As Corey says - a) We have very little resource here on this task and b) you guys have most of the great ideas
[11:00] <Ckenyon> Where are you based?
[11:01] <beuno> I'm in Argentina
[11:01] <Burgundavia> Ckenyon: if we are doing a single page for all of Feisty, better name it as such
[11:01] <beuno> as far as DIY goes, I can talk to elmo about requierments, they're pretty straight forward, basic LAMP
[11:02] <beuno> I'll probably get the rest of the code together by thursday
[11:03] <beuno> so we can make that "before fiesty" target loosely
[11:04] <beuno> Ckenyon: I think at the moment, everyone is a bit confused on "what we're suppose to be doing"
[11:05] <beuno> for example, for the lastest Feisty beta, there was a fiesty release page like for the rest of the "herds"
[11:06] <beuno> but it seemed unnecesarry at the end
[11:06] <beuno> I guess that might of been due to christina being on her way out, might be a grey area
[11:11] <Burgundavia> ok, summation email sent to teh lsit
[11:13] <Burgundavia> ok, I really need to get to bed
[11:13] <Burgundavia> good night all, Ckenyon, beuno
[11:14] <beuno> night Burgundavia, I'll be following you soon
[11:16] <beuno> well, not into *your* bed
[11:18] <Burgundavia> beuno: a good thing. My gf might be a tad miffed :)
[11:19] <beuno> well, you should hope so  ;)
[11:25] <beuno> anyway, chris, great catchin you for a few min, I'll look forward to helping you guys out
[11:46] <Jenda> hmm...?
[11:46] <Jenda> that sounds interesting...
[11:49] <Jenda> Burgwork: what was that about the DIY website?
[12:13] <juliux> hi Jenda
[12:13] <juliux> Jenda, how much posters you have left?
[12:15] <Jenda> juliux: I have about 60 right here, but I can get an unlimited amount made fairly quickly.
[12:15] <juliux> Jenda, they are all a3 right?
[12:15] <Jenda> yep
[12:16] <Jenda> If we were talking about 200 pieces or more, I could get any number made, I believe.
[12:16] <Jenda> *any size
[01:27] <juliux> wb jenda
[03:11] <MehdiHassanpour> hi :)
[03:11] <MehdiHassanpour> is the news published some where by canonical ?
[03:11] <MehdiHassanpour> http://lxer.com/module/newswire/view/84097/
[03:11] <MehdiHassanpour> Ubuntu Receives Editor's Choice Award from PC Welt
[03:13] <elkbuntu> there is the news module in the site, fridge, and UWN, people here can get to the latter two at least
[03:14] <jenda> ooh
[03:14] <jenda> MehdiHassanpour: the UWN is probably the best place for that.
[03:16] <MehdiHassanpour> I've translated it for our loco site and was looking for a link in ubuntu/canonical sites!
[03:17] <elkbuntu> MehdiHassanpour, it's probably in the queue
[03:20] <MehdiHassanpour> ok. ty :)
[03:31] <juliux> MehdiHassanpour, i saw the award at the canonical booth at cebit so i think they will write something about taht
[04:00] <yann> ping Ckenyon
[04:06] <MaXflY> hi
[04:06] <yann> hi MaXflY . Ckenyon , there?
[04:06] <yann> yann> jono > if we have a question to canonical, for an event where we would like to see canonical instead of ubuntu-fr which got asked, and if we need an answer today or tomorrow, where should we ask?
 yann, Ckenyon is online in -marketing, he'd probably be an appropriate victim
[04:06] <yann> :)
[04:07] <MaXflY> Ckenyon is busy ?
[04:07] <elkbuntu> gee thanks, dob me in why dont you? :
[04:07] <yann> hehe }:-]
[04:07] <elkbuntu> it's likely, he's at work and all
[04:08] <yann> Ckenyon, just ping us back when you're online :).... /me afk
[04:10] <MaXflY> When is it avaible ?
[04:10] <yann> MaXflY, just wait. he'll ping us.
[04:18] <boredandblogging> jenda,
[04:18] <boredandblogging> jenda, ping
[04:24] <jenda> PONG
[04:24] <boredandblogging> jenda, I was looking at the Go section of the DIY...thinking of just go through all the LoCo wiki pages and seeing what they have done
[04:24] <boredandblogging> to get the word out and documenting some of that
[04:25] <jenda> boredandblogging: that would be an immensely valuable contribution.
[04:25] <yann> if someone has the telefon number of Maria Bonnefon, it may help :)
[04:26] <boredandblogging> jenda, I might not be able to find all the details about them like the time required or project life expectancy, but I figure it will be enough of a starting point for people
[04:26] <jenda> certainly
[04:26] <boredandblogging> what is the timetable for this?
[04:26] <jenda> I don't expect all the info to be available immediately.
[04:26] <jenda> boredandblogging: we were hoping to have a presentable site up there by the time Feisty is out.
[04:27] <boredandblogging> jenda, ok, then we have some time, I'll start working on it
[04:27] <boredandblogging> in the next couple of days
[04:27] <jenda> Great, thanks a bunch, boredandblogging :)
[04:28] <boredandblogging> jenda, no problem
[04:28] <mrevell> Hi yann - why would Maria's phone number be useful?
[04:29] <yann> there is an event in france, where i think we (Ubuntu-fr) aren't big enough to handle it ourselves
[04:29] <yann> she's the marketing contact for france, we may sent her a mail, but we need an answer before tomorrow
[04:30] <mrevell> yann: Just a moment, I'll see if I can speak to her.
[04:30] <yann> thanks :)
[04:31] <mrevell> yann: what's the name of the event?
[04:31] <Ckenyon> Yann - ping her on<EMAIL_ADDRESS>and cc me<EMAIL_ADDRESS>[04:31] <Ckenyon> I am back online
[04:31] <yann> Digital Pathway Program
[04:31] <mrevell> yann: Ah, there you go, do what Ckenyon said :)
[04:32] <yann> Ckenyon, am i authoized to write in french and add french documents to the mail? :)
[04:32] <jenda> hey, mrevell, Ckenyon
[04:32] <mrevell> hey jenda
[04:32] <yann> I already have difficulties to understand the deal in french, so in english ^^
[04:32] <jenda> is this an invasion? ;)
[04:33] <mrevell> jenda: :)
[04:34] <mrevell> jenda: We should have a chat some time. I'm out of touch with the Ubuntu marketing stuff, it'd be good to get an update on what you're up to.
[04:34] <jenda> mrevell: anytime ;)
[04:34] <jenda> just... not now, I'm totally exhausted ;)
[04:34] <mrevell> jenda: :) I'm pretty busy right now, so that suits me too.
[04:34] <jenda> mrevell: we're planning to have the DIY project up and running by Feisty.
[04:34] <mrevell> jenda: Superb :)
[04:35] <jenda>
[04:43] <mrevell> yann: Feel free to send French language materials to Maria, certainly.
[04:44] <yann> just mailed in french, youre in cc :)
[04:45] <yann> euh, Ckenyon is in cc =)
[04:45] <mrevell> yann: Merci beaucoup. J'attend avec impatience :)
[04:45] <yann> mrevell = maria bonnefon? :)
[04:46] <mrevell> yann: No :)
[04:46] <yann> Matthew Revenn, ok... hey, nice french ;)
[04:48] <Ckenyon> yann  - Bien sur :-)
[04:49] <Ckenyon> On peut continuer comme ca!
[04:50] <elkbuntu> about all i know is "parlez vous anglais"
[04:50] <yann> mrfff. I'm moving to the UK in tyo yeeks. In a few monthes my english will b as good as your french, I promise :)
[05:07] <mrevell> yann: Where are you moving to?
[05:08] <yann> oxford
[05:08] <yann> got the job on ubuntu.com/employment ;)
[05:08] <jenda> tout le monde parle franais :) whee!
[05:08] <jenda> wow, congrats, yann :)
[05:08] <jenda> Ubuntu is loosing it's best people to Canonical ;)
[05:08] <yann> not really
[05:09] <jenda> :)
[05:09] <yann> got the only job which was not at canonical :D
[05:09] <mrevell> yann: Congratulations :)
[05:09] <jenda> oooh, that one... :)
[05:09] <jenda> Deserter.
[05:09] <jenda> :)
[05:09] <mrevell> jenda: I only have 24 hours in a day :)
[05:09] <jenda> :)
[05:10] <yann> jenda, someone working for canonical should not run a locoteam
[05:10] <yann> we do evangelisation, not marketing :)
[05:11] <jenda> endeed ;)
[05:11] <jenda> *i
[05:21] <Wicks> marketing people... has anyone thrown around the idea of a YouTube type video marketing scheme?
[05:24] <Wicks> because I may have access to a bbc set up studio.. and some funky camera
[05:36] <mrevell> Wicks: I'm slightly out of touch but I think there ubuntuvideo.com. BBC thing sounds cool :)
[05:36] <jenda> there's also ubuntuclips.org
[05:40] <Wicks> im talking about adverts
[05:41] <Wicks> like what Novell are doing with their mac spoofs *but not in the mac vs pc style.. im already sick of it lol
[05:42] <jenda> Wicks: I don't think we have anything like that in place yet.
[05:43] <Wicks> i have some free time coming up - mind if have a bash?
[05:50] <jenda> Wicks: of course not :) That would be very welcome :)
[05:59] <Wicks> awesome
[08:22] <jenda> somerville32: !!!
[08:22] <jenda> Hello :)
[08:22] <jenda> Welcome back, where've ya been, how are you, what's up, how's your dog and the weather?
[08:23] <somerville32> Welp, I'm still in the hospital.
[08:23] <somerville32> I'm doing better.
[08:23] <jenda> eek :(
[08:23] <jenda> what is it?
[08:23] <somerville32> A light is above me.
[08:23] <somerville32> My dog is doing well.
[08:23] <somerville32> And it is a nice day out :)
[08:23] <MenZa> o_O
[08:24] <jenda> (I've heard something's wrong, but have no idea what)
[08:24] <jenda> Get well soon in any case, we need you :)
[08:24] <somerville32> Well, I'll be out in about 2-3 weeks :)
[08:24] <somerville32> I might even be out in time for the Feisty Release.
[08:25] <jenda> whee ;)
[08:25] <somerville32> But regardless, I'm already pumped for Feisty+1 :)
[08:28] <somerville32> Are you guys pumped up for Feisty+1? :)
[08:29] <adamant1988> We'll see.
[08:29] <adamant1988> I take Ubuntu one release at a time
[08:29] <MenZa> Get well
[08:29] <MenZa> :o
[08:31] <somerville32> Thanks :)
[08:33] <somerville32> Welp, gotta run. *waves*
[08:34] <jenda> laters :)
[08:37] <MenZa> jenda: hopefully
[08:37] <MenZa> lts = <3
[08:38] <adamant1988> I hope so too
[08:38] <adamant1988> I'm really tired of the crappy artwork :(
[08:39] <jenda> O_O
[08:39] <jenda> adamant1988: make your own :)
[08:39] <adamant1988> jenda: I'm thinking about it
[08:39] <adamant1988> I might have to dust off PS7
[08:41] <adamant1988> I know LTS's are supposed to be polished, so.. we'll see.


[03:30] <pleia2> working on http://brainupdate.wordpress.com/2011/03/07/ubuntu-is-the-readers-choice/ now
[03:40] <pleia2> nhandler: do you know who handles the feedburner account?
[03:42] <nhandler> pleia2: No. Maybe akgraner or nick
[03:43] <pleia2> it's what feeds the planet and it's been broken since feb
[03:43] <pleia2> should we keep using it or just update planet with the proper feed?
[03:44] <nhandler> pleia2: I can't remember the reason for not using the native WP feed. It might have been so we can get some stats, but if it is broken, switching might be best. However, it might be best to confirm with amber
[03:44]  * pleia2 nods
[03:50] <pleia2> nhandler: can you check if it's associated with the<EMAIL_ADDRESS>account? I just get forwarded that email, I can't log in to the gmail account itself
[03:51] <pleia2> it == feedburner
[03:51] <nhandler> pleia2: I don't see any emails in that inbox about feedburner
[03:51] <pleia2> ok
[03:51] <nhandler> It is also relatively new
[03:53] <pleia2> I'll have to try track down akgraner again tomorrow
[17:25] <pleia2> akgraner: do you know who controls our feedburner account? feeds to planet have been broken since feb :( http://feeds.feedburner.com/ubuntu-news
[17:59] <akgraner> hmmm
[18:00] <akgraner> I think nick might have set that up..I know I didn't but I'll check into it


[13:33] <mgariepy> good morning everyone
[13:44] <highvoltage> good morning!
[14:27] <Hyperbyte> Hi!  New installation of Edubuntu 11.04... so new in fact, the server is still cooling down from all the work...
[14:28] <Hyperbyte> I configured http_proxy and ftp_proxy in /etc/profile
[14:29] <Hyperbyte> Logged in again via SSH so the variables get set
[14:29] <Hyperbyte> Run apt-get install thunderbird
[14:29] <Hyperbyte> "E: Encountered a section with no Package: header"
[14:30] <Hyperbyte> Looked online, saw something about removing /var/lib/apt/lists/*, which didn't help.  Also saw something about exchanging /var/lib/dpkg/status-old and status... no luck either
[14:30] <Hyperbyte> Anymore suggestions? :)
[14:30] <Hyperbyte> It also says to try aptitude by the way, which would be great if it was installed. :)
[14:31] <Hyperbyte> Also:  "W: GPG error: http://nl.archive.ubuntu.com natty InRelease: The following signatures were invalid: NODATA 1 NODATA 2"
[14:36] <Hyperbyte> This is when I run apt-get as root, by the way... as user it doesn't connect, not even a little.... even though the proxy settings are ok. :/
[14:36]  * Hyperbyte is confused.
[14:39] <highvoltage> hey Hyperbyte
[14:40] <highvoltage> what does your http_proxy say? I had a problem like that before when I didn't have a slash at the end of the proxy line
[14:40] <highvoltage> (like http_proxy="http://user:pass@host:port" instead of http_proxy="http://user:pass@host:port/"
[14:40] <highvoltage> )
[14:41] <Hyperbyte> Oh, hi-ghvoltage. :)
[14:41] <Hyperbyte> Nice to see you here as well
[14:42] <Hyperbyte> declare -x ftp_proxy="http://<IP_ADDRESS>:3128/"
[14:42] <Hyperbyte> declare -x http_proxy="http://<IP_ADDRESS>:3128/"
[14:42] <Hyperbyte> declare -x https_proxy="http://<IP_ADDRESS>:3128/"
[14:42] <Hyperbyte> (wget works, so proxy config should be ok)
[14:43] <Hyperbyte> You know you'd make my day if you'd help me fix this.
[14:47] <Hyperbyte> I've implemented LTSP with Fedora and I'm running into all sorts of problems.
[14:47] <Hyperbyte> So insanely big problems it needs fixing -now-, or so the boss says... he's right though, not just pushing me.
[14:47] <Hyperbyte> Thing is - Fedora sucks with LTSP.  In fact, I'd go as far as to say Fedora's GUI and the support that comes with it, is insanely bad.
[14:47] <Hyperbyte> So I've decided to switch to Edubuntu overnight (yes, I'm planning to work through the night if needed)... and get rid of Fedora
[14:47] <Hyperbyte> I'm not gonna get very far if I can't get this apt-get thing working though... so it would mean insanely much to me if you could help me fix this. :)
[14:47] <Hyperbyte> http://secondary.recreatie-zorg.nl/jan/aptget.png
[14:47] <Hyperbyte> That's the full 'apt-get update' output, which some stuff missing at the top, but it spits out of a lot of stuff
[14:47] <Hyperbyte> *with
[14:47] <highvoltage> I think you could make a file in /etc/apt/apt.conf.d that would contain Acquire::http::Proxy "http://<IP_ADDRESS>:3128/" that might work
[14:47] <highvoltage> (well, that's what I would try anyway)
[14:51] <JanMiddelkoop> Hmm...
[14:52] <JanMiddelkoop> Hyperbyte is lagging behind for some reason. :|
[14:52] <JanMiddelkoop> Did I miss anything?
[14:53] <highvoltage> maybe
[14:53] <highvoltage> 09:52 < highvoltage> I think you could make a file in /etc/apt/apt.conf.d that would contain Acquire::http::Proxy "http://<IP_ADDRESS>:3128/" that might work
[14:53] <highvoltage> 09:53 < highvoltage> (well, that's what I would try anyway)
[14:53] <Hyperbyte> I feel a netsplit coming up by the way... some major lag here...
[14:54] <JanMiddelkoop> Wow.  I typed that 5 minutes ago
[14:54] <JanMiddelkoop> root@terminaltest:~# cat /etc/apt/apt.conf.d/20proxy
[14:54] <JanMiddelkoop> Acquire::http::Proxy "http://<IP_ADDRESS>:3128/"
[14:54] <JanMiddelkoop> root@terminaltest:~# apt-get update
[14:54] <JanMiddelkoop> E: Syntax error /etc/apt/apt.conf.d/20proxy:2: Extra junk at end of file
[14:55] <highvoltage> maybe it doesn't want a newline or maybe there's whitespace at the end of the line
[14:56] <highvoltage> I guess the :2 is indicative of a newline
[14:56] <JanMiddelkoop> I checked, there isn't.
[14:56] <JanMiddelkoop> Checked with vi to make sure
[14:57] <JanMiddelkoop> Semicolon missing.
[14:57] <JanMiddelkoop> :)
[14:57] <JanMiddelkoop> Fixed that, same error.
[14:57] <JanMiddelkoop> It looks like it has no trouble finding my proxy actually...
[14:58] <highvoltage> ah
[14:58] <JanMiddelkoop> It's downloading even, so it says... it says there's a problem with some package or list or whatever
[14:58] <JanMiddelkoop> Hah, was waiting for that.
[14:58] <highvoltage> do you have lzma installed?
[14:58] <JanMiddelkoop> Yessir.
[14:59] <highvoltage> ok, looking at your screenshot it seems to have trouble with decoding lzma, but that could just be because the files its getting is 0b
[15:00] <highvoltage> can't think of anything weird that we do in edubuntu that would cause that, it might be a good idea to ask in #ubuntu too fwiw
[15:03] <JanMiddelkoop> Just did that.
[15:31] <highvoltage> stgraber: didn't you use to be able to log in as a guest user from GDM?
[15:32] <stgraber> highvoltage: nope, you can't
[15:32] <stgraber> highvoltage: you can only start a guest session from an existing user session
[15:32] <highvoltage> pity.
[15:32] <stgraber> it's certainly doable to have it in gdm, it just wasn't done for security reason


[04:22] <shadeslayer> morning
[05:47] <phoenix_firebrd> good morning everyone
[05:48] <shadeslayer> hi phoenix_firebrd :)
[05:48] <phoenix_firebrd> shadeslayer: hi
[05:48] <shadeslayer> phoenix_firebrd: so, I have a small task for you
[05:48] <shadeslayer> W: kdiamond source: syntax-error-in-dep5-copyright line 33: Duplicate field license.
[05:48] <shadeslayer> fix this ^
[05:49] <phoenix_firebrd> ok
[05:49] <shadeslayer> that's a lintian warning and is googlable
[05:49] <phoenix_firebrd> ok
[05:49] <shadeslayer> more specifically the syntax-error-in-dep5-copyright bit
[05:50] <shadeslayer> once you're done, here's another one : E: kfloppy source: malformed-override Override of dbg-package-missing-depends for kdeutils (expecting kfloppy) at line 1
[05:50] <phoenix_firebrd> is the kde 4.10 sc tars ready?
[05:50] <shadeslayer> yup, I'm running the script right now
[05:51] <shadeslayer> should take another 30-40 minutes
[05:51] <phoenix_firebrd> ok
[05:52] <shadeslayer> phoenix_firebrd: btw lintian.debian.org will also list packages that have a similar lintian error
[05:52] <shadeslayer> so if the package also exists there, you can ignore it
[05:54] <phoenix_firebrd> shadeslayer: pull-lp-source gives me kdiamond 4.9.98 you want this or 4.10
[05:54] <shadeslayer> use that for now
[05:54] <shadeslayer> or rather
[05:54] <phoenix_firebrd> ok
[05:54] <shadeslayer> do you have kubuntu-dev-tools installed?
[05:54] <phoenix_firebrd> shall i finish my breakfast in 10 min?
[05:54] <shadeslayer> sure
[05:55] <phoenix_firebrd> ok
[05:55] <shadeslayer> install kubuntu-dev-tools once you're done and run kbzr branch kdiamond
[05:55] <shadeslayer> in there, you'll find the latest packaging
[05:57] <phoenix_firebrd> i have done that already
[06:16] <phoenix_firebrd> shadeslayer: Can i edit the copyright file?
[06:19] <shadeslayer> sure
[06:30] <phoenix_firebrd> brb
[06:39] <phoenix_firebrd> shadeslayer: ok i soved the copyright issue for kdiamond what should i do
[06:40] <phoenix_firebrd> checking kfloppy
[06:40] <shadeslayer> install kubuntu-dev-tools , kbzr branch kdiamond , patch the copyright file and propose a merge on lp
[06:41] <phoenix_firebrd> ok
[06:41] <shadeslayer> see https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kdiamond
[06:43] <phoenix_firebrd> what should be the version and release name i should specify in the change log?
[06:43] <phoenix_firebrd> shadeslayer: ^
[06:43] <shadeslayer> don't
[06:44] <shadeslayer> phoenix_firebrd: just edit debian/copyright
[06:45] <phoenix_firebrd> ok
[06:51] <shadeslayer> kdeplasma-addons: bzr unclean or out of sync
[06:51] <shadeslayer> wot
[06:57] <phoenix_firebrd> shadeslayer: done
[06:58] <shadeslayer> cool :)
[06:58] <phoenix_firebrd> are you going to merge it noe?
[06:58] <shadeslayer> in a bit
[06:58] <shadeslayer> I want to push 4.10 branches first
[06:58] <phoenix_firebrd> ok
[06:59] <phoenix_firebrd> checking kfloppy
[06:59] <phoenix_firebrd> shadeslayer: there is a mistakle
[07:00] <shadeslayer> fix it :)
[07:00] <phoenix_firebrd> i have put "changelog" instead of "copyright" in changelog
[07:02] <shadeslayer> erm
[07:02] <shadeslayer> can not add an entry to the changelog?
[07:03] <shadeslayer> *can you
[07:07] <phoenix_firebrd> shadeslayer: corrected the change log and summited for merge
[07:10] <shadeslayer> phoenix_firebrd: can you drop the changelog entry?
[07:10] <shadeslayer> not required
[07:11] <phoenix_firebrd> shadeslayer: but yofel told me to mention anything that is changed
[07:12] <shadeslayer> yes, anything major
[07:12] <shadeslayer> that's a trivial change
[07:12] <shadeslayer> can be skipped
[07:12] <phoenix_firebrd> shadeslayer: ok if you say so
[07:19] <phoenix_firebrd> debuild succeeds for kfloppy 4.9.98
[07:19] <phoenix_firebrd> shadeslayer: ^
[07:20] <shadeslayer> look at the lintian output
[07:21] <phoenix_firebrd> shadeslayer: ya i can see that, i have come across that yesterday
[07:21] <phoenix_firebrd> checking for a solution
[07:22] <phoenix_firebrd> shadeslayer: but thats a warning right?
[07:22] <shadeslayer> yup
[07:22] <Quintasan> mfw shadeslayer is tutoring someone
[07:22] <shadeslayer> heh
[07:23] <Quintasan> God
[07:23] <Quintasan> Gotta take a look at maliit-frameworks
[07:23] <Quintasan> duh
[07:23] <shadeslayer> erm
[07:23] <Quintasan>  wat
[07:23] <shadeslayer> phoenix_firebrd: you have diff markers now
[07:23] <yofel_> morning
[07:24] <shadeslayer> hi yofel
[07:24] <yofel> bad shadeslayer not putting changes in changelog :P
[07:24] <yofel> anyway
[07:24] <phoenix_firebrd> yofel: morning
[07:24] <shadeslayer> it's a trivial change! :P
[07:24] <yofel> yeah, vm
[07:24] <yofel> *nvm
[07:25] <phoenix_firebrd> shadeslayer: without that debuild gives me error
[07:25] <yofel> re that copyright issue: do the buildlogs have the lintian output in them?
[07:25] <shadeslayer> yofel: I think so
[07:25] <shadeslayer> and I'm thinking the same thing you are
[07:27] <phoenix_firebrd> yofel: i solved the tomboy-blogsposter error
[07:28] <phoenix_firebrd> yofel: but i am not able to put the config  in place
[07:28] <yofel> shadeslayer: good :D - I'll try to write a check for it later
[07:29] <shadeslayer> okay, the buildd's don't have it
[07:30] <shadeslayer> the official ones
[07:31] <Quintasan> ☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭☭
[07:31] <jussi> hah
[07:31] <Quintasan> utf-8 ftw
[07:31] <jussi> good morning ladies and gents
[07:31] <Quintasan> wat
[07:31] <Quintasan> jussi
[07:31] <Quintasan> watwatwat
[07:31] <yofel> shadeslayer: hm, missing DH_VERBOSE?
[07:32] <Quintasan> shadeslayer: look who is here
[07:32] <jussi> Quintasan: which part didnt you understand? :D
[07:32] <shadeslayer> mmm
[07:32]  * jussi hides
[07:32] <yofel> od dh_lintian doesn't do a full check
[07:32] <Quintasan> jussi: I totally failed to comprehend the part where you show up on irc
[07:32] <Quintasan> :P
[07:32] <yofel> *or
[07:32] <yofel> ah, that's something else
[07:33] <shadeslayer> yofel: build logs show dh_lintian being run, but no output
[07:33] <Quintasan> jussi: don't hide on me, go to work!
[07:33] <Quintasan> :P
[07:34] <yofel> shadeslayer: yeah, but that's because it's just for copying the override files
[07:34] <yofel> so that's ok
[07:34] <shadeslayer> hm
[07:35] <shadeslayer> let's wait for kdiamond to build
[07:35] <yofel> http://yofel.dyndns.org/kubuntu/build_status_4.9.98_raring.html - I can't find anything in the logs
[07:37] <shadeslayer> yeah
[07:38] <shadeslayer> gosh, kdeartwork is huge
[07:40] <yofel> you don't say ;P
[07:40] <shadeslayer> hehe
[07:41] <yofel> kde-wallpapers is the new kdeartwork
[07:41] <yofel> and they don't seem to remove stuff from artwork anymore :/
[07:49] <shadeslayer> poor dpkg
[07:49] <shadeslayer> trying to install shank which is a 2GB deb
[07:51] <phoenix_firebrd> shadeslayer:  i can't understand the clauses 9.1.1, 9.1.4, 9.5, 10.7.4, 11.8 in the standards version 3.9.3. I have checked and updated the rest
[07:52] <yofel> note: we don't really care about the policy version usually
[07:53] <phoenix_firebrd> yofel: ok
[07:53] <yofel> the ubuntu-policy is still at 3.8.2, so that's all we really need to comply with
[07:53] <phoenix_firebrd> yofel: ok
[07:53] <yofel> knowing the policy is good though ;)
[07:53] <yofel> as we do try to follow it, we just rarely update that number
[07:54] <phoenix_firebrd> yofel: it seems that the package is upto the standards, sahall i bump the standards version?
[07:54] <shadeslayer> please don't bump standards
[07:54] <shadeslayer> unnecessary diff
[07:54] <shadeslayer> from debian that is
[07:55] <phoenix_firebrd> shadeslayer: why did you ask me to take a look at the lintian error?
[07:55] <shadeslayer> because it needs fixing?
[07:56] <shadeslayer> without bumping the standards version
[07:56] <phoenix_firebrd> shadeslayer: why not?
[07:56] <yofel> ^
[07:56] <shadeslayer> because it makes merging from debian easier
[07:56] <yofel> well, merging 4.10 will be fun anyway - if debian ever gets to package it in time for us
[07:56] <yofel> lag -.-
[07:57] <shadeslayer> why do you want to bump the standards version?
[07:57] <phoenix_firebrd> shadeslayer: ok in that case the package is updated to the new standards and i wont bump the version number so the lintian warning will remain , whats next?
[07:58]  * yofel wonders if importing debian git packaging into bzr and merging that would work
[07:58] <yofel> probably not
[07:58] <shadeslayer> wat
[07:58] <phoenix_firebrd> shadeslayer: next?
[07:58] <yofel> shadeslayer: nvm, me. I haven't had enough coffee yet :P
[08:01] <yofel> shadeslayer: hm, stuck at uploading kdeartwork?
[08:01] <shadeslayer> yofel: heh, yes kdiamond_4.10.0-0ubuntu1\~ubuntu13.04\~ppa1.dsc
[08:01] <shadeslayer> erm
[08:01] <phoenix_firebrd> shadeslayer: after updating the package standards, what should i do?
[08:01] <yofel> heh, ok
[08:01] <shadeslayer> you shouldn't update standards!!
[08:02] <shadeslayer> yofel: http://i.imgur.com/IOF1XRz.png
[08:02] <phoenix_firebrd> shadeslayer: then what should i do with the lintian error?
[08:02] <shadeslayer> phoenix_firebrd: fix it? :P
[08:02] <phoenix_firebrd> shadeslayer: how?
[08:02] <phoenix_firebrd> shadeslayer: "W: kfloppy source: out-of-date-standards-version 3.9.2 (current is 3.9.3)"
[08:02] <phoenix_firebrd> shadeslayer: thats the error
[08:03] <shadeslayer> whut
[08:03] <shadeslayer> not that one
[08:03] <shadeslayer> the other oen
[08:03] <shadeslayer> *one
[08:03] <shadeslayer> E: kfloppy source: malformed-override Override of dbg-package-missing-depends for kdeutils (expecting kfloppy) at line 1
[08:03] <shadeslayer> apparently we were talking about 2 different errors altogether :P
[08:03] <shadeslayer> phoenix_firebrd: you can ignore that warning
[08:04] <phoenix_firebrd> shit
[08:04] <phoenix_firebrd> shadeslayer: i will look at the other one
[08:07] <phoenix_firebrd> shadeslayer: i can see the error that you pointed in the debuild log http://paste.kde.org/661100/
[08:07] <phoenix_firebrd> shadeslayer: *i can't
[08:07] <shadeslayer> O_O
[08:07] <phoenix_firebrd> shadeslayer: version is 4.9.98
[08:08] <phoenix_firebrd> shadeslayer: am i wrong or what?
[08:08] <shadeslayer> lemme check
[08:08] <shadeslayer> yes
[08:09] <phoenix_firebrd> shadeslayer: ??
[08:09] <shadeslayer> http://paste.kde.org/661106/
[08:10] <phoenix_firebrd> shadeslayer: may be this happens with v4.10
[08:10] <phoenix_firebrd> shadeslayer: how can i get the 4.10 tar?
[08:11] <shadeslayer> mmm
[08:11] <shadeslayer> you'll have to request access
[08:11] <phoenix_firebrd> shadeslayer: shall i try with the master?
[08:11] <shadeslayer> no
[08:11] <phoenix_firebrd> shadeslayer: ok
[08:12] <shadeslayer> who has admin access to ninjas?
[08:12] <phoenix_firebrd> yofel:
[08:12] <shadeslayer> Riddell and apachelogger
[08:13] <shadeslayer> phoenix_firebrd: btw can you branch the packaging from bzr and use that?
[08:13] <phoenix_firebrd> shadeslayer: for kfloppy?
[08:13] <shadeslayer> yes
[08:13] <phoenix_firebrd> shadeslayer: ok\
[08:18] <yofel> phoenix_firebrd: about that error, just bzr rm the override file. kfloppy has no dbg package
[08:18] <phoenix_firebrd> yofel: ok
[08:20] <phoenix_firebrd> yofel: when i builddeb kfloppy  am getting this error "apt could not find the needed tarball.
[08:20] <phoenix_firebrd> "
[08:20] <yofel> yeah, because you don't have the 4.10 one :/
[08:21] <yofel> or are you building 4.9.98?
[08:21] <yofel> in that case you would be missing a deb-src line
[08:21] <phoenix_firebrd> yofel: when i bzr branch kfloppy what would i get?
[08:22] <yofel> 4.10, nvm
[08:22] <phoenix_firebrd> yofel: so ?
[08:22] <yofel> wait
[08:22] <phoenix_firebrd> ok
[08:24] <yofel> phoenix_firebrd: pm
[08:25] <shadeslayer> yofel: stuck on uploading kdeartwork :|
[08:25] <shadeslayer>   Uploading kdeartwork_4.10.0.orig.tar.xz: 140132k/140133k
[08:25] <yofel> heh
[08:25] <yofel> o.O
[08:25] <yofel> wait and hope :/
[08:33] <shadeslayer> yeag
[08:37] <shadeslayer> :S
[08:38] <shadeslayer> I'll upload kdeartwork and oxygen separately
[08:45] <phoenix_firebrd> shadeslayer: I am not getting the error that you pointed for kfloppy 4.10 . here is the builddeb log http://paste.kde.org/661184/
[08:45] <soee> good morning
[08:46] <shadeslayer> hm
[08:46] <shadeslayer> lintian too old?
[08:46] <shadeslayer> phoenix_firebrd: what version of lintian are you running?
[08:47] <phoenix_firebrd> shadeslayer: <IP_ADDRESS>
[08:47] <shadeslayer> can you check with 2.5.11?
[08:48]  * yofel as looking at the lintian changelog
[08:48] <yofel> wth is       - license-problem-json-evil
[08:48] <shadeslayer> lol
[08:48] <phoenix_firebrd> shadeslayer: is there a ppa for it?
[08:48] <shadeslayer> hmm
[08:49] <yofel> phoenix_firebrd: try just pulling the deb from raring
[08:49] <shadeslayer> phoenix_firebrd: just grab the lintian deb from raring?
[08:49] <phoenix_firebrd> ok
[08:51] <phoenix_firebrd> shadeslayer: yofel there is no amd64 build
[08:52] <shadeslayer> because it's an arch any package
[08:52] <shadeslayer> or was it arch all
[08:52] <yofel> all
[08:52] <shadeslayer> right
[08:52] <shadeslayer> I get confused easily between those two, always have to look it up
[08:52]  * yofel suggests s/all/indep/ -.-
[08:52] <phoenix_firebrd> shadeslayer: standards 3.9.3 has an update for that
[08:53] <shadeslayer> phoenix_firebrd: update for what?
[08:53] <yofel> then again, all makes some sense syntactically
[08:53] <shadeslayer> right
[08:53] <shadeslayer> yofel: it makes sense if you also know about any
[08:53] <phoenix_firebrd> shadeslayer: directions for using all or any for the arch
[08:53] <shadeslayer> okay, and?
[08:54] <shadeslayer> new symbols in kdelibs? :(
[08:55] <phoenix_firebrd> i am getting that error now
[08:56] <phoenix_firebrd> as yofel said i am going to remove the override files
[08:56] <shadeslayer> wait what
[08:58] <phoenix_firebrd> shadeslayer:  "about that error, just bzr rm the override file. kfloppy has no dbg package"
[08:59] <shadeslayer> I don't see a override file
[08:59] <phoenix_firebrd> shadeslayer: me too
[08:59] <phoenix_firebrd> shadeslayer: i am going to check for the configs
[08:59] <shadeslayer> ahh nvm
[09:00] <shadeslayer> phoenix_firebrd: drop debian/source/lintian-overrides
[09:00] <phoenix_firebrd> right
[09:01] <shadeslayer> who's up for packaging ktp-desktop-applets?
[09:03] <yofel> you :P
[09:03] <phoenix_firebrd> shadeslayer: should i push to my branch and request a merge?
[09:03] <yofel> or phoenix_firebrd
[09:03] <shadeslayer> yep
[09:03] <phoenix_firebrd> shadeslayer: ok
[09:04] <phoenix_firebrd> yofel: sure
[09:04] <shadeslayer> I'm working on kde bits today
[09:04] <yofel> phoenix_firebrd: just push to your branch and post the branch URL
[09:04] <shadeslayer> the sc bits
[09:04] <phoenix_firebrd> yofel: ya, just now i did for kdiamond
[09:05] <yofel> merge requests are just too much paperwork if we're already on IRC
[09:06] <shadeslayer> heh
[09:06] <shadeslayer> sometimes it's good to know the paperwork works ;)
[09:06] <phoenix_firebrd> yofel: i am following what you taught me
[09:06] <yofel> yeah, I did teach him how to do it
[09:07] <yofel> phoenix_firebrd: sure, but it's not really needed if we're already talking here. Merge requests make sense for complex reviews and when the reviewer isn't at hand
[09:08] <yofel> wth
[09:09] <phoenix_firebrd> yofel: ok. here is the link https://code.launchpad.net/~murthy/kubuntu-packaging/kfloppy-4.10.0
[09:09] <yofel> "Not attempting to fix packaging branch ancestry, missing pristine tar data for version 4.9.98."
[09:09] <phoenix_firebrd> whats that error?
[09:09] <yofel> no idea, first time I see it
[09:10] <phoenix_firebrd> yofel: which package?
[09:10] <yofel> phoenix_firebrd: http://paste.kde.org/661196
[09:10] <yofel> a) please don't add empty changelog entries
[09:11] <phoenix_firebrd> omg
[09:11] <yofel> b) that doesn't look like the right fix
[09:11] <phoenix_firebrd> my head is getting heated
[09:11] <yofel> lol, calm down, no harm done
[09:11] <yofel> that's why we're doing the reviews
[09:12] <yofel> I think the problem here is that there's a missing empty line missing between the 2 copyright sections
[09:12] <yofel> s/missing//
[09:12] <kubotu> yofel meant: "I think the problem here is that there's a  empty line missing between the 2 copyright sections"
[09:12] <yofel> that's invalid syntax
[09:13] <yofel> see http://dep.debian.net/deps/dep5/
[09:13] <phoenix_firebrd> whom should i follow you or shadeslayer
[09:13]  * yofel reads backlog
[09:14] <yofel> he didn't tell you *how* to fix it
[09:14] <yofel> and you didn't fix it right
[09:14] <phoenix_firebrd> yofel: i uploaded with a changelog, asked me to remove it
[09:14] <yofel> the reason lintian complains about a duplicate field, is because each chunk in the copyright file is seperated by an empty line
[09:15] <yofel> as the line is missing both license declarations belong to the same paragraph, which is invalid
[09:15] <phoenix_firebrd> yofel: thats ok
[09:15] <yofel> phoenix_firebrd: hm, the changelog was still there though
[09:15] <yofel> did you forget to push maybe?
[09:16] <phoenix_firebrd> yofel: should i meantion the copyright file change in the changelog?
[09:16] <yofel> probably not worth it
[09:17] <phoenix_firebrd> yofel: so  i don't have to update the change log now right?
[09:17] <yofel> or it would be an entry like "* Fix <lintian_error_name>"
[09:17] <yofel> phoenix_firebrd: this is really all that should be needed for kdiamond: http://paste.kde.org/661202
[09:17] <phoenix_firebrd> i will be back in 2 mins
[09:21] <phoenix_firebrd> yofel: i am back
[09:21] <phoenix_firebrd> yofel: can we take this step by step
[09:23] <yofel> hm, kfloppy:
[09:23] <yofel> - -- Rohan Garg<EMAIL_ADDRESS>Thu, 31 Jan 2013 11:18:16 +0530
[09:23] <yofel> + -- Prasad Murthy<EMAIL_ADDRESS>Thu, 31 Jan 2013 11:18:16 +0530
[09:24] <yofel> you changed the dch behaviour? (just curious)
[09:24] <phoenix_firebrd> yofel: ya
[09:24] <phoenix_firebrd> yofel: so that debuild will sign
[09:24] <yofel> aaaaah
[09:24] <yofel> wait, I have a workaround for that
[09:25] <phoenix_firebrd> yofel: -us -uc?
[09:25] <yofel> no
[09:25] <yofel> in ~/.devscripts put: DEBSIGN_KEYID=2EC0A9FF, except with your keyid instead of mine
[09:25] <yofel> that'll force it to use your key and ignore the changelog entry
[09:26] <phoenix_firebrd> yofel: ok
[09:26] <yofel> it's meant as a kind of safety measure, as you can always -us -uc and run debsing after that
[09:26] <yofel> but I find it mostly annoying
[09:27] <yofel> but back to the review: please don't *commit* such a change, as it's just unnecessary noise when reviewing
[09:27] <yofel> it's not wrong, and once you have commit permissions feel free to commit that, but for reviews it's just noise
[09:28] <phoenix_firebrd> yofel: ok
[09:28] <shadeslayer> heh
[09:29] <shadeslayer> I just aliased debsign to debsign -kkey
[09:29] <yofel> well, that works too
[09:29] <phoenix_firebrd> shadeslayer: can you give me the syntax?
[09:30] <shadeslayer> phoenix_firebrd: I put alias debsign='debsign -kF2672094' in my zshrc
[09:30]  * shadeslayer rages at dput
[09:32] <phoenix_firebrd> yofel: i have updated the ~/.devscripts , now going to look at the copyright file
[09:37] <yofel> phoenix_firebrd: about the copyright file: a dep5 copyright file has roughly the same syntax as a control file regarding spaces and empty lines
[09:37] <yofel> the current one violates that
[09:37] <phoenix_firebrd> yofel: i can see that its missing an empty line
[09:37] <yofel> exactly
[09:38] <phoenix_firebrd> yofel: but it says it detects duplicate field?
[09:38] <yofel> yeah, because the current paragraph has 2 License: fields (thanks to the missing line)
[09:38] <phoenix_firebrd> yofel: oh
[09:38] <phoenix_firebrd> yofel: ok i will update and upload
[09:39] <yofel> those are 2 paragraphs glued together causing a double definition
[09:39] <phoenix_firebrd> yofel: ok
[09:49] <Riddell> morning
[09:49] <phoenix_firebrd> Riddell: MORNING
[09:50] <phoenix_firebrd> oops
[09:50] <apachelogger> yo Riddell
[09:50] <yofel> moin
[09:50] <apachelogger> still needs a review: https://launchpad.net/~apachelogger/+archive/ppa/+files/mangonel_0.1~git20130130-0ubuntu1.dsc
[09:50]  * apachelogger pokes shadeslayer
[09:50] <Riddell> ooh 142 new tars
[09:51] <Riddell> sheytan: you're onto them?
[09:51] <shadeslayer> if you meant me, then yes
[09:51] <shadeslayer> almost done
[09:51] <Riddell> tab completion fail
[09:52] <shadeslayer> still need to upload kdeplasma-addons, oxygen-icons, kde-wallpapers, and kdeartwork
[09:55] <Riddell> shadeslayer: you've got the bandwidth for that?
[09:55] <shadeslayer> I don't think so :P
[09:55] <shadeslayer> you're welcome to take over those 4 if you want
[09:56] <shadeslayer> kdeplasma-addons need fixing in bzr firsst
[09:56] <sheytan> Riddell on what?
[09:58] <phoenix_firebrd> yofel: https://code.launchpad.net/~murthy/kubuntu-packaging/kdiamond-4.10.0
[09:59] <Riddell> sheytan: sorry I ment shadeslayer
[10:00] <Riddell> shadeslayer: ok I'll get onto them
[10:01] <Riddell> phoenix_firebrd: thanks, merging that in
[10:01] <phoenix_firebrd> Riddell: ty
[10:01] <shadeslayer> new kdepim tarball as well btw
[10:02] <yofel> shadeslayer: I'm on that
[10:02] <shadeslayer> awesome
[10:02] <shadeslayer> I'll step out for a bit then
[10:05] <sheytan> no problem. Happens to few ppl :D
[10:05] <yofel> shadeslayer: when are you going to upload the rest?
[10:05] <yofel> https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+packages?field.series_filter=raring&batch=200 shows plenty as missing
[10:05] <shadeslayer> yofel: already being uploaded
[10:06] <yofel> ah ok then
[10:06] <shadeslayer> it's uploading kstars at the moment
[10:06] <yofel> most of that'll be fast, I mostly want the libs up
[10:07] <shadeslayer> yep
[10:08] <shadeslayer> it's weird though, I've been throttled to about 512Kbps for uploads
[10:14] <Riddell> you should have asked for an ec2
[10:17]  * yofel wipes the old precise packages from ninjas to free some space up
[10:21] <shadeslayer> Riddell: too much of a hassle to setup and then everything downloaded at a good rate of 2 Mbps
[10:23] <apachelogger> make it a charm
[10:23] <apachelogger> \o/
[10:23]  * apachelogger is using words he does not understand now
[10:23] <shadeslayer> heh
[10:23] <Riddell> actually I went to the cloud dev room at the last uds and tried to do that and it wasn't possible
[10:23] <Riddell> seems copying a gpg key to a ec2 is too complex or something
[10:24] <shadeslayer> 0.o
[10:24] <shadeslayer> you're kidding right?
[10:24] <apachelogger> eh
[10:24] <apachelogger> Riddell: remotesign
[10:24] <apachelogger> also I doubt the key is the only thing you need
[10:24] <Riddell> yeah we got stuck in a few places
[10:25] <Riddell> juju is surprisingly complex just to do what a simple bash script can easily do
[10:25] <apachelogger> well
[10:25] <apachelogger> formalizing always comes at a price ^^
[10:26] <Riddell> yes and there will be reasons for that complexity, it's just a shame that it's complex even for a juju developer
[10:36] <shadeslayer> ok everything is up
[10:38] <Riddell> what to do about l10n?
[10:39] <Riddell> just throw it up on release day? or faff around with putting in a PPA and probably running out of space
[10:39] <shadeslayer> just throw it up on release day, fix as needed
[11:12] <yofel> vHanda: nepomuk-core commit c65f9cad breaks ABI of libnepomukcore4: http://paste.kde.org/661316
[11:13]  * yofel -> lunch
[11:20] <BluesKaj> Hiyas all
[11:23] <phoenix_firebrd> BluesKaj: hi
[11:24] <BluesKaj> hi phoenix_firebrd
[11:29] <Riddell> shadeslayer: hmm you probably did sensible, uploading from an ec2 to launchpad seems to be uber slow
[11:30] <shadeslayer> heh
[11:30] <shadeslayer> use my server?
[11:35] <yofel> you could've used mine...
[11:36] <yofel> then again, that was starved for bandwidth too earlier
[11:39] <phoenix_firebrd> yofel: tomboy-blogposter builds
[11:47] <vHanda> yofel: Removing a private function breaks ABI?
[11:47] <vHanda> are you sure?
[11:48] <yofel> is that Private?
[11:48] <yofel> if it is then nevermind, but it doesn't obviously look private to me
[11:50] <apachelogger> vHanda: removing a private function always breaks ABI
[11:50] <apachelogger> the impact of it depends on other factors though (for example whether the class/function is virtual)
[11:51] <Riddell> you can "remove private non-virtual functions if they are not called by any inline functions (and have never been). " says http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++
[11:52] <Riddell> that one is a "private Q_SLOTS:"
[11:52] <Riddell> so that's fine I think
[11:52] <apachelogger> it still breaks the ABI, it is however a binary compatible change
[11:53] <Riddell> is it ABI if it's a bit of the interface you can't use?
[11:53] <apachelogger> (the restrictedness of when it is a ok to remove a private is why one should generally avoid having privates)
[11:53] <apachelogger> Riddell: you can use it
[11:55] <apachelogger> ABI is really no philosophical topic :)
[11:55] <Riddell> hmm
[11:55] <apachelogger> BC is to some extent ^^
[11:55] <Riddell> anyway yofel you'll handle that?
[11:55] <apachelogger> Riddell: on the library level there is no difference between private and public
[11:55] <apachelogger> so I could link to the privates all the same
[11:56] <Riddell> '#define private public' is evil!
[11:56] <yofel> yeah, as soon as apachelogger is finished explaining...
[11:56] <apachelogger> actually let me speed this up
[11:56] <vHanda> yofel: Do you want me to add the private slot again?
[11:56] <apachelogger> whenever a binary interface disappears the change breaks ABI :P
[11:56] <apachelogger> whether that binary interface was from a private or not does not matter in that regard

[11:57] <Riddell> vHanda: no it's fine
[11:57] <vHanda> yofel: I'll have to run it by the release team
[11:57] <vHanda> oh
[11:57] <Riddell> apachelogger is just confusing matters!
[11:58] <yofel> ok, he did manage to confuse me at least
[11:58] <shadeslayer> apachelogger: how so? aren't privates not supposed to be exposed in the symbols file?
[11:58] <Riddell> yes the symbol has gone, no nothing uses it, so there's no problem
[11:58] <apachelogger> :(
[11:58] <apachelogger> Riddell: it's a library
[11:58] <apachelogger> the statement nothing uses it is simply wrong
[11:58] <yofel> so what would use it?
[11:58] <apachelogger> anything can use it so we must assume something uses it
[11:58] <yofel> outside of the library
[11:58] <shadeslayer> but if it's private, how can something use it?
[11:59] <apachelogger> shadeslayer: #define private public
[11:59] <apachelogger> #include <yourlib.h>
[11:59] <shadeslayer> bah
[11:59] <shadeslayer> if you do that
[11:59] <shadeslayer> then that
[11:59] <apachelogger> Foo foo; foo.yourprivates();
[11:59] <shadeslayer> then that's just shit
[11:59] <shadeslayer> and evil
[11:59] <vHanda> apachelogger: That's a neat trick. I didn't know you could do that!
[11:59] <yofel> I'm fairly certain we don't support *that*
[11:59] <apachelogger> it does not matter!
[11:59] <apachelogger> when talking about ABI any time you retract an interface it is breaking ABI
[12:00] <apachelogger> when talking about BC if you decided to link against a private then that is your fault
[12:00] <Riddell> vHanda: now you're just winding us up!
[12:00] <yofel> I think we can conclude that this is BC and go on with our lives
[12:00] <Riddell> yofel++
[12:01] <shadeslayer> *nod*
[12:01] <yofel> vHanda: so, sorry for the more or less false alarm
[12:01] <vHanda> uhm, okay. I'm still preparing a patch just in case someone else objects.
[12:02] <vHanda> The tarballs aren't going to get re-spun until monday
[12:02] <vHanda> so we have till then to decide if this should be fixed.
[12:03] <vHanda> http://paste.kde.org/661370
[12:04] <apachelogger> vHanda: btw, not sure if kde wants to use it but there is Q_PRIVATE_SLOT
[12:06] <apachelogger> it allows you to pass the slot call to the d ptr
[12:06] <apachelogger> and it expands to nothing in c++ so you end up having no symbol for the slot as the slot is entirely handled via the qmetaobject
[12:08] <Riddell> useful note: ec2's in ireland upload to launchpad much faster than those in the US
[12:19] <shadeslayer> Riddell: isn't LP based out of the UK
[12:19] <shadeslayer> like, hosted somewhere in the UK
[12:19] <Riddell> yes, london
[12:20] <Riddell> I remember persia saying he would never use UDD because bzr takes many days to do a checkout from launchpad
[12:20] <Riddell> for him in japan
[12:21] <Riddell> however ec2s are more expensive in ireland, despite being in a tax haven
[12:22]  * yofel times checking out kde-worspace just for fun
[12:24] <yofel> hm, ~70MB in about a minute, not as bad as I feared
[12:42] <Riddell> bah my addition of QextSerialPort to marble didn't get pushed
[12:44] <Riddell> ah yofel is on the case, good good
[12:51] <phoenix_firebrd> bbl
[12:54] <smartboyhw> Good evening
[12:54] <Riddell> hi smartboyhw
[12:54] <smartboyhw> Hi Riddell
[12:54] <Riddell> 4.10.0 being packaged
[12:54] <Riddell> http://notes.kde.org/kubuntu-ninjas
[12:55] <smartboyhw> Riddell, that is good:)
[12:55] <shadeslayer> Riddell: hm, odd, I thought S3 was *cheaper* in Ireland
[12:55] <shadeslayer> which was one of the reasons we chose the instance to be in Ireland
[12:56] <shadeslayer> as for bzr, it's painfully slow :(
[12:57] <yofel> weird bug of the day: bug 1111364
[12:57] <yofel> quantal-only
[12:58] <smartboyhw> Riddell, you want me to update ktorrent? new version out (4.3.1)
[12:58] <yofel> then there is bug 1107692 which is quantal-only too, happens only with the digikam-rc and I don't get what the issue is
[12:58] <Riddell> smartboyhw: yes please
[12:58] <smartboyhw> Riddell, well request sync bug then:p
[12:58] <yofel> don't forget about libktorrent
[12:59] <smartboyhw> Don't know that it is maintained by Debian side
[12:59] <yofel>  libktorrent | 1.3.1-1         | experimental      | source
[12:59] <BluesKaj> system settings crashes when opening user management
[12:59] <smartboyhw> How do you request syncs?
[12:59] <yofel> BluesKaj: still?
[12:59] <yofel> BluesKaj: and with what backtrace?
[13:00] <yofel> (I'm not surprised that it doesn't work, but it shouldn't *crash*)
[13:01] <BluesKaj> ok yofel . I was mistaken , noe I get the "orphaned module " message
[13:01] <BluesKaj> now
[13:01] <yofel> ah ok, then it crashed once to reload the lib
[13:01] <smartboyhw> Riddell, I think it will be up to the sponsors to do the actual syncing of ktorrent....So probably it will be difficult for me to do it
[13:03] <BluesKaj> well , yofel I still don't have access
[13:04] <yofel> BluesKaj: that's because the userconfig module doesn't work with python3.
[13:04] <yofel> that'll be the next thing to do
[13:04] <BluesKaj> ok , thanks yofel
[13:05] <yofel> which reminds me...
[13:06] <Riddell> smartboyhw: I can do that if you file the bugs
[13:06] <smartboyhw> Riddell, ok:)
[13:14] <yofel> ScottK: any ideas about this: http://paste.kde.org/661502 - that's caused by ki18n() when using python3
[13:16] <yofel> ki18n("Sebastian Kügler".encode('utf-8')) works, but we can hardly do that for all utf-8 strings
[13:18] <smartboyhw> Riddell, can't seem to find whether ktorrent is in Debian experimental main or non-free or anything else....
[13:19] <yofel> smartboyhw: it's in experimental http://paste.kde.org/661580
[13:19] <smartboyhw> yofel, experimental I know, but is it main or non-free?
[13:20] <Riddell> smartboyhw: packages.debian.org is your friend
[13:20] <smartboyhw> The Sync wiki page says I need to include that...
[13:20] <smartboyhw> Riddell, searching through packages.debian.org and I still can't find it...
[13:20] <Riddell> if it doesn't say anything it'll be in main
[13:20] <smartboyhw> Riddell, main then
[13:23] <yofel> ScottK: note that the utf-8 issue above is python3.2, I'll try it later with 3.3
[13:23] <smartboyhw> Riddell, Bug 1111452
[13:36] <smartboyhw> Riddell, bug 1111458
[13:45] <ScottK> yofel: That might be different in 3.3.
[13:48] <Riddell> ScottK: bug 1066225 refixed
[13:48] <ScottK> Riddell: Excellent.  Thanks.
[13:53] <smartboyhw> Riddell, so nothing for me to "play" with now?
[13:54] <Riddell> smartboyhw: check what needs done on 4.10 http://yofel.dyndns.org/kubuntu/build_status_4.10.0_raring.html
[13:54] <smartboyhw> Riddell, I do see some build failures...
[13:54] <smartboyhw> No access to build logs though...
[13:54] <yofel> those should just be archive skew I belive (libkdeedu related)
[13:56] <Riddell> smartboyhw: oh I'll put you in the team
[13:56] <smartboyhw> Riddell, ooh?
[13:57] <Riddell> we're not precious about it :)   it's only hidden because upstream wants it hidden until release
[13:57] <yofel> Riddell: mind adding phonix_firebird too unless you think he needs more time? I'll tell him what not to do later then
[13:57] <Riddell> yofel: what's his username?
[13:57] <yofel> ~murthy
[13:58] <smartboyhw> Riddell, ok
[13:58] <smartboyhw> thx
[13:58] <Riddell> voila
[13:58] <yofel> thanks :)
[13:58] <smartboyhw> libkmajjongglib-dev failed...
[13:59] <yofel> archive skew, just retry the build
[13:59] <yofel> hm, having a link to the build from the status page would be nice...
[14:01] <smartboyhw> Weird, why is ksnakeduel i386 showing a failure, when the logs said it is perfectly built?
[14:02] <yofel> smartboyhw: list-missing should be empty
[14:02] <yofel> but in this case the output looks weird
[14:02] <smartboyhw> Lots of .png and .desktop files
[14:03] <yofel> wth
[14:04] <yofel> ah no, makes sense
[14:04] <yofel> smartboyhw: a transitional package was added which is only built on i386 as it's arch "all", but nobody added an install file for ksnakeduel
[14:05] <smartboyhw> yofel, oh should I add one?
[14:05] <yofel> so the package needs ksnakeduel.install with "usr/*" in it
[14:05] <yofel> smartboyhw: yeah, but please do so in bzr as well
[14:05] <smartboyhw> yofel, OK
[14:06] <smartboyhw> yofel, where is the branch?
[14:06] <yofel> smartboyhw: usually it's best to add it in bzr and generate the package from there
[14:06] <yofel> smartboyhw: do you have kubuntu-dev-tools installed?
[14:06] <yofel> then it's just 'kbzr co ksnakeduel"
[14:06]  * smartboyhw finds himself a total idiot today
[14:07] <yofel> hey, everyone was new at some point ;P
[14:09] <yofel> *sigh*
[14:09]  * yofel goes fixing kolabxml properly
[14:09] <smartboyhw> Why I couldn't install the ppa for kubuntu-dev-tools?
[14:10] <smartboyhw> Cannot access PPA (https://launchpad.net/api/1.0/~bulldog98/+archive/kubuntu-dev-tool) to get PPA information, please check your internet connection.
[14:10] <smartboyhw> *sigh* use the manual method then
[14:13] <yofel> that's weird o.O
[14:14] <smartboyhw> yofel, anyway got it now, syncing
[14:20] <smartboyhw> yofel, added. Which place should I upload the branch to?
[14:21] <yofel> if you're not a kubuntu-member yet, put it in lp:~<your_id>/kubuntu-packaging/ksnakeduel-4.10 or so
[14:21] <yofel> then give me the url
[14:22] <smartboyhw> yofel, error
[14:22] <smartboyhw> bzr: ERROR: Cannot lock LockDir(chroot-75337488:///~kubuntu-packagers/kubuntu-packaging/ksnakeduel/.bzr/branch/lock): Transport operation not possible: readonly transport
[14:23] <smartboyhw> !?
[14:23] <yofel> ah, run 'bzr unbind' first. Checkout binds commit to the original launchpad location
[14:24] <yofel> forgot about that. Next time use 'kbzr branch <pkg>'
[14:24] <smartboyhw> OK
[14:24] <yofel> either that ^ or launchpad doesn't know you or your ssh key
[14:25] <smartboyhw> yofel, https://code.launchpad.net/~smartboyhw/kubuntu-packaging/ksnakeduel-4.10/
[14:26] <yofel> smartboyhw: please add something to the changelog too, just run 'dch' in the branch dir and it'll add you to the current entry
[14:27] <yofel> smartboyhw: ah wait
[14:27] <smartboyhw> !?
[14:27] <smartboyhw> Almost added it:P
[14:27] <yofel> nevermind, the entry is already there (see 4.9.98), Riddell just didn't actually add the file to bzr...
[14:28] <smartboyhw> yofel, :O
[14:28] <yofel> well, happens
[14:29] <yofel> merged
[14:29] <smartboyhw> yofel, thx
[14:29] <yofel> smartboyhw: now update the packagin in the PPA so it gets a clean status
[14:29] <yofel> *package
[14:30] <smartboyhw> yofel, so I bzr builddeb -S and upload it to PPA?
[14:30] <smartboyhw> Or anything?
[14:30] <yofel> first add ~ubuntu13.04~ppa2 to the version, change UNRELEASED to raring, then upload after bzr builddeb -S -- -sd
[14:30] <yofel> but don't commit those changes
[14:31] <smartboyhw> yofel: OK
[14:34] <smartboyhw> yofel, when you mean commit you mean locally?
[14:34] <yofel> yeah, bzr builddeb will use uncomitted changes
[14:35] <yofel> ok, with new libkolabxml kdepim-runtime will only need a simple retry in a bit
[14:36] <smartboyhw> yofel, http://paste.ubuntu.com/1593234/
[14:38] <yofel> aaah
[14:38] <yofel> ok
[14:38] <yofel> give me a minute
[14:38] <yofel> you need a deb-src line for the PPA
[14:38] <smartboyhw> yofel, I have
[14:38] <smartboyhw> yofel, you mean for the ninja ppa?
[14:39] <yofel> right
[14:39] <smartboyhw> k
[14:40] <yofel> smartboyhw: go to your launchpad page, click on "View your private PPA subscriptions", there beside ninjas, click on view
[14:40] <yofel> that will have the apt lines with your PPA password
[14:40] <smartboyhw> yofel, thanks
[14:41] <yofel> install apt-transport-https before adding that
[14:41] <yofel> after that apt-get update and bzr will be happy
[14:47] <yofel> oh, it's almost dev week time
[14:47] <yofel> shadeslayer: ^
[14:47] <shadeslayer> ah thanks for reminding me
[14:50] <smartboyhw> yofel, uploaded to PPA
[14:50] <yofel> \o/
[14:50] <smartboyhw> \o/
[14:57] <shadeslayer> yofel: iirc they had automated testing sessions at UDS
[14:57] <shadeslayer> UTAH or sth like that
[14:57] <yofel> ah, all I remember is that they have a jenkins instance for some things
[14:57] <shadeslayer> Canonical also has an automated testing lab
[14:58] <shadeslayer> thought that's mostly private afaik
[15:20]  * yofel grumbles something about chroot problems
[15:20] <yofel> hi phoenix_firebrd
[15:21] <phoenix_firebrd> yofel: HI
[15:21] <phoenix_firebrd> oops
[15:21] <phoenix_firebrd> capslock is on
[15:21] <yofel> phoenix_firebrd: you got promoted while you were away: https://launchpad.net/~kubuntu-ninjas/+archive/ppa
[15:21] <phoenix_firebrd> nice
[15:21] <phoenix_firebrd> thank you very much
[15:22] <yofel> so now you can actually see https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+packages?field.series_filter=raring&batch=200
[15:22] <yofel> and open the build logs on http://yofel.dyndns.org/kubuntu/build_status_4.10.0_raring.html
[15:22] <phoenix_firebrd> checking
[15:22] <shadeslayer> only with FF though
[15:23] <yofel> lol
[15:23] <shadeslayer> with chrom{e,ium} you can't open the build logs
[15:23] <phoenix_firebrd> why so?
[15:23] <shadeslayer> I have FF installed just so that I can look at the build logs
[15:23] <shadeslayer> bug in LP / Chrome
[15:23] <shadeslayer> not sure which
[15:23] <yofel> smartboyhw, phoenix_firebrd: one thing about ~kubuntu-ninjas membership: it also grants you upload rights to kubuntu-ppa/*, please be careful there
[15:23] <phoenix_firebrd> omg
[15:23] <phoenix_firebrd> sure
[15:24] <phoenix_firebrd> do i get a email id too?
[15:24] <yofel> no, that's for kubuntu members
[15:24] <phoenix_firebrd> ok
[15:25] <phoenix_firebrd> yofel: i not touch the kubuntu-ppa until you find me fit
[15:25] <phoenix_firebrd> yofel: *i will not
[15:25] <shadeslayer> yofel: question time btw
[15:26] <phoenix_firebrd> yofel: are you free now?
[15:26] <phoenix_firebrd> shadeslayer: what time do you go to bed?
[15:26] <yofel> not too much, but a quick question's ok
[15:26] <Riddell> phoenix_firebrd: I don't think shadeslayer goes to bed
[15:26] <smartboyhw> yofel, ok
[15:26] <shadeslayer> :P
[15:26] <phoenix_firebrd> wow
[15:27] <phoenix_firebrd> shadeslayer: so thats why the nick?
[15:27] <shadeslayer> it's quite random actually, anything between 10 PM to 5 AM
[15:27] <phoenix_firebrd> shadeslayer: my sleep cycle was like yours 1 month before, just had it reset
[15:27] <shadeslayer> heh
[15:28] <Riddell> + [laney] get maliit in the archive: DONE
[15:28] <Riddell> ooh, well done Quintasan
[15:28] <shadeslayer> my sleep cycle changes every 2 weeks
[15:28] <yofel> what
[15:28] <yofel> \o/
[15:28] <yofel> Quintasan++
[15:28] <shadeslayer> nice :)
[15:28] <Riddell> very generous of Quintasan to let laney take all the credit
[15:28] <shadeslayer> so now we have a keyboard , but no declarative-plasmoids
[15:29] <phoenix_firebrd> yofel: i was observing the actives in this channel from the morning, I can't figure out the procedure of tagging
[15:29] <yofel> phoenix_firebrd: tagging is meant as "create git tags in KDE svn/git and spin tarballs from that"
[15:29] <phoenix_firebrd> shadeslayer: mine shifts 1 hr everyday, delayed sleep syndrome
[15:29]  * shadeslayer looks that up
[15:30] <yofel> phoenix_firebrd: the kde-release-team folks do that, we just get the tars after that
[15:30] <phoenix_firebrd> yofel: ya, thats right
[15:31] <phoenix_firebrd> yofel: so did the tars are available for packaging?
[15:31] <yofel> phoenix_firebrd: the 4.10.0 release is a week away, till then the release team may re-spin some tarballs if some bugfixes need to get in
[15:31] <yofel> pretty much
[15:31] <phoenix_firebrd> yofel: ok
[15:31] <yofel> actually, kdepim got recreated today for that reaosn
[15:31] <yofel> *reason
[15:31] <phoenix_firebrd> yofel: the argument about the ABI?
[15:31] <yofel> that's why you'll find kdepim 4.10.0a in the ppa as that's the only way for us to update it
[15:32] <yofel> no, that was something different
[15:32] <phoenix_firebrd> yofel: if i am not mistaken the pim stuff is always problematic?
[15:33] <shadeslayer> heh no
[15:33] <yofel> well, a bit
[15:33] <yofel> shadeslayer: seems we disagree :P
[15:33] <shadeslayer> depends on what you call problematic :P
[15:33] <yofel> but maybe i just have a trauma from uploading kdepim 4.7
[15:33] <shadeslayer> I call it unusable xD
[15:33] <yofel> lol
[15:33] <phoenix_firebrd> yofel: i mostly see a known issue that saying about pim stuff
[15:33] <shadeslayer> I simply cannot import all of my email into KMail
[15:33] <yofel> well, it's not that bad, it just doesn't scale
[15:34] <shadeslayer> right, it doesn't scale
[15:34] <shadeslayer> it'll just take a batshit amount of time to import my email
[15:34] <yofel> phoenix_firebrd: with respinning tars I mean this btw. http://mail.kde.org/pipermail/release-team/2013-January/006809.html
[15:34] <phoenix_firebrd> shadeslayer: i like kdepim
[15:34] <yofel> oh right, talking about mailing lists
[15:35] <phoenix_firebrd> shadeslayer: my first patch was for akonadi backup
[15:35] <yofel> there's 2 that are relevant here<EMAIL_ADDRESS>which is mostly not interesting for us, but public. Then there's<EMAIL_ADDRESS>which is relevant to us but private to packagers
[15:35] <yofel> we need to get you added to the 2nd one eventually
[15:35] <yofel> same with smartboyhw
[15:35] <shadeslayer> actually the release team does get cc'd for the tars right?
[15:36] <shadeslayer> kde-packagers is mostly irrelevant from what I gathered at Akademy
[15:36] <yofel> yeah, tsdgeos always sends the mails to packager, release-team, and qa
[15:36] <yofel> it does feel a bit deprecated lately...
[15:36] <shadeslayer> it does have the odd interesting discussion ;)
[15:36] <shadeslayer> s/odd/occassional/
[15:36] <phoenix_firebrd> yofel:should i join this now<EMAIL_ADDRESS>[15:37] <kubotu> shadeslayer meant: "it does have the occassional interesting discussion ;)"
[15:37] <shadeslayer> phoenix_firebrd: you'll have to open a sysadmin bug report
[15:37] <shadeslayer> and ask Riddell to ack it
[15:37] <phoenix_firebrd> shadeslayer: am i qualified?
[15:38] <shadeslayer> qualified for what? reading emails? idk you tell me :D
[15:38] <yofel> release-team has more fun discussions lately
[15:38] <yofel> http://mail.kde.org/pipermail/release-team/2013-January/date.html
[15:38] <phoenix_firebrd> :D
[15:39] <phoenix_firebrd> so which one should i join now?
[15:39] <shadeslayer> both
[15:39] <phoenix_firebrd> yofel: I have successfully built the tomboy-blogposter, can you check my build log?
[15:39] <yofel> then release-team will be enough for now
[15:40] <phoenix_firebrd> yofel: ok
[15:40] <yofel> bug Riddell about packagers sometime
[15:40] <yofel> phoenix_firebrd: as I said, I don't know enough about mono packages to QA that
[15:40] <shadeslayer> #ubuntu-motu
[15:41] <shadeslayer> that channel probably has mono ninjas lurking in every corner
[15:41] <phoenix_firebrd> yofel: no just the common errors
[15:41] <yofel> not now then, maybe I'll have some time later
[15:42] <phoenix_firebrd> shadeslayer: its just that i am not confident enough to assume that i have suceeded in building this
[15:42] <phoenix_firebrd> yofel: thats ok
[15:42] <phoenix_firebrd> yofel: if its not a problem can i put it in my ppa?
[15:43] <shadeslayer> well
[15:43] <shadeslayer> there's #ubuntu-packaging
[15:43] <phoenix_firebrd> what for?
[15:43] <yofel> phoenix_firebrd: sure, but if you already want a review you might as well get someone competent to do it
[15:43] <shadeslayer> it's a channel specifically for people starting out with packaging
[15:44] <yofel> s/starting out//
[15:44] <kubotu> yofel: You did something wrong... Try s/you/me/ or tell me "help sed"
[15:44] <smartboyhw> yofel, oh what did I miss?
[15:44] <shadeslayer> yofel: people with packaging? :D
[15:44] <phoenix_firebrd> yofel: more like a patient one
[15:44] <yofel> err... yeah :D
[15:45] <yofel> smartboyhw: the mailing lists you might care about if you plan to work on kde sc releases
[15:45] <smartboyhw> yofel, ok
[15:47] <phoenix_firebrd> yofel:  shadeslayer . tomboy-blogposter log http://paste.kde.org/661886/
[15:48] <phoenix_firebrd> "Compilation succeeded - 2 warning(s)" does that mean i have a binary?
[15:48] <shadeslayer> looks fine
[15:48] <phoenix_firebrd> shadeslayer:  wow
[15:48] <shadeslayer> but don't take my word for it
[15:49] <yofel> the build worked, whether the package works I don't know
[15:49] <shadeslayer> that ^
[15:49]  * yofel broke libkolabxml
[15:49] <yofel> bah
[15:49] <phoenix_firebrd> shadeslayer: i have been repeatedly bulding this from 2 days, atleast it build now, i will check it deeply further
[15:50] <shadeslayer> kewl
[15:50] <phoenix_firebrd> yofel: what did you do?
[15:50] <phoenix_firebrd> shadeslayer: kewl , the hindi word?
[15:50] <yofel> I made it libkolabxml-dev depend on the libs that its cmake config file wants. But libcurl4 has more than just the gnutls variant
[15:51] <yofel> which causes conflicts
[15:51] <shadeslayer> kewl is a hindi word? drat
[15:51] <yofel> phoenix_firebrd: causing https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+build/4261395/+files/buildlog_ubuntu-raring-i386.kdepim-runtime_4%3A4.10.0-0ubuntu1%7Eubuntu13.04%7Eppa1_FAILEDTOBUILD.txt.gz
[15:51] <shadeslayer> I need to stop using that word, urban dictionary has a definition for it :|
[15:52] <shadeslayer> ... and it's not pretty
[15:52] <phoenix_firebrd> yofel: getting a 404
[15:52] <yofel> then you don't use firefox :D
[15:52] <phoenix_firebrd> yofel: chromium
[15:52] <yofel> https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+build/4261394
[15:52] <phoenix_firebrd> yofel: let me check with ff
[15:53] <shadeslayer> like I said
[15:53]  * yofel uploaded a fix in the meantime
[15:53] <shadeslayer> everything except rekonq and FF fails
[15:53] <phoenix_firebrd> shadeslayer: ha ha ha
[15:53] <phoenix_firebrd> shadeslayer: the urban dictionary
[15:54] <shadeslayer> :P
[15:54] <smartboyhw> yofel, suscribed to release-team
[15:54] <smartboyhw> good night everyone!
[15:58] <phoenix_firebrd> going to register for the mailing list
[16:00] <phoenix_firebrd> yofel:  this one<EMAIL_ADDRESS>or this one<EMAIL_ADDRESS>?
[16:01] <phoenix_firebrd> I saw Riddell uds 2012 interview and i am very inspired
[16:02] <yofel> well, both
[16:02] <yofel> packagers would be enough for your purposes I guess
[16:02] <phoenix_firebrd> yofel: ok
[16:02] <shadeslayer> for the former you need to open a sysadmin bug report
[16:03] <yofel> but some people don't make a distinction there
[16:03] <shadeslayer> and ask Riddell to vet it
[16:04] <Riddell> phoenix_firebrd: ooh where is that?
[16:04] <phoenix_firebrd> shadeslayer: youtube
[16:04] <phoenix_firebrd> r^
[16:04] <phoenix_firebrd> Riddell: ^
[16:04] <phoenix_firebrd> Riddell: I feel like you have become a celeb for some of us
[16:05] <shadeslayer> heh, I was sitting a couple of feet from Riddell when he gave that interview
[16:05] <shadeslayer> Riddell: you haven't seen it yet? :P
[16:05] <phoenix_firebrd> shadeslayer: awesome
[16:06] <Riddell> for any fans, I'll be signing copies of my autobiography at FOSDEM this weekend http://open-advice.org/
[16:06] <shadeslayer> lol
[16:06] <yofel> :D
[16:06] <BluesKaj> ...BBL
[16:06] <phoenix_firebrd> Riddell: with a gpg key?
[16:07] <Riddell> yeah less wrist strain that way :)
[16:07] <phoenix_firebrd> for the pdf
[16:08] <Riddell> Blizzzek: you guys coming to fosdem?
[16:08] <phoenix_firebrd> the most inspiring was how people came forward to contribute to kubuntu and how the team handles them
[16:08] <Blizzzek> Riddell: at least Frank and Björn will be there
[16:37] <phoenix_firebrd> shadeslayer: I have applied for the kde-packagers mailing list, will it get accepted eventually?
[16:37] <shadeslayer> did you open a bug report on bugs.kde.org
[16:37] <phoenix_firebrd> shadeslayer: no without that?
[16:37] <shadeslayer> nope then
[16:37] <phoenix_firebrd> shadeslayer: why so?
[16:38] <phoenix_firebrd> shadeslayer: is this an elite list?
[16:39] <shadeslayer> phoenix_firebrd: historically that's how it works
[16:39] <shadeslayer> https://bugs.kde.org/enter_sysadmin_request.cgi?component=packager
[16:39] <shadeslayer> since the tarballs are only released to a certain subset of packagers
[16:39] <shadeslayer> erm
[16:39] <shadeslayer> s/packagers/people
[16:44] <phoenix_firebrd> shadeslayer: filed a request
[16:44] <shadeslayer> phoenix_firebrd: you probably have to subscribe Riddell to it too
[16:44] <phoenix_firebrd> shadeslayer: cc ?
[16:44] <shadeslayer> yep
[16:45] <phoenix_firebrd> shadeslayer: forgot that let me update it
[16:45] <shadeslayer> idk what email address he uses for bugzilla
[16:45] <phoenix_firebrd> shadeslayer: googling
[16:45] <shadeslayer> huh?
[16:45] <shadeslayer> why not just ask him?
[16:46] <Riddell> jr@jriddell .org
[16:46] <phoenix_firebrd> ok
[16:48] <phoenix_firebrd> "CC: jr@jriddell .org did not match anything"
[16:48] <Riddell> without the space
[16:48] <phoenix_firebrd> right
[16:49] <phoenix_firebrd> done
[16:51] <phoenix_firebrd> I have subscribed to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>the first one is awaiting for approval
[17:03] <phoenix_firebrd> shadeslayer: the control file contails "XSBC-Original-Maintainer" but the dsc file contains "Original-Maintainer" and I am getting a warning during building that the later is an unknown variable. I am thinking that its because of the improper updating from cdbs. any idea why?
[17:19] <phoenix_firebrd> Riddell: did libmtp, rekonq and ktorrent got packaged?
[17:19] <yofel> ktorrent and rekonq are done
[17:20] <phoenix_firebrd> yofel: shall i try libmtp?
[17:22] <Riddell> phoenix_firebrd: you can see if there's anything to package there I'm not sure there is
[17:22] <yofel> phoenix_firebrd: you could, that's shadeslayer's expertise I believe
[17:22] <phoenix_firebrd> Riddell: sorry , i just saw your mail now, i am getting accustomed to the work flow
[17:23] <yofel> phoenix_firebrd: and as Riddell says, the packaging notepad linked in the topic points to the packaging todo's
[17:23] <phoenix_firebrd> yofel: ok
[17:23] <yofel> if you find something in the wild that needs to be done add it there
[17:24] <yofel> now if apachelogger would fix kubotu that would be great...
[17:24] <yofel> apachelogger: if my change doesn't work at all just throw it out and hardcode a login_with() that works for you...
[17:25] <yofel> kubotu: plugins
[17:25] <yofel> ~help plugins
[17:25] <kubotu> no help for topic plugins
[17:26] <phoenix_firebrd> shadeslayer: are you packaging libmtp?
[17:58] <phoenix_firebrd> good night everyone
[19:44] <yofel> ScottK: do we need these?
[19:44] <yofel> -./usr/bin/pykdeuic4-2.7
[19:44] <yofel> -./usr/bin/pykdeuic4-3.3
[19:44] <yofel> or is the generic pykdeuic4 enough
[20:16] <ScottK> yofel: We should have them.
[20:20] <yofel> ok
[22:06] <Riddell> yofel: I think we do have them already but under a different path.  i think.  check that
[22:07] <yofel> I didn't find them in the pykde4 install files
[22:49] <apachelogger> JontheEchidna: pingy
[22:49] <JontheEchidna> apachelogger: pong
[22:49] <apachelogger> JontheEchidna: it appears to me the qapt codec installer is misbehaving
[22:50] <apachelogger> remove gst fluendo and ugly, then try to play mp3 in amarok ... it will install -ugly properly but claim there was an error
[22:50] <apachelogger> PHONON-GST BEGIN: void Phonon::Gstreamer::MediaObject::setError(const QString&, Phonon::ErrorType)
[22:50] <apachelogger> PHONON-GST   "User aborted codec installation"
[22:50] <JontheEchidna> hmm
[22:51] <apachelogger> as per https://bugs.kde.org/show_bug.cgi?id=314191 I suspect shadeslayer has the same problem
[22:51] <apachelogger> i.e. since the installer reports abortion the registry is not actually reloaded before retrying to play, thus asking to install for a second time but this time around -fluendo
[22:55] <apachelogger> https://launchpad.net/~apachelogger/+archive/ppa/+files/mangonel_0.1~git20130130-0ubuntu1.dsc still needs a review
[23:24] <yofel> ooooops
[23:24] <yofel> my backport version parser doesn't play well with Riddell forgetting to add ~ppa to the version ^^
[23:24] <yofel> kdeplasma-addons (4:4.10.0-0ubuntu1) raring; urgency=low~ubuntu12.10~ppa1) quantal; urgency=low
[23:25] <yofel> is the result
[23:26] <yofel> Riddell: would it work better for you if we committed the version *with* ~ppa1 to bzr and adjusted the scripts to remove that before uploading to the archive?
[23:27] <yofel> because hell breaks loose if the ppa has something with simply "ubuntu1"
[23:28]  * yofel will try to fix the backport script again tomorrow
[23:28] <JontheEchidna> apachelogger: fixed
[23:29] <JontheEchidna> thx for the report
[23:30] <apachelogger> JontheEchidna: thank you
[23:30] <JontheEchidna> the worker was setting the transaction status to "finished" before setting the exit code, so when the gst helper checked, the exit code was still ExitUnfinished, the default value
[23:44]  * yofel gave 4.10.0 a short run on raring, no obvious issues
[23:44] <yofel> more testing tomorrow
[23:44]  * yofel is off to bed, good night