[01:52] damn lots of fails [03:21] hey Rick_Timmis [08:05] Good morning [10:28] so kubuntu images no longer fit on a CD?!? === sebas_ is now known as sebas [11:16] clivejo: they didn't fit on a CD since a long time ago [11:16] if anything, we've tried to not let the size go over 1G [13:13] Hi all === hggdh is now known as hggdh_ === hggdh_ is now known as hggdh__ === hggdh__ is now known as hggdh [15:09] muon (redesign) v5.4.0-49-g648d196 * Aleix Pol: discover/qml (2 files) [15:09] Work towards the vdg design in the ApplicationList [15:09] http://commits.kde.org/muon/648d196e074d5c31ca4a706367601cd8795432a4 [15:10] muon (redesign) v5.4.0-50-g9c9a6ef * Aleix Pol: discover/qml (3 files) [15:10] Better match to the VDG mockup look on lists [15:10] http://commits.kde.org/muon/9c9a6efd8bda9bb49f279dd9b37ac39c9487dd4c [15:10] muon (redesign) v5.4.0-51-g9def6b2 * Aleix Pol: discover/qml (2 files) [15:10] Implement the VDG's grid delegate [15:10] http://commits.kde.org/muon/9def6b206670d92af609c1a9506be6f73aca4129 [15:10] muon (redesign) v5.4.0-52-gd95fb2b * Aleix Pol: libmuon/backends/DummyBackend (4 files) [15:10] Make more artwork available from the Dummy backend [15:10] http://commits.kde.org/muon/d95fb2b7e933714e4c90b41e7a3779138f781c26 [15:28] muon (redesign) v5.4.0-53-gad1d0e7 * Aleix Pol: discover/qml (5 files) [15:28] Polishing [15:28] http://commits.kde.org/muon/ad1d0e7ef020afdbb11aa14be8f9a807f80a77dc [15:41] https://www.youtube.com/watch?v=svEMrNaQ50E [16:38] soee: did you see something like this lately? [16:38] [ 13.080221] sddm-greeter[2986]: segfault at 18 ip 00007fbb0289ade8 sp 00007ffdbec01190 error 4 in libqxcb.so[7fbb02851000+b5000] [16:38] I tried nvidia-352 again, and instead of an X crash, I now get that when using the nvidia profile [16:39] yofel: i have installed 355 but not latest (-1 version) [16:39] and all worsk fine her [16:39] *here [16:39] weird [16:39] let me try 355 again [16:40] yofel: all latest versions are broken imo [16:40] well, this was 352 from wily archive [16:41] thats why i used ai have 355.06 not 355.11 [16:41] i'v used this abandoned ppa to install it [16:41] https://launchpad.net/~mamarley/+archive/ubuntu/nvidia [16:42] soee: That one has been replaced by ppa:graphics-drivers/ppa. [16:43] mamarley: but it has newer version available and i needed older :D [16:43] i say one more time: latest version dont work atm. :) [16:43] Oh, sorry. [16:50] soee: That video is pretty sweet, I have to say [16:52] WTF [16:52] this is completely random [16:52] first I can see an X crash, then sddm crashes in qxcb, then X crashes again, now X is supposedly running, but the screen is still black [17:04] $ cat /sys/class/backlight/intel_backlight/bl_power [17:04] 4 [17:04] ok, no wonder the screen is black [18:55] is there a network install version of Kubuntu? [18:57] is noone fixing apps 15.08.1 ?!? [18:57] * clivejo nudges ahoneybun [18:57] what? [18:57] apps 15.08.1 [18:57] !minimal [18:57] The Minimal CD image is very small in size, and it downloads most packages from the Internet during installation, allowing you to select only those you want. The installer is text based (rather than graphical as used on the Desktop DVD). See https://help.ubuntu.com/community/Installation/MinimalCD [18:58] clivejo: are they ready to start packaging? [18:58] they are packaged and uploaded to the staging PPA [18:58] http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.08.1_wily.html [18:58] ahoneybun: they are alost ready http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.08.1_wily.html [18:59] so the CI ran though almost all of them [18:59] so we just need to fix a few things that the CI yelled about? [18:59] Im not sure about the CI [18:59] I think someone broke it :/ [18:59] well someone/something built those [19:00] I did, and cocked it up :/ [19:01] I made a typo and called them 1518.1 and put brackets in my chancelog entry === ahoneybun changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | apps 15.08.1 http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.08.1_wily.html - https://notes.kde.org/p/Applications_15.08.1 [19:02] I'll start fixing things in min [19:02] * ahoneybun pulls out his SSD Laptop [19:05] ahoneybun: how do you feel about opening an exception case for getting apps 15.08.1 into wily? [19:05] well it is just a bug fix release so it should not cause any big issues [19:05] so +1 from me [19:06] but apparently someone has to open a report or something7 [19:06] no clue [19:06] which package you going to look at? [19:07] amor [19:07] atm [19:07] ok, Ill take kcalcore [19:07] some errors in the changelog so should be simple [19:08] clivejo: update this: https://notes.kde.org/p/Applications_15.08.1 [19:10] why is dch -i not making a new log [19:10] just editing the old one [19:12] clivejo: dch -i should add a new entry no? [19:12] no [19:12] or well [19:13] it has me adding to the 15.08.0 release [19:13] depends on the set behavior. The current default is no - if last changelog is UNRELEASED [19:13] that sound very very broken [19:13] mm [19:13] clivejo: forgot to push something? [19:14] or rather, the 15.08.0 release being UNRELEASED is also very wrong [19:14] that should say wily from the point where it was uploaded to the archive [19:14] unless I'm in the debian on still... [19:15] which package? [19:15] yofel: the script went haywire on me [19:15] its quite possible [19:15] amor yofel [19:15] drat [19:15] ohh [19:16] amor does not have kubuntu_unstable [19:16] just kubuntu_wily_archive [19:16] oh lol, you're working on the wrong branch [19:16] clivejo: was the last one to edit that too lol [19:16] the script edited it on my behalf :P [19:17] now it has clivejo's edit for 15.08.1 release [19:17] :) [19:17] and generally, don't use -i with dch [19:17] unless you really want to increase the version [19:17] the heck is with aol email clivejo? [19:18] usually just dch will do the right thing [19:18] k thanks [19:18] ahoneybun: the one I signed up with [19:18] and now its stuck [19:19] nice [19:19] XD [19:21] the heck the deps for amor are kde-sc-dev-latest and kdelibs5-dev [19:23] no way those are right? [19:23] why not? [19:24] really old no/ [19:24] ? [19:24] well, amor is kde4 still [19:24] oh [19:25] my keys seem to not work on this laptop [19:25] I think I need to set that up again from the reinstall move to the SSD [19:25] yofel: when using pkgkde-symbolshelper batchpatch does the version need to include the epoch? [19:26] good question actually [19:26] it does [19:27] otherwise dpkg-shlibdeps will generate wrong depends [19:27] I do believe so [19:27] Yes [19:27] the heck is: "badly formatted trailer line" [19:27] I don't get that either [19:27] the changelog looks fine to me [19:28] ahoneybun: the signature line; does it have 2 spaces separating the timestamp? [19:28] from the email? [19:29] I think I see the issue [19:29] "badly formatted trailer line" ... I've seen that for a malformed sig line in the changelog entry [19:29] there was a . inbetween the time and date [19:29] and they were not spaced [19:29] ah right [19:29] wtf is that format [19:29] trying again [19:30] Was that manually added? [19:30] no clue [19:30] Tue, 09 Jun 2015.08.18:23 +0200 [19:30] seems to have fixed it [19:30] yea that! [19:30] wait [19:30] damn [19:30] 'dch -i' is always the best way to create a template entry for editing [19:30] I see [19:31] 08.17:23 needs to be 08:17:23 [19:32] alright that fixed it for sure [19:32] just need to sign it [19:32] somehow [19:32] sign it? [19:32] yea to upload no>? [19:32] it says secret key is not available [19:32] ah, is your gpg key in your keyring? [19:33] might not be from the reinstall to SSD [19:33] and does it try to use *your* key? [19:33] it has nothing to try I think [19:33] oh [19:33] clivejo: 's [19:33] since he last edited [19:34] I'll just email the fix or something? [19:34] I have the key ID set in an env-var and than pass "dpkg-buildpackage -S -k${UBUNTUKEY}" [19:34] m [19:34] you can override the used key in ~/.devscripts [19:34] I have that in there: DEBSIGN_KEYID=2EC0A9FF [19:34] I got my key in there [19:35] edit .devscripts [19:35] ? [19:35] Yeah; I have Ubuntu and Debian keys so I use env-vars to control which one. I don't want to accidentally use the wrong default [19:35] seems I don't have that file lol [19:37] see "man devscripts" or "man debsign" for the config files and vars [19:38] ~/.devscripts does not exist TJ- [19:38] create it? [19:38] I thought it should be there [19:38] No [19:39] that worked yofel [19:39] signed [19:41] checksum error when trying to upload to LP [19:41] mm [19:44] analitza is full of those same errors [19:45] clivejo: if I give you a paste of the changelog can you sign and upload amor? [19:45] I wonder if we shouldn't just whitelist those warnings [19:45] what did you do to fix it? [19:46] edit changlog [19:46] removed some . in the time slot and added a space on 2 lines [19:46] 08.17:23 needs to be 08:17:23 [19:46] hold on, let me look [19:50] thats so weird! [19:50] yofel: how did that happen? [19:51] dunno, I would guess a bug in something [19:51] but I'm not convinced that we should fix this [19:51] past changelog entry are usually considered immutable [19:51] *entries [19:51] its building fine, just lintian complaining [19:52] shadeslayer: your opinion? [19:52] well I can fix it? just say yeah or nah [19:52] what [19:52] I missed all of the discussion :P [19:52] changelog messed up? [19:52] in amor changelog there is time and date in weird format [19:53] shadeslayer: we have syntax errors in past changelog entries. One usually doesn't fix that, right? [19:53] 08.17:23 needs to be 08:17:23 etc and lintian is complaining about it [19:53] I think its better to fix them [19:53] but that's my opinion [19:53] * yofel can't make up his mind -.- [19:54] xD [19:54] yofel: I doubt it's that big of a problem [19:54] it's not, I'm mostly bothered by myself being indecisive :P [19:55] ah well [19:55] clivejo: go and fix it [19:55] yofel: what are the consequences? [19:55] If all bugs were immutable, we'd be out of a job! [19:55] clivejo: theoretically none [19:56] it's just really unusual to change old entries in any way, but I guess fixing the date format is ok [19:56] Did the package previously build with the 'bad' syntax? [19:56] As in, was it published in the archive? [19:56] yes [19:56] TJ-: yes, lintian complains [19:57] * TJ- raises an eyebrow [19:58] I think dpkg only cares about line 1, the rest has a format spec, but that's not really validated [19:58] The Debian policy is explicit about the date format [19:58] TJ-: https://paste.kde.org/p1chdu4vj [19:58] Section 4.4 covers it [19:59] eeeerm [19:59] wait a moment [19:59] * clivejo waits [19:59] clivejo: you should really learn to ALWAYS run git diff before comitting [19:59] look at the diff for a59a7f37 [20:00] The published changelog is correct: " -- Jonathan Riddell Tue, 09 Jun 2015 18:18:23 +0200" [20:01] TJ-: it was a very recent wrong commit [20:01] yofel: but it isn't published. I've just pulled that in with "apt-get changelog amor" [20:01] so the wrong versions aren't actually published anywhere [20:02] clivejo: also, "NOCI", isn't much of a commit message... [20:02] I don't think so. Did a 'grep' on the codebase accidentally change something there? [20:02] TJ-: more like sed on the changelog [20:03] there was a wrong version in the changelogs there we were talking about yesterday [20:03] and fixing that seems to have gone haywire [20:04] this is crazy [20:04] how did it match 15 18 as 15.18?!? [20:04] yofel: that was what I was thinking; dunno how my fingers translated that :) [20:04] clivejo: in regexp, '.' matches any character [20:05] clivejo: did you do "sed 's/x\.y/a.b/g' ... " [20:05] * TJ- stamps on his fingers [20:05] clivejo: did you do "sed 's/x.y/a.b/g' ... " [20:07] heh [20:08] basically I run the staging script but made a typo " * New upstream release (15.18.1)" [20:09] the script had to be restarted a few times and for the first few packages it added numerous entries to changelogs [20:09] clivejo: the proper fix for that would be to rever the broken commit, and then fix it properly [20:09] *revert [20:10] it was a complete disaster [20:10] spent most of yesterday in PM with Riddell trying to fix it [20:11] clivejo: hi, what is the problem, numerous entries to changelogs? [20:12] is that already in git? can you point me to an example? I think I can help [20:12] http://anonscm.debian.org/cgit/pkg-kde/applications/amor.git/log/?h=kubuntu_wily_archive [20:12] santa_: ^ [20:13] ah, the wrong changelog format [20:13] first of all a59a7f373dd49923c7ff282f9f355c10b74b85e1 needs to be reverted [20:16] so I have it open in git gui [20:16] clivejo: well they aren't so many packages having the timestamp issue I think [20:16] they can be fixed manually I guess [20:16] santa_: it was me made the issues :( [20:17] yeah, but the sed run only went wrong in a couple packages [20:17] so it's not that bad [20:18] here you got the list of packages having a lintian warning for the changelog: amor, analitza, ark, artikulate, kdenlive, mplayerthumbs, okteta [20:20] yofel: can you help me revert please [20:20] clivejo: I gave you the commit hash of the wrong commit, now just run git revert a59a7f373dd49923c7ff282f9f355c10b74b85e1 [20:21] then you can just fix things properly by hand and commit that [20:23] does my commit message still need to have NOCI ? [20:23] nah, after all you're fixing stuff [20:24] http://anonscm.debian.org/cgit/pkg-kde/applications/amor.git/log/?h=kubuntu_wily_archive [20:24] hows that? [20:25] good [20:27] ok uploaded to LP [20:35] yofel: http://anonscm.debian.org/cgit/pkg-kde/applications/ark.git/ [20:36] Ive changed both kubuntu_stable and kubuntu_wily_archive [20:37] did you push? [20:37] do I need to revert the two branches? [20:38] hm, I think changing archive is enough as stable should merge that [20:38] so revert f135fb89772f92fdab67036bbf1357f8018e3cca [20:40] yes [21:04] how do I verify that I got all of my cockups now? [21:04] the lintian warnings on the status page will be gone [21:05] could there be ones changed that lintian might not see? [21:05] yes, if something other than the date changed... [21:06] I'm not sure if there's an easy way to find that [21:06] I still that the directory I was working on [21:06] gif diff each folder? [21:07] right, you could probably script running 'git diff HEAD^' for each package [21:09] if that was the last commit on the branch in the clones you have [21:26] ok, looks like I got them all [21:29] :) [21:35] clivejo, thank you for your work! [21:36] thank yofel and Riddell for putting up with my silly mistakes [21:36] they happen. applications is just the worst place to do them [21:37] mistakes are difficult to work through, but that's how learning takes place [21:37] I appreciate you sticking to it [21:37] true, Ive learned a lot this past few days from trying to fix my mistakes [21:38] yofel: do you know where marble-config.cmake is built? [21:38] clivejo: did you fix amor? [21:38] ahoneybun: yes and my other mistakes [21:38] I see lots of green! [21:39] the heck is with gwenview [21:40] OPTIONAL packages [21:44] it built with no errors for me [21:45] maybe needs libkipi-devel [21:45] clivejo: marble would be my guess? [21:48] mm [21:48] cant find it in the files marble package builds [21:52] clivejo: what's the actual problem? [21:52] libkgeomap is looking for marble-config.cmake [21:53] I'll be working but g2g for now [21:53] * ahoneybun away [21:53] oops [21:53] I guess nobody removed that. libkgeomap is unbuildable in wily [21:53] nice to know [21:53] looks for qt4 marble, and we only ship qt5 marble