[00:00] <ovidiu-florin> and how can I test if it installs correctly?
[00:00] <ovidiu-florin> and if it uninstalls corerctly?
[00:01] <ovidiu-florin> or is that not part of the tests I'm supposed to do?
[00:03] <yofel> usually not.. the list-missing hook will tell you if you're missing a file in the package and that's what we usually check
[00:03] <yofel> we do test the installability of the packages, but only once all are done. Installing single packages is usually a dependency mess
[00:04] <yofel> as for uninstalling. dpkg is very reliable there. As long as you don't have a prerm/postrm script you may assume it will uninstall fine
[00:05] <apachelogger> also installability of one package has no value
[00:06] <apachelogger> only expresses whether it does not conflict with anything that was on the system prior to install (ignoring conflicts with other packages that are part of a KDE release and prior versions of those packages)
[00:14] <apachelogger> yofel: the trello tells me tomorrow is beta3
[00:14] <apachelogger> yofel: still held up on b1?
[00:17] <valorie> I guess it is worth another try to get our docs on the KDE wiki system, but I don't know how that would work, since they are our upstream
[00:18] <apachelogger> same river still :P
[00:22] <sgclark> they were asking me what kubuntu was going to do, I did not have answers. guess it is a good time to figure it out lol. they seem to be asleep now though. I keep asking around though
[00:28] <ovidiu-florin> sgclark: are you asking if kubuntu will use KDEs wiki?
[00:29] <valorie> well, I asked months ago, and was told then: No
[00:30] <sgclark> riddell asked me to someway use their wiki to get translation then I convert that to docbook
[00:30] <valorie> but I haven't been part of the doc or wiki team
[00:30] <valorie> right, that's what we have wanted from the beginning
[00:30] <sgclark> yeah I don't think they would host it, then they would have to for all using kde I suspect
[00:30] <valorie> because KDE's system is super, and the people running it are top-notch
[00:31] <valorie> another option we've been looking at is the mediawiki that KubuntuGuide is using
[00:31] <valorie> but they use google translate so far
[00:31] <ovidiu-florin> then why not host our own mediawiki?
[00:31] <valorie> and that sucks
[00:31] <valorie> ovidiu-florin: we don't have a sysadmin team
[00:32] <valorie> poorly administered wiki will be full of spam in days
[00:32] <ovidiu-florin> what woud that team need?
[00:32] <ovidiu-florin> need to do*
[00:32] <sgclark> I have been a sys admin in one of my lives. I tend my own web server, watcha yah need?
[00:32] <valorie> keep the software up-to-date, and monitor all posts for spam
[00:33] <ovidiu-florin> I pretty much do sysadmin stuff
[00:33] <sgclark> their are plugins that do most of the work, but yeah moderators for sure
[00:33] <ovidiu-florin> I maintain my own server and a few sites
[00:33] <valorie> what happens in KDE is the the post URLs are given out by the bot to the IRC channels
[00:34] <valorie> oops, that's the forum, sorry
[00:35] <valorie> and KDE has an established translator team which part of them work on the wikis as well
[00:35] <sgclark> while media wiki I think is a good idea, still need humans to translate
[00:35] <sgclark> ^^
[00:35] <valorie> using a Translate plugin which has been developed by some KDE people
[00:35] <valorie> YES, totally agreed
[00:35] <valorie> machine translation sux
[00:36] <valorie> we would be sort of on our own, which is why it makes me so nervous to think of leaving the Ubuntu infra
[00:37] <sgclark> that is very true
[00:37] <valorie> I know the Canonical sysadmin team isn't known for being responsive
[00:37] <valorie> but they are very competent
[00:38] <valorie> KDE sysadmins are gods, for sure
[00:38] <valorie> but I can't see how we can sneak into that tent
[00:38] <sgclark> hehe
[00:38] <sgclark> yeah
[00:39] <valorie> Amarok used to have their own wikis
[00:39] <valorie> full of spam
[00:39] <valorie> now that content is all on KDE wikis
[00:39] <sgclark> They will still do the heavy lifting for all docs KDE specific, but kubuntu specifc still needs a home
[00:39] <valorie> etc.
[00:39] <valorie> right
[00:40] <valorie> and we try to link to KDE content as much as possible, so we don't have to keep it current and/or translate
[00:40] <sgclark> exactly, I saw that, and that works perfect for what I want to do
[00:40] <valorie> ovidiu-florin: it would help if you would talk to the KDE wiki folks
[00:40] <ovidiu-florin> how about we just make the wiki not to allow anyone to register?
[00:40] <valorie> and see what it takes to do set up and maintainence
[00:41] <ovidiu-florin> and we jusst give accounts to the people who request it?
[00:41] <valorie> that would help, for sure
[00:41] <ovidiu-florin> ok, I'll contact them
[00:41] <valorie> but again, a lot of our content is on the ubuntu wiki too
[00:42] <sgclark> yeah, to be honest, I was so lost trying to find stuff
[00:42] <valorie> and as long as we are an ubuntu flavor, that is the way it is
[00:42] <sgclark> I finally found that commented installation lol
[00:42] <valorie> sgclark: that's why I don't make pages
[00:42] <valorie> wiki logic is not logical to me
[00:43] <valorie> and moinmoin is more opaque than most
[00:43] <sgclark> yeah docbook is easier lol. but I can get it figured out
[00:43] <valorie> I found docbook easier, tbh
[00:43] <sgclark> :)
[00:43] <valorie> it's just xml
[00:43] <sgclark> yeah
[00:43] <valorie> I used to handcode my own webpages too
[00:43] <valorie> easy peasy
[00:43] <sgclark> same
[01:01] <manchicken> Howdy
[01:03] <ovidiu-florin> hey manchicken
[01:04] <sgclark> hello
[01:15] <ovidiu-florin> yofel: how do I commit?
[01:16] <sgclark> ovidiu-florin: need to ask in kde-www for anything wiki related
[01:16] <ovidiu-florin> I asked in #kde-docs
[01:16] <sgclark> I tried earlier without luck, I am thinking most of them asleep now
[01:16] <ovidiu-florin> so that's not ok
[01:16] <ovidiu-florin> ?
[01:16] <sgclark> #kde-docs are the docbook folks
[01:17] <ovidiu-florin> aham
[01:17] <ovidiu-florin> sgclark: so you've already asked in #kde-www about how they maintain the wiki?
[01:19] <sgclark> I asked for assistance to translation / wiki -> docbook help, so not the same ? as yours
[01:19] <sgclark> just warned that I got no response :)
[01:25] <manchicken> apachelogger: ping
[01:25] <apachelogger> manchicken: almost-not-sleeping-pong
[01:25] <manchicken> apachelogger: ah!
[01:25] <manchicken> Did you see my call for a meeting?
[01:25] <manchicken> I want to discuss the status of the libqapt stuff.
[01:26] <apachelogger> manchicken: what rohan said :P
[01:26] <ovidiu-florin> manchicken: most of us are at the BSP
[01:26] <manchicken> Weaksauce.
[01:26] <manchicken> Could somebody counter with a time that works for them?
[01:26] <apachelogger> manchicken: not sure we will be around, though I suppose we will since that's 1600 munich time
[01:27] <manchicken> What's Munich? +0200?
[01:27] <apachelogger> +1
[01:27] <manchicken> That's right! I proposed 1500!  RED ALERT! We lost a brain. Get me a medic, NOW!
[01:28] <apachelogger> manchicken: not this weekend would help I guess, but as I said IMO there is nothing stopping us from doing it saturday either
[01:28] <apachelogger> munich isn't known to have bad uplink xD
[01:29] <ovidiu-florin> apachelogger: dr who?
[01:29] <manchicken> That seems like mixed signals.
[01:29] <manchicken> Would you guys prefer next weekend? After American Thanksgiving?
[01:30] <apachelogger> ovidiu-florin: doctor who isn't on at 1500 :P
[01:30] <ovidiu-florin> oh
[01:30] <manchicken> (a.k.a. the day we skew the Earth's rotation by each gaining 10 pounds in as many hours)
[01:30] <manchicken> Are you guys watching the premier?
[01:31] <apachelogger> sure
[01:31] <ovidiu-florin> I'm off to bed
[01:31] <ovidiu-florin> nighty night
[01:31] <apachelogger> nini
[01:32] <apachelogger> manchicken: I'd not want you to miss out on rotational skew
[01:32] <manchicken> apachelogger: It's no bother, I'll have already braced for impact.
[01:32] <apachelogger> but if it's all the same to you, maybe propose it on the list see what excuse shadeslayer has for next weekend :P
[01:33] <manchicken> Indeed.
[01:33] <manchicken> I'll send that out now :)
[01:33] <manchicken> I'm going to keep plugging away (slowly) at unit tests until then.
[01:34] <manchicken> I've re-factored quite a bit of the program, I think part of this meeting should be reviewing my changes to make sure that they're in line with what we want for the library.
[01:34] <manchicken> Much of my re-factoring is to make it more testable. It makes me uncomfy that so much stuff depends on a library with so little test coverage.
[01:34] <apachelogger> manchicken: libqapt?
[01:34] <manchicken> Yeah
[01:34] <apachelogger> pff
[01:35] <apachelogger> ALL of multimedia doesn't have test coverage
[01:35] <apachelogger> from driver to applications
[01:35] <manchicken> Yeah... but I'm not playing with those, am I? :)
[01:35] <apachelogger> it's all the more surprising that one does not get squeeky noises ever so often
[01:35] <apachelogger> manchicken: no, just putting things into perspective :P
[01:35] <manchicken> libqapt seems much riskier to get wrong though.
[01:36] <apachelogger> OTOH porn is much more appreciated by users than silly packages :P
[01:36] <manchicken> Especially seeing as how one of the bugs I'm fixing in it is the wholesale slaughter of your sources.list.
[01:36]  * apachelogger waves fist at qml
[01:37] <manchicken> Don't do that, the former Mono zealots will see you!
[01:37] <apachelogger> :O
[01:38] <apachelogger> manchicken: btw, I never quite understood why we ahve that sources.list thing anyway ... the script generating it is insanely spooky and would be 300% more readable if it treated each repository as a separate sources.list unit
[01:38] <apachelogger> things like that make life such a harsh mistress
[01:38] <manchicken> apachelogger: No argument... but that is exactly the use case which causes this problem.
[01:38] <manchicken> If you try to modify a source entry in a sources.list.d entry, it trashes sources.list.
[01:39] <manchicken> That's in the new version that is not yet released.
[01:39] <manchicken> (the one Jon gave me before)
[01:40] <manchicken> apachelogger: You mentioned Doctor Who earlier... you do know I work for ThinkGeek now, right? :)
[01:45] <apachelogger> I did not know that
[01:45] <apachelogger> though I always considered it a shame that kubuntu members do not get equipped with doctor who slippers
[01:45] <apachelogger> Riddell: I really think we should change that :P
[01:46] <manchicken> We have excellent TARDIS slippers, just recently went on sale, too.
[01:46] <manchicken> Very cozy.
[01:46]  * manchicken knows nothing of international shipping costs though...
[01:46] <apachelogger> valorie: can we haz sponsorship ^
[01:47] <manchicken> The 12 days of Doctor Who thing has been a fun marketing promo to watch... even though I know very little about marketing.
[01:49] <manchicken> I'm just a Perler for them, and they moved my family and me over to a very beautiful part of the country to do the job, too. It's been a good time. Supporting open source is one of our values, so I've actually been told that from time to time it's cool if I adjust my work hours to accommodate my open source stuff.
[01:49] <apachelogger> that's really awesome
[01:49] <manchicken> It is.
[01:50] <apachelogger> well, time for bed, nini
[01:50] <manchicken> How does one pull an automated test into the debugger in KDevel?
[01:50] <manchicken> nini
[01:50] <manchicken> ?
[01:51] <apachelogger> manchicken: #kde-devel may be able to help
[01:51] <manchicken> K
[01:51]  * apachelogger lives on the terminal and would gdb it simply :P
[01:52] <manchicken> Yeah, I may just do that... gdb hates me. I'm pretty sure it wants to kill me.
[02:22] <valorie> haha, doctor who slippers all around!
[02:34] <jalcine> \o/
[02:34] <jalcine> only like 4 days left!
[02:55] <manchicken> Indeed!
[02:55] <manchicken> valorie: I have our 10th Doctor pajamas... first set of pajamas I've worn in 15 years.
[02:56] <valorie> lol
[02:56] <manchicken> valorie: I fully expect David Tenant to send me a nasty letter.
[02:56] <valorie> i'm loving all the specials this week
[02:56] <jalcine> same here; way too excited
[02:56] <jalcine> I wish Tenant could stay
[02:56] <jalcine> he was the best doctor
[02:56] <jalcine> imho
[02:56] <manchicken> Tennant*
[02:56] <valorie> although BBC America is not top-notch
[02:56] <valorie> at least I have it
[02:57] <manchicken> I liked Tennant
[02:57] <jalcine> manchicken: thanks lol
[02:57] <valorie> yes, Tennant was awesome
[02:57] <valorie> but so is Matt
[02:57]  * jalcine stands on the Tennant side :p
[02:57] <manchicken> I liked Christopher Eccleston better... but his tenure was short-lived.
[02:58] <jalcine> Man, I almost forgot about him
[02:58] <jalcine> He reminds me of Harness when I think of him now
[02:58] <jalcine> a solider kind of guy
[02:58] <manchicken> I know I'm in the minority with him... but he just pulled the silly part off better, and I like silly.
[02:59]  * jalcine has to re-watch
[02:59] <jalcine> but time's against me
[02:59] <manchicken> Yes. Yes you do. Netflix is your friend.
[02:59] <jalcine> manchicken: but I have work :/
[02:59] <jalcine> I work in office and remotely in the evening
[03:00] <manchicken> (unless you want to watch Classic Doctor Who or anything after the first set with Amelia Pond)
[03:00] <jalcine> oh man that's going to be a challenge, saving that for the holidays
[03:00] <manchicken> Yeah... I know what you mean.
[03:00] <manchicken> Netflix has a terrible selection for Classic Doctor Who, and they don't seem to support GNU/Linux at all.
[03:01] <manchicken> Anyway, it's 2200 and I'm sleepy. I'm gonna head to bed.
[03:01] <jalcine> there's this
[03:01] <jalcine> http://www.compholio.com/netflix-desktop/
[03:01] <jalcine> manchicken: ah, you're over by me
[03:01] <jalcine> lol
[03:01] <manchicken> It's been a while since I went to bed the same night I woke up.
[03:01] <manchicken> jalcine: Where are you?
[03:01] <jalcine> Over in NYC
[03:01] <jalcine> Well, time zone wise
[03:02] <jalcine> literally, im in NYC
[03:02] <manchicken> I'm in the NOVA area, in Fairfax County, VA.
[03:02] <jalcine> ah! I think I've driven through there with a friend
[03:02] <jalcine> well, have a good nap o/
[03:02] <manchicken> Used to be in IL, moved out here recently to go work for ThinkGeek :)
[03:03] <jalcine> That's awesome!
[03:03] <manchicken> Yeah
[03:03] <manchicken> It is :)
[03:04] <manchicken> Anyway, bed time for me. Later all.
[03:05] <jalcine> o/
[03:13] <valorie> I get the DVDs for the old stuff
[03:13] <valorie> started with the first Doctor and am not done with that stuff yet
[03:54] <ScottK> apachelogger: Yes.  http://summit.ubuntu.com/uds-1311/meeting/21986/core-1311-qt5-versions-in-ubuntu/
[03:55] <ScottK> I sort of messed up my TZ math and missed it, but it seemed to work out OK.
[07:32] <lordievader> Good morning.
[08:06] <tsdgeos> Riddell: you guys didn't attend http://summit.ubuntu.com/uds-1311/meeting/21986/core-1311-qt5-versions-in-ubuntu/ ?¿
[08:10] <tsdgeos> ah, i see another guy that seems to have some kubuntu background joined later
[08:16] <jussi> tsdgeos: [05:54:55] <ScottK> apachelogger: Yes.  http://summit.ubuntu.com/uds-1311/meeting/21986/core-1311-qt5-versions-in-ubuntu/
[08:16] <jussi> [05:55:16] <ScottK> I sort of messed up my TZ math and missed it, but it seemed to work out OK.
[11:35] <Riddell> Sick_Rimmit: going to do the phonon SRU?
[11:35] <Riddell> do you know what you're doing?
[11:35] <apachelogger> does anyone? XD
[11:49] <Riddell> so philosophical
[12:24] <BluesKaj> Hi all
[12:36] <apachelogger> yofel: plingz
[12:41] <apachelogger> yofel: during the mighty neon5 build we need to have XDG_DATA_DIRS and XDG_CONFIG_DIRS exported, otherwise build tools relying on Qt's standardpaths foo will not be able to lookup their data/config files
[12:41] <apachelogger> leading to FTBFS like https://launchpadlibrarian.net/156993752/buildlog_ubuntu-saucy-amd64.project-neon5-kde-workspace_0.0%2Bgit20131120~6959c0a%2Bneon9~13.10.1_FAILEDTOBUILD.txt.gz where meinproc can't find its dtds
[12:41] <apachelogger> yofel: so I am wondering, should I simply add the exports to default-settings.mk
[13:11] <Riddell> shadeslayer: alive?
[13:30] <yofel> apachelogger: yeah, just add them
[13:37] <shadeslayer> Riddell: yes
[13:51] <manchicken> Guten tag
[13:55] <Riddell> manchicken!
[13:56] <manchicken> Riddell!
[13:56] <manchicken> How the hell are you?
[13:56] <Riddell> I'm awesome
[13:57] <Riddell> manchicken: what's all this you're doing with qapt?
[13:58] <manchicken> Funny you ask :)
[13:58] <manchicken> So for the kubuntu-debug-installer we need to be able to add a sources.list.d file and then remove it again.
[13:59] <manchicken> libqapt doesn't really support that… at all. Matter of fact, when you try, it trashes your sources.list.
[13:59] <manchicken> So I've been re-factoring that bit to fix the bug. In the course of fixing that, however, I got worried about how much this very important library has nothing really in the way of automated tests.
[14:00] <manchicken> So I refactored it a bit more so it takes arbitrary sources.list style files so that I could wrap some QtTests around it.
[14:00] <manchicken> Last night I finished the first of the seven tests I want to wrap around that library before I send it out to people.
[14:01] <manchicken> The reason I'm bugging everybody about it, however, is because I want to make sure that before I get too far — which I arguably may have already done — I get some other folks to look at it to make sure I'm not spending a bunch of time on what could be a fundamentally bad idea.
[14:01] <manchicken> I'm also trying to keep in mind that other programs use it, so I need to maintain a consistent interface.
[14:03] <manchicken> I know that's a lot, but that's what's going on.
[14:04] <Riddell> sounds like a good thing you're doing
[14:04] <Riddell> apol has been fixing muon recently, have you spoken to him?
[14:05] <manchicken> No, but that sounds like someone who has a stake in this whole thing.
[14:05] <manchicken> Why is it I always end up working on package management stuff? hehe
[14:06] <Riddell> because you're awesome
[14:06] <manchicken> Hah
[14:06]  * BluesKaj suspects muon isn't seeing some repos , since apt-get sees packages that muon can't find
[14:07] <manchicken> What's up with this virtual UDS stuff?
[14:15] <Riddell> manchicken: thanks for the reminder, in the qt session now :)
[14:15] <Riddell> manchicken: here's apol_ if you have questions on qapt
[14:15] <manchicken> Hah
[14:16] <manchicken> apol_: Did you see the message about the libqapt meeting I'm wanting to have next Saturday @ 1500 UTC?
[14:22] <apol_> I don't know
[14:22] <apol_> no
[14:22] <apol_> i havent
[14:22] <apol_> let me check
[14:23] <apol_> manchicken: yes... I don't think I can make it this saturday
[14:24] <apol_> you can find me here at many times
[14:24] <apol_> or just e-mail
[14:25] <apol_> manchicken: so what's your plan?
[14:33] <Riddell> apol_: http://paste.ubuntu.com/6448388/
[14:46] <apol_> manchicken: I've worked mostly on muon instead of qapt, so personally, as long as you don't break muon I'm happy
[14:46] <apol_> there's some sources.lists managing feature
[14:46] <apol_> if that's what it's not working for you, I'd love to see it fixed
[14:47] <apol_> I can look at your patches and give you my opinion
[14:47] <apol_> manchicken: I'd suggest to discuss over this issue through reviewboard instead of a meeting
[14:48] <lordievader> Good afternoon.
[15:07] <manchicken> apol_: What about next Saturday? I sent out a second proposal yesterday.
[15:08] <Riddell> manchicken: is there a need for a meeting rather than just a conversation?
[15:09] <manchicken> Riddell: Multiple parties involved was my justification.
[15:09] <manchicken> There are many programs linking against that library, no?
[15:11] <apol_> not that many that I know of
[15:11] <apol_> some Kubuntu tools and Muon, AFAIK
[15:11] <apol_> maybe I'm wrong though
[15:13] <Riddell> yep
[15:13] <Riddell> a patch in kde-runtime, debug-installer, muon, kde-config-grub2 and gstreamer0.10-qapt
[15:13] <Riddell> (the latter is part of qapt anyway)
[15:17] <Riddell> manchicken: so I think just code away and get apol to review
[15:17] <shadeslayer> ^^
[15:17] <manchicken> K
[15:17] <manchicken> I'm going to try to maintain calling compatibility, but I am adding the ability for libqapt to know that it's got multiple sources files.
[15:18] <manchicken> I changed internal storage to use a hash keyed by filename rather than a simple list.
[15:18] <Riddell> jonathan thomas is busy with a lady and university so can't do muon/qapt just now
[15:18] <manchicken> But as long as you didn't depend on any of the internals, the only real side-effect is that it might change the order of entries.
[15:19] <manchicken> That's cool, I have no problem with people taking time off.
[15:19] <manchicken> I took six years off.
[15:19] <manchicken> (almost six years)
[15:19] <manchicken> (maybe closer to five)
[15:20] <Riddell> welcome back :)
[15:21] <Riddell> manchicken: UDS moved to online only which does prevent a lot of the usefulness of it and possiblity for community cohesion, fortunately in Kubuntu we have some money so we can fund trips to meetings like the bus squishing party this weekend
[15:21] <Riddell> but it may not allow for trans-atlantic travel
[15:22] <manchicken> Riddell: Stupid Atlantic...
[15:24] <Riddell> shadeslayer: kdepimlibs has this in rules http://paste.ubuntu.com/6448632/
[15:24] <Riddell> shadeslayer: so that might need to be added to libkfbapi libkolab and libkgapi
[15:24] <Riddell> but the question of why those packages depend on kdepim-runtime is unknown and annoying me
[15:24] <shadeslayer> *nod*
[15:25] <shadeslayer> note : I think pkg-kde-tools is broken
[15:25] <Riddell> in what way?
[15:25] <shadeslayer> https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+build/5248662
[15:25] <shadeslayer> Looking at the Debian changelog to see if it's been fixed
[15:26] <ovidiu-florin> shadeslayer: I've made the changes to knavalbattle to make it work and I''ve changed the changelog
[15:26] <ovidiu-florin> how do I commit
[15:27] <shadeslayer> I just fixed that :(
[15:27] <shadeslayer> like 30 minutes ago
[15:27] <shadeslayer> but plz show your changes so that I can review them
[15:27] <ovidiu-florin> how?
[15:27] <Riddell> /var/lib/dpkg/info/libkabc4.symbols:libkabc.so.4 libkabc4 #MINVER#, kdepim-runtime
[15:27] <Riddell> shadeslayer: that's probably why ^^
[15:27] <shadeslayer> push them to lp:~LP_USERNAME/+junk/knavalbattle
[15:27] <shadeslayer> ovidiu-florin: ^^
[15:28] <ovidiu-florin> one moment
[15:29] <Riddell> shadeslayer: I can add ovidiu-florin to ~kubuntu-packagers if that's easier
[15:30] <shadeslayer> Riddell: I want to review what he did before I'd add him :)
[15:30] <Riddell> shadeslayer: got it http://paste.ubuntu.com/6448687/
[15:31] <Riddell> shadeslayer: so we can either remove what debian does there to get rid of the circular dependency or we can just add to debian/rules to exclude kdepim-runtime
[15:31] <shadeslayer> Riddell: maybe discuss with debian first?
[15:31] <shadeslayer> and why did it work until now
[15:32] <Riddell> shadeslayer: because there was no break << kdepim-runtime
[15:32] <shadeslayer> I see
[15:32] <Riddell> so kdepim-runtime could be installed while building kdepim-runtime fine
[15:32] <Riddell> but you broke that :)
[15:32] <shadeslayer> well, lets discuss with Debian first?
[15:32] <shadeslayer> hehe
[15:32] <shadeslayer> => master at breaking stuff now
[15:32] <Riddell> yeah, go ahead if you can, I need to pop out for an hour
[15:40] <shadeslayer> okay
[15:41] <shadeslayer> ovidiu-florin: once you're done, you can look at kate :)
[15:42] <ovidiu-florin> ok
[15:42] <ovidiu-florin> I'm at work now so I had to ssh into my laptop at home
[15:44] <ovidiu-florin> shadeslayer: how do I push?
[15:44] <ovidiu-florin> i changed just the changelog
[15:45] <ovidiu-florin> do I have to commit or something before?
[15:45] <shadeslayer> yes
[15:45] <shadeslayer> bzr commit
[15:45] <ovidiu-florin> I'm not familiar with bzr
[15:45] <ovidiu-florin> I know only git
[15:45] <shadeslayer> bzr push lp:~LP_NAME/+junk/PROJECT
[15:46] <ovidiu-florin> do I bzr commit from the host in the knavalbattle dir?
[15:46] <ovidiu-florin> because I get an error saying: not a branch
[15:47] <ovidiu-florin> shadeslayer: ^
[15:50] <shadeslayer> well, did you branch the packaging?
[15:50] <shadeslayer> kbzr knavalbattle
[15:50] <shadeslayer> erm
[15:50] <shadeslayer> kbzr branch knavalbattle
[15:52] <ovidiu-florin> it still says it's not a branch :(
[15:52] <ovidiu-florin> shadeslayer: ^
[15:52] <shadeslayer> Riddell: still there?
[15:52] <shadeslayer> ovidiu-florin: what are you doing 0.o
[15:53] <shadeslayer> ovidiu-florin: kbzr branch knavalbattle;cd knavalbattle;hack hack hack; bzr commit; bzr push
[15:53] <ovidiu-florin> shadeslayer: http://pastebin.kde.org/p37extzm5/ccf30l
[15:54] <shadeslayer> no no no
[15:55] <shadeslayer> ovidiu-florin: you haven't changed dir to the packaging folder :)
[15:55] <shadeslayer> cd knavalbattle
[15:55] <shadeslayer> and preferably not inside knavalbattle-4.11.80
[15:55] <ovidiu-florin> ok
[15:55] <ovidiu-florin> done that
[15:56] <ovidiu-florin> bzr: ERROR: No changes to commit. Please 'bzr add' the files you want to commit, or use --unchanged to force an empty commit.
[15:56] <shadeslayer> did you copy over your changes ?
[15:57] <shadeslayer> from the debian dir
[15:57] <ovidiu-florin> do I just copy the files I've changed?
[15:58] <shadeslayer> yes
[15:58] <shadeslayer> then run bzr diff / bzr commit
[15:58] <ovidiu-florin> then why not just give you a pastebin of the changes?
[15:58] <ovidiu-florin> it's much simpler?
[16:00] <shadeslayer> sure, but then you're learning the workflow this way
[16:04] <ovidiu-florin> done
[16:04] <ovidiu-florin> I've pushed
[16:05] <ovidiu-florin> shadeslayer: how do I show it to you?
[16:06] <shadeslayer> where did you push it to?
[16:06] <ovidiu-florin> shadeslayer: https://code.launchpad.net/~ovidiub13/+junk/knavalbattle
[16:06] <shadeslayer> ovidiu-florin: cool, looks good :)
[16:07] <shadeslayer> ovidiu-florin: now, similar issue with kate
[16:07] <shadeslayer> it has files that are new and are not installed
[16:07] <ovidiu-florin> ok
[16:07] <ovidiu-florin> I'll take a look
[16:07] <ovidiu-florin> thank you
[16:07] <shadeslayer> click "Show/Hide"
[16:07] <shadeslayer> and there are a bunch of files in the list-missing output
[16:07] <shadeslayer> copy paste them into a relevant install file
[16:07] <shadeslayer> usually there are other similar files
[16:08] <shadeslayer> so grep around for 'syntax'
[16:08] <shadeslayer> and put them in that file
[16:08] <ovidiu-florin> how do I get to that page again?
[16:08] <ovidiu-florin> I have the link
[16:08] <ovidiu-florin> I just want to know how do I get to it if I didn't
[16:14] <shadeslayer> I just go to qa.kubuntu.co.uk
[16:14] <shadeslayer> and then ninjas-status
[16:15] <shadeslayer> then the usually the last page on that list
[16:17] <ovidiu-florin> shadeslayer: The authorization page: ... should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf.
[16:17] <ovidiu-florin> how can I avoid this?
[16:17] <ovidiu-florin> I got it from $ pull-ninjas-source kate trusty
[16:18] <shadeslayer> ovidiu-florin: you need to authorize pull-lp-ninjas once the page opens
[16:18] <shadeslayer> like, Authorize forever or whatever
[16:18] <ovidiu-florin> I've done that
[16:18] <ovidiu-florin> every time
[16:18] <ovidiu-florin> it's been 3 times already
[16:19] <shadeslayer> make sure you click the right button?
[16:57] <shadeslayer> ovidiu-florin: btw kwallet is another one you can do
[16:57] <shadeslayer> exact same issue as kate
[16:59] <ovidiu-florin> shadeslayer: I'm working on my laptop via ssh
[16:59] <ovidiu-florin> I can't get pull-ninjas-source to be authorized
[17:02] <tester56> hi, stupid question, but does anyone know how to remove the file extension from a relative path like "./a/bc.png"  in bash without knowing the extension?
[17:02] <shadeslayer> oh
[17:03] <shadeslayer> yofel: ^^ ideas on how to solve that
[17:03] <shadeslayer> ovidiu-florin: usually I use w3c on servers
[17:03] <shadeslayer> and then it opens the page in w3c
[17:03] <ovidiu-florin> w3c?
[17:06] <ovidiu-florin> shadeslayer: what's w3c?
[17:06] <shadeslayer> command line browse
[17:06] <shadeslayer> +r
[17:06] <shadeslayer> !info w3c
[17:06] <shadeslayer> ah
[17:06] <shadeslayer> something else
[17:06] <ovidiu-florin> lynx?
[17:06] <shadeslayer> no, that is not supported
[17:06] <ovidiu-florin> anyhow
[17:07] <ovidiu-florin> I've made an alias for the command and asked my Fiancee to run it at home
[17:07] <ovidiu-florin> and it didn't ask for authorization
[17:07] <ovidiu-florin> I don't get it
[17:07] <ovidiu-florin> localy it doesn't require authorization but over ssh it does?
[17:08] <ovidiu-florin> it's the same PC
[17:08] <shadeslayer> no clue, yofel usually knows more about auth issues
[17:11] <ovidiu-florin> shadeslayer: the kate issue is only on i386 not on amd64
[17:11] <shadeslayer> yep
[17:11] <ovidiu-florin> do I have to sudo -E DIST=trusty ARCH=i386 pbuilder --login --save-after-login
[17:11] <ovidiu-florin> ?
[17:11] <shadeslayer> well
[17:12] <shadeslayer> have you fixed the issue?
[17:12] <shadeslayer> in the install files?
[17:12] <ovidiu-florin> since I only have one for the amd64
[17:13] <ovidiu-florin> shadeslayer: doing it now
[17:14] <shadeslayer> ovidiu-florin: once done, just create a pbuilder for i386
[17:14] <ovidiu-florin> likt this: sudo -E DIST=trusty ARCH=i386 pbuilder --login --save-after-login ?
[17:14] <shadeslayer> same as amd64 command, just with ARCH=i386
[17:17] <mamarley> ScottK: debfx:  Sorry for the huge delays again, but I finally got around to making a quassel-core.preinst file to stop quasselcore when upgrading to Upstart-enabled version.  https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1244036
[17:56] <yofel> shadeslayer: for the authorization part I use an ugly solution on my server: a copy of pull-ppa-source with my credfile hardcoded. If you go over ssh it can't connect to the running keyring where the authorization is stored (and python keyring is broken on my server)
[17:56] <yofel> ovidiu-florin: ^
[17:56] <yofel> I'm not sure how to best improve that
[17:57] <yofel> maybe just implement --credfile for now
[18:01] <yofel> ovidiu-florin: the kate issue is in fact not only on i386, you can also build in amd64 pbuilder locally to verify the fix. In the archive we only do the list-missing check on i386 because it would be a) redundant, b) incomplete on amd64 (related to the way the archive builders work)
[18:03] <shadeslayer> Riddell: yofel apachelogger Doctor Who in the chinema?
[18:03] <shadeslayer> *cinema
[18:04] <shadeslayer> yofel: ideas on http://paste.ubuntu.com/6448894/
[18:05] <shadeslayer> oh
[18:05] <shadeslayer> wait
[18:06] <yofel> not changed soversion in sameversiondep? ^^
[18:06] <shadeslayer> no
[18:06] <shadeslayer> someone forgot to rename files
[18:06] <shadeslayer> :P
[18:06] <yofel> lol
[18:07] <shadeslayer> and I've been bashing my head against cmake for the last hour
[18:08] <yofel> as for dr.who: not that I know of, it's not a very big deal here in germany
[18:17] <Riddell> shadeslayer: yeah the 50th anniversary one is being shown in cinemas worldwide
[18:17] <Riddell> but not in india http://www.doctorwho.tv/watch-the-day-of-the-doctor/
[18:18] <Riddell> shadeslayer: did you ask about kdepim-runtime?
[18:18] <shadeslayer> no
[18:18] <shadeslayer> Riddell: got busy with libkdcraw
[18:18] <shadeslayer> plz ask
[18:22] <Riddell> hmm http://lists.debian.org/debian-qt-kde/2013/11/msg00485.html  Bug#729363: libkdepim4: circular dependency hell
[18:22] <Riddell> shadeslayer: how come you were talking to maxy about coinstallability?
[18:23] <shadeslayer> Riddell: he added stuff to https://notes.kde.org/p/kubuntu-munich
[18:23] <shadeslayer> regarding co installability
[18:23] <Riddell> oh cool
[18:24] <Riddell> ximion is going too, lovely
[18:25] <shadeslayer> yep :)
[18:25]  * Riddell puts "ximian to showcase tanglu?" on https://notes.kde.org/p/kubuntu-munich
[18:25] <yofel> is he? Last he told me was that he planned to but can't make it as he was busy in karlsruhe last weekend
[18:26] <Riddell> his name is on https://wiki.debian.org/BSP/2013/11/de/Munich
[18:26] <ovidiu-florin> mc
[18:26] <yofel> yeah, but not confirmed
[18:27] <Riddell> oh I see
[18:27] <ximion> Riddell: yes, sorry :(
[18:28] <ovidiu-florin> shadeslayer: I don't understand how to determine if the build was successfull with no warnings
[18:29] <ximion> just came back from Karlsruhe last weekend, and I need some time for university work... (I have to give a seminar 'till 6 am on friday, and there's also stuff on monday)
[18:30] <ovidiu-florin> I have a line near the end that says: -- SUCCESS making standard target 'binary'. so I guess that means it's ok
[18:30] <yofel> ovidiu-florin: if you're using our hooks: when the build ends without errors then it at least built fine, on failure you would get a shell
[18:30] <shadeslayer> ^^
[18:30] <ximion> but I think I'll finally make it to FOSDEM next year :D (trying to get a lighting talk and/or one at the distro-devroom, so I *have* to be there ^^)
[18:31] <yofel> you can check if the list-missing hook showed any files
[18:31] <yofel> if you miss something the build status script will show it ^^
[18:32]  * shadeslayer already booked tickets for FOSDEM
[18:32] <ovidiu-florin> shadeslayer yofel I saw when testing on navalbattle that when the build failed I got the chroot shell and when it succeded I got the host shell
[18:33] <shadeslayer> right, so you have the hooks
[18:33] <shadeslayer> ovidiu-florin: bump the ppa version and upload to ninjas :)
[18:33] <shadeslayer> then send a merge request to lp:~kubuntu-packagers/kubuntu-packaging/PROJECT
[18:34] <ovidiu-florin> bump the ppa version?
[18:35] <shadeslayer> ovidiu-florin: change ppaX to ppaY in debian/changelog
[18:35] <shadeslayer> then run debuild -S -sd
[18:35] <Riddell> shadeslayer: easy answer 18:32 < svuorela> lib packages should add a -xkdepim-runtime on their shlibdeps calls
[18:35] <shadeslayer> yep saw that
[18:35] <Riddell> so we need to edit libkolab etc
[18:36] <shadeslayer> are you taking care of that?
[18:36] <Riddell> shadeslayer: I can do it now quickly
[18:37] <Peace-> Riddell: look at this program ! isn't  nerd :D http://wstaw.org/m/2013/11/20/plasma-desktopKN2873.png
[18:37] <shadeslayer> thx
[18:37] <Riddell> oh I got a build failure earlier on libkgapi so it might not be so easy
[18:37] <shadeslayer> :(
[18:37] <shadeslayer> note that 4.12 is almost done in the PPA
[18:38] <shadeslayer> once Riddell fixes kdepim-runtime, it should be installable
[18:39] <manchicken> Tomorrow's sessions don't seem particularly useful to me.
[18:40] <Riddell> manchicken: this is true of most of UDS if that's what you're talking about
[18:40] <shadeslayer> ^^
[18:40] <shadeslayer> plus hangouts are shit
[18:40] <shadeslayer> so much lag
[18:40] <manchicken> Yeah
[18:40] <ovidiu-florin> shadeslayer: there's not ppa in debian/changelog
[18:41] <shadeslayer> ovidiu-florin: can you pastebin head | debian/changelog
[18:41] <shadeslayer> ovidiu-florin: you're working on kate correct?
[18:41] <ovidiu-florin> yes
[18:41] <yofel> ovidiu-florin: are you in bzr?
[18:41] <manchicken> II think the face-time and working directly with people - breakout sessions and on-the-fly discussions - were more useful at the one I attended than anything else.
[18:41] <ovidiu-florin> in the new branch
[18:42] <yofel> ok, then do it like this:
[18:42] <yofel> bzr-buildpackage-ppa -s 2, or whatever number you want ppaX to be
[18:42] <ovidiu-florin> I don't understand the ppa numbering thing
[18:42] <yofel> it's just to increase the version of ppa packages
[18:42] <ovidiu-florin> what is it? what does it mean?
[18:43] <ovidiu-florin> aham
[18:43] <yofel> every upload needs to have a higher version than the previous one
[18:43] <yofel> and it's common to append ~ppaX to PPA packages
[18:43] <ovidiu-florin> yofel: how do I see the current ppa number?
[18:43] <yofel> the ~ubuntu14.04 part is to differentiate between packages for different releases
[18:44] <yofel> ovidiu-florin: check the version in the PPA, or you can look at the buildlog URL on the status page, that has the version in it
[18:44] <ovidiu-florin> this is the first line of debian/changelog: kate (4:4.11.80-0ubuntu1) UNRELEASED; urgency=low
[18:44] <yofel> right, correct for bzr
[18:44] <shadeslayer> arghhhh
[18:44] <shadeslayer> https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+build/5230568
[18:45] <shadeslayer> builds in a pbuilder
[18:45] <yofel> bzr-buildpackage-ppa will change that to 4:4.11.80-0ubuntu1~ubuntu14.04~ppa3 or so temporarily
[18:45] <yofel> and s/UNRELEASED/trust/
[18:45] <yofel> y
[18:47] <yofel> ovidiu-florin: you can find the spec for the package version on http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
[18:48] <yofel> esp. note that ~ lowers a version. I.e. 1~ < 1
[18:49]  * ovidiu-florin is confused
[18:49] <yofel> anything I can help with? or my fault? ^^
[18:50] <ovidiu-florin> not sure
[18:50] <ovidiu-florin> wait one moment
[18:52] <ovidiu-florin> https://code.launchpad.net/~ovidiub13/+junk/kate
[18:53] <ovidiu-florin> Rev 149
[18:53] <ovidiu-florin> I didn't write the commit message properly
[18:54] <ovidiu-florin> shadeslayer yofel I've pushed to a +junk ppa on my account so you can take a look. I didn't understand what to do next
[18:57] <shadeslayer> ovidiu-florin: I don't see the install file in the diffg
[18:57] <yofel> ovidiu-florin: current kate version in the ppa is ~ppa1, so run 'bzr-buildpackage-ppa -s 2' in the branch
 run bzr-buildpackage-ppa -s 2 (or higher) - but how do I know what is the correct number to use?
[18:57] <ovidiu-florin> look at the buildlog URL on the status page, where is that?
[18:57] <yofel> check the version in the PPA
[18:58] <ovidiu-florin> shadeslayer: I forgot to run diff
[18:58] <Riddell> waa libkolab fails http://paste.ubuntu.com/6449655/
[18:58] <yofel> you can either check on https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+packages?field.series_filter=trusty&batch=300
[18:58] <shadeslayer> ovidiu-florin: no, you forgot to push the changes to the install file here http://bazaar.launchpad.net/~ovidiub13/+junk/kate/revision/149
[18:59] <yofel> or you can look at the URL that the buildlog link on the status page points to
[18:59] <Riddell> and libkgapi with the same http://paste.ubuntu.com/6449657/
[18:59] <yofel> whatever is faster for you
[19:02] <ovidiu-florin> I understood this: https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+packages?field.name_filter=kate&field.status_filter=published&field.series_filter=trusty and I understand how to get there. But I don't undestand the other option.
[19:03] <yofel> then nvm, as long as that works for you
[19:06] <ovidiu-florin> shadeslayer: pushed with changes
[19:06] <ovidiu-florin> http://bazaar.launchpad.net/~ovidiub13/+junk/kate/revision/150
[19:06]  * Riddell uploads libkfbapi at least
[19:07] <yofel> ovidiu-florin: looks good (bonus points if you sort the file after editing ^^)
[19:12] <shadeslayer> gtg cya at the sprint
[19:12] <ovidiu-florin> shadeslayer: done
[19:14] <yofel> thanks!
[19:15] <ovidiu-florin> yofel: bzr: ERROR: There was an error parsing the changelog: Could not parse changelog: Unexpected line while looking for first heading: kate (4:4.11.80-0ubuntu1~ubuntu14.04 LTS~ppa2) trusty; urgency=low
[19:15] <yofel> ovidiu-florin: merged
[19:15] <yofel> o.O
[19:15] <yofel> where did that LTS come from
[19:16] <ovidiu-florin> trusty = LTS
[19:16] <yofel> right, but you don't put that in the version
[19:16] <yofel> the version is not allowed to have spaces too
[19:16] <ovidiu-florin> I didn't
[19:16]  * yofel checks the script
[19:17] <yofel> >>> print(UbuntuDistroInfo().devel(result='release'))
[19:17] <yofel> 14.04 LTS
[19:17] <yofel> WTF
[19:18] <yofel> ovidiu-florin: I need to fix that, give me a bit
[19:20] <ovidiu-florin> ;)
[19:20] <yofel> appending .split(' ')[0] should help for now ^^
[19:21] <yofel> ovidiu-florin: please pull kubuntu-automation and try again
[19:21] <yofel> possibly run "bzr revert debian changelog"
[19:22] <ovidiu-florin> Now on revision 284.
[19:22] <yofel> ack
[19:23] <ovidiu-florin> bzr: ERROR: Path(s) are not versioned: changelog
[19:23] <ovidiu-florin> yofel: ^
[19:23] <ovidiu-florin> isn't it bzr revert debian/changelog
[19:23] <ovidiu-florin> ?
[19:24] <yofel> er, right...
[19:25]  * Sick_Rimmit wakes up and waves
[19:26] <yofel> heyho
[19:27] <ovidiu-florin> yofel: it's trying to sign with Rohan Garg
[19:27] <ovidiu-florin> as*
[19:27] <ovidiu-florin> and fails
[19:27] <ovidiu-florin> obviously
[19:27] <yofel> ah, that's a safety check but annoying with the current dch behaviour, do this:
[19:28] <yofel> put "DEBSIGN_KEYID=your_key_hash" in ~/.devscripts
[19:28] <yofel> that'll force your key
[19:28] <ovidiu-florin> my key hash?
[19:30] <ovidiu-florin> yofel: from launchpad? or ssh?
[19:31] <yofel> your gpg key id. (what's shown on launchpad/the pub part of gpg --list-keys)
[19:32]  * Sick_Rimmit Begins work on Phonon SRU,
[19:33] <ovidiu-florin> yofel: where?
[19:34] <ovidiu-florin> I'm looking here: https://launchpad.net/~ovidiub13
[19:34] <yofel> ovidiu-florin: hm, do you *have* a gpg key?
[19:34] <ovidiu-florin> I don't know of one
[19:34] <yofel> ok ^^
[19:35] <ovidiu-florin> if I didn't get one by default, then no
[19:36] <ovidiu-florin> yofel: shadeslayer gave me this command, is it related: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv b2c30b9a0945a8e2
[19:36] <yofel> no, that's the overly complex version of the apt-key command I gave you
[19:36] <yofel> ovidiu-florin: https://fedoraproject.org/wiki/Creating_GPG_Keys#Creating_GPG_Keys_Using_the_KDE_Desktop
[19:37] <yofel> then follow https://help.launchpad.net/YourAccount/ImportingYourPGPKey after the key is on the keyserver
[19:39] <Sick_Rimmit> SRU Docs say: Ask someone in the Ubuntu bug control team to nominate the bug for the appropriate Ubuntu release(s)
[19:40] <Sick_Rimmit> Was that done via apachelogger 's email ?
[19:42] <yofel> Sick_Rimmit: that's done when you have a release task on the bug report
[19:42] <yofel> note that every developer here can do that
[19:44] <Sick_Rimmit> yofel: OK, I am way short of knowledge about what the Step 5 actions are in SRU Process. But first I will run the test cases against 12.04 and 14.04 and make sure it works
[19:44] <Sick_Rimmit> which is Step 4, I feel comfortable to take care of that
[19:47] <yofel> Sick_Rimmit: what bug are we talking about btw.?
[19:47] <Sick_Rimmit> Oh I'm sorry Yofel
[19:47] <Sick_Rimmit> https://bugs.launchpad.net/ubuntu/+source/phonon-backend-gstreamer/+bug/1154630
[19:48] <yofel> Sick_Rimmit: which release should it be applied to?
[19:49] <Sick_Rimmit> I believe its 12.04 LTS
[19:49] <Sick_Rimmit> If I understand the SEU instructions correctly I need to test in 14.04 (development release) and then in (12.04 LTS) then move to SRU step 5
[19:50] <Sick_Rimmit> Which is more complex, I am just going through the Sponsorship docs now
[19:51] <yofel> usually yes, but you can do the verification on 13.10 too as that's where it was fixed in
[19:52] <yofel> Sick_Rimmit: added a task for precise
[19:52] <Sick_Rimmit> OK looking now
[19:55] <Sick_Rimmit> OK Have assigned to me with notes and set to inprogress, hope thats correct
[19:57] <yofel> Sick_Rimmit: unassign yourself and set it to confirmed after requesting sponsorship
[19:57] <yofel> for that it's fine
[19:57] <yofel> s/that/now/
[19:57] <kubotu> yofel meant: "for now it's fine"
[19:58] <Sick_Rimmit> OK
[19:59] <Sick_Rimmit> Hmmm, that lost me.
[20:00] <Sick_Rimmit> It seems that at this stage I may only be able to run the Test Case
[20:00] <Sick_Rimmit> No worries, I'll keep chugging on, and see where it goes.
[20:01] <Sick_Rimmit> I'll get the tests done shortly, just await LTS Install to VM to complete
[20:22] <ahoneybun> hello all
[20:37] <lordievader> Hey ahoneybun, how are you doing?
[20:46] <Sick_Rimmit> hello folks
[21:09] <manchicken> Hi
[21:42] <ahoneybun> lordievader: sorry I did not read that till now, good you?
[23:09] <Sick_Rimmit> Well thoroughly frustrated with the whole SRU thing. I actually think I know 50% less now than when I started reading the docs :-(


[16:02] <yano> .tw https://twitter.com/NBCNightlyNews/status/727888186051989504
[16:02] <jenni> BREAKING: John Kasich to suspend his campaign for president, senior campaign adviser says - @mitchellreports https://twitter.com/NBCNightlyNews/status/727888186051989504/photo/1 | By: @NBCNightlyNews, Date: Wed May 04 15:50:41 +0000 2016, RT#: 419, Favs: 104


[05:37] <anrah_> Does destroy-model and destroy(kill)-controller use same methods to delete instances from openstack provider?
[05:37] <anrah_> I have weird problem where I can not delete model correctly, as the destroy fails to juju.worker.dependency engine.go:492 "undertaker" manifold worker stopped: destroying storage: listing volumes: <openstack IP> x509: certificate signed by unknown authority
[05:39] <anrah_> I have ssl-hostname-verification     model    false on both controller and other models
[06:25] <kklimonda> how do I access models of other users?
[06:25] <kklimonda> seems like juju status -m user/model doesn't work
[06:25] <kklimonda> and I can't do juju switch user/model
[07:13] <anrah_> kklimonda: Has the other user granted permissions for your user?
[07:14] <kklimonda> @anrah_ should he, if I'm a superuser?
[10:38] <blahdeblah> BlackDex: are you Fairbanks from launchpad?
[10:53] <BlackDex> blahdeblah: Yes
[10:53] <blahdeblah> BlackDex: Got your message about nrpe charm - good to hear the patch worked for you.  I'd like to do a little more testing over the weekend if that's all right with you.
[10:53] <blahdeblah> I'm happy to push to candidate channel if you have some things you'd really like to do with it today.
[10:54] <BlackDex> Ow, now, i can deploy it localy :)
[10:54] <BlackDex> and i can switch to the cs version when it is pushed
[10:54] <blahdeblah> OK - cool
[10:54] <BlackDex> that doesn't bother me
[10:54] <blahdeblah> thanks
[10:54] <BlackDex> But nice that is is fixed :)
[10:55] <BlackDex> You thx :)
[10:55] <BlackDex> for fixing this
[10:55] <blahdeblah> np
[12:52] <dgonzo> SaMnCo: following your blogpost I'm able to get a gpu/cpu kubernetes cluster deployed
[12:53] <dgonzo> I'm hitting an error when to trying to `juju deploy mydir/bundle.yml`
[12:53] <dgonzo> ERROR cannot deploy bundle: cannot resolve URL "local:xenial/cuda-1": unknown schema for charm URL "local:xenial/cuda-1"
[12:54] <dgonzo> now that path i put in there was just a guess
[12:54] <dgonzo> How can I list locally build charms?
[12:56] <tvansteenburgh> dgonzo: just use a local path to the charm
[12:57] <tvansteenburgh> dgonzo: in your bundle -> charm: /path/to/my/charm
[12:58] <tvansteenburgh> dgonzo: which blog post are you following? maybe i can help.
[13:34] <SaMnCo> dgonzo: Cool, happy you succeed :)
[13:35] <SaMnCo> https://usercontent.irccloud-cdn.com/file/Be2u6c50/enable-efs.sh https://usercontent.irccloud-cdn.com/file/DW4bx2vM/enable-gpu.sh https://usercontent.irccloud-cdn.com/file/DUCnVqKo/k8s-gpu.yaml
[13:35] <SaMnCo> dgonzo: these are my latest versions. deploy the bundle first, then watch until it is finished
[13:36] <SaMnCo> this deploys 3x CPU workers on m4.xlarge, and 3x on p2.xlarge
[13:36] <SaMnCo> then run enable-gpu.sh
[13:36] <SaMnCo> if you need an EFS drive, edit enable-efs.sh and add the EFS ID, then run it
[13:38] <SaMnCo> regarding building charms, you need the charm-tools package
[13:40] <SaMnCo> then there is a fair amount of info here : https://jujucharms.com/docs/stable/developer-getting-started
[13:41] <SaMnCo> this describe how to get started
[15:24] <Budgie^Smore> o/ juju world :)
[16:57] <stormmore> o/ juju world
[19:07] <kklimonda> is there a way to forward agent with juju ssh?


[00:53] <bcurtiswx> BUGabundo1: got a few free minutes to help me out
[00:53] <bcurtiswx> BUGabundo: got a few free minutes to help me out
[00:54] <BUGabundo> a few
[00:54] <BUGabundo> sup?
[14:19] <nigel_nb> hggdh: are you around?
[14:19] <nigel_nb> can someone wishlist bug 493973 for me please
[14:19] <ubot4> Launchpad bug 493973 in evolution "evolution can't send messages using smtp.gmail.com with default gmail settings" [Undecided,New] https://launchpad.net/bugs/493973
[14:31] <hggdh> nigel_nb: hi, -- not being a bother, but why do you think it is a wish (*I* know why *I* would think so, but... changes in status and importance should have a comment)
[14:31] <mac_v> pedro_: hi.. when a bug which was earlier present , but seems solved by an unknown fix... should it be marked "fix released" or "invalid" ?
[14:32] <mac_v> just asking , since the stock responses has such unknown fixes to me marked as "invalid"
[14:32] <nigel_nb> hggdh: I understand the bug and its a minor and * genuine * feature request (which should be filed upstream, which I'm doing now)
[14:32] <nigel_nb> its not causing any problems, just the user needs to do it manually
[14:33] <pedro_> mac_v, invalid is ok in that particular case
[14:36] <mac_v> pedro_: so should i change this to invalid > Bug #413729 ?
[14:36] <ubot4> Launchpad bug 413729 in f-spot "f-spot.exe crashed with signal 5 in _XError()" [Medium,Fix released] https://launchpad.net/bugs/413729
[14:37]  * mac_v gets confused , since seb128 marks them fix released and a few others mark them invalid... :(
[14:37] <pedro_> mac_v, don't bother about those closed reports
[14:37] <nigel_nb> hggdh: so, am I correct?
[14:38] <mac_v> pedro_: ah.. ok.. thanks .. but in future such bugs are to be marked 'invalid' ?
[14:38] <pedro_> mac_v, if the bug was "fixed" by an unknown way, yes, set those to invalid
[14:38] <pedro_> often people reboot their machine and the bug is fixed
[14:39] <pedro_> or for what ever other reason, marking those as invalid is ok
[14:39] <mac_v> pedro_: if fixed by an update?
[14:39] <pedro_> fix released
[14:39] <mac_v> ah ok
[14:39] <seb128> mac_v, I tend to use fix released when a new version fix the issue
[14:40] <seb128> and invalid when it magically went away after a restart or on next try
[14:40] <mac_v> ah... got it
[14:52] <nigel_nb> pedro_: you're the contact for evolution?
[14:52] <pedro_> nigel_nb, i'm getting the email for the bugs upstreamed there, that'd be a yes
[14:53] <nigel_nb> pedro_: ah, just forwarded an enhancement request upstream
[14:53] <hggdh> nigel_nb: done
[14:53] <nigel_nb> saw your name come up :)
[14:53] <hggdh> nigel_nb: yes, you are correct. But we have to comment on status/importance changes
[14:54] <hggdh> poor pedro_ would really like somebody else to get Evo ;-)
[14:54] <pedro_> btw I moved the bug to Triaged, since nigel_nb sent it upstream
[14:55] <nigel_nb> pedro_: you want some help on evo? I could help
[14:55] <hggdh> oh, I updated in between, I guess
[14:55] <nigel_nb> I sort of started liking upstream gnome :)
[14:56] <hggdh> see you all this evening (US central time evening)
[14:56] <pedro_> nigel_nb, sure! help is always welcome :-)
[14:57] <pedro_> nigel_nb, if you want to send some upstream there's a few on evolution just search for bugs that need to be forwarded upstream in the advanced search
[14:57] <pedro_> there's ~10 that need to be confirmed by someone getting the issue and then be send upstream to the Gnome BTS
[14:58] <nigel_nb> I'll look into it now :)
[15:00] <pedro_> cool! gracias!
[15:01] <nigel_nb> pedro_: how do I search by package?
[15:02] <pedro_> nigel_nb, what do you mean?
[15:02] <nigel_nb> I got it
[15:03] <pedro_> ok
[15:03] <nigel_nb> I wanted to search for evolution, figured it ot
[15:29] <nigel_nb> pedro_: 403682, reported upstream, change status
[15:29] <pedro_> bug 403682
[15:29] <ubot4> Launchpad bug 403682 in evolution "Some attached emails (ie MIME digest) are empty when downloaded from IMAP" [Low,New] https://launchpad.net/bugs/403682
[15:31] <pedro_> done thank nigel_nb
[15:31] <nigel_nb> :)
[15:43] <hggdh> bddebian: boo ;-)
[15:51] <bddebian> Boo too :)
[15:58] <nigel_nb> pedro_: other upstream forwardable bugs, I'm not sure if I can confirm... :(
[15:59] <pedro_> nigel_nb, no problem, thanks for working on those! :-)
[15:59] <nigel_nb> happy to be of help :)
[16:00] <bdmurray> Hello!
[16:00] <pedro_> hola bdmurray
[16:00] <nigel_nb> hello bdmurray :)
[16:01] <andresmujica> hola a todos!  hi everyone !
[16:01] <bdmurray> So, its that time of the month ... for the bug squad meeting!
[16:01] <andresmujica> hi bdmurray hi pedro_
[16:01] <thekorn> hey bugsquad!
[16:02] <andresmujica> hi thekorn
[16:02] <bdmurray> I don't see micahg...
[16:03] <bdmurray> So we'll skip the first two things in the agenda until he shows
[16:04] <bdmurray> Moving on we have "Documented policy for revision of Wiki pages. Some of them need revamp but seems most are unsure of how to go about it."  -- cyan-spam
[16:04] <bdmurray> While I don't think they are present I think there is enough information to discuss this
[16:04] <yofel> hi folks
[16:05] <thekorn> https://wiki.ubuntu.com/BugSquad/Meeting  -- for the reference ;)
[16:05] <bdmurray> I'm personally subscribed to most of the wiki pages I care about
[16:06] <bdmurray> so I'd prefer people just edit them however, from changes of wide scope I like what qsense did with e-mailing the bugsquad
[16:06] <bdmurray> er for changes
[16:06] <bdmurray> Additionally, I believe there was one issue where pages contradicted each other or it was not clear which page was correct.
[16:07] <bdmurray> In that case again e-mailing the bug squad for clarification on a policy makes the most sense to me.
[16:07] <bdmurray> Are other ideas on that topic?
[16:07] <bdmurray> Any - even!
[16:08] <pedro_> indeed that's the best way to go
[16:08] <yofel> well, I mostly agree that the ML would be the best place to discuss propsed changes to the wiki
[16:08] <yofel> and for direct questions we have this channel
[16:09] <bdmurray> yofel: ah, yes that's a good point
[16:09] <andresmujica> subscribing the ML to the bugsquad wiki pages could work too, or would it be just too much noise??
[16:10] <bdmurray> andresmujica: that's an interesting idea as if a policy changed everyone would be notified too
[16:10] <yofel> not if ediors use the 'trivial change' checkbox when needed
[16:10] <yofel> bdmurray: +1
[16:11] <thekorn> maybe we can just give this subscribe ML to wike pages idea a try for a few month
[16:11] <thekorn> s/wike/wiki
[16:11] <andresmujica> yeap
[16:11] <bdmurray> Okay, I see 2 actions to do then.  1) Publicize wiki editing policy.  2) Check with mailing list regarding subscribing to wiki pages.
[16:12] <bdmurray> I can take #1 any volunteers for #2?
[16:12]  * hggdh is still trying to load the wiki page :-(
[16:13] <hggdh> bdmurray: I am not sure I understand #2
[16:14] <hggdh> oh, wait
[16:14] <bdmurray> propose that the bugsquad mailing list be subscribe to "key" wiki pages and run a trial of it
[16:14] <hggdh> yes. As usual, I am slow
[16:14] <bdmurray> or I'm vague ;-)
[16:14] <hggdh> I can do it
[16:14] <bdmurray> hggdh: awesome, thanks!
[16:15] <bdmurray> Are there any other topics for the meeting?
[16:16]  * hggdh apart from the additionals, no, AFAICU
[16:16] <bdmurray> hggdh: additionals?
[16:16] <pedro_> yes, just one
[16:16] <pedro_> well from me at least
[16:16] <pedro_> I'm looking for people to help to organize the next bug days
[16:16] <hggdh> defining a roadmap, single use apport, etc
[16:17] <pedro_> that means , the one for this week and the next one
[16:17] <bdmurray> hggdh: right, however micahg isn't here :-(
[16:17] <pedro_> so if you want to help: just drop your name on https://wiki.ubuntu.com/UbuntuBugDay/Planning
[16:17] <hggdh> pedro_: I am not really available right now (taking time unpaid to be here), otherwise I would be there
[16:17] <pedro_> so we can start to coordinate
[16:17] <pedro_> also, we're looking for a target for the next week
[16:18] <pedro_> so if you have *any* idea don't be shy and add it to the wiki page
[16:18] <bdmurray> pedro_: the no package bugs are quite out of hand
[16:18] <pedro_> also put your name on the organizers section so we can make sure you're going to help with that task too
[16:19] <pedro_> bdmurray, yes and those bug days are always a total success
[16:19] <pedro_> hggdh, no worries, you're having a lot over your plate right now :-)
[16:19]  * pedro_ hugs hggdh
[16:20]  * hggdh blushes, and hugs pedro_ back
[16:20] <pedro_> ok that's all i got from here
[16:20] <bdmurray> pedro_: okay, thanks!
[16:20] <thekorn> I think this daily PPA topic is an important one to discuss, what are the plan for daily PPAs and how is managing bugs in this packages planned?
[16:20] <hggdh> +1
[16:21] <hggdh> the apport one-run (force_start=1) has just been resolved via an update to Karmic
[16:21] <hggdh> thanks goes to micahg for it
[16:21] <bdmurray> hggdh: can you elaborate?
[16:22] <hggdh> apport would not start single-time on karmic due to the change to upstart
[16:22] <hggdh> Lucid was fixed, and micahg prepared a debdiff for Karmic -- and pitti approved and uploaded it yesterday
[16:22] <bdmurray> ah, thanks to micahg then!
[16:23] <hggdh> but, now, back to dailies
[16:23] <hggdh> I think this is more complex than it seems
[16:23] <hggdh> but is extremely needed -- more so given all the blueprints we had at UDS
[16:25] <bdmurray> I'd proposed an idea at https://lists.launchpad.net/ubuntu-bugcontrol/msg00496.html
[16:25] <bdmurray> I'm not sure why that thread is on the bugcontrol mailing list but whatever
[16:26] <hggdh> bdmurray: I think it is because we are the ones to set it INVALID
[16:27] <thekorn> ok, so the proposal is: marking them all (by tagging and modifieing the title) but closing most of them
[16:27] <bdmurray> right unless there is a well known call for testing
[16:28] <thekorn> only letting the one open which are part of a public announced testing iniative of a big ubuntu team
[16:28] <hggdh> and then the owners can search for their packages. The only issue is it is not easy to search for INVALID (must go to advanced/extended/whatever)
[16:29] <bdmurray> but its still possible
[16:29] <thekorn> damn, yeah
[16:29] <bdmurray> and maybe we could make a launchpadlib script to make it easier for them
[16:29] <hggdh> good idea
[16:30] <thekorn> show-me-all-my-valid-but-invalid-bugs-because-I-used-a-PPA.py
[16:30] <hggdh> perhaps a slightly smaller name ;-)
[16:30] <hggdh> :-)
[16:31] <thekorn> ;)
[16:31] <bdmurray> show-me-all-my-valid-but-invalid-bugs-because-I-used-a-PPA-and-launchpad-doesn't-have-ppa-bug-filing.py
[16:31] <pedro_> lol
[16:31] <thekorn> yeah, exactly
[16:31] <hggdh> THAT'S better. Go for broke
[16:31] <bdmurray> tab completion!
[16:32] <hggdh> so we would need to (1) update the wiki (2) get the .py, (3) publish
[16:32] <bdmurray> and announce the policy
[16:32] <hggdh> getting the py is not a critical path, though, just makes life easier
[16:33] <hggdh> so, 4 actions, the announcement being the last. Volunteers?
[16:33] <bdmurray> and maybe make a standard response that modifies ppa reports appropriately
[16:33] <hggdh> 5 actions
[16:33] <bdmurray> and... ;-)
[16:34] <hggdh> you mentees, this is a point where you can get your hands dirty ;-)
[16:34] <bdmurray> I'll do 4 and 5
[16:34] <thekorn> hey micahg
[16:35] <thekorn> I can do (2) over the next weekend
[16:35] <hggdh> morning micahg
[16:35] <nigel_nb> anyone asked for volunteer mentees?
[16:35] <hggdh> thanks, thekorn
[16:35] <micahg> hi thekorn hggdh
[16:35]  * hggdh has
[16:35] <nigel_nb> I volunteer though u'll have to tell me what about
[16:35] <hggdh> nigel_nb: we will help
[16:35] <nigel_nb> hggdh: I'm in
[16:35] <hggdh> cool
[16:36] <hggdh> bdmurray: where would we publish it? lp-improvements?
[16:36] <bdmurray> hggdh: item 2 should likely be put in ubuntu-qa-tools and pointed to from the wiki and announcement
[16:37] <bcurtiswx_> announcement of????
[16:37] <hggdh> ok, makes sense. We can assume it will be there
[16:37] <hggdh> abd prepare the wiki accordingly
[16:37] <bdmurray> announcement of the policy regarding ppa bug reports
[16:37] <thekorn> hmm, we cannot address (2) aka the script yet, easiliy and with good performance
[16:37] <bcurtiswx_> ah, for now we've been invalidating them
[16:37] <hggdh> thekorn: what gives?
[16:38] <thekorn> the API has no way to search for tasks of a user
[16:38] <thekorn> means:  launchpad.people ["thekorn"].searchTasks()
[16:38] <thekorn> is not working
[16:38] <bdmurray> we can hash this out later but I'd imagined it would search for package bugs tagged ppa
[16:39] <thekorn> haha, ok
[16:39] <thekorn> yeah, that's easy
[16:39] <hggdh> and with a given pacakge
[16:39] <bdmurray> okay, so micahg is here!
[16:39] <thekorn> this smells a bit like bughelper ;)
[16:39] <micahg> sorry I was late
[16:40] <micahg> did you get through all the items on the agenda already?
[16:40] <hggdh> thekorn: it does indeed...
[16:40] <bdmurray> micahg: no problem since we only have 20 minutes are any of your items more pressing?
[16:40] <bdmurray> micahg: we covered wiki page editing policy and bugs for daily ppas
[16:40] <micahg> what was the decision for PPAs if I may ask
[16:41] <hggdh> we will be following https://lists.launchpad.net/ubuntu-bugcontrol/msg00496.html for now
[16:41] <micahg> ok, that sounds good
[16:42] <micahg> can we make a list of packages that PPA bugs are allowed for?
[16:42] <micahg> on the wiki
[16:42] <hggdh> and we will change the wiki to reflect that, a .py will be written to facilitate the search, published on the qa-tools, and an announcement made
[16:43] <hggdh> micahg: I would expect this will be part of the wiki changes
[16:43] <bdmurray> micahg: that makes sense
[16:43] <micahg> ok, yeah, perfecrt
[16:43] <hggdh> as long as there are few such cases
[16:43] <thekorn> but this is not a static list, right?
[16:43] <hggdh> I do not see it as static. Probably a subpage
[16:44] <thekorn> so there can be short "official" testing periods for some packages
[16:44] <hggdh> +1
[16:46] <hggdh> micahg: what did you mean with "how to connect upstream bugs in LP"?
[16:46] <micahg> well, I was wondering about bugs that their upstream uses LP for bug tracking
[16:47] <hggdh> ah, good one
[16:48] <hggdh> bdmurray: how do we deal with upstream-at-LP? Do we still open an Ubuntu bug and an Upstream one? Does it even make sense?
[16:48] <thekorn> I don't get it, maybe I'm too slow, as usual ;)
[16:48] <bdmurray> hggdh: it depends on the upstream.  for ubiquity and update-manager no
[16:49] <bdmurray> hggdh: for terminator or something used by another distribution yes
[16:49] <andresmujica> hmm, i believe that usually the upstream has a project inside LP, so is a matter to add a task for the project and for the ubuntu package
[16:49] <bdmurray> andresmujica: yes
[16:49] <hggdh> so ubiquity bugs should be open against which?
[16:49] <hggdh> (for example)
[16:49] <bdmurray> hggdh: only the Ubuntu package not the project
[16:50] <hggdh> do we have a list of these packages? It would help, I think
[16:50] <andresmujica> bug 422101
[16:50] <ubot4> Launchpad bug 422101 in ubiquity "initramfs-tools package seems to fail postinstall on armel" [Undecided,Fix released] https://launchpad.net/bugs/422101
[16:50] <bdmurray> speaking of an awesome thing to do would be to review https://bugs.edge.launchpad.net/update-manager and open ubuntu tasks
[16:50] <andresmujica> this could be an example
[16:50] <micahg> so we open an upstream task vs bug?
[16:51] <mvo> bdmurray: great idea!
[16:51] <bdmurray> mvo: and maybe disable bug filing when finished?
[16:51] <thekorn> argh, this "hot bugs" overview sucks, I thought for one seconds update-manager only has 10 open bugs ;)
[16:53] <bdmurray> so generally speaking there should be a bug opened against the upstream project unless they are Ubuntu only packages like ubiquity and update-manager
[16:53] <bdmurray> There is no list of those packages that I know of
[16:54] <thekorn> what is the reason for this exception?
[16:55] <bdmurray> the package doesn't exist anywhere else and its just extra work to close the upstream task
[16:55] <thekorn> it complicates everything, and I personally don't see the positive outcome
[16:55] <bdmurray> I believe that ideally the project wouldn't allow bug filing / use lp for bug tracking
[16:56] <micahg> bdmurray: that can be set by the project owner
[16:56] <thekorn> no ideally launchpad would also close "upstream" tasks when sth. like (LP: #123456) is found in changelogs
[16:57] <micahg> thekorn: that doesn't make sense as we might have a patch that upstream doesn't
[16:58] <thekorn> hmm, good point
[16:59] <micahg> bdmurray: if those project are set for no bug tracking, a note should be on the project homepage to use the ubuntu package for bug tracking
[16:59] <micahg> also, what if another distro wants to adopt one of those packages as well
[16:59] <bdmurray> micahg: well, to use 'ubuntu-bug packagename' ;-)
[17:00] <bdmurray> micahg: well, then bug filing would be allowed again
[17:00] <micahg> bdmurray: ok
[17:01] <micahg> as we're out of time, I just wanted to make a quick note the single apport crash reports is fixed in -proposed
[17:01] <micahg> for karmic
[17:01] <thekorn> I think any policy makes sense here, as long as this policy is explained and announced somewhere
[17:01] <bdmurray> micahg: hggdh told us - that's outstanding!
[17:02] <micahg> I'm assuming it's ok to ask people to enable -proposed for the moment to generate the crash report
[17:02] <hggdh> micahg: the only thing is -proposed *may* be dangerous generically
[17:03] <hggdh> probably not, though, one hopes
[17:03] <bdmurray> well, it shouldn't be but yes ;-)
[17:03] <micahg> so we should wait until it reaches -updates before asking then?
[17:03] <bdmurray> I'm sure we can get the sru verification fast tracked
[17:03] <hggdh> we can fast-track it, yes
[17:03] <micahg> ok
[17:03] <hggdh> micahg: what was the bug #?
[17:04] <micahg> bug 476513
[17:04] <ubot4> Launchpad bug 476513 in apport "/etc/default/apport comment outdated" [Low,Fix committed] https://launchpad.net/bugs/476513
[17:04] <hggdh> thanks
[17:07] <bdmurray> Thanks everyone!
[17:08] <hggdh> am I still here?
[17:08] <micahg> hggdh: yep
[17:09]  * micahg goes to read the beginning of the meeting
[17:09] <hggdh> oh, OK. bloody wifi is slow as molasses (but then what could I expect from wardriving?)
[17:09] <thekorn> alos freenode is on fire today ;)
[17:10] <thekorn> ok, thanks everybody
[17:10] <thekorn> I'll write down some mmeting notes later today, ok?
[17:10] <hggdh> since this early morning (about 0900 UTC)
[17:10] <hggdh> thekorn: thank you
[17:11] <micahg> ah, all caught up
[17:15] <hggdh> yeee another netsplit
[17:24] <mvo> bdmurray: (sorry for the delay) - yes, disabling upstream tasks of u-m is a great idea
[17:24] <bdmurray> mvo: no problem, thanks for getting back to me
[17:40] <nperry> bug #493384
[17:40] <ubot4> Launchpad bug 493384 in nvidia-graphics-drivers-173 "xorg crashes at start with nvidia drivers. Karmic Koala. Nvidia Drivers." [Undecided,Invalid] https://launchpad.net/bugs/493384
[17:40] <nigel_nb_> hggdh: meeting is over?
[17:40] <nperry> Whats the best next step
[17:41] <nigel_nb_> I think i missed the ending due to netsplits
[17:41] <hggdh> nigel_nb_: yes, it is over. freenode is having a lot of netsplits, it seems
[17:43] <nigel_nb_> hggdh: aw, too bad, anyway what did I volunteer for?
[17:43] <nigel_nb_> I got split after that
[17:43] <hggdh> nigel_nb_: heh. You volunteered to update the wiki pages abou how we will deal (at least for now) with PPA bugs
[17:44] <hggdh> nigel_nb_: and thank you, BTW
[17:44] <nigel_nb_> hggdh: okay, that connects with the link the lists.launchpad mailing list, correct?
[17:45] <hggdh> yes -- partially. We need to state that all PPA bugs (except for a list of them) will (1) be tagged PPA; (2) have the title prepended with [PPA]; set to INVALID
[17:46] <nigel_nb_> hggdh: why are we setting to invalid?
[17:46] <nigel_nb_> so what the author can deal with it?
[17:46] <hggdh> because they are not real Ubuntu bugs -- an Ubuntu bug is a bug in an official Ubuntu package
[17:47] <hggdh> at the same time, we cannot leave then off, given all the push to PPA usage
[17:47] <hggdh> but LP still does not support PPA bugs
[17:47] <nigel_nb_> so we mark them invalid, but tag them and prepend PPA so that the authors can look for it or a script can be generated for them, correct?
[17:49] <hggdh> development will provide us with a list of PPA packages that are to be accepted (packages in transition/turmoil, like -- say -- X video drivers). We expect this list to be dynamic
[17:49] <nigel_nb_> okay :)
[17:49] <nigel_nb_> so where should I update?
[17:50] <hggdh> what you can do, if you want: look at the wiki bugsquad/bugs pages, and find where this could be put; suggest a change, and -- so that you will not feel roasting alone -- show us the changes
[17:50] <hggdh> and we will discuss, change, propose, accept in group
[17:51] <nigel_nb_> suggest a change on the mailing list?
[17:51] <hggdh> you can, if you wish. Or propose here, if no response, then ML
[17:52] <hggdh> here, via pastebin, for example
[17:52] <hggdh> or a temp page showing the changes
[17:52] <nigel_nb_> I'll do it on my sandbox
[17:53] <Wazzzaaa> Hey, I have a bug in Karmic
[17:53] <Wazzzaaa> bug #460654
[17:53] <ubot4> Launchpad bug 460654 in linux "speakers don't mute when plugging in a headphone" [Undecided,New] https://launchpad.net/bugs/460654
[17:53] <hggdh> thank you. If in doubt, ask. We will be more than happy to help. And we are very happy you volunteered :-)
[17:53] <Wazzzaaa> I'm willing to do some research in finding the cause of this bug.. But I do not know where to start
[17:55] <hggdh> Wazzzaaa: I am sorry, I personally do not do sound, but perhaps somebody else here does
[17:55] <Wazzzaaa> ok :)
[17:56] <Wazzzaaa> Im a programmer, and Im even willing to fix this bug if I can find it. Do you have pointer to sites which I can read ?
[17:56] <nigel_nb_> Wazzzaaa: it is a known issue
[17:56] <Wazzzaaa> ok
[17:56] <Wazzzaaa> so....?
[17:56] <nigel_nb_> I believe the audio team will get back to you on that one
[17:57] <Wazzzaaa> hehe, I hope it is fixed in lucid
[17:57] <nigel_nb_> I think it will be fixed in the next kernel relesae
[17:58] <Wazzzaaa> ok, is it a kernel issue?
[17:58] <nigel_nb_> no, its a alsa issue
[17:58] <nigel_nb_> what make is your laptop?
[18:10] <Wazzzaaa> make?   it is a desktop...
[18:17] <nigel_nb_> Wazzzaaa: daniel knows the details, dont worry he'll look into it when he gets time
[18:17] <nigel_nb_> he's kinda over worked, so dont worry if it takes time
[18:18] <Wazzzaaa> ok, I'll idle here...
[18:18] <Wazzzaaa> thnx voor the help
[18:19] <BUGabundo> boas
[18:41]  * BUGabundo is back
[22:04] <maco> umm im confused. what does openafs have to do with bug 453365 ?
[22:04] <ubot4> Launchpad bug 453365 in dkms "dkms should start before gdm if needed for video driver" [Undecided,In progress] https://launchpad.net/bugs/453365
[22:07] <micahg> maco: https://bugs.edge.launchpad.net/ubuntu/+source/dkms/+bug/453365/comments/9
[22:07] <ubot4> Launchpad bug 453365 in dkms "dkms should start before gdm if needed for video driver" [Undecided,In progress]
[22:08] <maco> micahg: oh. ok. i should click through instead of just going by bugmail i guess...
[22:08] <maco> i was just going "openafs... video... what?"
[22:08] <maco> micahg: thanks. and sorry
[22:08] <micahg> yep :), each task says who opened it, so you can look for their comment


[23:08] <thumper> \o/ small milestone passed
[23:09] <thumper> machine agent for the bootstrap "machine" of the local provider starts and works (after more munging)
[23:09]  * thumper works on next step, getting the identity for containers working