[00:28] <StevenK> cjwatson: r=me. I'll land it if you haven't already when I return from breakfast.
[02:33] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/dump-top-level-yui/+merge/158837 I can't see anything in the deployment stuff that needs the top-level directory
[02:33] <StevenK> Unsure about buildbot
[02:36] <wgrant> StevenK: That seems fine, if anything breaks then we'll fix it.
[02:38] <wgrant> StevenK: You'll want to check that the tree on carob doesn't have it
[02:38] <wgrant> But I think clean_buildout should remove it, so that'll be fine
[02:45]  * wgrant disappears for lunch for an hour or so
[02:58] <StevenK> wgrant: Added a clean_js rule to remove it, with a comment
[03:36] <StevenK> wgrant: Not landed it yet, I don't know where the built tree on carob is
[04:03] <wgrant> StevenK: /home/warthogs/archives/rocketfuel-built
[04:03] <wgrant> IIRC
[04:05] <StevenK> Right, it has an empty yui directory
[04:06] <StevenK> wgrant: Strangely, there's a full LP tree under ~lpqateam
[04:06] <StevenK> Revision 108xx
[04:07] <wgrant> StevenK: That was used to run the PPR until yesterday
[04:07] <wgrant> I think it's unused now
[04:08] <wgrant> It had to be out of date because the PPR was moved to lp-dev-utils
[04:08] <StevenK> Ah
[04:08] <wgrant> Yesterday I fixed the lp-dev-utils version and changed the crontab to use it
[04:10] <StevenK> Ah
[04:10] <StevenK> wgrant: Should I remove it, or that can wait a few days?
[04:10] <wgrant> StevenK: Check that nothing in the crontab uses it, and then kill it I guess
[04:11] <StevenK> DBR=/home/lpqateam/launchpad/utilities/report-database-stats.py -U devpadreports -d launchpad_prod_master -H lp-prod-pgbouncer.internal --limit=30
[04:11] <StevenK> Not exactly
[04:11] <wgrant> Ah, that is unfortunate.
[04:11] <wgrant> So leave it, I guess :)
[04:12] <StevenK> Yeah, it's not like carob is currently begging for space
[04:14] <StevenK> wgrant: How does a branch to promote 3.9.1 sound?
[04:16] <wgrant> StevenK: It's been almost 48 hours, so sounds good.
[04:54] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/391-by-default/+merge/159546 trivial
[04:55] <wgrant> StevenK: k
[05:33] <StevenK> I do not get why the CSS rules are not applied
[05:55] <wgrant> StevenK: Do you have a branch?
[05:56] <StevenK> wgrant: For this YUI calendar? Nope
[05:56] <StevenK> wgrant: I can push one up if you'd like to have a play and hopefully fix some of it
[05:56] <wgrant> I can hopefully at least fix the CSS
[05:57] <StevenK> "Note: be sure to add the yui3-skin-sam classname to the page's <body> element or to a parent element of the widget in order to apply the default CSS skin."
[05:57] <StevenK> Which I've done, but it doesn't help
[06:00] <StevenK> wgrant: lp:~stevenk/launchpad/new-yui3-calendar it's based off devel as of last week, so you'll likely get an easy to resolve conflict in Makefile
[06:05] <wgrant> StevenK: I'd avoid destroying yui2 in the same branch, simply to avoid confusing things, but let's see.
[06:06] <StevenK> I can probably do that pretty easily
[06:06] <StevenK> wgrant: So we continue building it, but drop it from the combo loader and yuixhr?
[06:08] <wgrant> StevenK: I'd drop it all in one hit
[06:08] <wgrant> Dropping it is not a prereq for adding the new calendar.
[06:08] <StevenK> True
[06:08] <wgrant> If I want to see what your calendar changes were in a year, I don't want to have to wade through 30000 lines of YUI2 diff that are in the same rev for no reason :)
[06:09] <StevenK> But I live to make your life hard ... :-P
[06:12] <wgrant> I know :)
[06:12] <StevenK> wgrant: Right, done. I can delete current branch and push this small and clean up if you wish
[06:12] <wgrant> I imagine it's about 1% of the size :)
[06:12] <wgrant> But I've got your existing one running now
[06:13] <StevenK> 9.5%
[06:13] <StevenK> 257 lines versus 26808
[06:16] <StevenK> wgrant: In the depths of calendar.js, I create a container_div where I set the classes. That was testing a theory, which turned out to be false, but I'm not certain if we care about another level of <div>'s
[06:16] <StevenK> The Calendar docs do say parent node, but I'm not clear if that's immeadiate parent or up the chain
[06:17] <wgrant> StevenK: I make that 0.95%, not 9.5%
[06:17] <StevenK> Oh
[06:18] <StevenK> Missed a zero
[06:24] <wgrant> StevenK: Fixed
[06:25] <StevenK> wgrant: What is the fix?
[06:25] <wgrant> StevenK: The main CSS is in calendar-base, not calendar
[06:25] <wgrant> +    <link rel="stylesheet" type="text/css" href="/+icing/yui/calendar-base/assets/skins/sam/calendar-base.css" />
[06:25] <wgrant> +    <link rel="stylesheet" type="text/css" href="/+icing/yui/calendar-base/assets/skins/sam/calendar-base-skin.css" />
[06:26] <wgrant> It's still ugly and the nav buttons are oddly unthemed, but it's a bit of an improvement
[06:26] <StevenK> wgrant: We can include them directly in combo.css if you wish
[06:26] <wgrant> that might need calendarnavigator stuff
[06:27] <wgrant> StevenK: Yes, that's what we'll want to do eventuall
[06:27] <wgrant> Once we work out which bits we need.
[06:27] <wgrant> Or we could comboload them somehow
[06:28] <wgrant> Ah
[06:28] <StevenK> wgrant: It's an extra 130 lines
[06:29] <wgrant> They get merged.
[06:29] <wgrant> build/js/yui/assets/skins/sam/calendar-base.css and build/js/yui/calendar-base/assets/skins/sam/calendar-base.css are the same file
[06:29] <wgrant> So we probably just want to include all the calendar stuff under yui/assets
[06:29] <wgrant> Oh, only the skin bits end up under there
[06:30] <wgrant> So we need calendar-core.css and calendar-base-core.css from elsewhere
[06:31] <StevenK> assets/skins/sam/calendar{,-base,navigator}.css ?
[06:31] <wgrant> I assume navigator is needed for the month switching arrows
[06:31] <wgrant> Checking now
[06:33] <wgrant> The -skin variants seem to be minified
[06:33] <wgrant> I should probably read some documentation
[06:34] <wgrant> I wonder if the stuff in yui/assets/skins/sam is concatenated core and skin
[06:34] <wgrant> Yeah
[06:35] <StevenK> I think it's tiny enough to go into combo.css
[06:35] <wgrant>     <link rel="stylesheet" type="text/css" href="/+icing/yui/assets/skins/sam/calendar-base.css" />
[06:35] <wgrant>     <link rel="stylesheet" type="text/css" href="/+icing/yui/assets/skins/sam/calendar.css" />
[06:35] <wgrant>     <link rel="stylesheet" type="text/css" href="/+icing/yui/assets/skins/sam/calendarnavigator.css" />
[06:35] <wgrant> That should be all we need
[06:35] <wgrant> Though the navigator buttons have now entirely disappeared, that's possibly because they're not enabled?
[06:40] <wgrant> Ah, no, the skin replaces the < and > with background images that don't display, because the nodes end up contentless
[06:40] <wgrant> StevenK: Are you more on track now?
[06:40] <wgrant> StevenK: And do you understand how skins work now? Each component's -core and -skin files are combined into a single file that ends up under yui/assets/skins/foo
[06:42] <StevenK> Right
[06:42] <StevenK> Why don't the background images display?
[06:43] <wgrant> I suspect because the sole node inside them is display: none, so the node has no size.
[06:44] <wgrant> It may work better if the core sam stuff is loaded
[06:44] <wgrant> But it's not clear whether we actually want to use that.
[06:52] <wgrant> StevenK: Ah
[06:52] <wgrant> I think it's our obsolete grid CSS
[06:52] <wgrant> Setting display: inline-block gets the images to show
[06:53] <StevenK> Are they both on the left and cut off?
[06:53] <wgrant> (we're still using 3.0.0preSOMETHING grids, I assume because 3.0.0 final changed them incompatibly)
[06:53] <wgrant> StevenK: Not if you set display: inline-block on the header
[06:53] <StevenK> You're hacking that in using firebug?
[06:55] <wgrant> StevenK: Using Chromium's dev tools I added .yui3-u { display: inline-block }
[06:55] <StevenK> Ah.
[06:56] <StevenK> If I edit the header div to add style="display: inline-block" I get both buttons, but they're both on the left
[06:57] <wgrant> StevenK: Yes, due to how inline-block works it needs to be on the parent.
[06:57] <wgrant> I think the only yui3-u might be the "April 2013" header text
[06:57] <wgrant> So try setting it there.
[06:58] <StevenK> No, the two a's are also yui3-u
[07:00] <wgrant> So they are.
[07:01] <wgrant> Oh
[07:01] <wgrant> We can probably include the modern CSS
[07:01] <wgrant> The modern cssgrids CSS, that is
[07:01] <wgrant> Since it's all yui3-*
[07:01] <wgrant> Whereas our old embedded copy is YUI2-style cssgrids, with yui-*
[07:02] <StevenK> Huh, so it is
[07:02] <wgrant> I thought they were incompatible
[07:02] <wgrant> But it seems not
[07:03]  * StevenK sprinkles in yui/cssgrids/cssgrids.css
[07:03] <wgrant> A significant improvement
[07:04] <StevenK> BAH
[07:04] <StevenK> I had a make run backgrounded
[07:05] <StevenK> Caught it early enough that it didn't spew processes
[07:05] <StevenK> wgrant: Indeed, that looks great
[07:07] <wgrant> StevenK: It's still obese, but that might just be the overlay being too wide to start with?
[07:07] <StevenK> It looks pretty much exactly like the example
[07:08] <wgrant> Yeah, setting a width on the yui3-calendar-content makes it much more sensible.
[07:08] <StevenK> To what?
[07:08] <wgrant> The main difference is the background colour and the centred ths, and at least the latter is CSS specific to the example page
[07:08] <wgrant> StevenK: I just set it to 300px to see if it worked.
[07:09] <StevenK> wgrant: The width can be set for the widget on creation
[07:09] <wgrant> Ah, right
[07:10] <wgrant> Indeed, I now see width: 340px on the example.
[08:09] <cjwatson> StevenK: thanks
[08:10] <StevenK> cjwatson: Happy to help
[08:39] <cjwatson> Hmm, is it intentional that, after I upgraded dogfood, https://dogfood.launchpad.net/ubuntu/raring/+queue?queue_state=1 no longer has expanders?
[09:00] <StevenK> cjwatson: Did you leave the combo_url hack in place?
[09:00] <cjwatson> yes
[09:04] <StevenK> cjwatson: Restart the webapp, the JS should work
[09:05] <StevenK> cjwatson: The combo_url hack includes a revision number which qas doesn't have any more
[09:06] <cjwatson> thanks, I did wonder if it might be something like that but wasn't sure what the correct target would be
[09:06] <cjwatson> also: lxc is actually rather tasty once I've got it set up for testing in place of schroot
[09:06] <cjwatson> I expected it to be more work but more accurate/better; I didn't expect it to actually be less work
[09:07] <StevenK> I've ignored lxc. My only experience has been with fiddling the Jenkins setup to make use of it
[09:08] <StevenK> Maybe we should just get +combo configured on mawson
[09:08] <StevenK> Then we can drop that horrid hack
[09:10] <cjwatson> ok, why am I getting 503 on everything after restarting the server ...
[09:11] <cjwatson> ah, I just didn't wait long enough
[09:11] <cjwatson> yep, expanders back, thanks
[09:12] <StevenK> cjwatson: Yes, mawson's webapp takes an eon to actually start serving requests
[09:13] <StevenK> cjwatson: I tend to tail -f the nohup file just so I can know when it's actually going to answer
[09:35] <cjwatson> when do deployments lock down for Ubuntu release?
[09:36] <cjwatson> (I actually think that caution is rather less necessary now than it used to be, but perhaps now isn't the time for that debate)
[09:49] <StevenK> cjwatson: We tend to not want to deploy during release week
[09:49] <StevenK> But given it's NDT, it might be okay
[09:55] <wgrant> Deployments are safe now
[09:55] <wgrant> I wouldn't even suggest avoiding fdts during release week
[09:55] <wgrant> It's been a very long time since something broke badly
[09:55] <czajkowski> wgrant: lets not jinx it ;)
[09:55] <wgrant> cjwatson: Did you use /Running/LXC?
[09:55] <cjwatson> wgrant: Yes
[09:56] <StevenK> wgrant: I seem to recall you objecting to +combo on mawson
[09:56] <cjwatson> wgrant: No hitches at all
[09:56] <wgrant> StevenK: Only in that I needed it working earlier than I could convince ops to set up convoy
[09:57] <wgrant> cjwatson: Great, wasn't sure if that still worked
[09:57] <StevenK> wgrant: convoy is on mawson
[09:57] <wgrant> StevenK: Installed
[09:57] <cjwatson> With a raring host, for the record
[09:57] <wgrant> But not configured in apache
[09:57] <StevenK> wgrant: Right, but we can probably just get the snippet from qas clagged into mawson
[09:57] <wgrant> cjwatson: btw, I think that any Ubuntu developer who isn't using LXC is probably missing out
[09:57] <StevenK> With a path change or two
[09:58] <wgrant> StevenK: Probably
[09:58] <wgrant> Feel free to convince ops to do it :)
[09:58] <cjwatson> Well, it depends what you're doing, but it does seem pretty useful.  I used it seriously for the first time yesterday to debug an Upstart problem
[09:58] <cjwatson> stgraber has been pimping it at us for a year or more
[09:59] <wgrant> Until 9 months ago or so it was dreadfully buggy and unstable
[09:59] <wgrant> But it's great now
[10:01] <StevenK> wgrant: Sure, but I've forgotten how qas is set up :-)
[10:48] <czajkowski> cjwatson: the bug you just commented on that seb128 filed is that something you will be working on
[10:48] <czajkowski> if so waht way do you want it triaged
[10:48] <cjwatson> not immediately since it has some complex dependencies
[10:49] <cjwatson> feel free to triage as you would normally do
[10:49] <wgrant> That's Low at highest
[10:49] <wgrant> It's tempting to introduce a new priority just to use that :)
[10:49] <wgrant> A new, lower priority :)
[10:49] <cjwatson> it's not entirely unimportant for us
[10:49] <cjwatson> since it just caused a big argument on -release :)
[10:50] <cjwatson> as I say I personally think we should do this by (a) get build cancellation working reliably (b) make builds auto-supersede cleanly even before the new source publishes, which would be lovely anyway both for Ubuntu and PPAs (c) change our queue handling policy to accept all the uploads for a source at once
[10:50] <cjwatson> there are a few other possibilities but I think that's the least broken
[10:51] <wgrant> Quite possibly, but the auto-superseding before the publisher bit will be problematic.
[10:57] <cjwatson> I assumed it wasn't easy or we'd already be doing it
[10:57] <cjwatson> But even so :)
[23:14] <StevenK> wgrant: The overlay seems very attached to being wide


 Oh
[09:49] <BluesKaj> Hey folks
 Hey blueskaj
[13:00] <BluesKaj> hi Swift110
 How r u
[13:15] <BluesKaj> ok here, and you?
 Im good just relaxing for now
[16:30] <jubo2> I need clean systems
[17:34] <magic_ninja_work> is the connection manager just a frontend to ip addr
[17:49] <BluesKaj> magic_ninja_work, connection manager or network-manager?
[17:56] <richkub> hello?
[17:57] <diogenes_> hi
[18:00] <richkub> is this a place you can post questions about kubuntu?
[18:04] <lordievader> Yes
[18:06] <diogenes_> more than that, sometimes you can even get an answer :)
[18:08] <richkub> :S
[18:08] <richkub> well I have a quick question then: Does Kubuntu 19.04 come with ufw?
[18:09] <lordievader> Preinstalled? No idea. You can install it though.
[18:09] <diogenes_> richkub, you can check it yourself right here: https://distrotest.net/Kubuntu
[18:09] <lordievader> Easy way to check is to download and run a live-cd.
[18:09] <diogenes_> just start it in your browser and have a look.
[18:12] <richkub> well
[18:12] <richkub> i did sudo ufw enable
[18:12] <richkub> and it enabled
[18:13] <richkub> so I guess that means it's on the ISO?
[18:14] <richkub> i can't find it being mentioned anywhere in the documentation
[18:14] <richkub> ubuntu says they have it
[18:14] <richkub> but not kubuntu
[18:14] <diogenes_> richkub, run: apt list --installed | grep ufw
[18:15] <diogenes_> you nned to have 2 packages, ufw and gufw (for gui applications)
[18:39] <magic_ninja_work> BluesKaj, I had my questions answer in the ubuntu channel. It was regarding the general function of networking and how it worked.
[18:41] <BluesKaj> magic_ninja_work, ok
[18:42] <magic_ninja_work> Seems the connectionsmanager in kde uses network manager
[18:47] <BluesKaj> connection manager is for messaging cklients mostly , is it not?
[18:48] <lordievader> Most gui network managers are just frontends for NetworkManager.
[18:53] <BluesKaj> yeah, i don't use NM anymore, back to the interfaces file for me  with ifupdown :-)


[15:59] <FKAShinobi_> Is there a way to identify a drive (not a partition) by UUID or some other non-changing id?
[16:02] <raub> FKAShinobi_: AFAIK yes since that is used sometimes in /etc/fstab
[16:04] <raub> NVM, I mentioned partition
[16:04] <InPhase> FKAShinobi_: Run blkid as root, then run it again but pass the /dev/ without the partition label.
[16:04] <InPhase> FKAShinobi_: There is a "PTUUID" number which appears.  I think that is disk-specific.
[16:04] <InPhase> FKAShinobi_: I am not sure what it means or where it is stored, but it is there.  :)
[16:06] <InPhase> FKAShinobi_: Example, my root partition is on /dev/nvme0n1p3, and "sudo blkid /dev/nvme0n1" gives the PTUUID which I think is disk-specific.
[16:07] <InPhase> FKAShinobi_: I think it can be overwritten though upon wiping the disk and recreating the partition table from scratch.
[16:07] <Sand-dan-Glokta> hello, anyone experienced with amd egpu?
[18:36] <ashu> hi everyone, I'm ashutosh raj(/nickname - ashu) ,undergraduate from computer science and engineering ,currently at my third yr in NIT HAMIRPUR, INDIA .Looking for contribution on metabrainz repo with tech stack Reactjs and perl.hope u guide me through the whole process .
[18:37] <lotuspsychje> !contribute | ashu
[18:43] <zealot666> https://ok.ru/video/1150628203114
[18:43] <leftyfb> zealot666: spamming is offtopic here
[18:43] <zealot666> ok
[18:44] <zealot666> hello ubuntu kick ass
[18:44] <leftyfb> *** fair warning, nobody click that link ***
[18:44] <zealot666> thank you lefty
[19:02] <Chunkyz> I clicked it, too late.
[19:22] <amosbird-> Hello! Why do I get some "sshd: amos@pts/1" consuming 100% CPU after ssh-connecting to a ubuntu jammy server? It happens after connecting to the server for some time
[19:28] <amosbird> flamegraph shows rarely useful information, something around ppoll http://oracle.wentropy.com/a6da2c4b6013a776
[19:53] <ravage> amosbird, https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1986521 is this your bug?
[19:53] -ubottu:#ubuntu- Launchpad bug 1986521 in openssh (Ubuntu Jammy) "ssh client spins if output fd closed" [Medium, Fix Committed]
[19:55] <amosbird> ravage: I'm not sure. Is it already released?
[19:56] <ravage> its in -proposed
[19:56] <ravage> so if you enbale that you should get the update
[19:57] <amosbird> ravage: hmm, how can I enable that?
[19:59] <ravage> sudo sh -c "echo 'deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe' > /etc/apt/sources.list.d/proposed-repositories.list" && sudo apt update
[20:00] <ravage> maybe look if you see the update there before just upgrading all packages
[20:00] <ravage> i would just do "sudo apt upgrade openssh-server"
[20:00] <ravage> then remove the list file again
[20:00] <ravage> and do another apt update
[20:03] <amosbird> ravage: cool. thanks
[20:05] <amosbird> ravage: hmm, but sudo apt upgrade openssh-server still prompts  : 174 upgraded, 7 newly installed, 0 to remove and 1 not upgraded.
[20:08] <morgan-u2> MAMA TRIED: zoom from browser, chrome. died: and this -  gnome-shell[1934]: libinput error: event14 - Lite-On Technology Corp. USB Multimedia Keyboard: client bug: event processing lagging behind by 29ms, your system is too slow
[20:08] <ravage> amosbird: did you start from a fully upgraded system?
[20:08] <amosbird> nope
[20:09] <ravage> that is strongly adviced :)
[20:09] <amosbird> ok)
[20:09] <ravage> so remove that list file. do "apt update" and then "apt full-upgrade"
[20:09] <ravage> then try again
[20:10] <ravage> should look like this: https://p.haxxors.com/ar5jik79.txt
[20:11] <ravage> sorry. https://p.haxxors.com/zjitr5fs.txt
[20:19] <amosbird> hmm, I just did apt upgrade. Do I need apt full-upgrade?
[20:20] <ravage> full-upgrade is fine. but only without the added proposed
[20:21] <amosbird> After fully upgraded, I add the -proposed list and do sudo apt upgrade openssh, it still prompts a lot of packages  http://oracle.wentropy.com/da580ab3101ecb08
[20:22] <ravage> those updates will arrive sooner or later anyway. its always good to have backups of course
[20:23] <ravage> so i would just let it upgrade those packages. then remove the proposes repo agaon
[20:23] <ravage> *again
[20:23] <amosbird> Ok
[20:51] <FKAShinobi_> How do I enable SMART reporting on my Samsung 980 PRO on Ubuntu 22.04? GSmartControl does not allow me to enable it...
[21:54] <jhutchins> FKAShinobi_: That's likely because the drive doesn't support smart.
[21:55] <jhutchins> FKAShinobi_: Make sure you check with the actual CLI tools, the GUI wrappers can induce problems.
[21:56] <jhutchins> FKAShinobi_: It's also best to look for info on the actual drive, Samsung may use dozens of different makes and models in any given device.
[21:56] <rfm> my 980 PRO certainly reports SMART (but it's on Windows)
[21:58] <jhutchins> Ah, I see, that's an actual drive, not a device with a drive in it.
[22:06] <renanntj> Opa
[22:07] <leftyfb> renanntj: hellp, what can we help you with?
[22:08] <renanntj> opa
[22:08] <renanntj> clear
[22:22] <Macwinner> on my jammy server, i did "apt upgrade", and got "The following packages have been kept back: grub-common grub2-common"
[22:22] <Macwinner> curious why they are held back. "grub-common/jammy-updates 2.06-2ubuntu7.1 amd64 [upgradable from: 2.06-2ubuntu7]"
[22:22] <rbox> try dist-upgrade
[22:22] <Jeremy31> Macwinner: Might be phased updates
[22:23] <leftyfb> !phasedupdated | Macwinner
[22:23] <leftyfb> !phasedupdates | Macwinner
[22:23] <Macwinner> oh, got it.. thanks!
[22:23] <jhutchins> Clearly apt's response messageing could use some work.
[22:24] <Macwinner> yeah.. maybe just an indication of "... held back (phased updates)"
[22:26] <torbjorn_> how do I find out how my network is configured? I installed (what I believe is) a fairly minimal ubuntu 22.04 virtual guest, using libvirtd, and configured static ip during installation, and now when its up and running, it has that IP but I dont know how its configured. There is no interfaces file. NetworkManager is not installed, there is no network service installed. Yet the ip coms up as it should
[22:26] <torbjorn_> when I reboot.
[22:26] <rbox> torbjorn_: netplan
[22:26] <leftyfb> !netplan | torbjorn_
[22:28] <torbjorn_> thanks
[22:31] <torbjorn_> so its systemd-networkd.service that does the actual work?
[22:33] <leftyfb> yes, but it's never a good idea to mess with that directly unless you know exactly what you are doing and how to recover when it breaks
[22:33] <leftyfb> torbjorn_: netplan is how you configure your network
[22:34] <torbjorn_> how do I implement changes to network config on a running system, short of rebooting it?
[22:34] <leftyfb> !netplan | torbjorn_
[22:35] <torbjorn_> apply, gotcha
[22:37] <torbjorn_> in my parcitular case, I lose my original default gateway when I restart my openvpn connection, but that might aswell be an openvpn problem.
[22:37] <torbjorn_> knowing how to get it back the right way, helps
[22:37] <Bashing-om> torbjorn_: Once edits are made: ' sudo netplan --debug generate ' <-  test the configuration -- ' sudo netplan apply ' <- make the settings stick/
[23:01] <torbjorn_> I installed network-manager, and added `  renderer: NetworkManager`  on the 2nd indent level in my only netplan yaml file, and stopped systemd-networkd, ran netplan generate and then apply and also restarted NetworkManager. I still had my static ip setup afterwards, but I cuold no longer resolve hostnames.
[23:02] <torbjorn_> after rebooting I could though. not one to split too many hairs over something thats working, but that switch from entworkd to NM should have worked, right?
[23:02] <leftyfb> why?
[23:03] <leftyfb> torbjorn_: what was wrong with just using netplan? What are you trying to accomplish that netplan doesn't let you achieve ?
[23:03] <torbjorn_> openvpn
[23:03] <leftyfb> client or server?
[23:03] <torbjorn_> client
[23:03] <torbjorn_> but surely using netplan to render network-manager config qualifies as still "using netplan"?
[23:04] <leftyfb> you shouldn't need to do all of this just to use an openvpn client on an ubuntu server with netplan
[23:04] <torbjorn_> I mean I'm letting it render the config files, just opted for what renderer I wanted
[23:04] <torbjorn_> not render, "im letting it configure the network"
[23:04] <torbjorn_> leftyfb: I dont consider manually assigning networkmanager as renderer is "all of this"
[23:05] <torbjorn_> its just a single line in a netplan yaml file
[23:06] <torbjorn_> and I have my ip address config just right afterwards, worked flawlessly. it was just dns lookups that was broken.
[23:06] <leftyfb> you have 3 layers of network management as opposed to 2. If it were me, I would troubleshoot what your openvpn client/config is doing that you don't want and resolve that. Not add another layer on top that isn't likely to solve anything
[23:06] <torbjorn_> sorry I swapped from networkd to network-manager, how is that adding a layer
[23:06] <torbjorn_> (not saying it isnt)
[23:10] <torbjorn_> leftyfb: ?
[23:12] <leftyfb> torbjorn_: I'm sure someone here might be willing and able to help you with that configuration.
[23:12] <torbjorn_> thats be fine. i was just curious what you meant wiht 3 layers
[23:13] <torbjorn_> surely NM _replaces_ networkd, it doesnt add ontop of it
[23:14] <Quark> Does Ubuntu offers the choice to install on ZFS (at install time)?
[23:15] <Quark> Ubuntu server, that is.
[23:17] <Bashing-om> Quark: Not at this time. See: https://discourse.ubuntu.com/t/future-of-zfs-on-ubuntu-desktop/33001 .
[23:43] <morgan-u2> Yes!
[23:43] <morgan-u2> as long as your specs aren’t terrible (16gb RAM, i5, gtx1050 should be fine) you can get 60fps at 1080p or above. (tomr luck sarnold arraybolt3 whoever else has been into this if any are on sunday that is)
[23:44] <morgan-u2> nono... forget it. I asked 3 hrs ago.
[23:44] <morgan-u2> this was a wrong...
[23:49] <hao> using 22.10. the dmesg is flooded with error:  RTW: ERROR [RFK-CHK] RF-K not allowed due to ifaces under site-survey
[23:52] <hao> RTW seems to be the rtl8821CU wireless usb driver, indeed when using firefox, every time when there is significant lag when receiving pages, the error log will be written into dmesg
[23:54] <Quark> Bashing-om, thank you! You saved me quite a bit of time. Appreciated.
[23:54] <hao> there is also errors regarding complaining firefox can not read dconf/db/*, also gnome-shell complaining can not update views actor, but I think those are irrevalant
[23:54] <hao> there is too few results online, anyone have similar wifi issue? I?
[23:55] <hao> s/I?//


[18:14] <ibeardslee> morning
[18:59] <Atamira> morning
[19:49] <hads> morning
[20:57] <olly> morning


[03:36] <smartboyhw> ScottK, when can you approve the in-queue raring SRU for ibus-cangjie for me?
[03:51] <smartboyhw> Season of KDE... Any ideas as to how to join?
[03:55] <valorie> do you have a project in mind?
[03:56] <valorie> and a willing mentor?
[03:56] <valorie> we're not quite ready for students to sign up, but the announcement will be published Any Time Now
[03:56] <smartboyhw> valorie, the problem is no and no. (I don't know who really wants to be a mentor of me)
[03:57] <valorie> think about a project that will take you between one and two months
[03:57] <smartboyhw> em.......
[03:57] <valorie> and we'll try to find you a mentor if you can't find one
[03:58] <smartboyhw> BTW, someone add the new SSH key from my Launchpad profile to the KDE sftp plz (yes, again)
[03:58] <valorie> it can be programming, but it doesn't have to be
[03:59] <smartboyhw> And is anybody doing Calligra 2.7.1 ?
[04:02] <smartboyhw> valorie, I will not try a programming project..
[04:02] <smartboyhw> My programming is crap
[04:02] <valorie> heh
[04:03] <smartboyhw> valorie, yeah....
[04:04] <valorie> so what do you like to do?
[04:05] <valorie> I think packaging is not on the list of possible projects
[04:05] <smartboyhw> valorie, I know :P
[04:05] <smartboyhw> Probably doc
[04:06] <smartboyhw> http://community.kde.org/Getinvolved
[04:06] <smartboyhw> Sounds like the only thing I can do (non-dev wise)
[04:06] <smartboyhw> translations takes me 3 months:P
[04:06] <smartboyhw> And my art is ****
[04:07] <valorie> is there anything you like (an application, an area) that lacks good documentation?
[04:07] <valorie> that's how I got involved in the first place: user docs for Amarok
[04:08] <smartboyhw> Let me see...
[04:10] <smartboyhw> valorie, I don't know, really.
[04:11] <valorie> you might ask on the KDE docs list
[04:12] <valorie> I'd suggest the IRC channel, but there is little discussion there
[04:12] <smartboyhw> valorie, is there any list of previous projects for SoK 2012?
[04:12] <valorie> oddly enough, the mail list is: https://mail.kde.org/mailman/listinfo/kde-doc-english
[04:13] <smartboyhw> valorie, oddly?
[04:14] <valorie> http://community.kde.org/GSoC/2012/Ideas
[04:14] <valorie> I think it's odd that the main list is called KDE-Doc-English
[04:14] <smartboyhw> valorie, eh hum GSoC != SoK !?
[04:16] <valorie> I guess googling in general is the only way to get a list
[04:16] <valorie> however, there are lots of reports
[04:17] <valorie> it's true that in general SoK projects are smaller than GSoK
[04:17] <smartboyhw> valorie, oh reports, where're they?
[04:17] <valorie> I mean GSoC
[04:18] <valorie> I googled for "projects for SoK 2012"
[04:18] <valorie> and got quite a few individual, different hits
[04:21] <smartboyhw> valorie, email sent to the KDE Doc list
[04:21] <valorie> nice
[04:29] <smartboyhw> valorie, ooh
[04:29] <smartboyhw> Moreover, as Kubuntu was mentioned, can you look into Muon and document its usage if you find this appropriate.
[04:29] <smartboyhw> In a reply email
[04:29] <smartboyhw> Hmm, probably Muon then (LOL)
[04:30] <valorie> if you find a mentor, which.... seems like a slam-dunk
[04:31] <smartboyhw> valorie, which... ?
[04:31] <valorie> jontheechidna
[04:32] <valorie> the creator of muon
[04:32] <valorie> that sounds like a win win win for everyone
[04:38] <smartboyhw> valorie, yeah yeah :P
[04:41] <valorie> including you: tshirt, certificate, etc.
[04:45] <smartboyhw> valorie, and experience, that's more important la;P
[04:45] <valorie> of course
[04:45] <smartboyhw> So, wait for jontheechidna to come online then:P
[04:45] <valorie> or drop him an email
[04:46] <smartboyhw> valorie, if I can't see him when I sleep I will drop an email
[04:48] <valorie><EMAIL_ADDRESS>[04:48] <smartboyhw> valorie, got it
[05:19] <smartboyhw> Hey JontheEchidna
[05:20] <smartboyhw> Read http://paste.ubuntu.com/5935253/ :)
[05:23] <smartboyhw> kubotu: newversion calligra 2.7.1
[05:23] <kubotu> https://bugs.launchpad.net/bugs/1207172
[05:25] <JontheEchidna> smartboyhw: I was actually just about to go to bed, but I think that would be a good project.
[05:25] <smartboyhw> JontheEchidna, :)
[05:25] <smartboyhw> So, you are willing to be mentor right?
[05:26] <JontheEchidna> Yes
[05:26] <smartboyhw> \o/
[05:26] <smartboyhw> Thank you JontheEchidna and valorie :)
[05:27] <JontheEchidna> You're welcome
[05:27] <JontheEchidna> Anyway, I'm off to bed.
[05:28] <smartboyhw> Good night JontheEchidna :)
[05:31] <valorie> \o/
[05:57] <smartboyhw> s******** I can't access my blog....
[05:59] <valorie> why?
[06:00] <shadeslayer> !info libgles2-mesa-dev-lts-raring
[06:00] <shadeslayer> !info libgles2-mesa-dev-lts-raring precise
[06:00] <shadeslayer> smartboyhw: did you use the same password as in ubuntuforums?
[06:00] <smartboyhw> shadeslayer, uh hum, I can still access it yesterday
[06:00] <smartboyhw> shadeslayer, look at smartboyhw.tk/wordpress_smartboyhw
[06:01] <smartboyhw> I can't even get to it
[06:01] <smartboyhw> Memory full~!??
[06:01] <shadeslayer> oh
[06:01] <shadeslayer> seems to have OOM'd
[06:01] <shadeslayer> *giggle*
[06:01] <shadeslayer> smartboyhw: can you reboot the server
[06:01] <smartboyhw> shadeslayer, how?
[06:02] <smartboyhw> Actually I discovered that one of my web host server is down for maintenance sigh
[06:02] <shadeslayer> how would I know
[06:02] <shadeslayer> my VPS provides a reset button
[06:03] <shadeslayer> via the control panel thingy
[06:03] <smartboyhw> shadeslayer, no. Can't find reset...
[06:04] <smartboyhw> Yeah, my server is down
[06:04] <smartboyhw> Due to maintenance
[06:04] <smartboyhw> Damn
[06:05] <valorie> woah
[06:05] <valorie> not even a nice "fixing, hang on" page
[06:06] <shadeslayer> hurrah
[06:06] <shadeslayer> yofel: I think I might have to recompile Qt against the new HWE stack to fix the kde-workspace FTBFS in precise
[06:07] <shadeslayer> yofel: http://paste.kde.org/p27df6da3/
[06:07] <shadeslayer> which probably makes sense tbh
[06:08] <smartboyhw> valorie, they do have a notice, IIRC:P
[06:08] <smartboyhw> Server #10 is under the maintenance
[06:08] <smartboyhw> We are currently performing a maintenance on the Server #10. It is estimated that this maintenance should be completed within 2-3 hours.
[06:08] <smartboyhw> Please do not submit and tickets about this issue and do not increase our work load as we are fully dedicated in resolving this server problem. We thank you for your patience and understanding.
[06:08] <smartboyhw> MEH
[06:09] <shadeslayer> o_o
[06:09] <shadeslayer> the most my VPS was down was for 6 hours
[06:09] <shadeslayer> when they were moving from SF to Las Vegas
[06:09] <shadeslayer> ( yeah my server is hosted in Las Vegas, sin city \o/ )
[06:10] <smartboyhw> lol
[06:14] <soee> good morning
[06:39] <jussi> Riddell: you about yet?=
[06:42]  * shadeslayer tackles jussi for not putting more pictures of Elodi on G+
[06:43] <jussi> shadeslayer: cripes... how many dfo you want? :P
[06:43] <shadeslayer> I haven't seen any recent ones on G+ I think
[06:44] <shadeslayer> possibly the algorithm is broken, because I see loads of star wars and stuff
[06:45] <shadeslayer> jussi: also, there can never be enough :P
[06:45] <Tm_T> shadeslayer: there's reason I don't have star wars stuff in my circles on G+
[06:46] <shadeslayer> Tm_T: yeah, I think I'll have to remove that community
[06:46] <shadeslayer> it's overwhelming my feed
[06:46] <Tm_T> also it's mostly junk /:
[06:46] <shadeslayer> true ^^
[06:47] <shadeslayer> not to metnion, overly sexist
[06:47] <Tm_T> shadeslayer: as in, there' way more sane ways to follow SW
[06:47] <Tm_T> that
[06:47] <shadeslayer> I see
[06:49] <shadeslayer> agateau: are you around?
[06:49] <smartboyhw> Can anyone provide patch to https://launchpad.net/ubuntu/+source/amarok/2:2.7.90-0ubuntu1 plz?
[06:49] <smartboyhw> For the you know qreal thing
[06:49]  * shadeslayer looks
[06:50] <shadeslayer>   (found suitable version "4.8.4", minimum required is "4.8.2")
[06:50] <shadeslayer> what o_o
[06:50] <shadeslayer> ah
[06:50] <shadeslayer> opengl
[06:50] <smartboyhw> opengl
[06:50] <smartboyhw> ah
[06:50] <smartboyhw> What happened to opengl now?
[06:50] <smartboyhw> I mean, is it updated now?
[06:50] <shadeslayer> well
[06:50] <shadeslayer> there is no opengl on arm afaik
[06:50] <shadeslayer> there's only GLES
[06:51] <smartboyhw> shadeslayer, ah yeah
[06:51] <smartboyhw> So, either we move it to -release, or it will be forever stuck:P
[06:52] <smartboyhw> We had this discussion before I left for UK
[06:52] <shadeslayer> ScottK: ^^ plz be forcing amarok
[06:52] <smartboyhw> And it is still here after I came back>>>>>>>
[06:52] <ScottK> smartboyhw: I can remove the arm binary, but forcing it causes more problems than it solves.
[06:53] <smartboyhw> ScottK, oh. Rm ARM binary then
[06:58] <smartboyhw> WHO DIDN"T UPDATE THE -l10n for 2.7.0!??!?!?
[06:58] <smartboyhw> Anyways
[06:59] <ScottK> Gone.
[07:00] <ScottK> Someone go make sure it's not seeded on arm now.
[07:00] <smartboyhw> I nominate yofel or shadeslayer
[07:02] <smartboyhw> Or Riddell
[07:04] <smartboyhw> Ouch, or rather: Why is calligra-l10n 2.7.0 stuck in proposed!/
[07:04] <smartboyhw> ScottK, can you unfreeze the calligra-l10n 2.7.0 stuck in proposed?
[07:05]  * ScottK looks to see why it's there.
[07:06] <smartboyhw> ScottK, and also (personal favor) approve ibus-cangjie in raring SRU queue.
[07:06] <smartboyhw> Sorry for making you doing a lot of things:P
[07:06] <ScottK> Not today.  It's 3AM here.
[07:07] <smartboyhw> ScottK, OK.
[07:09] <ScottK> smartboyhw: I think the issue is that it's blocked on language-pack-kde-en due to calligra-l10n-engb being dropped.  Than lang pack needs to be fixed to not need that.
[07:09] <smartboyhw> ScottK, oh oh
[07:09] <ScottK> You need Riddell or apachelogger for that kind of thing, I think.
[07:09] <smartboyhw> OK, apachelogger Riddell ^^
[07:10] <smartboyhw> ScottK, wait. If I upload a 2.7.1 ver of calligra-l10n without calligra-l10n-engb and without language-pack-kde-en as build-dep
[07:10] <smartboyhw> will it get through?
[07:12] <smartboyhw> Or you mean that language-pack-kde-en is killed?
[07:13] <smartboyhw> Or you mean that language-pack-kde-en depends on calligra-l10n-engb?
[07:13]  * smartboyhw thinks the third
[07:16] <smartboyhw> OK I got it
[07:16]  * smartboyhw roars at the packages
[07:16] <smartboyhw> Can somebody kindly fix that?
[07:30] <lordievader> Good morning.
[07:32] <agateau> shadeslayer: I am there now
[07:32] <shadeslayer> ah hi
[07:33] <shadeslayer> agateau: is this all I need to do to setup codereviews in Qt https://qt-project.org/wiki/Setting-up-Gerrit
[07:33] <shadeslayer> and should I be using a branch for my commits and push that to gerrit?
[07:34] <agateau> shadeslayer: yes, this page is enough
[07:35] <shadeslayer> agateau: ack, and is there some sort of agreement that I have to sign?
[07:35] <agateau> one question at a time :)
[07:35] <agateau> shadeslayer: using branches is a good idea if you start multiple changes
[07:35] <shadeslayer> right :)
[07:35] <agateau> especially since it can take some back and forth before it is merged
[07:36] <agateau> but the trick is you don't push your branch to a branch named the same on gerrit
[07:36] <agateau> you push using "refs/for/$foo", where $foo is the name of the branch you want to get your patch in
[07:37] <agateau> so if you created a branch to add a new feature for the "dev" branch, you would push using "git push gerrit HEAD:refs/for/dev"
[07:37] <agateau> this will give you an url for your change in the output of your push
[07:38] <agateau> whenever you change the fix, you update your commit (you don't create a new commit) and push again to the same refs/for/$foo
[07:38] <shadeslayer> uhm, isn't for/dev a common branch for everyone?
[07:38] <shadeslayer> and won't that conflict and what not? or does gerrit just post the diff from the current dev and adds a patch to reviewboard
[07:39] <agateau> "dev" is a common branch, "refs/for/dev" is gerrit magic to make it create a request, as I understand it
[07:39] <shadeslayer> okay
[07:40] <smartboyhw> valorie, http://season.kde.org/?q=program_home&prg=8
[07:40] <smartboyhw> LOL
[07:40] <valorie> yep, we're not quite ready
[07:40] <valorie> soon, soon
[07:40] <agateau> shadeslayer: regarding agreement: yes you need to agree to qt cla. this can be done online.
[07:41] <smartboyhw> Oops
[07:41] <smartboyhw> I clicked on "Apply to mentor" (I thought it was apply for student) DAMN
[07:41] <smartboyhw> valorie, plz get that off:P
[07:41] <agateau> shadeslayer: assuming you have an account on gerrit already, there is a page in your gerrit profile to do so
[07:41] <agateau> shadeslayer: it does not take long
[07:41] <shadeslayer> yep, was just looking at that
[07:46] <valorie> I'll see if I can, smartboyhw
[07:47] <valorie> rejected
[07:48] <smartboyhw> valorie, Your mentorship application has been declined and you cannot participate in this program does that mean I now can't even participate as student?
[07:48] <valorie> no
[07:48] <valorie> It means you tried to apply too early
[07:48] <smartboyhw> valorie, phew
[07:49] <valorie> I'm sure we'll pull the reset button before launching
[07:49] <valorie> I reported what happened just now, just in case
[07:49] <valorie> good to know that the email function is working
[08:04] <yofel> smartboyhw: rebuilding qt probably makes sense, but this is really apt-get's dependency resolver being crap in precise, aptitude resolves that fine
[08:04] <yofel> er, shadeslayer ^
[08:04] <shadeslayer> heh
[08:05] <yofel> I did manage to reproduce that with pbuilder-satisfydepends-classic, but didn't have time to do anything more than that
[08:31] <Quintasan> \o
[08:54] <Riddell> jussi: you pinged?
[09:04] <Riddell> hmm, qtwebkit built but with a new gl(es) error on arm
[09:25] <Riddell> we got our first donation!
[09:26] <Riddell> $30 turned into £29.10
[09:26] <Tm_T> woo
[09:27] <Riddell> no wait, £30 turned into £29.10 sent from a USD paypal account
[09:27] <Tm_T> Riddell: where's donation details? was going to add link to it to my email sig
[09:28] <Riddell> hmm no even worse, Net amount:	 £28.33 GBP
[09:28] <Riddell> Fee amount:	 -£1.67 GBP
[09:28] <Riddell> these paypal people know how to make money
[09:28] <Riddell> Tm_T: just made this yesterday, think it's good enough to launch? http://www.kubuntu.org/donate
[09:28] <jussi> Riddell: we should direct people to the Holvi thing. its 90c per transaction
[09:29] <Riddell> jussi: mm have I heard of that?
[09:30] <Tm_T> Riddell: I'm ok with it, although I hope paypal isn't mandatory
[09:30] <jussi> Riddell: yeah, its the thing I have been planning to use as the tshirt selling platform - we talked about it before
[09:30] <jussi> with the open budget and all
[09:31] <Riddell> ah hah
[09:32] <Riddell> well this'll be good enough to get on with for now
[09:42] <agateau> Riddell: have you considered setting up a flattr account for Kubuntu?
[09:44] <Riddell> agateau: nope, baby steps
[09:44] <Riddell> agateau: do you think we'd get much money through flattr?
[09:44] <Riddell> ta da! kubuntu.org/news/now-open-donations
[09:45] <agateau> Riddell: I would not expect you'd get overflowed by donations, but more channels to receive money is always a good thing I guess, and you may also get people to subscribe to it (ie, automatically flattr kubuntu every month)
[09:46] <Riddell> another item for the todo :)
[09:47] <agateau> Riddell: link in the news is wrong
[09:47] <agateau> Riddell: it points to /news/donate instead of /donate
[09:47] <Riddell> well spotted, fixed
[09:50] <agateau> Riddell: just read planetkde... so my new nickname is "Aurélien Le Cake"? :)
[09:54] <jussi> Riddell: I put up some examples here: https://holvi.com/shop/Kubuntu/
[09:56] <jussi> Riddell: and the open budget you can see by clicking the link in the top corner, or here: https://holvi.com/avoinbudjetti/Kubuntu/
[09:58] <Riddell> ah yes, only Finland for now
[10:00] <jussi> Riddell: only finland for admin side - worldwide for actual payments and so on
[10:06] <smartboyhw> Riddell, yofel http://paste.kde.org/p2cc15469/ for Calligra, anything you think that shouldn't be there?
[10:07] <smartboyhw> It's 2.7.1 BTW
[10:08] <Riddell> smartboyhw: oh cool
[10:08] <Riddell> I think all those lintian issues are acceptable
[10:08] <smartboyhw> Yeah, packaging 1 day after I came back from London... Really busy:P
[10:08] <smartboyhw> Riddell, greato
[10:13]  * Riddell puts a banner on http://www.kubuntu.org/
[10:13] <smartboyhw> Riddell, can you fix the language-pack-base-en depend on calligra-l10n-engb problem
[10:16] <Riddell> smartboyhw: I think that needs calligra-l10n-engb removed from the archive
[10:16] <smartboyhw> Riddell, meh
[10:16] <smartboyhw> Riddell, you are archive admin, remove it:P
[10:17] <Riddell> all our calligra-l10n package are an old version
[10:17] <Riddell> smartboyhw: so first step is packagine 2.7.1
[10:17] <smartboyhw> Riddell, because 2.7.0 is stuck in -proposed
[10:17] <smartboyhw> Due to that problem
[10:17] <smartboyhw> So even if I upload anything, it will still be stuck
[10:18] <Riddell> ah, circular, the language-pack script looks to see what's in the archive
[10:19] <Riddell> well can be easily done by hand
[10:19] <smartboyhw> Riddell, hand = you:p
[10:19] <smartboyhw> Thank you:)
[10:20] <smartboyhw> BTW, what's the best way to branch the calligra-l10n 2.7.0 source so I can work on the 2.7.1 one?
[10:20] <smartboyhw> Download, rather
[10:21] <Riddell> smartboyhw: apt-get, download from https://launchpad.net/ubuntu/+source/calligra, it should be in bzr if I did it right
[10:21] <Riddell> kbzr co calligra
[10:21] <smartboyhw> Riddell, I mean -l10n
[10:21] <smartboyhw> Not the main one
[10:21] <smartboyhw> Almost finishing the main here
[10:22] <Riddell> oh I had a script for that
[10:22] <Riddell> calligra-l10n-package in kubuntu-automation
[10:23] <smartboyhw> Riddell, :O
[10:23] <smartboyhw> Oops
[10:23] <smartboyhw> LOL
[10:23]  * Riddell runs dput ubuntu language-pack-kde-en_13.10+20130705.0ubuntu1_source.changes
[10:32] <agateau> mmm, that qtchooser thing is getting on my nerves. How do I get qmlscene to open a silly qtquick2 example?
[10:33] <agateau> it complains about QtQuick not being installed, even if I have libqt5quick5 installed
[10:34] <smartboyhw> Riddell, eh hum add back my SSH key to the ftpmaster.kde.org plz (yes, my computer can't boot when I came back, so...)
[10:36] <smartboyhw> It's in my LP page launchpad.net/~smartboyhw
[10:36] <Riddell> smartboyhw: mm I wouldn't have removed it
[10:36] <smartboyhw> Riddell, it's new
[10:36] <smartboyhw> Shouldn't have used the word "back"
[10:37] <Riddell> I see smartboyhw@smartboyhw-Compaq-Presario-CQ41-Notebook-PC is on there
[10:37] <smartboyhw> Riddell, it's a new one, trust me
[10:37] <smartboyhw> BTW, Review time for https://launchpad.net/~smartboyhw/+archive/ppa/+files/calligra_2.7.1-0ubuntu1.dsc
[10:37] <Riddell> smartboyhw: remove your old one?
[10:37] <smartboyhw> The changes are on the kubuntu-packaging branch already
[10:37] <smartboyhw> Riddell, I removed it already.
[10:38] <smartboyhw> Or you mean in ftpmaster.kde.org
[10:38] <smartboyhw> ?
[10:38] <Riddell> smartboyhw: key added
[10:39] <smartboyhw> Riddell, thank you
[10:39] <smartboyhw> Good, the script now works
[10:40] <smartboyhw> That script is real great!
[10:43] <smartboyhw> Riddell, got anytime to review the calligra 2.7.1 package?
[10:43] <Riddell> smartboyhw: yep, anything changed since 2.7.0?
[10:44] <smartboyhw> Riddell, you mean the packaging or?
[10:44] <Riddell> yeah packaging
[10:44] <smartboyhw> The packaging changes are in the kubuntu-packaging branch
[10:44] <smartboyhw> Basically the qreal patch dropped (included in upstream)
[10:44] <smartboyhw> And some files removed from install files
[10:44] <smartboyhw> Nothing much
[10:45] <Riddell> /usr/share/kde4/apps/mime/packages/krita.xml disappeared?
[10:45] <Riddell> hmm and libkochart too?
[10:47] <smartboyhw> Riddell, eh heh.
[10:47] <smartboyhw> Maybe I should check the build logs
[10:48] <smartboyhw> Nothing special except I think a new build-dep
[10:49] <smartboyhw> Which I've never heard of...
[10:49] <smartboyhw> It's optional
[10:49] <smartboyhw> And doesn't even exist within Ubuntu repos
[10:50] <Riddell> opensomething?
[10:50] <Riddell> it's not got an upstream release
[10:50] <Riddell> so the upstream (who is both calligra and opensomething) said to leave it for now
[10:51] <smartboyhw> Riddell, uh hum then those files are REALLY missing then
[10:52] <smartboyhw> hot says:
[10:52] <smartboyhw> Should the support for PowerPC Desktop be continued?
[10:52] <smartboyhw> Yes, continue support - 20.7% (167 votes)
[10:52] <smartboyhw> No, don't support and bury it - 79.3% (639 votes)
[10:52] <smartboyhw> so Ubuntu Desktop discontinued powerpc
[10:52] <smartboyhw> Hmm..... (smartboyhw wants to re-mention killing it for Kubuntu)
[10:53] <Riddell> where is that?
[10:53] <smartboyhw> Riddell<EMAIL_ADDRESS>[10:53] <smartboyhw> A Russian survery
[10:53] <Riddell> [ubuntu/saucy] calligra-l10n 1:2.7.0-0ubuntu1 (Accepted)  ta da
[10:53] <smartboyhw> + former announcements about killing
[10:53] <Riddell> just in time for 2.7.1 :)
[10:53] <smartboyhw> Riddell, \o/
[10:54] <smartboyhw> srsly, should we kill ppc?
[10:55] <Riddell> I'd be all for it
[10:55]  * smartboyhw is for PPC
[10:55] <smartboyhw> Killing I mean
[10:55] <Riddell> micahg: kde-workspace change made, debian agreed it should be added
[10:55] <smartboyhw> Riddell, I am suggesting to put forward to Kubuntu Council for a vote:P
[10:55] <Riddell> kwin-style-crystal uploaded
[10:55] <apachelogger> the only reason we have ppc still is becasue the case was made that since we have builds and as long as someone QAs the iso there is no reason not to have ppc
[10:56] <apachelogger> so I suppose we are rather indifferent :P
[10:57] <smartboyhw> apachelogger, so?
[10:57] <smartboyhw> Damn, why am I included in the elementary-l10n-council!?!?
[10:57] <smartboyhw> What the
[11:01] <smartboyhw> Anyways, I will start a discussion about Kubuntu PPC builds on<EMAIL_ADDRESS>Anyone object?
[11:02] <Riddell> go ahead
[11:08] <apachelogger> what's there to discuss?
[11:10] <smartboyhw> apachelogger, bury it?
[11:13] <apachelogger> why would we discuss this in a kubuntu scope?
[11:13]  * apachelogger thinks a pointer to the ubutnu-devel discussion is what should be sent to kubuntu-devel
[11:13] <smartboyhw> apachelogger, why shouldn't we?
[11:14] <apachelogger> because we cannot discuss whether to kill a build architecture, that's a discussion that needs to happen at global ubuntu project scope
[11:15] <apachelogger> we can discuss whether to kill our ppc iso, which we did not too long ago as I mentioned earlier
[11:15] <smartboyhw> apachelogger, I mean to kill the PPC ISO ofc
[11:15] <apachelogger> we did that
[11:15] <apachelogger> answer is no
[11:15] <smartboyhw> apachelogger, but that is before Ubuntu decided to drop desktop PPC
 the only reason we have ppc still is becasue the case was made that since we have builds and as long as someone QAs the iso there is no reason not to have ppc
[11:17] <smartboyhw> apachelogger, I know.
[11:17] <smartboyhw> But I think that needs to change.
[11:17] <apachelogger> right
[11:17] <apachelogger> so here's how I will dismantle any argument you could bring up
[11:18] <apachelogger> ... some time ago we decided that we want to keep ppc as  long as we can and as long as we get actual release/iso QA for it
[11:19] <apachelogger> so unless we cannot keep ppc anymore (i.e. the build architecture was dropped from launchpad or put into ports or whatever) or we have a lack of QA suddenly I ask you why your opinion should outweigh the combined opinion of the community as previously stated.
[11:19] <smartboyhw> And then I will object in the QA part.
[11:19] <smartboyhw> Really.
[11:20] <apachelogger> lol?
[11:20] <apachelogger> pleas go ahead :P
[11:22] <BluesKaj> Hiyas all
[11:33] <smartboyhw> Sent.
[11:38] <Quintasan> apachelogger++
[11:41] <Tm_T> smartboyhw: about powerpc images: I haven't managed to get lubuntu running on my machine
[11:41] <Tm_T> maybe I should try the last kubuntu build
[11:41] <smartboyhw> Tm_T, you mean Alpha 2?
[11:41] <smartboyhw> If yes, it is broken
[11:42] <Tm_T> smartboyhw: I mean tested release
[11:42] <smartboyhw> They say they will fix it
[11:42] <smartboyhw> Tm_T, you mean Alpha 2 or 13.04
[11:42] <smartboyhw> ?
[11:42] <Tm_T> I mean 13.04, 12.10 and what else I already tried
[11:42] <smartboyhw> Tm_T, :O
[11:42] <smartboyhw> That's quite a problem
[11:42] <Tm_T> installs fine, then fails to boot with kernel errors
[11:43] <smartboyhw> You should tell the Lubuntu guys:P
[11:43] <Tm_T> I should first pinpoint the issue and make sure it's not my hardware though
[11:43] <smartboyhw> Riddell, is calligra OK?
[12:14] <smartboyhw> Riddell, if you have uploaded calligra 2.7.1 then here's https://launchpad.net/~smartboyhw/+archive/ppa/+files/calligra-l10n_2.7.1-0ubuntu1.dsc for you
[12:20] <smartboyhw> And someone please deal with https://code.launchpad.net/~smartboyhw/ubuntu-seeds/kubuntu.saucy.rm.amarok.armhf/+merge/178054
[12:23] <apachelogger> ^ I think markey fixed opengl requirement upstream already
[12:26] <Tm_T> aaand yet again, in one building, ~5000 people competing and gaming, 4 days http://www.assemblytv.net/pages/player?file=hd.stream&height=720&width=1280
[12:27] <smartboyhw> apachelogger, .........
[12:27] <kubotu> ::workspace-bugs:: [1206176] Powerdevil does not start, linking problem? @ https://bugs.launchpad.net/bugs/1206176 (by aydin demircioglu)
[12:27] <smartboyhw> OK, then may apachelogger fix it:P
[12:27] <smartboyhw> I mean patch it to current version
[12:28] <markey> apachelogger: yes, fixed
[12:28] <apachelogger> smartboyhw: is armhf seed building failing right now?
[12:28] <smartboyhw> apachelogger, not yet, but ScottK told me to do so:P
[12:28] <apachelogger> ah, well just wait for new amarok :P
[12:28] <apachelogger> we have a prerelease right now anyway
 Someone go make sure it's not seeded on arm now.
[12:28] <smartboyhw> :)
[12:29] <smartboyhw> apachelogger, oh really?
[12:29] <apachelogger> ScottK: isn't the seed architecture stuff for stuff we do not want on the seed for seed reasons? like say grub-pc on armhf
[12:29] <apachelogger> smartboyhw: yes
[12:30] <smartboyhw> apachelogger, meh, let me package it then:)
[12:30] <smartboyhw> Is it in ftpmaster?
[12:46] <ScottK> Images will fail until it's fixed.
[12:46] <ScottK> Once we have a new  amarok, we can add it back.
[12:47] <ScottK> There will also have to be a kubuntu-meta upload.
[12:54] <ScottK> I'm away from my computer, so someone please do the merge.
[13:26] <smartboyhw>  Philip Muškovac 71572 points
[13:26] <smartboyhw> Colin Watson 71289 points
[13:26] <smartboyhw> yofel is being chased!
[13:32] <smartboyhw> Darkwing_ (in a G+ post): As of this last week I have migrated my desktop to #Fedora #KDE.
[13:32] <smartboyhw> MEH!
[13:32] <smartboyhw> I'm not fully leaving #Kubuntu but, I'll be far scaled back and far removed.
[13:32] <smartboyhw> :(
[13:32] <smartboyhw> Stay Kubuntu Darkwing_ !!!
[13:50] <Riddell> smartboyhw: does he say why?
[13:50] <smartboyhw> Riddell, if you mean Darkwing, um
[13:50] <smartboyhw> Riddell, The reason for this is twofold. First it was time for a change of pace. I have never used a #RedHat based system and need to learn more and second, I was getting tired of the petty infighting happening within the ubuntusphere.
[13:51] <smartboyhw> Uh hum:P
[13:55] <Riddell> hmm
[13:55] <Riddell> more than petty alas
[13:56] <smartboyhw> Riddell, OK.... (/me still waits for the calligra reviews)
[13:56] <smartboyhw> And should I also run the script to update kubuntu-meta or?
[13:56] <smartboyhw> Wait, you need to merge it first
[13:57] <Riddell> smartboyhw: calligra good, uploading now
[13:57] <smartboyhw> Riddell, :)
[13:57] <Riddell> yeah I'll do that next
[13:57] <Riddell> I had backported calligra 2.7.0 to raring
[13:57] <Riddell> would be worth doing thatwith 2.7.1
[13:59] <smartboyhw> Riddell, good.
[14:00] <smartboyhw> Um, I forgotten that backport function existing in ubuntu-dev-tools again...
[14:00] <smartboyhw> Anyways, just do a changelog upate
[14:01] <smartboyhw> s/upate/update/
[14:01] <kubotu> smartboyhw meant: "Anyways, just do a changelog update"
[14:05] <smartboyhw> Riddell, backport to quantal and precise too? (Without vc-dev as build-dep?)
[14:06] <Riddell> smartboyhw: I might well have done those
[14:06] <Riddell> well not quantal,never seen any point in backpointing to that
[14:07] <smartboyhw> Riddell, yeah, you've done Precise
[14:12] <smartboyhw> Riddell, OOPS I uploaded to wrong PPA......
[14:12] <smartboyhw> I should have done it in backports and instead I did it to the main one.
[14:13] <Riddell> doh
[14:13] <Riddell> smartboyhw: can you delete that?
[14:13] <yofel> delete it while it's not published
[14:13] <yofel> the it won't matter
[14:13] <smartboyhw> Riddell, I think I can copy and delete
[14:13] <yofel> *then
[14:14] <smartboyhw> It will take some time to copy to there....:P
[14:16] <smartboyhw> OK, it's copied.
[14:16] <smartboyhw> DELETE
[14:18] <smartboyhw> DONE
[14:27] <smartboyhw> Riddell, backported to raring, quantal, precise (including -l10n)
[14:29] <smartboyhw> OK, what TODO?
[14:31] <Riddell> smartboyhw: you just put them in the PPA without testing I guess?  that's fine but mind and keep an eye on it for failures
[14:31] <smartboyhw> Riddell, I know. I at least removed vc-dev for quantal and precise, so less chance of failing.
[14:32] <smartboyhw> But, GCC and that sort of stuff
[14:32] <smartboyhw> SIGH
[14:33] <smartboyhw> Ha, I know why the image builds don't fail even with Amarok out of armhf sight: It's still stuck in -proposed
[14:34] <smartboyhw> Riddell, plz unstuck Amarok 2.7.90 in -proposed
[14:35] <Riddell> smartboyhw: what's stuck about it?
[14:37] <smartboyhw> Riddell, no opengl exist in armhf. ScottK removed the armhf binaries, but obviously it's still stuck
[14:49] <soee> guys atm custom background image for login screen does not work right ?
[14:49] <soee> only white background shows up
[14:49] <soee> *saucy
[14:54] <tester56> vHanda, are you there?
[14:54] <tester56> does anybody know how to get appmenu-gtk working on saucy?
[14:54] <genii> soee: I have a custom background which is working fine. I'm using lightdm-kde-greeter, not kdm though.
[14:55] <tester56> i have tried to install aindicator-appmenu ... no success exporting a gtk menu
[14:55] <soee> genii, lightdm is used by default i think
[14:57] <tester56> and I think appmenu-gtk was obsoleted for unity-gtk-module
[14:57] <tester56> any idea if this can work on kubuntu?
[14:58] <tester56> Riddell, any idea? , as you have been involved on launchpad
[15:04] <Riddell> tester56: yeah I think appmenu-gtk is now dead
[15:04] <Riddell> it should still work for kde apps
[15:05] <tester56> yeah but that's only half of the fun
[15:05] <Riddell> but gtk apps you'll need to live with a menu bar on (I assume it has a sensible fallback)
[15:05] <Riddell> tester56: I uploaded kde-workspace with your suggested plasma login change, testing would be good when it arrives in the archive
[15:05] <tester56> in neon it worked
[15:06] <tester56> so, there is no chance to get appmenu-gtk for saucy?
[15:08]  * smartboyhw decides to upload quantal 4.10.97 to ninjas:P (Any objections?)
[15:08] <yofel> staging please
[15:09] <smartboyhw> yofel, oh yeah staging/
[15:09] <smartboyhw> Then why is precise in ninjas?
[15:09] <yofel> because staging is full
[15:09] <yofel> we have no PPA that can hold 4 releases, so it's split
[15:10] <smartboyhw> Which textfile in kubuntu-automation am I supposed to use for getting package names?
[15:10] <tester56> Riddell, self compiling should still work, right?
[15:10] <tester56> Riddell, (appmenu-gtk)
[15:10] <smartboyhw> Damn..
[15:10] <smartboyhw> Anyways, it doesn't affect the build...
[15:10] <smartboyhw> calligra (1:2.7.1-0ubuntu1~ubuntu13.04~ppa2) raring; urgency=low
[15:10] <smartboyhw>   * Backport to quantal.
[15:10] <smartboyhw>   * Drop vc-dev as build-dep since it does not exist in raring.
[15:11] <yofel> the script should choose the right one by itself
[15:11] <smartboyhw> Uh hum.. Quantal
[15:11] <smartboyhw> yofel, I need to run ./kdesc-package-names right?
[15:11] <yofel> oh right, rohan lost his quantal changes, so you'll have to create the file first
[15:11] <yofel> no
[15:11] <smartboyhw> yofel, no?
[15:11] <yofel> take the current list for saucy and check if something needs to be removed (pykde at least)
[15:12] <smartboyhw> yofel, I would rather take the list from precise:P
[15:12] <yofel> well, you *could* run kdesc-package-names, but that'll just give you the list for saucy
[15:12] <yofel> well, or do that, yeah
[15:13] <yofel> and don't forget to use -T unstable, or you'll use the wrong set of hooks
[15:14] <Riddell> wow
[15:14] <Riddell> 7 donations :)
[15:15] <Riddell> almost at £100, drinks are on the Kubuntu Council!
[15:15] <smartboyhw> yofel, um no need for --sru right?
[15:16] <smartboyhw> ./kubuntu-initial-upload -d quantal -v 4.10.97 -m "quantal backport" -y 12.10 -T unstable -t ~/kde/temp
[15:16] <smartboyhw> is that correct?
[15:16] <smartboyhw> Riddell, that's a lot
[15:17] <yofel> wrong script
[15:17] <smartboyhw> yofel, oh?
[15:17] <smartboyhw> batch-backport?
[15:17] <yofel> ./kubuntu-batch-backport -v 4.10.97 -f saucy -t quantal -V 12.10 -T unstable -u medium
[15:18] <yofel> then again, leave -u away
[15:18] <smartboyhw> yofel, so don't use -u you mean?
[15:19] <yofel> yeah, not important enough
[15:36] <BluesKaj> ok, if anyone on Kubuntu 13.10 has lsb-core and ia32-libs installed then trying to upgrade or dist-upgrade today may create a dependency hell loop. Especially if you had google-earth installed which was taken out by yesterday's upgrade
[15:37] <BluesKaj> or not  , iit also affects those without the google earth depends as well
[15:39] <BluesKaj> I cross posted this in #ubuntu+1
[15:40] <BluesKaj> it's an issue with libgphoto2-2
[15:41] <smartboyhw> What's the issue?
[15:42] <BluesKaj> http://pastie.org/private/g8wndrs2y2peq6omq5jilg , smartboyhw
[15:43] <smartboyhw> BluesKaj, OK, what happened is that libgphoto2-2 is clearly NOT supposed to have Multi-Arch
[15:44] <BluesKaj> well I have other stuff to do , so i'll have to leave it for now, smartboyhw
[15:45] <BluesKaj> smartboyhw, check with chjunior over at #ubuntu+1, he p[osted that url , originally
[15:45] <BluesKaj> gotta go
[15:46] <BluesKaj> he's on ubuntu btw
[21:05] <volkan_> hi all. can someone add Turkish Kubuntu mirror into download page? ftp://ftp.linux.org.tr/kubuntu/
[21:52] <volkan_> Riddell: hi Jonathan. who is responsible for download page?
[21:58] <valorie> volkan_: it's really late in the UK where Riddell is -- maybe drop an email to kubuntu-devel list?
[22:00] <volkan_> valorie: thanks valorie. i will send an e-mail than
[22:01] <valorie> :-)
[22:22] <ahoneybun> lordievader: hey
[22:34] <Quintasan> agateau: Is that a T430?


[16:08] <blackboxsw> hey folks, I think it's about time for our bi-weekly cloud-init  status meeting.
[16:08] <blackboxsw> #startmeeting
[16:08] <meetingology> Meeting started Mon Aug 20 16:08:48 2018 UTC.  The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:08] <meetingology> Available commands: action commands idea info link nick
[16:08] <blackboxsw> #endmeeting
[16:08] <meetingology> Meeting ended Mon Aug 20 16:08:52 2018 UTC.
[16:08] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.08.moin.txt
[16:09] <blackboxsw> #startmeeting Cloud-init bi-weekly status meeting
[16:09] <meetingology> Meeting started Mon Aug 20 16:09:08 2018 UTC.  The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:09] <meetingology> Available commands: action commands idea info link nick
[16:09] <blackboxsw> For those around, let's kickoff another cloud-init status meeting.  Feel free to interrupt as we go through the agenda for today.
[16:10] <blackboxsw> agenda: Previous Actions, Recent Changes, In-progress development and office hours (~30 minutes)
[16:13] <blackboxsw> #topic Previous Actions
[16:13] <blackboxsw> nothing to speak of here as far as I recall.
[16:13] <blackboxsw> #topic Recent Changes
[16:14] <blackboxsw> We have recently landed the following content in tip of cloud-init over the last 2 weeks
[16:14] <blackboxsw>   - Add datasource Oracle Compute Infrastructure (OCI).
[16:14] <blackboxsw>   - azure: allow azure to generate network configuration from IMDS per boot.
[16:14] <blackboxsw>   - Scaleway: Add network configuration to the DataSource [Louis Bouchard]
[16:14] <blackboxsw>   - docs: Fix example cloud-init analyze command to match output.
[16:14] <blackboxsw>     [Wesley Gao]
[16:14] <blackboxsw>   - netplan: Correctly render macaddress on a bonds and bridges when
[16:14] <blackboxsw>     provided. (LP: #1784699)
[16:14] <blackboxsw>   - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.
[16:14] <blackboxsw>   - redhat: remove ssh keys on new instance. (LP: #1781094)
[16:15] <blackboxsw>   - Use typeset or local in profile.d scripts. (LP: #1784713)
[16:15] <blackboxsw>   - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)
[16:15] <blackboxsw> most notable is the new datasource for Oracle and Azure datasource now emitting network configuration per boot.
[16:21] <blackboxsw> new Ubuntu cosmic images should contain 18.3-24-gf6249277-0ubuntu1 with the lastest patches
[16:21] <blackboxsw> #topic In-progress Development
[16:23] <blackboxsw> The team in general is perparing for the cloud-init summit conference which will be the second half of this week with cloud and distro vendors so we'll probably be landing a couple more branches in preparation for talks/demos there.
[16:23] <blackboxsw> *preparing* rather
[16:24] <blackboxsw> Our trello board is a good representation of any existing work we are "Doing"
[16:24] <blackboxsw> #link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin
[16:26] <blackboxsw> recently powersj has also moved our jenkins server around to a new network so there has been a good bit of work getting all things jenkins back up and running behind the new proxies/firewalls etc.
[16:26] <blackboxsw> thanks for the heavy lift powersj
[16:27] <blackboxsw> I think that wraps up all things cloud-init....
[16:27] <blackboxsw> #topic Office Hource (next ~30 mins)
[16:28] <blackboxsw> We'll have eyes on this channel for any quips, complaints, bug, feature or branch discussions for the next half hour
[16:28] <blackboxsw> Otherwise, we'll be excited to see a few of you again in this year's cloud-init summit.\
[16:28] <paulmey> Hi all, I'd like to request a review for this MP: https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742 (attached to LP: #1722959)
[16:29] <paulmey> Hoping we can get this merged sometime soon. :-)
[16:29] <blackboxsw> Hi paulmey thanks for the ping on this.
[16:29] <blackboxsw> #link https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742
[16:30] <blackboxsw> #action rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742
[16:30] <meetingology> ACTION: rharper/blackboxsw close out on this review before cloud-init summit https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742
[16:30] <blackboxsw> that has gotten dusty, thank you
[16:31] <blackboxsw> I'll start a review in earnest now
[16:31] <paulmey> Thanks. The dust is mostly mine... Andy has been working on this, but he's in a different time zone, so I'm still pushing it...
[16:31] <paulmey> 😉
[16:32] <blackboxsw> paulmey: I'll try spinning up an azure vm to test this out
[16:34] <paulmey> let me know if you need anything
[17:04] <blackboxsw> ok thanks folks for tuning in. See you next time
[17:04] <blackboxsw> #endmeeting
[17:04] <meetingology> Meeting ended Mon Aug 20 17:04:48 2018 UTC.
[17:04] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/cloud-init/2018/cloud-init.2018-08-20-16.09.moin.txt
[17:08] <blackboxsw> just published minutes to https://cloud-init.github.io/
[17:56] <blackboxsw> smoser: rharper do you guys recall what platforms we expect don't have jinja2 support?
[17:56] <rharper> blackboxsw: hrm, I feel we discussed but I don't recall the details
[17:56] <blackboxsw> it's an optional dependency from the looks of things in cloudinit/templater.py
[17:56] <rharper> there was a reason we had the simple renderer
[17:59]  * blackboxsw was thinkings centos 6... but python-jinja2-2.2.1-3.el6.x86_64 exists... hrm
[17:59] <blackboxsw> many non-epel customer or something
[17:59] <smoser> it was probably just added as optional because we didn't want to break existng installations (or supported/sttable OS... like trusty or something)
[18:00] <rharper> related to cheetah being dropped too
[18:00] <rharper> which was pre jinja IIRC
[18:00] <smoser> blackboxsw: why do you care ?
[18:00] <blackboxsw> in jinja template parthandler, I'm trying to decide if I can rely on jinja2 module to exist or do the try/except ImportError dance
[18:02] <smoser> in this scenario, when rendering the thing, the user has declared the template to be jinja
[18:02] <smoser> right?
[18:02] <blackboxsw> yeah, they have
[18:03] <blackboxsw> so that shouldn't run unless ##template: jinja is in user-data
[18:03] <smoser> well, its going to fail either way.
[18:03] <smoser> user is not going to get what they wanted.
[18:05] <smoser> we could chooes to hold off because vmtest seems failing. as a result of the journal colleciton change that rharper memtioned today
[18:06] <rharper> smoser: I've a fix for that now
[18:06] <rharper> I'll put up an MP
[20:45] <apollo13> let's assume I have set some data wrong in cloud-init userdata (namely the hostname). Can I edit that somehow after the instance booted? modifying set-hostname didn't seem to work
[20:46] <apollo13> the metadata service (cloud-init) did update
[20:48] <rharper> apollo13: the default is for metadata (and userdata) to be only applied once per instance (first boot on a platform);   If you do make manual modifications (and don;t mind re-running things, which will for example, change the instance host ssh keys) then you could do something like 'cloud-init clean --logs --reboot' which will remove the current instance information and boot like it was a new instance
[20:49] <apollo13> lets see what that does :D
[20:49] <rharper> apollo13: if you wanted to do a more targetted run of a specific module you can make use of cloud-init single,   something like
[20:49] <apollo13> to late
[20:50] <apollo13> worst case I nuke the machine and redo it
[20:50] <rharper> hehe
[20:52] <rharper> https://paste.ubuntu.com/p/dRfsfX8gzt/
[20:52] <rharper> apollo13: there's a forced update of hostname via a local cloud-config file
[20:53] <apollo13> but that will still keep the old data around?
[20:54] <apollo13> anyways /etc/hosts etc is correct now
[20:54] <apollo13> all that did change seems to be ssh key
[20:54] <apollo13> ansible is now refixing the rest
[20:58] <rharper> cool
[20:59] <rharper> yes, it would leave the old data around in the metadata/user-data  but the hostname files would have the values you wanted
[21:00] <blackboxsw> ok just pushed up the cloud-init devel render CLI subcommand to https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/335290   think I'll just await ci builds on that.
[21:00] <apollo13> rharper: ok thanks, cloud-init is still magic; not exactly sure what it all touches and when :D
[21:05] <apollo13> rharper: shouldn't the reinit process recreate the default user? (I mean I am happy it did not, but…)
[21:06] <rharper> apollo13: well, I didn't think users got nuked with a clean; but if it did, then yes the default user should have gotten recreated via a clean --logs --reboot
[21:08] <apollo13> ah no, digitalocean overrids it to root via vendor-data
[21:08] <rharper> yes, that makes sense after looking at source
[21:08] <rharper> clean nukes stuff down /var/lib/cloud and logs
[21:09] <apollo13> anyways, thanks for the help. all is well now :)
[21:28] <rharper> apollo13: sure thing; glad you're good to go
[22:52] <blackboxsw> paulmey: I did a  pass on  https://code.launchpad.net/~andyliuliming/cloud-init/+git/cloud-init/+merge/351742   I still need a bit more time to think a bit about how we want to handle threading/queues in cloud-init for this feature. but initial comments are up
[23:39] <paulmey> blackboxsw: Thanks, I'll take a look (and ask Andy to take a look)


[01:17] <delt> oh btw 12:46 < ubottu> nbcardoso: Por favor, use #ubuntu-br para ajuda em portugu�s. Para entrar no canal por favor fa�a "/join #ubuntu-br" sem as aspas.  He better accept my return request.......
[01:37] <delt> :/
[20:42] <fenix_> muito obrigado estou adorando o OS
[22:26] <hlblyhipy> Hi,i have questions regarding jack and ardour,im using ubuntustudio 14.04.1.Am I in the right place
[22:30] <sunstar> sure.
[22:31] <sunstar> there is also #jack and #ardour and #opensourcemusicians   im on my way out the door myself.
[22:32] <sunstar> what's the issue?
[22:33] <hlblyhipy> multiple xruns after fresh install of ubuntu studio
[22:38] <zequence> hlblyhipy: Default jack settings?
[22:38] <zequence> hlblyhipy: Which audio device?
[22:40] <zequence> Did you have no xruns on the same machine with a previous install?
[22:41] <hlblyhipy> yes this all happened after i tried the kx repos
[22:42] <hlblyhipy> im really new to the terminal so ill have to take it slow
[22:43] <hlblyhipy> jack settings now1024,48k and 2 peroids
[22:44] <hlblyhipy> was able to set jack to 256,48k and 2 with absolutely noxruns
[22:44] <hlblyhipy> audio device lexicon omega
[22:59] <zequence> hlblyhipy: After you added kx repos, technically, it's not Ubuntu Studio anymore
[23:00] <hlblyhipy> well thats why i reinstalled US i had nothing but trouble with the kx repos.And after reinstalling US now I have the problems I am encountering
[23:01] <zequence> Ok, so you don't have kx repos installed right now?
[23:02] <hlblyhipy> I tried KX first with the live cd had a few problems but after installing the repos my machine was horrible.No a fresh install of US
[23:03] <hlblyhipy> I instaled US from a usb if that matters
[23:03] <zequence> Doesn't matter
[23:03] <hlblyhipy> ok
[23:03] <zequence> I'm assuming you are comfortable with jack, and are able to select the correct device infor example qjackctl
[23:03] <zequence> ?
[23:04] <hlblyhipy> yes I have my lexicon as the interface
[23:04] <hlblyhipy> i can send you my aplay -l if that would help
[23:06] <zequence> Are you having xruns now, at 256,48k?
[23:09] <hlblyhipy> ya i have to go to 1024 to stop them.Im not even recording or monitoring I just have jack started and at 512 just sitting there the xruns just kep popping up
[23:09] <zequence> I've heard that using 3 periods/buffer is sometimes good for usb devices. No idea why
[23:09] <hlblyhipy> i tried raising the periods to 3 at 512 but i get xruns there to
[23:10] <zequence> ok
[23:10] <hlblyhipy> not as many but before i had it down to 256 48k and 2 periods with no xruns at all
[23:10] <zequence> could you paste the output of this command at http://paste.ubuntu.com: cat /proc/interrupts
[23:10] <zequence> Using the same usb port?
[23:11] <hlblyhipy> ya but after pasting it in to pastebin what do i do never used pastebin b4
[23:11] <zequence> Just paste it there, and give me the resulting link
[23:12] <zequence> Example http://paste.ubuntu.com/9544846/
[23:13] <hlblyhipy> ok give me a minute
[23:14] <hlblyhipy> http://pastebin.com/KY2gJgrW
[23:14] <zequence> No irq conflicts at all, so that's not it
[23:15] <hlblyhipy> ive been trying to learn the command line but damn that one was greek to me
[23:16] <zequence> cat is a command that prints out contents of files
[23:16] <zequence> /proc/interrupts is a file
[23:16] <hlblyhipy> right now i dont have jack started
[23:16] <zequence> no problem
[23:16] <zequence> If this is a fresh install, I really have no ideas why you have problems, tbh
[23:17] <zequence> But, one trick you could try..
[23:17] <zequence> If you have Hyper Threading (Intel CPUs), you could try disabling that in your BIOS.
[23:18] <zequence> Not always possible to do
[23:18] <hlblyhipy> ill give it a try this is a lenovo not sure if its intel or amd though
[23:18] <zequence> Hyper Threading normally gives you two threads per core, but it'll make latency less reliable
[23:19] <zequence> hlblyhipy: Sometimes wifi drivers act badly. You could try disabling wifi
[23:19] <hlblyhipy> well thats worht a try but like i said nevr had these problems till i tried the kx repos
[23:20] <hlblyhipy> oh ya i did that and disconnected my wired connection to no go with that
[23:20] <zequence> Normally, I wouldn't say kx repos would cause any problems, but who knows, maybe there is a bug somehwere that normally isn't there
[23:21] <hlblyhipy> im on the machine in question now so ill have to try that when i shut down
[23:22] <hlblyhipy> well i tried installing from the iso but had problems with kx that way to then i tried with the repos,so im at the point now i wouldnt try it again.US was working great for me
[23:22] <zequence> I'm more inclined to think that it'
[23:22] <zequence> ..it's some kind of a hardware problem
[23:23] <zequence> The biggest difference with kx is that it packages some applications differently (and some applications are more updated)
[23:23] <zequence> ..on top of that, there are some applications that you can't find in Debian/Ubuntu repos, because of licensing issues
[23:23] <hlblyhipy> well after the install Of US i noticed some changes to the system.I know now there are certain things i used to be able to do but now i need root privealges to do them
[23:23] <zequence> kx is more progressive in a way that Ubuntu Studio can't be
[23:24] <zequence> I have to go, sorry. bb tomorrow :)
[23:24] <hlblyhipy> well im using US and ardour to record bands and it never failed me before the only things i can see that kx has is alot of midi stuff that im just getting started with
[23:25] <hlblyhipy> that US doesnt
[23:25] <hlblyhipy> well thanx for the help


[03:20] <scoundrel> hello all
[03:20] <scoundrel> if anyone could help with this: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/199708 I'd really appreciate
[03:20] <ubotu> Launchpad bug 199708 in linux-source-2.6.22 "OOM killer kills all processes on an "empty" server" [Undecided,New]
[18:10] <bullgard4>  What is the function of the kondemand/0 process? How does it control the CPU clock frequency?


[01:27] <rozika> could i ask for some help on this channel, or does it have a topic already?
[04:22] <Eeyore-Jr> k, i forget, where is the manual again?
[05:13] <Eeyore-Jr> nn
[05:26] <sbalneav> evening all
[08:01] <generalsnus> What is the best disk cloning tool, i can use for linux? i have a HD here, id like to clone. ive tried ghost, but it wont find my external hd, so i can save a image
[09:00] <willvdl> jaunty jackalope. heh. still makes me laugh
[15:45] <sbalneav> Morning all
[15:48] <sbalneav> generalsnus: There is a "ghost fo linux" or g4l project
[15:48] <sbalneav> http://sourceforge.net/projects/g4l


[03:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #353: STILL FAILING in 5 min 33 sec: https://kci.pangea.pub/job/zesty_unstable_messagelib/353/
[03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #345: STILL FAILING in 5 min 57 sec: https://kci.pangea.pub/job/xenial_unstable_messagelib/345/
[03:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #346: STILL FAILING in 5 min 23 sec: https://kci.pangea.pub/job/xenial_unstable_messagelib/346/
[03:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #354: STILL FAILING in 7 min 2 sec: https://kci.pangea.pub/job/zesty_unstable_messagelib/354/
[03:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #221: STILL FAILING in 4 min 1 sec: https://kci.pangea.pub/job/xenial_unstable_mailcommon/221/
[03:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailcommon build #200: STILL FAILING in 3 min 46 sec: https://kci.pangea.pub/job/zesty_unstable_mailcommon/200/
[03:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_messagelib build #153: FIXED in 24 min: https://kci.pangea.pub/job/artful_unstable_messagelib/153/
[03:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #222: STILL FAILING in 4 min 32 sec: https://kci.pangea.pub/job/xenial_unstable_mailcommon/222/
[03:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailcommon build #201: STILL FAILING in 5 min 13 sec: https://kci.pangea.pub/job/zesty_unstable_mailcommon/201/
[03:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:38] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_mailcommon build #94: FIXED in 18 min: https://kci.pangea.pub/job/artful_unstable_mailcommon/94/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1728: SUCCESS in 1 min 5 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1728/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1728: SUCCESS in 1 min 16 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1728/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1728: SUCCESS in 4 min 19 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1728/
[08:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1728: SUCCESS in 5 min 16 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1728/
[11:21] <BluesKaj> Hey folks
[14:09] <ahoneybun> anyone else has a broken locker?
[14:09] <clivejo> nope
[14:10] <ahoneybun> mm everytime I lock it, it brakes
[14:11] <clivejo> are you running anything that interferes with the lock screen or mods it?
 nope
[14:12] <clivejo> https://forums.opensuse.org/showthread.php/518831-The-screen-locker-is-broken-and-unlocking-is-not-possible-anymore
[14:13] <clivejo> is /tmp full?
 nope using 1%
[14:17] <acheronuk> seems fine here
[14:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami2 build #144: FIXED in 10 min: https://kci.pangea.pub/job/xenial_unstable_kirigami2/144/
[14:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami2 build #149: FIXED in 10 min: https://kci.pangea.pub/job/zesty_unstable_kirigami2/149/
[14:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ksirk build #50: NOW UNSTABLE in 19 min: https://kci.pangea.pub/job/artful_unstable_ksirk/50/
[14:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ksirk build #108: NOW UNSTABLE in 20 min: https://kci.pangea.pub/job/xenial_unstable_ksirk/108/
[14:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ksirk build #122: NOW UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_ksirk/122/
[14:20] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:20] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kirigami2 build #98: FIXED in 11 min: https://kci.pangea.pub/job/artful_unstable_kirigami2/98/
[14:34] <DarinMiller> screen locker is working fine here too and virtual keyboard now works with touchscreen.  Nice!
[14:34] <ahoneybun> I had more updates somehow
[14:34] <ahoneybun> but still brakes on locking
[14:34] <ahoneybun> might reboot later, since it's a pain with my monitor setup
[14:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:35] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kreport build #85: FIXED in 16 min: https://kci.pangea.pub/job/artful_unstable_kreport/85/
[14:36] <clivejo> DarinMiller: are you around this morning?
[14:36] <clivejo> in like 20mins?
[14:36] <DarinMiller> yes
[14:37] <clivejo> see you on BBB then :)
[14:37] <DarinMiller> very good
[14:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdevelop build #103: STILL FAILING in 22 min: https://kci.pangea.pub/job/artful_unstable_kdevelop/103/
[14:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-runtime build #120: FIXED in 22 min: https://kci.pangea.pub/job/artful_unstable_kdepim-runtime/120/
[14:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1729: SUCCESS in 1 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1729/
[14:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1729: SUCCESS in 1 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1729/
[14:46] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_artful_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #9 1 mo 4 days ago)
[14:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1729: SUCCESS in 4 min 22 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1729/
[14:47] -kubuntu-ci:#kubuntu-devel- Project iso_artful_unstable_amd64 build #13: STILL FAILING in 1 min 1 sec: https://kci.pangea.pub/job/iso_artful_unstable_amd64/13/
[14:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1729: SUCCESS in 4 min 51 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1729/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1730: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1730/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1730: SUCCESS in 1 min 8 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1730/
[14:51] <acheronuk> clivejo: bug #1713212
[14:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1730: SUCCESS in 4 min 17 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1730/
[14:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1730: SUCCESS in 4 min 48 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1730/
[15:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdevelop build #104: STILL FAILING in 20 min: https://kci.pangea.pub/job/artful_unstable_kdevelop/104/
[15:15] <clivejo> DarinMiller: acheronuk https://wiki.ubuntu.com/ArtfulAardvark/Beta1/Kubuntu
[15:32] <blaze> I need a person who uses something without SNI tray like lxde to reproduce an issue for me
[15:38] <clivejo> Home Page - https://phabricator.kde.org/project/profile/214/
[15:38] <clivejo> Work Board - https://phabricator.kde.org/project/board/214/
[15:38] <clivejo> Dev Docs - https://phabricator.kde.org/w/kubuntu/
[15:39] <clivejo> Status - https://phabricator.kde.org/w/kubuntu/packaging/status/
[15:39] <clivejo> QA - http://qa.kubuntu.co.uk/
[15:43] <clivejo> valorie: can we get these links shortened KDE ones please?
[15:44] <clivejo> http://go.kde.org/u/3
[15:45] <clivejo> http://kubuntu.org/1 => https://phabricator.kde.org/project/profile/214/
[15:46] <clivejo> .htaccess
 Clivejo, I've seen your message. Thanks for the help. I think my system has stabilize now and I'll be wrapping that package later tonight
[15:47] <clivejo> gsilvapt: I pushed the fix
 Ah ok. Thank you and sorry for the trouble
[16:10] <clivejo> https://distrowatch.com/table.php?distribution=kubuntu
[16:10] <clivejo> category: Server ?
[16:20] <acheronuk> clivejo: https://git.launchpad.net/network-manager/commit/?h=artful&id=2b7d9cbec93e4d08d458ae9963d2a7c34f90e8db
[16:39] <blaze> tray in Qt 5.9.1 is utterly broken :\
[16:40] <acheronuk> broken, how?
[16:42] <blaze> acheronuk: unset KDE_FULL_SESSION and XDG_CURRENT_DESKTOP variables and run any app which have tray icon
[16:58] <blaze> I can't get xembed tray working, that's the problem
[16:59] <blaze> outside of the major DEs xembed is still the only option
[16:59] <ahoneybun> screenshot?
[18:03] <clivejo> well at least santa's server is back up
[19:33] <mparillo> Are you on 17.04? I just saw this post on #kubuntu: <slyrobot>  I have a Kubuntu Installation. 17.04. There seems to be a problem with my session. As soon as the PC locks itself it displays a message "The Screen Locker is broken anf unlocking is not possible anymore. To unlock press Ctrl + Alt + F2. I have done this to get my session back but this is occuring almost every single time. Is there a fix for this ?
[19:33] <mparillo> Are you on 17.04? I just saw this post on #kubuntu: <slyrobot>  I have a Kubuntu Installation. 17.04. There seems to be a problem with my session. As soon as the PC locks itself it displays a message "The Screen Locker is broken anf unlocking is not possible anymore. To unlock press Ctrl + Alt + F2. I have done this to get my session back but this is occuring almost every single time. Is there a fix for this ?
[19:33] <mparillo> Are you on 17.04? I just saw this post on #kubuntu:
[19:33] <mparillo> sorry. Scrolling fail.
[19:33] <mparillo> I meant that for ahoneybun
 I'm on artful tho
[20:44] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #148: STILL UNSTABLE in 4 min 51 sec: https://kci.pangea.pub/job/mgmt_tooling/148/
[20:44] -kubuntu-ci:#kubuntu-devel- Clive Johnston: Add falkon
[20:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #73: SUCCESS in 24 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/73/
[20:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #73: SUCCESS in 34 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/73/
[20:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #73: SUCCESS in 58 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/73/
[20:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #73: SUCCESS in 1 min 6 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/73/
[20:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1731: SUCCESS in 1 min 2 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1731/
[20:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1731: SUCCESS in 1 min 12 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1731/
[20:50] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1731: SUCCESS in 4 min 17 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1731/
[20:51] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1731: SUCCESS in 4 min 51 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1731/
[21:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_falkon build #1: FAILURE in 2 min 45 sec: https://kci.pangea.pub/job/xenial_unstable_falkon/1/
[21:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_falkon build #1: FAILURE in 6 min 33 sec: https://kci.pangea.pub/job/zesty_unstable_falkon/1/
[21:07] <clivejo> Project ERROR: Falkon requires at least Qt 5.8!
[21:07] <clivejo> great!
 But we have 5.9
[21:07] <clivejo> in artful yes
[21:07] <clivejo> not on xenial or zesty
 no backports then
 Well it would be hard to do anything with xenial or zesty
 minimum webengine requirement I would guess
[21:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_falkon build #2: STILL FAILING in 2 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_falkon/2/
[21:10] <clivejo> looks like that
[21:10] <acheronuk> well, should be ok in KCI
[21:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_falkon build #2: STILL FAILING in 3 min 52 sec: https://kci.pangea.pub/job/zesty_unstable_falkon/2/
 @mparillo> Are you on 17.04? I just saw this post on #kubuntu: <slyrobot, I have a possible fix in mind for that
 @clivejo, Yes. Apparently the electicity was down and the bios isn't configured yet to start automatically when it's up again.
[21:31] <clivejo> ah, did you have to boot it manually?
 Yes. I couldn't configure the bios because the new motherboard doesn't have a graphics card yet. I will get one this monday. Let's when I can install it.
[21:38]  * acheronuk watches QtWebEngine build.... ZZZZzzzz.... snore....
[21:43] <mparillo> Santa, first welcome back. Second, ahoneybun was experiencing something on AA that sounded similar to something I saw in the #kubuntu channel. The first thing I do after install is turn off screen locking, but I have two 17.04 VMs (One has backports, and one has proposed enabled) and could try to test but I think I am going out for the evening (US time).
[21:47] <acheronuk> right. webengine will take forever. time for a large JD
[21:47] <clivejo> me me me
[21:48] <acheronuk> ice?
[21:48] <clivejo> pls
[21:49] <acheronuk> *clink* *clink* ... *long glug*
[21:49] <acheronuk> cheers
[21:54] <clivejo> thanks for fixing kmail :P
[21:55] <clivejo> working again
[21:57] <acheronuk> simon fixed the last two without bumping the abi. shall have to see about that. would be ok if we don't ship 17.08 in artful, but not if we do
[21:57] <acheronuk> but for now it should work
[22:09] <clivejo> well falkon seems to work
[22:09] <clivejo> still a lot of rebranding todo!
[22:10] <clivejo> Ill disable the XX and ZZ builds
 McDonald's now sells Americano
[22:26] <acheronuk> ooh https://mail.kde.org/pipermail/release-team/2017-August/010588.html
 Basically it looks like pure espresso and water!
[22:41] <clivejo> go Ben!
[22:53] <clivejo> I would kinda like PIM to be separated out into its own release
[22:53] <clivejo> It's just such a beast of a thing
[22:56] <clivejo> it doesn't have the same versioning internal anyways
[22:56] <clivejo> and it makes no sense :/


[00:53] <Unit193> bluesabre: In case you didn't see, as promised xfce4-whiskermenu-plugin 2.6.0-1 is up, can sync after beta.
[01:19] <DarkTrick> bluesabre, yes: https://github.com/shimmerproject/Greybird/issues/300#issuecomment-913229555
[01:27] <bluesabre> Unit193: thank you!
[01:28] <bluesabre> DarkTrick: thanks, will nudge ochosi or maybe peek myself this weekend
[05:27] <DarkTrick> bluesabre, I think I got a solution
[05:28] <DarkTrick> ochosi, FYI: ↑
[10:15] <ochosi> DarkTrick: i still don't see a PR or a finished solution though
[10:15] <ochosi> not to be rude, but i simply haven't had time to look into this myself at all
[10:16] <ochosi> so I'd need an end-to-end solution, not a "hunch" where the fix may have to be created
[10:46] <DarkTrick> ochosi, sorry, I guess that came through the wrong way. I understood you to be very busy, so I got on it myself.
[10:46] <DarkTrick> ochosi, I'm still smoothing the code out, but I will do a merge request with an end-to-end solution as soon as I'm done :)
[11:02] <ochosi> cool!
[11:02] <ochosi> thanks a bunch :)
[11:59] <DarkTrick> :)
[12:00] <Unit193> I don't mean to be rude, but if you're going to get that in impish, https://ubottu.com/y/ii it'll need to be pretty quick. :3
[23:32] <DarkTrick> Unit193, I want to submit within the next 12 to 20 hours