[00:00] http://paste.kde.org/492536/ [00:00] ! [00:00] phew [00:00] copying from konsoel is not bugged at all [00:01] fglrx-- [00:31] JontheEchidna: -v or ../merge-buildpackage for merges please :) [00:31] oops [01:10] JontheEchidna: thoughts on what should be autocompleted in a script for simple kde packaging? [01:10] taking a template and stuffing it in the source [01:10] hm [01:11] dh $@ --with kde --parallel --dbg-package=$pkg-dbg [01:35] JontheEchidna: I do disapprove that last argument [01:35] as I have said countless times ... dbg packages should be injected automagically [01:35] our current approach does not scale [01:36] enjoy scripting that - or wait until I'm done doing that for neon [01:36] which is on place ~100 in my todo list [01:36] 100 being the best? [01:37] hrm, dbgsym support is available in PPAs (don't know how to use it though) [01:37] refactor your todo :P [01:37] no, 1 :P [01:37] if dragon were a todo and it had 100 entries I would rewrite it :P [01:37] oh hold on, I should rewrite dragon [01:37] oh, nvm, I did that already [01:37] see, I do things before they even get on my todo :P [01:37] using dbgsyms wouldn't make much sense, as we would mostly duplicate our symbols then [01:37] micahg: oh is it? [01:38] yofel: we can throw away our packages [01:38] in fact that is simpler scripting :) [01:38] apachelogger: I don't know that it's enabled (maybe ask the launchpad folk) [01:38] * apachelogger points out that only using dbgsyms would make kubuntu-debug-installer perfect [01:38] find out how to use it then. I know it's available for OEM archives [01:39] they might not want ot give us dbgsyms because we like to eat the disk space ^^ [01:39] I've once tried to make pkg-create-dbgsym and pkgbinarymangler produce dbgsyms in PPA's but failed [01:39] apachelogger: it would be perfect once you do that, AND make it auto-add the dbsym archive for official packages [01:40] yofel: yes, pitti added that support a while back [01:41] yofel: you do not want the ddeb archive on all the time :P [01:41] yeah, I was subscribed to the bug report for that. I stopped following after it was clear that it won't be enabled for the wide audience [01:41] but yeah, the idea would be to only ever use dbgsym [01:41] apachelogger: sure, still requires auto-add, install, auto-remove then [01:41] the reason it does not do that right now is because you'll run into incompatibility clashes [01:41] leading ot overall crappier backtraces [01:42] also it goes whooop when you add our PPAs and suddenly foo has a higher version than the dbgsym [01:42] seriously though, what's so hard about just adding a dbg package in control? [01:42] the rules part can be scripted fine [01:42] it does not scale [01:42] it takes less than a minute, and requires pretty much no changes later... [01:43] pretty much != nil [01:44] I'll agree with that, I'm just saying that it scales RIGHT NOW. I did say I want to add that for neon [01:44] our packaging isn't flexible enough there [01:52] yes, but it is the wrong way to look at it... I can spend more time doing it proper right now completely removing the need to ever think about it again [01:52] vs. doing it latter and perhaps having to remove the dbg packages from all 30000 packages created in the mean time [01:54] ack then [01:55] were you planning to add that to your simple packaging script, or did you mean that pkg-kde-tools should take care of that at build-time? [01:58] talk to lunchpad people -> no dbgsyms for us -> hack pkg-kde-tools -> fail to do that -> keep manually adding dbg packages add appropriate functionality to skeletor [01:59] ok [02:08] omg, it's getting light again [02:08] meh [02:09] that's the sun [02:09] it provides warmth for plants and such [02:17] what a silly invention [02:19] you only say that because you're not a plant [02:34] hm, here some bird is starting to get annoying outside [02:35] * yofel is off to bed [02:36] gosh i've got the same problem. the birds won't stop tonight [02:41] you people and your European time zones [02:51] const QString summary = i18n( "Resource %1 is broken. This resource is now %2", instance.name(), instance.isOnline() ? i18n( "online" ) : i18n( "offline" ) ); [02:51] this is too funny [02:51] how broken can it be and still be online [02:54] lol, no way that will translate [02:56] http://www.youtube.com/watch?v=qB1_DDv7iF0 [02:56] all I gotta say [03:02] Oo -.- :O :( [03:05] akonadi is a big fat spooky monster [03:25] yofel: It appears that the password has been changed as I can't get in anymore either. [03:25] ryanakca: Are you still webmastering for us? Any idea about the password change? [03:42] * apachelogger sighs [05:40] BUG [05:40] pfft, no one around [05:40] how boring [07:25] good morning apachelogger [07:26] yo jussi [07:26] apachelogger: not so boring then :D (unless you consider me boring) [07:27] look at the time stamps :P [07:27] I just got pissed at unity and moved back to kde [07:27] lol [07:27] you were using unity? [07:27] spooky [07:28] apachelogger: yeah, but no one said anything, I just assumed you were sitting there twiddling your thumbs :P [07:28] I had to try it out [07:29] * apachelogger spent his time better and tried win8 :P [07:29] lol [07:30] Ive got cookies for anyone who recreates my quassel darktheme for irssi... [07:33] morning friends [07:39] Riddell: youre back!! :D [07:39] jussi: oh I couldn't leave for long :) [07:41] Riddell: so you getting decent speed internet made me all jealous and so I moved to helsinki and got propper internet... [07:41] erk, really? [07:42] I wouldn't want you to relocate your family and job just because you're jealous of me! [07:42] yeah, had to move for work sadly [07:42] but at least the internet is good [07:42] (I pay €8.90 for 100mbit) :D [07:43] now I'm jealous [07:43] is that government subsidised somehow? [07:43] no [07:44] its just we have fibre to the building, and the rental cost includes 10/10 [07:44] so the upgrade to 100/10 is only a minimal cost [07:45] mm, interesting [07:45] well you're only a short ferry ride away from akademy now [07:48] yeah, Im going to try get there for at least a day or so - dont think I can get time off work for it [08:13] didrocks: do gnome packagers get the tars a few days before release? [08:13] I seem to remember that was changed a couple of years ago [08:14] Riddell: no, it's all public, the announce for the release is on Wednesday, but most of tarballs are posted to the GNOME ftp (there is a ML to subscribe) started Monday [08:28] Riddell: it doesn't make sense to keep it embargoed if half the people having access don't play by the rules anyway [08:32] apachelogger: it's always been a contentious issue for KDE [08:32] but generally it works well [08:49] didrocks: doesn't that lead to lots of comments on news sites and user forums "gnome 3.2 is released, why don't I have packages yet?" [08:50] Riddell: no, never saw that for the past 6 years (when this process was built upon) [08:51] tarballs are coming one after another in the ftp, we are pushing at the same speed. Finally, the announce is done on wednesday by the GNOME release manager and we mostly have the stack up to date in ubuntu [08:53] * apachelogger blinks [08:53] didrocks: so the packages are in Ubuntu before they are announced as released? [08:53] Riddell: yeah [08:54] afiestas: check out t3 and 1: http://paste.kde.org/492614/ [08:54] same for other distros [08:54] compleltely wicked [08:54] didrocks: doesn't that lead to issues with users reporting bugs to upstream before they're announced as released? [08:54] Riddell: doesn't matter as they are the final tars already [08:55] Riddell: from Monday to Wednesday, the timing is short and the tarball is here [08:55] sometimes, that enables to spot something really bad [08:55] and so the module maintainer can release a .1 [08:56] didrocks: what about bugs found by packagers? kde has about 5 days for packagers to go "err this app needs an unreleased libfoo" or "it doesn't compile with gcc 10.1" [08:57] Riddell: that's another case where we told GNOME what went wrong (the release manager is doing the same at the same time as well and talk to the maintainers), this lead to release a .1 when a real error occurs. If the new nautilus needs the new glib, we just want for the glib tarball even if nautilus tarball is already posted [08:57] s/want/wait/ [08:57] didrocks meant: "Riddell: that's another case where we told GNOME what went wrong (the release manager is doing the same at the same time as well and talk to the maintainers), this lead to release a .1 when a real error occurs. If the new nautilus needs the new glib, we just wait for the glib tarball even if nautilus tarball is already posted" [08:57] fun, didn't know about the kubotu ;) [08:58] didrocks: can I paste bits of this conversation to kde-release-team? there's a discussion happening about these issues [08:58] Riddell: of course, no worry :) [08:58] thanks [08:58] yw [09:32] * jussi notes his post to the ml :D [09:42] jussi: which post? [09:42] ooh a new councillor [09:45] :) === Blizzzek is now known as Blizzz === seaLne_ is now known as seaLne [10:26] I'll test a script that mass uploads point release to the ninjas ppa so please don't upload any KDE 4.8.4 packages [10:32] debfx: nice! [11:17] hey agateau bug 998630 the fix you released for the plasma widget menu bar doesnt fix the crash, i got another back trace which i submitted in the bug, but now i have no menu bar what so ever and for some reason the menu bar is taking the focus of my chromium tabs. what other information can i provide you with to help narrow this issue down even further [11:17] Launchpad bug 998630 in plasma-widget-menubar (Ubuntu) "plasma netbook shell crashes on kubuntu 12.04 and 12.10" [Undecided,New] https://launchpad.net/bugs/998630 [11:19] JontheEchidna: has the jockey replacement discussion reached any conclusion in your mind? [11:20] Riddell: yes, I believe I can write a KDE frontend that utilizes the UbuntuDriver python bits that Albert Malone/Pitti wrote. [11:21] and once the dependency situation is worked out for ubuntu-drivers-common, it should be all good [11:24] JontheEchidna: nice, a frontend integrating with muon or standalone? [11:25] Riddell: I was thinking about making a "Drivers" KCM Module for the Display and Monitor KCM in Sytem Settings, though we (Kubuntu Dev) should definitely discuss the best venue for presenting a GUI for restricted drivers. [11:26] yep, thanks for taking it on [11:28] no problem. :) [11:29] off to start my morning commute, so bbiab [12:19] eagles0513875: answered on report [12:27] thanks agateau :) [12:30] agateau: should i remove my .kde folder as well or just restart for now? [12:41] eagles0513875: restart should do [12:41] ok :) give me a few moments [12:45] Hiyas all [12:45] hey BluesKaj :) [12:46] hi eagles0513875 [12:48] agateau: im eating a single line and nothing is starting QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave [12:49] eagles0513875: that line should be ignored, all kde apps produce it these days :/ [12:49] ok well its not outputting anything else agateau and still no menu bar [12:50] eagles0513875: and do you get a menubar if you downgrade to 0.1.17, [12:50] ? [12:50] agateau: stupid question here how can i downgrade it? [12:51] eagles0513875: how did you upgrade? [12:51] apt-get update && apt-get dist-upgrade [12:51] prior to you releasing the fix i was getting a menubar [12:51] and which version of plasma-widget-menubar is installed? [12:51] just the random crash with the trace in the report [12:52] 0.1.17 [12:52] so you did not get the new version: I marked it as fix-released on the upstream project, meaning I released a new tarball. It has not been packaged yet. [12:53] ahh ok :) where can i get the tar ball so i can package it? [12:53] https://launchpad.net/plasma-widget-menubar [12:54] agateau: curious question why is there a 2nd package that is affected but its new on the report? [12:54] eagles0513875: the first line is the upstream project [12:54] the 2nd line is the package for the project in ubuntu [12:54] ahh ok :) [12:55] thanks agateau :) [12:57] agateau: will keep you posted if 18 resolves the problem :) [12:57] eagles0513875: thanks [12:58] agateau: I'm guessing there are compiling instructions in the tarball? [12:58] eagles0513875: should be [12:58] :) ok [12:59] eagles0513875: I must confess I am not tracking this project very closely [12:59] agateau: no problem bro :) I'm just trying to get my hands dirty with contributing and helping out with kubuntu [13:00] eagles0513875: why not let someone who knows how to package it actually package it so you can test it [13:00] eagles0513875: that way it's a sane test [13:01] ikonia: taking this to offtopic [13:01] err why ? [13:01] it's relevent [13:02] eagles0513875: be aware that if you don't use a package then the test could be void as how you build it blindly maybe different from how the package is put together [13:03] ikonia: i need it rather urgently packaged though cuz as we speak i have no menu bar what so ever [13:03] eagles0513875: ok, so find someone who can package it for you [13:03] ok [13:03] rather than a blind test [13:03] * eagles0513875 hops into the packaging channel [13:03] no no no [13:03] that means not hitting random people on irc [13:03] ok [13:04] please stop expecting everything to be fixed "now" on "irc" [13:04] you've got a fix released upstream, so who is responsible for building the KDE packages ? [13:04] the kubuntu kde team [13:05] depends what you mean by poking. But as a note, for kde related stuff better poke me here than in -packaging. And I don't have time right now === yofel_ is now known as yofel [13:05] yofel: ah, so you would be one of the members responsible for packaging it [13:05] perfect, [13:06] yofel: ok :) would you like the bug number as to what needs to be packaged for when you get a moment? [13:06] eagles0513875: can you not assign it to the KDE team [13:06] so that a free member can pick it up for the next stage of testing ? [13:06] rather than again just poking people constantly on IRC [13:06] update the bug with the information and assign it to the right team [13:06] ikonia: from the looks of the bug report the fix was released upstream and it is new for downstream so i don't know if that still would go to the kde team [13:07] https://bugs.launchpad.net/ubuntu/+source/plasma-widget-menubar/+bug/998630 [13:07] Launchpad bug 998630 in plasma-widget-menubar (Ubuntu) "plasma netbook shell crashes on kubuntu 12.04 and 12.10" [Undecided,New] [13:07] eagles0513875: the fix has been released as you where shown above [13:07] so that fix now needs packaing into the kde package with the right build options/process [13:07] ok [13:07] so the team that would do that would be.....$X ? [13:07] ikonia: the kde team but obviously set the down stream ubuntu package to needs packaging? [13:08] eagles0513875: right so which is the kubuntu team that builds the packages [13:08] got it :) [13:08] stop depending on just asking people on IRC [13:08] the bug process is there so it's tracked and managed [13:08] and "I'll poke on irc" [13:08] you can't expect everything "now" [13:08] no point until you've managed the bug [13:09] ok [13:09] getting a bit tedious to have to keep asking you to work the bug through rather than just asking people on irc to fix it for you [13:09] ikonia: there are two teams kubuntu testers or users [13:09] remember, this is one of the reasons you where banned in the past from all the development channels for just hassling people [13:09] please don't get into that again, work the process/bug through [13:10] kubuntu-dev would be the relevant theam, but I don't know if the assignment would actually do something - try it [13:10] *team [13:10] ok yofel [13:10] no match [13:10] only two kubuntu teams I'm seeing are testers and users [13:10] eagles0513875: make sure you update it with good info explaining that you are ready/willing to test the package and the upstream source is updated [13:11] searching for kubuntu-dev gives me "Kubuntu Developers (kubuntu-dev)" [13:11] ikonia: will do [13:11] y [13:11] o [13:11] yofel: odd not for me O_o [13:11] o. [13:11] if you have a 64-bit install you can try this package I whipped together: http://www.2shared.com/file/f_PReX8q/plasma-widget-menubar_0118-0ub.html [13:11] eagles0513875: also look in the team list see who is a member, you can then prod them appropiratly if "needed" not as a first resort [13:11] ok [13:11] jtechidna: 32bit sadly [13:12] meh, oh well [13:12] I don't have access to my private signing key handy so I can't upload to the PPA or the archive [13:13] for now you can just remove the widget from plasma, and restart any applications without menus. You'll at least have a menu that way [13:14] eagles0513875: was is only for some applications? [13:14] jussi: the crash was occurring quite often when listening to music on my external hard drive then at one point it randomly happened at shut down [13:15] agateau: Im curious, what happens with the ctrl+m menu hiding thing in kde? does it hide the menu in the menu bar? [13:15] yofel: where are you clicking to assign a team to the bug? [13:16] jussi: if the application supports it, it show/hides the menubar [13:16] eagles0513875: the yellow button where it says "unassigned" for the package task [13:16] jussi: whats happening now after running todays updates is that the menu bar seems to take the focus from chromium tabs and i end up with chromium tabs where the menubar should be [13:17] yofel: could it be i don't have sufficient rights or something to add the kubuntu-dev team to the bug [13:18] apol: yeah, we should just filter out the multiarch-dupes in app backend init [13:18] could actually be... I'm in too many teams to confirm that [13:18] jtechidna: good :) [13:19] that was just me being a bit short-sighted when I originally did that filter :P [13:19] jtechidna: are you ok if I just change this on my branch? [13:19] or you prefer to put it in master already? [13:19] eh, it's not super important to put in to master right away [13:20] so go ahead and just keep it in the resources branch. [13:20] * apachelogger waves fist [13:20] akonadi is so implicit if you start writing explicit code it will go kaput, that is how implicit it is [13:20] oh fun, launchpad gained status/importance desriptions in the UI. [13:20] *descriptions [13:21] apol: the good thing is that ~ 40% of the packages on an amd64 system are actually the i386 versions of packages that are also available natively, so this should help with init times + memory usage [13:21] :) [13:21] yep [13:22] apachelogger: i wish it wasn't so closely integrated with a number of kde apps such as kopete and conversation. [13:23] that does not even make sense [13:24] afiestas: ping [13:26] is anyone able to reproduce bug 966913 with a new user? [13:26] Launchpad bug 966913 in kdepim (Ubuntu) "Akonadi contact resource wrong defaults" [High,Confirmed] https://launchpad.net/bugs/966913 [13:26] that is 3 distinct errors: a) contacts dir not there b) invalid maildir c) boken resource [13:30] I've usually had things ~work~ with a new user. akonadi just reliably barfs on upgrades from kdepim << 4.6 [13:30] brb [13:31] yofel: that doesn't help me fixing the bug tho? :P [13:31] or rather validate my fix [13:31] true :P [13:31] * apachelogger fails to produce error b now [13:32] yofel: also FWIW, not every random contributor becomes MOTU [13:32] ScottK: I haven't done any webmaster work since the wiki theme. I was unaware of the password change. Is there something that needs doing? I'm still interested in posting announcements and whatnot [13:33] apachelogger: well, leaving single package PPU's aside, someone will still have to sponsor the upload [13:33] and I'm not particulary interested in switching to UDD to resolve this [13:34] * apachelogger fails to compute [13:34] yofel: what's the conern ... that MOTUS can generally upload or that they would have to follow our workflow? [13:34] * Peace- -.- 27 degree [13:35] apachelogger: that if they upload, our branches get out of sync because they don't have commit permissions. That's currently only for ~kubuntu-members and ~ubuntu-core-dev [13:35] * apachelogger should blog about bluray in dragon [13:36] yofel: well, I don't see the problem in adding motu to the packagers team [13:36] that is to say, core-dev or motu they'd actively have to use our branches to prevent the sync problem [13:36] uhm, I'm not particulary against it, I just wanted to bring it up so it's not forgotten [13:36] which is not even a given with full UDD [13:36] yofel: kk [13:37] UDD is another thing I'm concerned about. I don't like it, but most other people seem to use it [13:38] * apachelogger wonders what to get for lunch [13:38] * yofel catches up on the kde-release discussion [13:38] yofel: that is their problem [13:39] if they want to use a flawed workflow,that is very much their decision ;) [13:41] JontheEchidna: I didn't go through this yet and just realized [13:41] I'll have to remove the QApt:: signals from the ApplicationBackend [13:42] do we need to upload bindings packages even though they didn't change? [13:42] apol: just install kubuntu, and execute Kontact with the new installation [13:42] reproduced it just right now [13:42] and iirc happens with new users too [13:43] afiestas: wrong ping (I hope :D) [13:43] debfx: no point in doing that IMO [13:43] apachelogger: ping redirection :p [13:44] the less we update the better [13:44] afiestas: if you get a minute, please build kdepim-runtime from master and see whether it fixes all 3 akonadi setup issues [13:44] yofel: I ask because kdelibs gained new methods so maybe they need to be updated [13:45] hm, good point [13:45] apachelogger: I won't be able, maybe with a package and test it in the kubuntu I have on the virtual machine [13:45] and if so, which ones need to be updated [13:45] pff [13:45] which reminds me [13:45] we also need a SRU script [13:46] anyone remember where the kubuntu council voting rules are written? [13:47] Riddell: did we formalize them? [13:49] argh, I still dont have oxygen widget style anymore [13:49] Riddell: ah you mean quorum and whatnot? [13:50] apachelogger: I've a half working sru script done [13:50] question is whether we really need one but per package affected... [13:50] s/but/bug/ [13:50] yofel meant: "question is whether we really need one bug per package affected..." [13:51] yofel: isn't a bug against meta-kde enough for SRU tracking? [13:51] that's what I'm asking. I tried to do one bug with all packages affected, but launchpad errors out if you have that may nominations [13:52] so that leaves either one simple bug, or one bug per package [13:52] one bug would be a lot easier, and the only sane way to script stuff [13:52] yofel: seek approval from ubuntu-sru team I guess [13:52] also I was thinking about individual SRUs outside the scope of a KDE release [13:52] unless you make the package update and upload script also file the sru bug to get the bug # [13:53] ryanakca: I don't know why yofel was trying to do something with the web site, but if the password is changed without people knowing, I think it's concerning. Maybe Riddell knows. [13:53] apachelogger: individual SRU's need an amount of information in the description that makes writing a script for it unpractical IMO [13:53] I'd say we use one bug unless ~ubuntu-sru strongly disagrees [13:54] ScottK: the link to the release announcement on the download page is broken [13:54] We've always used one bug. [13:54] +1 for that then [13:55] apachelogger: yes [13:55] I'll leave my script somewhere as proof-of-concept if it's needed in the future [13:55] Riddell: Can you get access to the web site? Several of us with (what we think is) the password can't. [13:55] ScottK: trying [13:55] Thanks. [13:55] Riddell: might have gotten lost [13:55] I think the password is actually right, but 'admin' has no admin permissions anymore [13:56] though I only have a blurry recollection of us having that stuff written down ... so it might well be that I am thinking of other voting rules (from another council) ^^ [13:56] ScottK: no :( [13:56] yofel: I can't log in as admin [13:57] * apachelogger wonders what to have for lunch [13:57] afiestas: x64 or x86? [13:57] 64 [13:57] apachelogger: kaiserschmarr'n [13:57] hmmmmm [13:57] that idea is not half bad [13:58] Riddell: So who can do a password reset? [13:58] ScottK: canonical sysadmin I guess [13:59] ScottK, yofel, ryanakca: shall I file an RT request to work out what is going on? [13:59] Riddell: Yes. Please. [14:00] oh boy oh boy, nowadays you even need to turn on -updates to build stuff -.- [14:01] Regarding voting rules, I ran the last election and all I did was set up the ballot on civs with the names of qualified nominees, feed it a list of email addresses, and hit send. [14:01] It's pretty much automatic after that. [14:03] yofel: how does one pbuilder with -updates? [14:03] ScottK: it's for writing this constitution https://wiki.kubuntu.org/Kubuntu/Council [14:03] ScottK, yofel, ryanakca: rt sent [14:03] login to pbuilder with --save-after-login, edit sources.list, save [14:03] Thanks. [14:03] dafuq [14:03] but england is on holiday until wednesday so don't expect a fast reply [14:04] that's what I do [14:04] using OTHERMIRROR might do what you want too [14:04] I've only tried that for neon so far, where it adds the ppa on creation fine [14:05] Riddell: thanks [14:05] yofel: good point [14:09] yofel: have you bumped any build-depends other than kde-sc-dev-latest in the past for KDE point releases? [14:10] usually not. If we script the updating, we could bump the depends for anything kde-sc-dev-latest breaks. Then the packages would be in dep-wait on launchpad and we wouldn't have to constantly retry manually [14:10] for point releases nothing should break? [14:11] and if it does I'd say there is a policy violation to be looked into [14:11] I meant the versioned breaks in kde-sc-dev-latest, as that's the point of the package [14:11] yofel: yes, but it makes no difference to the point release if you build against kdelibs .1 or .2 [14:12] kde-runtime-4.8.4/CMakeLists.txt: [14:12] find_package(KDE4 4.8.4 REQUIRED) [14:12] yes, ti does [14:12] pfft [14:13] *it [14:13] complaint to kde-release plz [14:13] that does not make any sense [14:13] or maybe I am not thinking of a rationale [14:14] for example smokdekde build-depends on smoke-dev-tools (>= 4:4.8.1) [14:14] I'm not sure if it always needs to be the latest version [14:14] Riddell: Re the consitution and elections: I'd say something like: "One of the Kubuntu Council members not up for re-election in the current year will run the election for new Kubuntu Council members. All Kubuntu members are eligible to vote. Elections will be conducted using the Condorcet method (currently using the CIVS system) after a period of open nominations. The top ranked nominees win. In the event of a tie for the last seat [14:14] available, a runoff election will be held with just those two candiates." [14:15] probably not, and I might even have changed that once without need to be done in time [14:16] yofel: shouldn't we add those to kde-sc-dev-latest then? [14:16] Riddell: https://wiki.ubuntu.com/KubuntuMaverickCouncil [14:16] all I can find [14:16] the debian team hasn't done so, so I'm not sure if we need to [14:19] Riddell: Thanks :) [14:19] well we can also hardcode a list of packages that need to be bumped in build-depends [14:25] Riddell: I can only find quorum definition on kubuntu-dev memberships [14:26] perhaps that is the one you think of? [14:26] apachelogger: I just wrote the same thing to the ML. [14:27] though I think we at least once referred to some other council's rules stating a quorum of 3 [14:27] that is because the councils of 6 had a quorum of 3 [14:29] * apachelogger needs to consult with the kitchen about the possibility of kaiserschmarrn for lunch [14:30] afiestas: http://people.ubuntu.com/~apachelogger/src/ uppng kdepim-runtime*deb ... should be done in about 15 minutes [14:43] right now my script generates this report: http://felix.fobos.de/kubuntu/sru/ [14:44] debfx: cor that's awfae clever, how did you do that? [14:45] Riddell: I'll push the script to a branch soon [14:45]