=== ubott2 is now known as ubottu [06:17] sgclark: received and distributed [06:17] you already got a patron === tazz_ is now known as tazz === fregl_ is now known as fregl [09:09] mck182__: http://wiki.bazaar.canonical.com/BzrFastImport [09:09] seems to not be packaged in ubuntu? [09:12] it was in the past [09:12] Deleted on 2015-08-21 by Steve Langasek [09:12] (From Debian) RoQA; orphaned, unmaintained upstream, rc-buggy; Debian bug #742416 [09:12] Debian bug 742416 in ftp.debian.org "RM: bzr-fastimport -- ROM; orphaned, unmaintained upstream and rc-buggy" [Normal,Open] http://bugs.debian.org/742416 [09:13] vivid and older have it in the archive if you need it [10:13] mgraesslin: what do you think about the symbol diff at the bottom of https://launchpadlibrarian.net/224122678/buildlog_ubuntu-xenial-amd64.kwin_4%3A5.4.2-0ubuntu2_BUILDING.txt.gz ? [10:13] It looks like libepoxy 1.3 is namespacing things? [10:14] yofel: yes, see https://git.reviewboard.kde.org/r/125883/ [10:14] ah, nice, thanks! [10:14] yofel: if you have any additional input, please add [10:29] what a mess :S [12:16] phew, running KDE on xenial on Qt 5.5.1, just in time to mention it in the Qt session [12:22] and nothing exploded? sweet \o/ [12:29] Mirv: I have been running your 5.5.x packages on Wily for quite some time now. I like them alot because they fix an issue I had been having on some of my older computers where the mouse cursor would jerk alot when starting a Qt5 application. Thanks! [12:31] mamarley: you're welcome! :) and I moved the wily packages today to a new location as documented on https://wiki.ubuntu.com/Touch/QtTesting since I guessed some people will want to use them. that way they can be kept in a more permanent place than that landing PPA. [12:31] Yep, I saw that when I suddenly had a bunch of "local or obsolete" packages this morning, so I looked at the wiki and found the new location. [12:32] yofel: well, after fixing kwin symbols, nothing exploded. others recompiled without problems. [12:32] but no issues I can immediately see from user point of view when doing the siwtch [12:32] mamarley: heh, good to have up-to-date documentation then [12:32] Yep :) [12:33] * mamarley probably won't be able to resist upgrading to Xenial for that much longer. [12:41] yofel: the heck are you doing on trello [12:42] removing me from the cards and moving done cards over [12:47] yofel: I see you're moving everithing now [12:47] I was planning to move the thing from promotion myself [12:48] and then review each one if it's still valid or not [12:48] but I can go through the whole backlog [12:48] and add labels [12:48] to all of them [12:51] ahoneybun: I didn't move anything that was actually marked was DONE [12:51] ovidiu-florin: I didn't touch promotion, I'll leave that to you [12:52] mm [12:52] ahoneybun: sorry about the removals, I forgot to add people to the board *before* moving the cards -.- [12:52] it's all good [12:57] yofel: I'm just happy to see movement :) [13:17] Howdy folks [14:01] FYI, http://summit.ubuntu.com/uos-1511/meeting/22570/qt-for-1604-lts/ is starting now [14:02] morning [14:24] hola [14:24] como les va [14:24] mi jente === rdieter_work is now known as rdieter [14:47] yofel: my computer was acting and had to reboot and missed most of qt uos, did you catch what we need to do to get 5.5 going? === Guest91343 is now known as yaoista [14:47] well, 5.5 is mostly ready from what I gathered. So adding the landing PPA and reporting any issues we see would be the way to go [14:48] for those of us that are running xenial at least [14:50] ok, guess I should do that [14:51] I am about to release my trusty backports, look out for any issues and let me know all [14:52] this should get a news post on the website [14:52] ovidiu-florin: could you add that? [14:52] or give me Author permissions? [16:12] hm, python3-only on images session going on right now [16:12] that would be a fun task.... [16:15] ouch [16:15] so we have to get core-dev it seems yofel [16:16] to be on the release team? yes, Scott already told me that [16:16] ok [16:18] thanks for telling me that someone replied though ^^ [16:18] np [16:18] do you know where we atart to get going on that? [16:18] start* [16:21] well, you need to gather some recommendations for the application and need to know how to work with software in 'main' [16:21] so we would need to work on something in there (e.g. Qt) [16:22] ok [16:23] additionally, you need to know how the release process works to not step on other people's feet during freezes etc. [16:23] but that's already a MOTU requirement [16:24] <_Ridgewing> Hiya guys _Ridgewing here ! [16:24] hiyas [16:24] hey [16:24] <_Ridgewing> 'allo. [16:24] <_Ridgewing> When the podcast due, today ? [16:25] if the schedule doesn't lie, 19:00 UTC [16:25] * _Ridgewing already consumed numerous beers :-) [16:25] ahoneybun: ^ [16:26] <_Ridgewing> Looking forward to the hangout and getting wiki.kubuntu.org up-and running. [16:26] hm, installing kubuntu-desktop in a chroot and then apt-get purging python2.7 results in 63 removals [16:26] not as bad as I thought [16:26] <_Ridgewing> We could make it as good as the KDE one. [16:37] sgclark: FYI: after 24 hours using your trusty staging-applications I've seen no regression. Great work! [16:40] great :) thanks allee [16:42] yofel: do you know who looks after node.js in ubuntu? [16:42] no, best ask in #ubuntu-devel [16:45] :( do I have to? [16:46] hey, they don't bite! [16:46] we're all ubuntu devs after all [16:46] I beg to differ [16:46] #ubuntu-server might be another place [16:46] Ill just install for source [16:48] this is weird, Ive had more problems with wily from it was release than the entire time it was in devel! [16:50] that's the usual pattern... [16:50] maybe I should upgrade to xenial [16:50] that could be fun! [17:03] make sure to also add the qt5.5 PPA [17:03] otherwise not much changed so far :P [17:06] prth: yo? [17:07] hi Riddell [17:07] prth: want to talk ubiquity? [17:08] sure [17:09] i'm planning to first port kde_ui.py so that other individual pages & plugins can be tested [17:09] prth: do you know the project timeline? [17:09] yes, 4 months till Feb I think [17:10] finish end of feb, loads of time [17:10] yupp [17:10] main priority being to port ubiquity to PyQt 5 [17:10] which probably isn't so difficult [17:11] is ubiquity using python 3? [17:11] yes it is so that's fine [17:11] prth: have you used PyQt before? [17:12] yes but while creating patches for Ubiquity [17:13] prth: I guess reading the general qt 4->5 documents would be worth doing as well as any pyqt specific ones [17:13] prth: have you used bzr? [17:13] sure, I have read it & will be referring it a lot [17:14] Riddell, yes I have used bzr & am comfortable with it [17:14] prth: presumably start off by making a branch for this port in launchpad [17:15] Riddell, I have set up the project & started hacking on the VM [17:15] Riddell, sure [17:15] prth: did you read agateau's blog post about working on ubiquity? [17:15] http://agateau.com/2013/hacking-on-ubiquity-the-setup/ [17:15] yes I followed that only [17:16] prth: do you have a blog on planet kde? will you do a starting blog post? [17:16] Riddell, should i use kubuntu 16.04 daily build because once the current build was buggy [17:17] Riddell, no but I can. [17:17] I'll publish the starting blog this weekend [17:18] prth: use whatever works, I would think kubuntu 15.10 release is fine and will not be as unstable as 16.04 daily [17:19] I'll open a bug report to add my blog's kde feed [17:22] prth: presumably you're still at university during this time? [17:23] yes Riddell [17:23] prth: do you have exams? [17:24] yes first week of december [17:25] ok, so obviously those will take priority [17:27] prth: hopefully you can finish off the qt5 port with plenty time to fix other bugs in ubiquity :) [17:27] sure Riddell [17:27] :) [17:27] prth: have you ever used oem-config? [17:28] no but i know about it [17:29] prth: worth trying out an oem install to make yourself familiar, oem-config is ubiquity in a different mode and it's possible to break oem-config when working on ubquity [17:30] ok, i'll try it Riddell [18:45] anyone notice that the clock on the login screen seems to stand still? [19:03] clivejo: no. I've tried: Loggged out -> 20:02 Now it shows 20:03 [19:04] <_Ridgewing> I see you in the video. Yay \o/ [19:05] <_Ridgewing> "Tings could go wrong" hehe. [19:05] _Ridgewing: URL? [19:05] <_Ridgewing> http://summit.ubuntu.com/uos-1511/meeting/22565/kubuntu-podcast/ [19:06] sgclark: saw your blog post. is the ppa the staging area for moving things into the official backports repos? [19:07] Afraid I do not know how that process works. ANother thing to learn. Going in blind on all this. [19:08] wxl: ^ [19:08] okie dokie, sgclark. do you know who i might ask? [19:08] He quit [19:08] yofel: might know [19:09] okie dokie [19:10] wxl: kde is so large and has so many dep relationships that we gave up putting it into the official backports years ago [19:10] yofel: ok, so then the recommendation for production machines running kubuntu is to add the backports ppas, then? is this documented anywhere? [19:11] probably... [19:11] hahah [19:11] there is https://community.kde.org/Kubuntu/PPAs [19:11] thx [19:12] Do things ever get moved from Kubuntu backport PPAs to just the regular backport repositories? [19:12] no [19:13] well, maybe single things, but usually that's just a lot of effort for little benefit [19:13] So it's not some concious separation from the regular repos then [19:15] * genii wanders back to struggling with sddm [19:15] dunno I think it may be worth it for point releases. I will look into it if I have time. [19:16] the problem is that the backports also requires regression testing, so you're expected to test all rdepends of libs that you update for regressions [19:16] with the size of kde that's a crapton of work [19:18] ahh, perhaps if we get bigger with a larger tester ool lol [19:18] pool* [19:21] ovidiu-florin: for the podcast. Wouldn't it help if you reduce the screen resulution to e.g.1280x1024 this way the installation window is almost as big as your Monitor. Makes no sense to transmist > 50% of an gray area. [19:43] ovidiu-florin: k-menu->type info -> start kinfocenter: kernel listed on 'about system' that is opened by default [19:44] allee: please join in #kubuntu-podcast or #ubuntu-uos-showandtell [19:52] yofel: can we program the bot to point to sections of the manual? [19:52] like !repos [19:52] !install [19:52] Ubuntu can be installed in lots of ways. Please see https://help.ubuntu.com/community/Installation for documentation. Problems during install? See https://wiki.ubuntu.com/CommonProblemsInstall - Don't want to use a CD? See http://tinyurl.com/3exghs - See also !automate [19:53] well, the factoids would need adjusting, so you need to talk to someone from the IRC team [19:53] genii: ^ [19:54] yofel: Putting me to work now? ;) [19:54] you and unity are the only people I know :P [19:54] erm, Unit [20:00] PM some suggestions for what you want as Kubuntu-specific !repos or !install and I'll see what I can do [20:01] what a great podcast, guys [20:02] yep indeed, was fun to watch :) [20:02] heh, I was just thinking about factoids too [20:03] ovidiu-florin: https://kubuntu.org/wp-admin/post.php?post=2467&action=edit [20:03] !kubuntudocs = http://docs.kubuntu.org for instance [20:03] valorie: I am only a bot, please don't think I'm intelligent :) [20:03] !kubuntudocs [20:03] Sorry, I don't know anything about kubuntudocs [20:03] !kubuntumanual [20:03] Sorry, I don't know anything about kubuntumanual [20:03] silly ubottu, why aren't you easy to edit like the amarok bot is? [20:21] ok, bbl [20:34] ubottu: docs-#kubuntu is Kubuntu documentation can be found at http://docs.kubuntu.org General linux documentation can be found at http://www.tldp.org and http://rute.2038bug.com [20:34] I'll remember that, genii [20:34] * genii goes back to coffe [20:37] !docs [20:37] documentation is to be found at http://help.ubuntu.com and http://wiki.ubuntu.com - General linux documentation: http://www.tldp.org - http://rute.2038bug.com [20:37] !docs-#kubuntu [20:37] Kubuntu documentation can be found at http://docs.kubuntu.org General linux documentation can be found at http://www.tldp.org and http://rute.2038bug.com [20:41] ahoneybun: It only changes it in this case to be specific to the #kubuntu channel [20:41] right [20:41] oh cool [20:41] thanks genii [20:41] np [20:44] I'll add one later for Kubuntu-specific !repo factoid also [21:05] There was already a Kubuntu specific !repos which did not seem to need changing. I did add a new one for !backports now however. [21:05] !backports-#kubuntu [21:05] If new updated packages are built for an application, they may go into Kubuntu Backports, which is one of the official Kubuntu PPAs. See https://community.kde.org/Kubuntu/PPAs for more information. === rdieter is now known as rdieter_work [21:11] I was looking into this: https://trello.com/integrations and integrated a bot for telegram that shows trello updates in the telegram group we have [21:14] would someone be kind enough to add me to that group? [21:16] yofel: you have telegram? [21:16] yes [21:17] @Yofel over there [21:41] something is badly wrong with Kontact :( [21:47] * clivejo cries [21:51] define "wrong" [21:51] there's a lot of "wrong" with akonadi....... [21:53] its throwing a tantrum, so I took a backup and deleted all the accounts [21:53] tried to restore the backup and the tool crashed [21:54] so trying to add the account manually [21:56] Stupid wizard wont work either [21:57] has anyone upgraded their system to xenial yet? [22:01] nope [22:04] curious on how it running [22:10] clivejo: xenial? [22:10] really? [22:11] * clivejo nods [22:11] why not? [22:15] ;) [22:15] at this point it really is just a nightly of wily [22:18] bragging rights are important ;P [22:19] just the man [22:19] is QT5.5 in xenial yet? [22:19] no, still in the landing PPA [22:19] will land sometime this month [22:19] I guess nothing to test it with yet? [22:20] well, you can test the _existing_ stuff with it [22:20] or will you recompile old stuff? [22:20] LOL [22:20] Mir_v already recompiled the necessary parts in the PPA [22:20] have you tried compiling frameworks with it? [22:21] no, I was hoping we could use the new tooling for that, but that's not at that point yet [22:22] and well, ENOTIME [22:22] yofel: did you know rick has secured $500 of credit on Digital Ocean? [22:23] yes, he did say that in the meeting yesterday [22:23] that'll be really handy for our CI setup [22:23] * clivejo nods [22:23] get some heavy CPU droplet running [22:24] nah, a 4GB or even 2GB one would be sufficient, maybe another one on demand if the queue gets too long [22:24] otherwise we're just wasting mondey [22:24] what a word invention.. [22:24] mondey [22:27] hi santa_, how are the automation ng scripts coming along? [22:27] clivejo: good, I tested what I have so far today [22:29] what you test it on? [22:29] a test rebuild [22:29] kde stuff? [22:30] yes, now In just need to make the new-release script so it would be usable fo the next kde releases [22:30] yofel: If you guys need Digital Ocean credit, I have some laying around that I am never going to need. It is only like $20 or $25, but you guys can use it if you want. [22:32] I thought you could customise your droplet, ie 4 cores, 2 GB RAM, 20GB SSD and 1TB Transfer [22:32] for building its all about the CPU :/ [22:34] not from what I can see, but the instances are still cheaper than EC2 [22:38] yofel: is there such a thing as a distributed build server? Kinda like the SETI Project, World Community Grid etc where you can donate unused CPU cycles? [22:39] not that I know of, but I'm not sure that's something we would want to use for security reasons. (How do you guarantee that nobody tampered with the packages?) [22:40] ok, for the CI that might not be much of a priority [22:40] but if we can make the slave setup easy people can still donate build hardware (tanglu runs mostly on donated hardware) [22:46] what is the SC is KDE SC? [22:47] software compilation [22:47] strange thing to make an acronym out of === tazz_ is now known as tazz [22:48] maybe that's why digikam dropped it [22:48] well it's still on the wiki https://community.kde.org/Kubuntu/PPAs [22:49] right, because they weren't updated in ages, the KDE SC is KDE4 [22:49] for the new releases you have sepeare kde frameworks 5, plasma 5 and applications YY.MM [22:50] ahh so SC is the intergration of frameworks and plasma [22:50] (i see apps referred to as a separate thing from the SC) [22:50] no, SC is obsolete branding for kde workspace 4 + plasma 2 + the rest of the applications [22:50] oh ok [23:54] I think at this point we just say "KDE" and then wave vaguely in the direction of both software and community ;)