=== Guest16046 is now known as ikonia === rudydog is now known as monkeyjuice === sfn is now known as mauved [08:01] Good morning. [08:08] good morning everyone [08:10] hi ho [08:12] valorie: hi, now that the GCC 5 transition is settled and I finished pondering about the kubuntu-automation design, I'm starting to look forward to become a kubuntu member, I have just read https://community.kde.org/Kubuntu/Membership so the next thing I'm planing to do is writing a couple of wiki pages with my contributions, anything else that I should prepare? [08:13] do that, and schedule a meeting [08:14] also write to the devel list and ask for nice statements at the bottom of your wiki page [08:14] you can do that in one email, actually [08:15] we usually schedule meeting using doodle or something like it [08:17] where is the meeting suposed to happen: here, #ubuntu-meeting, somewhere else? [08:18] here is fine [08:18] ubuntu-meeting has some weirdness to the scheduling [08:19] ok, thank you [08:19] btw I have a mail with a patch awaiting approval :P [08:24] santa_: I'll run listadmin immediately [08:24] :-) === vinay is now known as Guest26340 === Squt is now known as Sput [08:35] santa_: approved [08:35] * valorie heads to bed [08:35] niters all [08:36] valorie: thanks! [08:38] sitter: so ... there is in kubuntu-devel new version of the patch providing git-clone-all and the new way of bumping of the build depends [08:39] regarding git-clone-all now I'm cloning using the upstream names obtained from ftp, not the static list of source packages we have [08:40] however there is just a loose end: the kdelibs repository is named kde4libs (following source package name) and not kdelibs [08:41] if you could make a symlink in alioth from kde4libs.git to kdelibs.git we won't need to harcode an if or use json file with "exceptions" (which is the kind of "staticness" which we don't like) [08:42] lrwxrwxrwx 1 apachelogger-guest scm_pkg-kde 12 Okt 19 08:42 kdelibs.git -> kde4libs.git [08:43] let me test... [08:46] gonna take a while, l have to thread the clone processes like you suggested :P [09:52] !testers [09:52] testers is Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, Quintasan, lordievader, shrini, tester56, parad1se, mamarley, alket, SourBlues, sgclark, neo31, vip, mparillo for information [09:52] ↑ [09:55] Riddell: http://iso.qa.ubuntu.com/qatracker/milestones/347/builds ??? [09:55] yep === vinay is now known as Guest45253 [10:35] $ git-clone-all [10:35] Summary: [10:35] All packages were cloned succesfully [10:39] Riddell: I have been thinking this saturday how to improve the automation scripts so they could be used anywhere ~ kubuntu/neon/siduction I you have a few minutes I could explain you the overall design I have in mind [10:39] s/I you/if you/ [11:13] anyone else have issues with konsole not opening ? [11:24] Just downloading the 347 iso, then I will test [11:25] mm I'm not on a daily build [11:25] just normal [11:26] morning sick_rimmit [11:26] checking for updates [11:27] so I got konsole to start within /usr/bin [11:27] WFM, any error when opening it from some other terminal? Or something in .xsession-errors or dmesg? [11:27] QCoreApplication::arguments: Please instantiate the QApplication object first [11:28] ah, so opening it from kickoff doesn't work? [11:28] yea [11:28] QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. [11:28] I got it to open with the terminal plugin in dolphin [11:31] santa_: sure [11:31] do you see more than one konsole in kickoff if you search for it? Is the Icon correct? [11:34] i did updates today here atmy work pc and have this message about kwalled5.rc not writable or something after boot [11:35] Riddell: one the thing I wanted to is spliting a bit this tasks: 1. changing the files in debian/* 2. building the source 3. uploading the source [11:35] I think 1 sould be done in a separate script specific to the distro, we can share the other 2 with different files in kubuntu-automation/conf/ [11:36] so the workflow would be something like this: [11:36] supose we have a ~/kde-all/ directory containing all the git repos [11:37] and that we have a new applications version to work on [11:37] inside ~/kde-all/ we would do: [11:38] $ do-all -r applications new-release [11:38] $ do-all -r applications buildsource [11:38] $ do-all -r applications uploadsource [11:38] or everything toghether [11:39] please add a $ do-all -r applications push-changes, that should not be part of new-release [11:39] $ do-all -r applications "new-release && buildsource && uploadsource" [11:39] yofel: that would be [11:39] running git push over all changes [11:39] $ do-all -r applications git push origin branch [11:40] ok, perfect :) [11:40] I'm doing something similar in siduction and works pretty well [11:41] sounds intertesting [11:41] right, now that's synchronously run as part of the branch updates, and it's a rather common source of bad changes when the script crashes [11:41] note that also being able to execute the scripts that changes the packaging i.e. "new-release" makes things easier to debug [11:41] oh and one thing more [11:41] thats sounds nice [11:42] I have an script in siduction to check if there are missing changes or upload files [11:42] to detect if something is missing [11:42] that would be: [11:42] do-all -r applications check-changes [11:42] or [11:42] do-all -r applications check-upload [11:43] we currently detect that with exception handling, how would do-all handle command errors? [11:43] hmm, let me clarify something [11:44] new-release, buildsource, uploadsource and check-* would be separate scripts in $PATH [11:45] and they are all meant to be run in the git repo of a package [11:45] so they would do what they have to do inspecting the debian/* files [11:46] sounds good so far [11:47] it worked reasonaby well for me @ siduction [11:48] right, but currently our script detects that e.g. a patch cannot be applied which makes the package build fail, will move that to manual/ and at the end tell you why it moved it [11:49] so, if I run do-all over all 200-something applications, how would I see which ones couldn't be built? [11:49] (ok, missing .changes would be one way) [11:49] do-all -r applications check-changes [11:49] right, so back to my question, why is that seperate? [11:50] In general, I think your design is great and solves a bunch of pain points in our current process. Just this part is nagging me a bit [11:51] check-changes? separate from what? [11:51] well, you have the information that something went wrong when e.g. buildsource is being run, why do I need another script to check whether something went wrong? [11:52] maybe I'm just misunderstanding the architecture...? [11:52] ah, because buildsource spits the output of dpkg-buildpackage -us -uc -sa -S [11:52] mm yeah, I would like to know at end of script if I need to fix stuff [11:53] (in its current state in siduction) [11:53] and at end will it spit out these packages failed? [11:53] which I believe returns !=0 when something fails [11:53] I tend to wander off when 200 packages are running [11:54] hmm, you gave me another idea XD [11:54] that's why our script does subprocess.check_call or so to get the return code of whatever it runs [11:55] we could indeed print a summary of the failed commands in do-all [11:55] excellent. [11:55] that would remove the need of a separate check-changes script [12:04] mgraesslin: nice blog post [12:04] where's the bugtracker for plasma-sddm again? [12:04] thanks [12:06] muon (redesign) v5.4.1-96-ge601286 * Aleix Pol: discover/qml/UpdatesPage.qml [12:06] While loading, show a special loading page [12:06] Instead of lying saying there's no updates [12:06] http://commits.kde.org/muon/e60128613acc6285f6f258c13b6ce49a2216ad69 [12:06] muon (redesign) v5.4.1-97-g70d80c4 * Aleix Pol: discover (2 files) [12:06] Fix some issues in the PaginateModel [12:06] ModelTest for king [12:06] http://commits.kde.org/muon/70d80c4770298ac8bb413f944bc9419dd3ed89f5 [12:07] muon (redesign) v5.4.1-98-g696cc2f * Aleix Pol: discover/qml/BrowsingPage.qml [12:07] Add a scrollbar to the main page [12:07] So that if the view is too small, we can scroll down [12:07] http://commits.kde.org/muon/696cc2f67e1ab5245c13492c51a36b27995ba547 [12:07] muon (redesign) v5.4.1-99-gffc9657 * Aleix Pol: libmuon/backends/PackageKitBackend/PKTransaction.cpp [12:07] Also show packagekit errors on the console [12:07] http://commits.kde.org/muon/ffc9657a4e80c7d1fe5ecdd0473a9fdd1c944d62 [12:07] muon (redesign) v5.4.1-100-gad4336b * Aleix Pol: discover/PaginateModel.cpp [12:07] debug-- [12:07] http://commits.kde.org/muon/ad4336b67098774d5b08811527fcf6715e4d9006 [12:07] muon (redesign) v5.4.1-101-gd14bec8 * Aleix Pol: libmuon/backends/DummyBackend/DummyBackend.cpp [12:07] Delay dummy backend initialization [12:07] This way it's more similar to other backends [12:07] http://commits.kde.org/muon/d14bec86d4237241a36396d6cee9fc64704bc103 [12:29] Initial Wily RC Tests going well. I am still getting this: https://bugs.kde.org/show_bug.cgi?id=351805 [12:29] KDE bug 351805 in general "Configuration file "//.config/kwalletd5rc" not writable. Please contact your system administrator." [Normal,Needsinfo: waitingforinfo] [12:46] mparillo: so this is what i had after updates [12:50] Ah, I still have a Vivid laying around, time to upgrade I guess. [13:30] anyone here? [13:32] Riddell: do you know how can I add KDevelop to the kci? [13:32] kci only does frameworks builds, does kdevelop have one? [13:33] yes [13:33] Kdevelop is on frameworks for some time now [13:34] https://www.kdevelop.org/frameworks/kdevelop-master-now-depends-kde-frameworks-5 [13:34] since august [13:41] ovidiu-florin: do the kubuntu_unstable branches compile with it? === mhall119_ is now known as mhall119 [13:42] fresh wily networkm.: why is by default there is no shared DHCP connection for any ethernet anymore? Do we expect people to setup a DHCP ethernet config themself? [13:58] yofel, sgclark: https://paste.kde.org/ph9spnecw [13:58] Testing the Wily Release Candidate install in a VM. I got a black screen. Alt F2 brought up krunner and I could type firefox and konsole and both work, but alt f1 does not bring up the Kicker. Is this an existing bug? First time I ran into it, and I install frequently into VMs. [13:59] I had that when I clicked enable 3d.. [13:59] turned it off and desktop was happy again [14:00] guess it does not like that (nvidia here) [14:01] santa_: that works for me [14:01] okay, why the hell did my default browser change to rekonq?!? [14:01] oh my [14:01] Hmm, I see it is checked, but it is greyed-out (not modifiable) in VMware. [14:06] I will install open-vm-tools-desktop and ugrade my packages. [14:08] Riddell: ping [14:09] Riddell: doesn't https://anonscm.debian.org/cgit/pkg-kde/frameworks/ktexteditor.git/tree/debian/patches/kubuntu_workaround-katehighlightingindexer-arm.diff?h=kubuntu_unstable need to only kick in during PPA builds [14:09] becuase it feels like it'll kick in during regular archive builds too [14:10] :O [14:10] shadeslayer: ideally yes, do you have any way to achieve that? [14:11] Riddell: I think so, the binary mangler doesn't run for PPA's [14:11] so I'm sure there's a way [14:11] as well as pkg-kde-tools doesn't do the po stuffing in PPA's [14:11] so needs looking into how they achieve that [14:11] oh [14:11] hm [14:12] santa_: yes, that's what I meant, thanks! We can then extend that as needed. [14:12] Riddell: looking into it [14:14] Well that was funny. A full upgrade, and installing open-vm-tools-desktop and I do not have the black screen. Alt F1 works and I have the drunken tartan. [14:15] And yes, 3D graphics are checked, and not changable. [14:16] Riddell: do we even build for armhf via kci now? [14:16] one would presume everything goes through kci [14:18] shadeslayer: ppa builds happen for frameworks before we upload [14:18] Riddell: for armhf? [14:18] oh, probably not no [14:18] right, so we can drop the patch [14:18] yes you should be able to just remove it [14:18] since KCI doesn't build armhf on LP anymore [14:18] okay [14:22] Riddell: cheers, pushed [14:22] I wonder if that counts as a pass or a fail. [14:27] muon (redesign) v5.4.1-102-g229612f * Aleix Pol: discover/qml (2 files) [14:27] Workaround stupid crash in Qt [14:27] http://commits.kde.org/muon/229612fba2cee65937a6daba6ddf0ed7184c364e [14:27] muon (redesign) v5.4.1-103-g31b4746 * Aleix Pol: discover/qml (3 files) [14:27] Generalize the padding in the PageHeader [14:27] This way all of the pages look similar [14:27] http://commits.kde.org/muon/31b47462a386315bb898761542971daaef122fae [14:31] Riddell: I don't know. I don't know how to test. [14:31] ovidiu-florin: have a look at debian/control in the packaging see if it build-depends on kf5 bits === perezmeyer is now known as lisandro [14:48] While upgrading 15.04 to 15.10 I ran into a problem with nfs-common about python3.4 being deleted. Should I report this on launchpad. [14:50] ? [14:50] lordievader: sure [14:51] Hmm, running apt-get dist-upgrade again fixed it.... Should I still report it? [14:52] Riddell: we need to do some upgrader pitchy patchy tomorrow [14:52] in fact [14:52] SRU [14:52] because the fetcher actually is the broken bit and that is installed [14:53] uses self._warning were it should use _warning causing exception and the upgrader not to come up at all. although i feel like I fixed that at some point in the past Oo [14:53] hum really? I'm sure I fixed it too no [14:53] and I figured out why I hade 403 thrown on the releaseannouncement... archive.ubuntu throws 403 if you try to access the html version via urllib [14:54] so we need to change the thing back to use the txt version instead [14:54] which is a bit of a visual loss but the entire upgrader looks like shit anyway [14:55] https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:15.04.14.1 I fixed bug 1488843 [14:55] bug 1488843 in ubuntu-release-upgrader (Ubuntu Wily) "SRU: upgrader kde frontend fails to start" [Critical,Fix released] https://launchpad.net/bugs/1488843 [14:55] Riddell: twas still broken for me for some reason [14:56] ah yes [14:56] fooey, I'll test it when I can [14:56] Riddell: that's another bug supposedly [14:57] Riddell: https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:15.10.4 the warning change here needs a SRU [14:57] sitter: I worked out why everyone was complaining about kmix still being around, plasma-pa install the kconf update script for kf5 but kmix is kdelibs4 [14:58] and this url change http://paste.ubuntu.com/12861695/ to make the notes actually work [14:58] Riddell: yeah, I just got annoyed by that today. good stuff [14:58] self.new_dist.self.new_dist that makes no sense [14:59] ah wait [14:59] yeah [14:59] Riddell: - the dup :P [14:59] anyway [14:59] I am off [14:59] have fun [14:59] because my brain is fried [14:59] o/ [15:00] After a reboot I can conclude the upgrade was successfull. === wendar_ is now known as wendar [15:53] The Snappy folk are doing a broadcast in a few minutes if anyone is interested... http://ubuntuonair.com/ [16:26] ( they are accepting questions about the broadcast in their channel #snappy and not in the usual #ubuntu-classroom/#ubuntu-classroom-chat channels) [18:26] hi everyone, I was reading Martin's blog post http://blog.martin-graesslin.com/blog/2015/10/some-thoughts-on-the-quality-of-plasma-5/ and wondering if we are guilty of any of the problems he pointed out [18:28] he mentioned that there's an extra repo (PPA maybe?) that has more up to date Plasma 5 packages, do we have instructions somewhere about where that is and how to use it? [18:30] tjaalton took care of the intel crash at least [18:32] yofel: is that in the main archives for 15.10? [18:32] or a PPA [18:32] yes, was part of the first mesa 11 upload [18:33] ok [18:33] how about for 15.04? [18:36] AFAIK it doesn't apply there, at least we got no reports for that [18:37] when it comes to the PPA, it is indeed recommended to use the kubuntu backports PPA. Vanilla vivid isn't that great [18:37] yofel: are there instructions for enabling that, or is it just an add-apt-repository line? [18:38] we usually tell people how to enable it everytime we post update news on kubuntu.org, and yes, it's just add-apt-repository ppa:kubuntu-ppa/backports [18:39] thanks yofel [18:40] but yeah, to actually "solve" the problems martin points out we would need a blank MRE (or rather major release update exception) for around 400 packages [18:41] I think having the PPA is solution enough, it effectively does the same thing, right? [18:42] Kubuntu does have a problem with multi-display related crashes (https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1492778). As I just posted in the bug report, this would get a lot worse with Qt 5.5 for users with multiple DisplayPort monitors, causing a crash back to sddm whenever the user wakes the displays from sleep. [18:42] yes, except for the people that don't know what a PPA is. OTOH, I'm not convinced that the migrations are tested enough for that user base [18:42] Launchpad bug 1492778 in kubuntu-meta (Ubuntu) "kde crashes when powering on/off monitor" [Undecided,Confirmed] [18:50] Here is an example of Kubuntu News (from the Kubuntu.Org site that flows to both planets) that shows backports PPA to Vivid: http://kubuntu.org/news/plasma-532-and-frameworks-5120-backported-kubuntu-1504/ [18:51] That said, I have been preferring Wily to Vivid ever since Alpha 1. [18:51] thanks marco-parillo [18:51] marco-parillo: yeah, and after this week there's no reason to not recommend wily [18:52] No official reason. I have been recommending it unofficially since Beta-2 ;-) [18:52] ahoneybun: ping (about DVDs) [19:10] It actually looks like https://codereview.qt-project.org/#/c/138201/ will fix the resume-from-DPMS crashing that was caused by Qt 5.5 [19:16] yofel: ping [19:16] hm? [19:16] anyone working on calligra? [19:17] not that I know of [19:21] Ive grabbed git.debian.org/git/pkg-kde/kde-std/calligra.git, but when I do a dch -i its not updating the version number, do you know why? [19:23] because the last changelog is UNRELEASED [19:23] dch will only edit that one [19:24] but -i should still have increased the version number (which is usually not what you want) [19:24] hm... [19:26] for some reason, kubuntu_wily_archive is not kubuntu [19:26] seems to be debian [19:28] Maintainer: Debian Qt/KDE Maintainers [19:29] or is the packaging still on bazaar? [19:35] looks like somebody tried to move it and didn't finish the job [19:36] could have been me [19:51] <[Akeno]> Hi everyone! In my attempt to re-install Kubuntu 14.04.3 on my ASUS R515M I encountered this bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1271304 [19:51] Launchpad bug 1271304 in ubiquity (Ubuntu) "crash when restoring previously installed packages" [Undecided,Confirmed] [19:51] <[Akeno]> Is there any way to disable/stop ubiquity from re-installing the packages? [19:51] <[Akeno]> So that I can re-install them manually? [19:55] <[Akeno]> Anyone? [20:11] \a+666/////8/777777 [20:11] 44444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444444 [20:13] <[Akeno]> Guess someone fell asleep on his keyboard lol [20:18] yowz [20:35] [Akeno]: I don't see any replies to that bug, which was reported by Riddell [20:36] I assume a work-around would have been posted if one was known [20:45] mhall119: what about them? [20:51] <[Akeno]> valorie: Yeah, with new install (different partition) I also encountered this message: [20:51] <[Akeno]> Installation failed: The installer encountered an error copying files to the hard disk: [Errno 30] Read-only file system: '/target/usr/share/doc/libautodie-perl'. This is often due to a faulty hard disk. It may help to check whether the hard disk is old and in need of replacement, or move the system to a cooler environment. [20:51] ahoneybun: are you going to want 32bit or 64bit? IIRC, we only do 64bit for Ubuntu desktop anymore [20:52] <[Akeno]> Laptop is around 1 year old by now [20:52] whichever you pick, it should say in the CD or sleeve what it is [20:52] 64 would be best I think [20:53] <[Akeno]> Gonna attempt to install on that partition again [20:53] ahoneybun: ok, and if I remember correctly we were going to do 500 of the 4/4 DVD 5 from https://docs.google.com/spreadsheets/d/1HnooSpzP9p9cvql8GEQe7J-A1rNLq8qpRs_cH_gaZIk/edit#gid=0 is that correct? [20:53] is it going to be 15.10? [20:54] ahoneybun: yeah [20:54] we would do more for 16.04 [20:55] yay 15.10! [20:55] mhall119: I need the wily werewolf logo [20:56] for the DVD? [20:58] yea [20:59] ok, I'll see who can get you that [20:59] for the inside I think would be cool [21:01] yeah, I'd forgotten about that, asking the design team now [21:02] cool [21:39] ahoneybun: can you go ahead and file a community donations request for the amount in cell K4? We can work on getting the money approved and allocated while we finish getting the artwork together for the printer [21:41] * ahoneybun finally bookmarks the page [21:43] filled out mhall119 [21:45] thanks [22:43] muon (redesign) v5.4.1-104-g49d6d83 * Aleix Pol: discover/qml/CategoryDelegate.qml [22:43] Align categories grid [22:43] http://commits.kde.org/muon/49d6d8388b1411b28f00b79cca13f4d0762fa964 [23:01] muon (redesign) v5.4.1-105-gdd4367b * Aleix Pol: discover/qml (3 files) [23:01] Better adapt the carroussel animation to the vdg demands [23:01] http://commits.kde.org/muon/dd4367b3dda722b9e50a8d329b1b4e84dfdb771d