[07:32] yofel, Riddell: because I am a lazy bum never doing the fun things... how exactly does post-release KDE release SRUing work in terms of packaging branches? [07:32] do we branch trunk into something series specific? [07:35] shadeslayer: http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/marble/revision/110/debian/marble.install bug 1312104 consider yourself shouted at [07:35] bug 1312104 in marble (Ubuntu Utopic) "Marble Menu Squashed/Unreadable" [Critical,Triaged] https://launchpad.net/bugs/1312104 [07:38] something looks awfully crapped with the marble packaging [08:07] good morning [08:31] ScottK: bug 1312104 ... marble package contains marble and marble-mobile, for utopic I split out marble. should we split for trusty as well (preserving dependencies) or should we go the less intrusive route of also applying the split to trusty? the non-split option would be to hide the marble-mobile desktop file to avoid confusion (which would also not be much worse because marble-mobile seems jolly broken with desktop qml components) [08:31] bug 1312104 in marble (Ubuntu Trusty) "Marble Menu Squashed/Unreadable" [High,Triaged] https://launchpad.net/bugs/1312104 [08:35] hrm, anybody about to confirma a bug for me? [08:35] (Kontact users) [08:50] apachelogger: we mostly don't use branches for SRUs [09:05] Riddell: how does that work with making !SRU changes on the trunk packaging? [09:05] like say, splitting pacakges [09:06] apachelogger: the bzr branches are for development releases [09:06] so if it's for utopic put it in bzr [09:10] shadeslayer: new testers needed for bug 1289600 [09:10] bug 1289600 in qt4-x11 (Ubuntu Saucy) "Fix for crashes due to ubuntu-specific accessibility patch" [Undecided,Fix committed] https://launchpad.net/bugs/1289600 [09:26] anyway, the bug is this: if you use the search in kontact(email) then use the lock to make search persist even when changing folders, it does not re-search when you move folders. anyone else get that? [09:44] Riddell: so 4.13.1 SRUs are created on the packages from trusty rather than from any bzr? [09:46] apachelogger: oh backporting the whole SC into -updates I don't know about, backporting into PPA we don't have branches and SRUs for bugfixes we don't tend to have branches [09:56] yofel: ^? [10:02] apachelogger: hm, since last release we do have branches, although I'm not sure whether it's worth the trouble [10:02] if you're not against it I would revert the changes in the tools for that [10:03] then we would only have devel in bzr, and everything else would be just packages [10:06] [00:38:55] -*- lisandro gives everyone Qt 4.8.6 [10:06] :D [10:06] yofel: fine by me, I was just wondering whether we roll the SRUs from bazaar cause that obviously would be bad ^^ [10:07] we do for 13.10, but we have '-saucy' branches there [10:07] or -13.10, I don't quite remember [10:10] FWIW, we have 'kubuntu-create-sru-branches' in the tools which initialize those. But I didn't manage to run that on release day so it would require some branch fixing later on to be usable :/ [10:11] I would rather remove that, then people don't have to worry about what's where [10:12] doctorpepper: still lots to fix up http://qa.kubuntu.co.uk/ninjas-status/build_status_4.13.0_precise.html [10:30] did I mention that the policy says backports for 2 years? [10:35] apachelogger: yes but 4.13 release was 6 hours inside that schedule and doctorpepper did ask nicely [10:36] Riddell: it however means that .1 .2 .3 will not get backported, rendering the backport moot [10:37] also I am reasonable certain workspace is oudated as well, so is akonadi .... [10:38] it's an exiting waste of time [10:50] apachelogger: thx [11:04] kubotu: newversion plasma-nm 0.9.0.11 [11:04] https://bugs.launchpad.net/bugs/1312664 [12:03] Riddell: after much failure getting request sync to work, I tried it on another computer with success. libical first attempt is ready. [12:04] sgclark: ooh? where? [12:04] * Riddell discovers bug 1312689 [12:04] bug 1312689 in libical (Ubuntu) "Sync libical 1.0-1 (main) from Debian unstable (main) No difference between the two at this time." [Undecided,New] https://launchpad.net/bugs/1312689 [12:06] yeah there [12:06] sgclark: synced! [12:21] 'Morning folks [12:22] morning [12:23] Riddell: ScottK: we are at 1.41-1 liblog4perl-perl and unstable is at 1.43-1, how do I proceed? [12:24] liblog-log4perl-perl rather [12:26] sgclark: ubuntu is at 1.41-1.1ubuntu1 [12:26] sgclark: so work out what the ubuntu change is for and then if we want to keep that [12:26] if we do, merge it into the debian 1.43-1 version [12:27] ok [12:27] md5sums do not match obviously [12:28] nope, so start with the .orig from debian === ikonia is now known as Guest8168 === Guest8168 is now known as ikonia [12:57] Riddell: ok on this one, we drop some dependencies that are not being used at build time yet listed. [12:57] Riddell: so I suspect keep [12:58] sgclark: I think these are dropped because they're not in ubuntu main (they'll be in universe) and packages in main can only build-dep on packages also in main [12:58] so yes I suspect keep too [12:59] sgclark: see the last merge changelog entry, that explains why they're gone and what's changed [13:06] assuming someone has written a decent changelog entry :) [13:07] Scott wrote the last one ;) [13:10] then I assume he has! [13:23] Riddell: umm sorry irc kicked me. looks like they merged a spelling error patch into one with some cherry picks of other patches. [13:26] sgclark: who what? [13:26] still on liblog-log4perl-perl? [13:26] Riddell: yeah [13:26] Riddell: debian merged one of the patches into a new one, I am going to build with that [13:27] see what happens [13:27] spokes like a ture computer scientist :) [13:27] * Riddell gets kwin from kf5 working and cheers [13:30] * mgraesslin had been at that stage months ago but joins in the cheers nevertheless ;-) [13:48] Riddell: it builds, kept our changes. Do I do a requestsync? or something else when we keep our changes? [13:49] sgclark: tidy up the package and give me the package [13:49] sgclark: add your own changelog entry with a ubuntu1 version number [13:49] sgclark: merge in the old changelog entries in some sensible way [13:49] debuild -S [13:49] give them to me or ScottK for review [14:03] Riddell, sgclark: we have 'merge-changelog' from ubuntu-dev-tools for changelog merging.. [14:04] yofel: noted for next time, thank you [14:04] * Riddell never trusted that script [14:05] worked fine for me so far [14:08] there's dpkg-mergechangelogs [14:08] which might be what merge-changelog uses [14:09] the dpkg thing is official and works definitely though [14:09] sgclark: If you use the grab-merge script in ubuntu-dev-tools it'll download the last common point in the code, the latest Debian, the latest Ubuntu, and a draft merged package from merges.ubuntu.com. I'd start there. [14:09] * apachelogger is using that for git merges [14:12] wow that sounds spiffy and easier. I will try it on next one I do. Finished this and you can find it here: https://www.dropbox.com/sh/p8hlhv9lztlyyjl/4RjZyLGlfY/kubuntu-files [14:16] sgclark: Looking. Typically merges.ubuntu.com doesn't help us much for KDE stuff, but for most things in the archive, it's a huge help. [14:18] ScottK: ok ty [14:22] sgclark: It looks like you managed to lose some debian/changelog entries in the merge. Also, for packages that we modify, you need to remember to make the maintainer an Ubuntu one. The update-maintainer script in ubuntu-dev-tools will do this automatically. These things are easy enough to fix, but as a learning exercise, why don't you grab-merge liblog-log4perl-perl and try it that way. Also, once you're done, I'll ask you why we make the [14:22] changes we make. [14:22] Generally good though. [14:25] ScottK: ok [14:25] Thanks. [14:36] ScottK: bug 1312651 [14:36] bug 1312651 in pkg-kde-tools (Ubuntu Utopic) "trying to overwrite '/usr/bin/extractattr', which is also in package pkg-kde-tools 0.14.2ubuntu5" [Medium,Fix committed] https://launchpad.net/bugs/1312651 [14:36] apachelogger: Already done. [14:36] huh, thx ;) [14:37] ScottK: did you see my question about the marble thing from earlier? [14:37] If I did, I don't remember it. [14:37] [10:31] ScottK: bug 1312104 ... marble package contains marble and marble-mobile, for utopic I split out marble. should we split for trusty as well (preserving dependencies) or should we go the less intrusive route of also applying the split to trusty? the non-split option would be to hide the marble-mobile desktop file to avoid confusion (which would also not be much worse because marble-mobile seems jolly broken with [14:37] bug 1312104 in marble (Ubuntu Trusty) "Marble Menu Squashed/Unreadable" [High,Triaged] https://launchpad.net/bugs/1312104 [14:37] desktop qml components) [14:38] there's a logic issue somewhere [14:38] "or the less intrusive route of not splitting in trusty" ;) [14:38] Right, so if marble-mobile is broken, I'd say just ditch the .desktop. Let's do it the easy way. [14:38] aye [14:39] We can look at doing the split in trusty if in a point release it gets fixed. [14:39] I don't mind that split because it wouldn't affect anyone who wasn't trying to get marble-mobile to start with (unlike the baloo thing which would have affected all our users). [14:40] *nod* [14:40] ScottK: is this something I need to worry about http://paste.ubuntu.com/7330229/ [14:41] sgclark: Generally not. I always thought that warning was excessively harsh. It's mostly there to tell you where you can find unreleased packaging changes if you need to look. [14:42] ScottK: ok, yes it had me scared haha [14:42] sgclark: The most interesting part of the REPORT file is where it talks about conflicts. Those have to be manually resolved. [14:50] apachelogger: We do need to decide what baloo kcm we ship for utopic. I think the regular one is a bit basic. [14:52] apachelogger: there's a choice? [14:52] * yofel didn't realize there's more than one either.. [14:52] I thought Kubuntu was all about shipping a vanilla kde experience? [14:53] why don't you guys ship tracker? It's config dialog is even better. [14:53] *Its [14:58] vHanda: there's the vanilla experience, and then there's usability. And with all the fragmentation in kde going on there won't be any kind of *THE* vanilla kde experience anymore in the future [14:58] ScottK: there's a choice? [14:58] as everyone will ship a random set of application versions [14:59] as long as every application has a "Did you know" dialog I am happy [14:59] If do you plan to ship the alternate one, then please do it properly. No, one person decision or a decision based on the more vocal users [14:59] what's the alternate one? [15:00] well, we'll have half a year to talk it out [15:00] btw, the plan from my end was always to ship the alternte one (90% is my code, btw) as a separate app [15:00] mind you, I think there should be no kcm, at best an on/off switch xD [15:00] * yofel would've been happy with that ^^ [15:01] see :P [15:01] ScottK: https://www.dropbox.com/home/Public/kubuntu-files new one [15:08] ScottK: and we made the changes because those depends are used at run-time not build time. [15:18] Quintasan: how was the talk? [15:18] Riddell: not bad, we had some people following along [15:18] not much response though [15:19] probably could have done with some more advance notice and publicity [15:19] Yeah [15:19] thanks for doing it [15:20] No problem [15:48] kubotu: newversion kde-workspace 4.11.9 [15:49] https://bugs.launchpad.net/bugs/1312806 [15:51] do we have any use of SC 4.12.5? [15:52] not really [15:52] could update saucy if anyone cares to [15:53] would have to be done by hand, we can only script update the latest release we have (4.13) and backport that. Not update an arbitrary release in some PPA [15:55] mm [15:55] let's leave it then :) [16:01] sometimes I hate the interview process [16:03] "tell us a time you were challenged and how you overcame this" [16:04] yup lol [16:07] I'm sure Kubuntu could be used for a lot of such questions [16:11] Riddell: unless you have something that needs to be done with extreme urgency, I need to run some errands. [16:11] sgclark: errand away :) [16:12] Riddell: ScottK: https://www.dropbox.com/home/Public/kubuntu-files has the new liblog4perl files done. email me if you have questions or concerns and I will get back to you when I return. [16:12] Riddell: thanks! [16:25] LOL Riddell [16:25] Well, I'm happy with my answers and he was too. [16:25] Plus, the company would be amazing to work for. [16:29] Darkwing: what's the gossip? [16:33] Riddell: It's the Events Manager for the Linux Foundation. :) [16:34] oh yes that would be lovely [16:34] Had a second interview today. [16:35] Darkwing: more conferences in edinburgh is the way to go :) [16:35] I'll def come out and visit lol [16:44] ::workspace-bugs:: [1312806] Please update kde-workspace to 4.11.9 @ https://bugs.launchpad.net/bugs/1312806 (by Kubuntu IRC Bot) [17:46] ::workspace-bugs:: [1312849] kcheckpass fails due to not chmoded 4755 @ https://bugs.launchpad.net/bugs/1312849 (by Jim Peterson) [18:23] sgclark: That url isn't the public one or something. [18:23] can't see the directory. [18:29] apachelogger: marble accepted. [18:37] ScottK: umm, was same folder as earlier [18:37] ScottK; try this, https://www.dropbox.com/sh/p8hlhv9lztlyyjl/4RjZyLGlfY/kubuntu-files [18:38] sgclark: That works. [18:38] super [18:44] sgclark: Almost there. The maintainer should be something in Ubuntu and the original maintainer should be the Debian person. Also, since this is not a Kubuntu specific package, the maintainer should be Ubuntu Developers . If you just delete the XSBC-Original-Maintainer line in debian/control and then run update-maintainer you'll get the right answer. [18:45] sgclark: Also, why do we drop those from Recommends to Suggests? [18:45] ScottK: ok [18:45] A key think about merges is understanding why we have difference with Debian. A lot of people seem to miss that. [18:47] ScottK: The reason I can see is that, those depends are needed at runtime not buildtime. as for suggests by definition is that the depends are related and not functionality [18:47] Build time is described by build-depends. [18:47] This is all about run time. [18:47] ScottK: I admit admit the clear difference is still a bit fuzzy for me [18:48] sgclark: Look at the results of rmadison liblog-dispatch-perl [18:49] Then do the same for liblog-log4perl-perl [18:51] ScottK: dispatch one is Universe is the difference I see [18:52] Yes. [18:52] Sinc liblog-log4perl-perl is in Main, it can't depend on or recommend anything from Universe. [18:53] ScottK: aha! I understand now, thank you [18:53] In this case, whoever initially diverged the package determined it'd make more sense to drop to suggests than to get them promoted to main too. [18:53] sgclark: So get me one with the maintainer fixed and I'll sponsor it for you. [18:54] ScottK: new files in the dropbox :) [18:55] OK. Looking [18:59] Warning: Unknown distribution "uptopic". Do you want to continue [y|N]? [18:59] Oops. [18:59] oops [18:59] My fault. [19:09] sgclark: Uploaded. Thank you for your contribution to Ubuntu. [19:10] ScottK: thank you for your help! [19:11] There's a lot of stuff to learn and you can get exposed to more of it by working on stuff outside Kubuntu every now and then. [19:54] ::workspace-bugs:: [1312895] Cannot login into KDE after upgrade from 12.04 to 14.04 @ https://bugs.launchpad.net/bugs/1312895 (by HugoHirsch) [21:22] ::qt-bugs:: [1312924] package libqt4-dev-bin 4:4.8.3+dfsg-0ubuntu3.3 failed to install/upgrade: impossible de co... @ https://bugs.launchpad.net/bugs/1312924 (by fankrid) [22:13] Riddell: digikam needs a merge and it's more than I can get my head around at the moment. You merged it last time, would you please take a crack at it again.