[07:04] <orated> Hello! Are ubuntu kernels released every 2-3 months? Can I give a request of a change here?
[08:07] <orated> When will there be support for Sandy bridge processors?
[08:13] <broder> orated: Ubuntu has had basic support for sandy bridge processors since Ubuntu 10.10, and supported 3D acceleration since 11.04
[08:18] <orated> broder: Apart from graphic, are there any performance issues? Like system running in performance mode than normal mode
[08:20] <broder> orated: That's not something I pay attention to, so I don't really know
[08:21] <orated> broder: Well, that really drains life out of laptops with it..
[08:23] <orated> The processor fan running at performance mode even when idle
[08:51] <RAOF> No.  There's the PCIE PM power thingy, but that's not related to the cpu.
[08:51] <RAOF> orated: Sandy Bridge processors are well supported in 11.10 (and slightly less well supported in 11.04)
[08:54] <smb> RAOF, Hm, actually makes me wonder (since I got no hw to look at): is the graphics card you see on those somehow presented as being connected via pcie?
[08:55] <RAOF> It does show up in lspci.
[08:57] <smb> Its hard to say for sure but that still may leave a little opportunity of someone twiddling pcie pm and having some magic impact back on the cpu doing gpu'y things. (totally unrelated to any knowledge here, just thinking)...
[08:57] <smb> cking, Hey how are you feeling today?
[09:07] <orated> RAOF: I didn't get the reason for that. What is PCIE PM?
[09:09] <RAOF> PCI Express power management; there's ambiguity between what the spec says and what Windows does.
[09:09] <apw> RAOF, isn't there also some rc6 related power drain on sb ?
[09:10] <RAOF> Yeah, there's that too.
[09:10] <orated> Well, I n Windows it works absolutely fine. In Ubuntu it starts the fan in performance fan
[09:10] <RAOF> That could just be your BIOS being stupid.
[09:11] <orated> er
[09:11] <RAOF> Which we *should* obviously deal with, but might not.
[09:11] <apw> RAOF, is that the 'performance MSR' thing?
[09:11] <apw> sb is a bit of a mess, and thats an upstream issue in the main
[09:12] <RAOF> apw: EAMBIGOUSTHAT
[09:12] <apw> and its going to take a while to perculate out into release
[09:12] <orated> RAOF: I have the BIOS updated
[09:12] <apw> RAOF, stupid BIOS> wondering if thats the 'CPU in performance by default' thingy thats controlled by a CPU msr or something more general
[09:13] <RAOF> Oh, no.  I was thinking "fan speed need not have any relationship to CPU performance mode"
[09:14] <apw> ahh, more possibilities.  i hate bios vendoes
[09:14] <orated> RAOF: But isn't that proportional?
[09:14] <RAOF> orated: Not necessarily; the fan control isn't wired up directly to a thermal sensor or anything like that.  At least, not all the time :)
[09:15] <RAOF> In other words: CPU state and fan state can be totally independent.
[09:16] <orated> I'm not aware of the different states but I think the CPU fan rpm will increase/decrease as per CPU/GPU load
[09:16] <orated> as far as I'm aware
[09:16] <RAOF> No, that's by no means guaranteed.
[09:17] <RAOF> Same with gpus, which is why the nouveau guys are paranoid about enabling fan control.  It *is* entirely possible to turn off the fan and have the GPU cook itself.
[09:18] <orated> So my system to run cpu fan in performance mode can be only due to power management?
[09:18] <RAOF> What should happen is that the kernel should see that ACPI thermal zone $X has hit $TRIP_POINT and turn the fan on to $POWER_LEVEL.  At least on most hardware.
[09:19] <RAOF> orated: You CPU fan may be running at 100% simply because the BIOS starts it up at 100% and doesn't hand control off to the kernel correctly.
[09:19] <orated> On what does it depend to hand over control to kernel?
[09:20] <RAOF> It needs to say that the fan should be controlled by the OS.
[09:20]  * RAOF → dinner.
[09:21] <orated> Well, I'm not that aware of proper technicalities but I only presented my observation here of system performance in Windows and Ubuntu. But if its BIOS issue, how can I fix it? Its updated ...
[09:22] <orated> ah-ok. Catch up with you later then ...
[09:40] <dupondje> The thing thats really missing atm is Optimus support. That drains the battery :)
[09:40] <apw> that one will be a while coming
[09:41] <dupondje> are things getting in kernel for that ?
[09:42] <broder> apw: yeah, but we *should* be able to stopgap that some by being sure to power down the unused chip, at least in theory
[09:49] <apw> broder, in some cases for some hardware with a machine specific quirk in every case
[09:50] <apw> broder, its not going to be pretty until the proper support comes and no mistake
[10:10] <cking> as it is, the fans are normally controlled by System Management Mode, so it's normally totally out of our control and up to the firmware to get it right.
[10:12] <smb> cking, btw just found a funny state of brokenness: while everything else seemed ok, the discharge rate was reported as 0. Wonder whether its worth bailing out of powerstat and tell users to try to connect and disconnect ac (that was how I "fixed" it).
[10:14] <cking> smb, yep, I can add that logic to cater for broken machines like yours ;-)
[10:15] <cking> did you tinker with the other powerstat options? I'm interested to see if it looks useful or if we need to add more goodness to it
[10:17] <smb> cking, I am pretty sure there are many more. :) Not yet, just had a quick run. Oh and it will actually run without complaining but with 0W power consumption on a desktop without any battery at all. ;)
[10:18] <cking> gah, I didn't think of that, I'll fix that too :-)
[10:20] <smb> cking, I feel a bit like the devil's advocate here, though. :)
[10:20] <cking> smb, I appreciate you checking for things that I overlooked
[10:22] <smb> cking, It is quite cool and I am sure apw will love it
[10:22]  * smb already does
[10:22] <cking> did you try the funky -r and -s options?
[10:23] <smb> cking, will look at those next. they sound pretty interesting
[10:23] <cking> netlink was fun to figure out, but there was plenty of good documentation lying around
[10:24] <tjaalton> i sent an email to kernel-team@, but seems it didn't get through
[10:24] <smb> tjaalton, Are you normally subscribed?
[10:24] <apw> tjaalton, may be in the moderation queue, we get a _lot_ of spam
[10:25] <tjaalton> i'm subscribed yes, checking which address i have there
[10:26] <smb> cking, Another completely unimportant note: -r is missing in the usage summary...
[10:26] <apw> tjaalton, it was in the mod queue, i've poked it
[10:26] <orated> smb: Can I ask which command you are using?
[10:27] <cking> smb, err, try updating
[10:27] <cking> ./powerstat -h
[10:27] <cking> usage: ./powerstat [-s] [-h] [-d N] [delay [count]]
[10:27] <cking> 	-s show process fork/exec/exit activity log
[10:27] <cking> 	-d specify delay before stating, default is 15 seconds
[10:27] <cking> 	-r redo a sample if we see process fork/exec/exit activity
[10:27] <cking> 	-h show help
[10:27] <cking> 	delay: delay between each sample, default is 10 seconds
[10:27] <cking> 	count: number of samples to take, default is 10
[10:27] <cking> oh, yeah, I see now.
[10:27] <tjaalton> apw: thanks
[10:27] <smb> orated, Something cking is currently whipping together
[10:27] <orated> got it
[10:28] <cking> orated, technically know as "work in progress"
[10:30] <cking> smb, suppose I should write a man page too
[10:30] <tjaalton> ok, I had the wrong email address on the list, changed it now
[10:31] <smb> cking, When things settle down, I guess that is a good idea, and in the end probably have it in a ppa
[10:32] <smb> cking, Just an idea, you think it would be useful to have -r also redo the sample if idle is below a threshold (like 99)?
[10:33] <cking> smb, yes, but how about making that another option, like -i, so we have more fine tuning?
[10:34] <orated> cking: Regarding the fan rpm related to firmware you said above, I checked with dmidecode and the BIOS is updated and current A06 ...
[10:34] <smb> cking, sounds good. probably could become -rf and -ri
[10:35] <cking> smb, good suggestion, will do
[10:37] <smb> cking, maybe not that simple with getopt (without making those --)...
[10:38] <cking> smb, it's OK, getopt long is easy to use
[11:19]  * ppisati -> post office
[12:46] <smb> herton, Quick question: is there currently a lucid-ec2 tracking bug open that I missed? Seeing the other uploads...
[12:47] <herton> smb: yes, let me find the bug here
[12:47] <herton> smb: bug 888700
[12:47] <ubot2> Launchpad bug 888700 in linux-ec2 "linux-ec2: <version to be filled> -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/888700
[12:48] <smb> herton, Thanks, that one I totally missed somehow...
[12:48]  * ppisati wonders how much does it take to setup a local ubuntu repository...
[12:49] <ppisati> space-wise i mean
[12:51] <smb> ppisati, A lot probably does not help, but the sync would also take long. That is why I went for apt-cacher-ng
[12:52] <ogra_> do you really need a full archive copy ?
[12:52] <ogra_> i woudl go with something like approx instead
[13:00] <ppisati> i was just wondering since this morning i read an article about "how to setup your own builder" or stuff like that, and one of the prerequisites was a local repostiory
[13:02] <ogra_> well, approx, apt-cacher and friends work in a way that they pull from the archive *if* there is a newer package, else they use the local version
[13:02] <ogra_> that has the advantage that you only use the diskpace for packages you actually need and that it only pulls updates if there actually are updates
[13:02] <smb> Probably more of a recommendation to avoid you pulling packages over and over for each build. But as ogra_ said, you can use the proxy cachers as servers
[13:03] <ogra_> indeed its slower than having a full local mirror ... on the first run
[13:03] <ppisati> yep
[13:03] <ppisati> but i still need a new 2tb disk, and latest flooding didn't help... :)
[13:03] <ogra_> subsequent builds of the same package are fast though
[13:03] <ogra_> oh, you only want to justify buying a new disk
[13:03] <ogra_> go for a full mirror them :P
[13:04] <ogra_> *then
[13:04] <ppisati> asd :)
[13:04] <ppisati> do you think 2tb is big enough?
[13:04] <ppisati> don't think so
[13:04] <ogra_> one arch one release ?
[13:04] <ppisati> pretty much
[13:04] <ogra_> shoudl be ok ... i guess
[13:04] <ogra_> but better ask someone who actually has a full mirror at home
[13:05] <ogra_> GrueMaster has one for example
[13:05] <smb> ppisati, Oh you really want to buy three to have it raid5'd :-P
[13:05] <ogra_> infinity too
[13:05] <ppisati> ah
[13:05] <ogra_> smb, 3 ? you need 5 for a 5.1 :P
[13:05] <ppisati> smb: better to raid 0 then
[13:05] <ppisati> i mean
[13:05] <ppisati> raid 1, mirror
[13:05] <smb> ppisati, yep
[13:06] <smb> ppisati, But I thought you wanted more arguments for yourself to buy many disks... :)
[13:06] <ppisati> ah :)
[13:08] <smb> Cause in reality with caching (I use it a lot and currently got 4G used) you do not really need a new one and any raid is not really needed because you can always start over from the archive
[13:09] <ppisati> smb: thgat
[13:09] <ppisati> smb: that's true
[13:10] <ppisati> but with a big enough disk i can offload not only the archives, but even the OS and all the rest
[13:10] <ppisati> one raid to rule them all
[14:45] <mdeslaur> hi herton, any ETA on a regression fix for lucid? (LP #875300)
[14:45] <ubot2> Launchpad bug 875300 in linux "[Realtek ALC268] ALSA test tone not correctly played back (regression in lucid from 2.6.32-33.72)" [Medium,Triaged] https://launchpad.net/bugs/875300
[14:47] <herton> mdeslaur: I can revert the patch causing it, the problem is reverting should bring the previous regression the "fix" is handling. I plan to see if I find a solution until the end of the week.
[14:48] <mdeslaur> herton: but, have you actually seen the regression? AFAIK lucid sound on mini 9's has always worked...
[14:51] <herton> mdeslaur: it's just a problem with quirks, machines with same id but codec differences, so one quirk was applied to one model, but the same id make the quirk brake other models. Newer kernels have a better hda auto-config, and I suppose will handle this better. It's not so bad, you still can use model=dell (options snd-hda-intel model=dell), to avoid the breakage for now
[14:53] <mdeslaur> herton: oh, hrm...I wonder if breaking people to fix others who's sound never worked in the first place is an acceptable trade-off
[14:54] <herton> mdeslaur: yeah, may be we'll just revert the fix, I'm going to take a look at it if there is some we can do on lucid to have both cases fixed, if not revert it
[14:54] <mdeslaur> herton: cool, thanks :P
[14:55] <mdeslaur> herton: if you need any testing, let me know
[14:55] <herton> ok, once I have something I'll let you know
[15:03]  * herton -> lunch
[15:29]  * ogasawara back in 20
[15:53] <GrueMaster> ppisati: My mirror is currently at 325G, but it is only arch armel/armhf/all binaries.  I do not currently mirror source.  Initial mirror setup and pull can take a weekend, depending on your bandwidth and the bottlenecks between you and the original source (I would assume ports).
[15:55] <GrueMaster> My mirror is a 1U rack system w/ 4-1T sata drives in a soft raid (apparently, most SATA raid controllers are software raid, with software raid drivers for Windows - hence the raid marketing).
[16:09]  * ogra_ guesses armhf doesnt actually take much space yet :P
[16:16] <mpoirier> ogasawara: good day
[16:17] <ogasawara> mpoirier: hi
[16:17] <mpoirier> ogasawara: I have a brain bug this morning
[16:17] <mpoirier> ogasawara: ages ago you have me a make command to upgrade a target config .
[16:17] <mpoirier> something like make updateconfig
[16:17] <mpoirier> but I can't remember...
[16:18] <ogasawara> mpoirier: fdr updateconfigs
[16:18] <mpoirier> ha !
[16:18] <mpoirier> fantastic thanks.
[16:18] <ogasawara> fdr == fakeroot debian/rules
[16:18] <mpoirier> yep.
[16:35] <sforshee> cking, didn't you have something to execute an AML method and get the result from the command line?
[16:52] <ppisati> mpoirier: any chance you give me an update on that patch i asked you?
[16:52] <cking> sforshee, yep, lemme find it for you
[16:53] <ppisati> GrueMaster: just 325GB???
[16:53] <ppisati> GrueMaster: entire armel repository?
[16:53] <GrueMaster> ppisati: Armel, armhf (which I expect to almost double the sixe), and arch-all.
[16:54] <mpoirier> ppisati: you asked me for a patch ?
[16:54] <ppisati> mpoirier: i think i did... wait a sec...
[16:54] <ppisati> GrueMaster: i expected to take much more space... uhmm...
[16:54] <cking> sforshee, git://kernel.ubuntu.com/cking/systemtap-scripts.git
[16:55] <GrueMaster> ppisati: As I said earlier, no source (yet).
[16:55] <ppisati> mpoirier: subject "Patch review/comment (from O to P)"
[16:55] <sforshee> cking, thanks
[16:55] <cking> sforshee, in acpi-eval, you can hack that script
[16:55] <ppisati> mpoirier: i think the patch is not needed anymore, but i wanted you to give it a look
[16:55] <mpoirier> ppisati: that was in an email ?
[16:55] <ppisati> mpoirier: yep
[16:56] <cking> sforshee, you may like to also use the amltrace script too, perhaps a combo of both


[03:57]  * pleia2 gets to work on newsletter things
[04:18] <pleia2> Unit193: link check? https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue442
[05:05] <Unit193> http://loco.ubuntu.com/events/ubuntu.cat/3250-festa-wily-werewolf---ubuntu-15.10/ - http://loco.ubuntu.com/events/ubuntu-fr/3244-ubuntu-party-paris-15.10/
[17:23] <PaulW2U> links fixed + editorial review done
[19:15] <pleia2> thanks Unit193 and PaulW2U
[19:19] <pleia2> PaulW2U: how do you keep up with the Q&A/Ubuntu on Air type videos?
[19:19] <pleia2> I use rss feeds and email alerts for most things
[19:20] <PaulW2U> I just know that they're every Tuesday :)
[19:20] <pleia2> aha, so manually checking? I guess I do that for the dev team meetings on wiki pages too
[19:22] <pleia2> Welcome to the Ubuntu Weekly Newsletter, Issue 442 for the week November 9 - 15, 2015 https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue442
[19:27] <pleia2> jose: if you're bored one of these days, fridge could use another spam culling
[19:27]  * pleia2 might take care of it during some mindless downtime otherwise
[19:28] <jose> pleia2: gotcha! will look when I have some time :)
[19:36] <pleia2> ok, I think that's releasing complete
[19:39]  * pleia2 packs up for airplane time


[01:52] <ginggs> michi: i was asking about a no-change rebuild of persistent-cache-cpp to pick up PIE. i uploaded 1.0.4+16.04.20160117-0ubuntu2, but the copyright test failed. i now see the "$distro" = "xenial" line in check_copyright.sh
[01:52] <michi> ginggs: Sec, ping you back shortly.
[01:55] <michi> ginggs: Do you have a build log?
[01:55] <michi> Unfortunately, license-check is brittle.
[01:55] <michi> And keeps changing all the time.
[01:56] <ginggs> buuild logs here https://launchpad.net/ubuntu/+source/persistent-cache-cpp/1.0.4+16.04.20160117-0ubuntu2 but you probably will just want to skip the check for yakkety too, so long
[01:56] <ginggs> interesting that they passed on big-endian
[01:57] <michi> The copyright check just runs license-check and does some post-processing.
[01:57] <michi> It’s a shell script.
[01:57] <michi> So I doubt its caused by anything we are doing directly.
[01:58] <michi> Aargh.
[01:58] <michi> Bloody license-check changes yet again.
[01:59] <michi> Need more suppressions for the post-processing.
[01:59] <michi> That bit is easy to fix.
[01:59] <michi> I don’t get why it worked on big-endian either.
[02:45] <michi> ginggs: Fix is sitting in silo 29 now. I can’t build for yakkety right now but, from the build log, this should fix it.
[07:29] <ginggs> michi: i see it, thanks!
[07:29] <michi> ginggs: It’s in the proposed pocket now.
[07:29] <michi> Please, do me a favour...
[07:29] <michi> Next time you do a manual upload, can you give me heads-up please?
[07:30] <michi> I had a really hard time figuring out why the train wouldn’t accept the changes because the new changelog entry.
[07:30] <michi> See the scrollback in ubuntu-ci-eng
[07:32] <ginggs> michi: will do, sorry about that
[07:32] <michi> The upload wasn’t available via apt-get source either, so it wasn’t until robru dug it up that I could actually see the changelog entry.
[07:32] <michi> Anyway, it’s fixed now.
[07:33] <robru> michi: yeah you can get those from lp if you click enough.
[07:33] <michi> robru: You are *still* up?!!!
[07:33] <robru> michi: *crippling* insomnia
[07:33] <michi> Oh man...
[07:33] <michi> Sorry to hear that :(
[07:34] <robru> michi: no worries.
[07:34] <robru> michi: it's only 2:30
[07:34] <michi> *only*...
[07:40] <michi> https://wiki.canonical.com/InformationInfrastructure/OSA/ScreenSharingWithDevs
[10:41] <attente> bdmurray: hi, for gnome-software, it doesn't seem like that error is a new regression: https://errors.ubuntu.com/problem/58f08ffc3281621f3df0ae8b636df69edadf0f02
[12:38] <lamont> are the armhf testers that backed up, or is there an actual issue with them?
[12:38] <lamont> pitti: ^^
[13:28] <pitti> lamont: both really, but I restarted the tmpfailed ones an hour ago
[13:29] <pitti> they caught up with 2/3 of the backlog now
[13:36] <lamont> yay
[14:00] <bdmurray> attente: okay, I'll override that


[20:19] <cr3> if anyone happens to have a touchscreen detected as a multitouch device, would you mind sharing the output of xinput --list --long?
[20:39] <dandrader> cr3, I have one
[20:39] <dandrader> cr3, just a sec
[20:39] <cr3> dandrader: thanks, let me know if you need my email address if it'll make things easier
[20:40] <dandrader> I can just pastebin it
[20:40] <cr3> dandrader: that works for me
[20:40] <dandrader> cr3, that's the relevant bit http://paste.ubuntu.com/1248302/
[20:41] <dandrader> but I don't recall if the events when I tested, came from "N-Trig MultiTouch" or "N-Trig Touchscreen"
[20:42] <cr3> dandrader: probably from "N-Trig MultiTouch" since it's the only one with the XITouchClass class
[20:43] <dandrader> I always wondered why there are those two virtual devices if my laptop has only one touchscreen (what's the function of each) but I never mustered the energy to investigate the answer
[20:43] <dandrader> sould be
[20:43] <cr3> dandrader: I've been wondering what the purpose of the Virtual core pointer device that seems to be a superset of other devices
[20:45] <dandrader> one thing is that many input devices can control the same, single, mouse pointer on the screen
[20:45] <dandrader> likewise for keyboard/text input
[20:45] <dandrader> or maybe that's the whole point
[20:46] <cr3> dandrader: hm, that's indeed weird about input devices


[14:32] <sarnold> good morning
[14:33] <slyon> hello o/
[14:34] <slyon> I think c_paelzer is out at a sprint. So maybe I can run the meeting again.
[14:34] <slyon> #startmeeting Weekly Main Inclusion Requests status
[14:34] <meetingology> Meeting started at 14:34:33 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:34] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:34] <slyon> Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage
[14:34] <slyon> #topic current component mismatches
[14:34] <slyon> Mission: Identify required actions and spread the load among the teams
[14:34] <slyon> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:34] <slyon> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:35] <slyon> -release looks all fine
[14:35] <sarnold> I'm loving the new 'known false positives' bug :)
[14:35] <slyon> :)
[14:36] <slyon> -proposed: libwacom -> python-libevdev is a new component mismatch..
[14:36] <slyon> the source is a desktop package, so I'd like to ask didrocks to investigate
[14:36] <slyon> (who apparently isn't here today, so maybe postpone to next week)
[14:37] <sarnold> that's getting mighty close to feature freeze
[14:38] <slyon> right. but I think promotions to main are usually not cosidered feature freeze critical (unless they explicitly are for enabling new features, of course)
[14:39] <slyon> inetutils looks interesting, never saw such mismatch before (dependency on itself)...
[14:39] <slyon> it seems to be related to telnet, which is a foundations package, so I'll try to investigate what's going on there.
[14:39] <sarnold> oh wow, heh I missed that..
[14:40] <slyon> also gsasl -> libgssglue seems new, it's foundations, too. I'll ask jawn-smith about that, who did the other mutt related MIRs
[14:40] <slyon> #topic New MIRs
[14:40] <slyon> Mission: ensure to assign all incoming reviews for fast processing
[14:41] <slyon> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[14:41] <slyon> we have bug #1986591
[14:41] <slyon> sarnold: you had some opinion on this apparently?
[14:42] <sarnold> slyon: mostly I wanted to push back against adding these packages to main in focal
[14:42] <sarnold> slyon: as far as I know there's no business demand for this feature; I'm completely fine with community-driven feature requests, but doing a ton of work for it on a two year old release doesn't seem productive to me
[14:43] <slyon> I agree. And I think we should postpone this to next week, too. So we can discuss the case with more MIR team members.
[14:43] <slyon> so, leaving it open and moving on.
[14:43] <slyon> #topic Incomplete bugs / questions
[14:43] <slyon> Mission: Identify required actions and spread the load among the teams
[14:43] <slyon> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[14:44] <slyon> bug #1963707 is still pending the "hw available for testing?" question
[14:44] <sarnold> aha, nice, I wondered why it was back :)
[14:45] <slyon> bug #1909665 is still incomplete (does not have a MIR template). It should probably be assigned to whoever is working on this
[14:45] <sarnold> lua transition, is that a foundations thing?
[14:46] <slyon> no. it's server
[14:47] <slyon> at least lua5.3 is subscribed to ~ubuntu-server
[14:48] <sarnold> okay, having read more of the bug I think you're right, ubuntu-server, and it feels like they're pretty close :)
[14:48] <slyon> yes. so let's keep it open until ready, maybe next week.
[14:49] <sarnold> comment #13 does suggest it might be a few months -- is it fine to leave it in this list until then? or should we move it to ubuntu-server so they don't lose track of it?
[14:49] <sarnold> I don't want to be hectoring about it :) but I also would hate for it to be overlooked when it feels close
[14:49] <slyon> sarnold: that's a good idea! We should assign ubuntu-server
[14:50] <sarnold> done
[14:50] <slyon> thx
[14:50] <slyon> bug #1986592 is incomplete. I'll assign it to the reporter, to make it disappear from our list until ready
[14:50] <sarnold> good idea
[14:50] <sarnold> I have stronger opinions here
[14:50] <sarnold> we do not need every single popularly used vpn in main
[14:52] <slyon> sarnold: could you put that as a comment into the LP bug report?
[14:52] <sarnold> openconnect sounds like it may be better than the proprietary stuff it is meant to replace, but it almost always interops with horrible old proprietary junk that's a decade behind the times, or more
[14:53] <slyon> to start a discussion before the reporter puts lots of effort in preparing the MIR templates
[14:54] <slyon> #topic MIR related Security Review Queue
[14:54] <slyon> Mission: Check on progress, do deadlines seem doable?
[14:54] <slyon> #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir
[14:55] <slyon> sarnold: any news on the security reviews?
[14:55] <sarnold> mark esler has been an absolute machine chewing through MIRs :) I'm feeling so much better about this list today than eg two weeks ago
[14:56] <sarnold> I'm concerned about nullboot; chrisccoulson's time is limited and in very high demand
[14:56] <slyon> anything we can help with wrt nullboot? to speed things up? cc juliank ^
[14:56] <sarnold> all the smart-card related packages are shared security/desktop, and so long as our security certifications team is short-staffed I can't imagine those getting traction
[14:58] <sarnold> nothing comes to mind; I'll ask chris when he thinks he might be able to get to it, but as usual, there's almost always a steady-stream of high-priority Interrupt-Driven sorts of needs..
[14:59] <jbicha> slyon: I asked about hardware for libqrtr-glib. I don't think the desktop team has access to this hardware directly. We need to check with Canonical's hardware certification team
[14:59] <slyon> jbicha: thanks for the update. we'll keep tracking the bug as "Incomplete" until there is a testing opportunity
[15:01] <slyon> sarnold: wrt nullboot: I cannot find a definitive deadline in the MIR report. but it seems to be entangled with enabling FDE functionallity, which might bring up some discussions during the next sprint
[15:01] <sarnold> definintely :)
[15:01] <slyon> #topic Any other business?
[15:01] <sarnold> none here
[15:02] <slyon> we had very little attendence during today's meeting, which is sad :(
[15:02] <slyon> thanks for being here and updating things with me sarnold!
[15:02] <slyon> #endmeeting
[15:02] <meetingology> Meeting ended at 15:02:41 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-08-16-14.34.moin.txt
[15:02] <sarnold> thanks slyon :)
[15:03] <sarnold> oh, heh, the meeting actually has properly declined notes from folks who didn't show (as well as folks who can't show :)
[15:03] <slyon> indeed! I didn't see that before :)
[15:04] <slyon> and it's summer time, people might be on vacation
[15:04] <sarnold> *nod*
[15:08] <juliank> slyon: we're shipping nullboot to CVM already I think, would be good to get it done
[15:08] <juliank> slyon: chris wrote all security bits of it, so he can't really review it I suppose
[15:09] <sarnold> lol
[15:09] <sarnold> while that's a strong vote in favor of it being done right, that also complicates finding someone to review this :)
[15:10] <juliank> you could say chris reviewed the bits already :D
[18:54] <vorlon> cyphermox: hi, are you here today? :)
[19:00] <rbasak> o/
[19:00]  * vorlon waves
[19:00] <vorlon> sil2100 is OoO today and declined the meeting in his google calendar, so I think we're dependent on cyphermox's IRC client being a pointer to an actually present cyphermox for us to be quorate
[19:05] <vorlon> cyphermox_: hi?
[19:05] <cyphermox_> Hi
[19:05] <vorlon> hurray
[19:05] <cyphermox_> Almost there, on my phone
[19:09] <cyphermox_> Are we quorate? I do not have access to backlog
[19:10] <sarnold> cyphermox_: just rbasak, vorlon, and you :)
[19:10] <cyphermox_> Oh yay
[19:10] <vorlon> #startmeeting
[19:10] <meetingology> Meeting started at 19:10:23 UTC.  The chair is vorlon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:10] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:10] <vorlon> #topic Action review
[19:11] <vorlon> ACTION: (everyone) review the Ubuntu Backports Team Charter for ratification
[19:11] <rbasak> Still pending I think.
[19:12] <vorlon> I recently stumbled across this in one of my browser tabs; I guess this is still a current action we need to follow through on, so carry-over
[19:12] <vorlon> ACTION: (everyone) formal ratification of third party seeded snap security policy (finalize wording on the Google Doc)
[19:12] <vorlon> rbasak: is that an accurate current action, I think we were waiting for you to finalize drafting?
[19:12] <vorlon> #action (everyone) review the Ubuntu Backports Team Charter for ratification
[19:12] <meetingology> ACTION: (everyone) review the Ubuntu Backports Team Charter for ratification
[19:14] <rbasak> I did have a draft that I proposed quite a long time ago to the ubuntu-backports@ list, but haven't really had a response.
[19:14] <rbasak> I'll need to take it up with the backporters team to find a solution.
[19:15] <vorlon> rbasak: sorry, I was asking about the snap security policy ratification
[19:15] <rbasak> Oh. Right. I'm still working on that. I have been making some progress in the doc.
[19:15] <vorlon> should I replace this action with one for you?
[19:15] <rbasak> Sure
[19:15] <rbasak> Assuming everyone is happy with the rest of the doc?
[19:16] <vorlon> #action rbasak to finalize third-party seeded snap security policy
[19:16] <meetingology> ACTION: rbasak to finalize third-party seeded snap security policy
[19:16] <rbasak> I'm working on analysing/assessing/speaking to stakeholders of existing snaps
[19:16] <vorlon> I was happy with the doc last I looked :) cyphermox_ had you reviewed it recently?
[19:16] <cyphermox_> Yes, I was happy with it as well
[19:17] <vorlon> excellent
[19:17] <vorlon> ACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance. (rbasak, 19:06)
[19:18] <vorlon> I've been postponing this until the draft is finalized because I think it will be subsumed; I'll carry over
[19:18] <vorlon> #action vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.
[19:18] <meetingology> ACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.
[19:18] <vorlon> ACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:18] <vorlon> sil2100 not here so carrying over
[19:18] <vorlon> #action sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:18] <meetingology> ACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:18] <vorlon> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:18] <vorlon> rbasak: still current?
[19:19] <rbasak> Yes that's on me still
[19:19] <vorlon> #action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:19] <meetingology> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:19] <vorlon> ACTION: cyphermox to follow up with the CC regarding the TB nominations and election
[19:19] <vorlon> cyphermox: ?
[19:21] <vorlon> cyphermox: are you still on point for talking to the CC about TB elections?
[19:21] <cyphermox_> Yes
[19:21] <cyphermox_> I had, but I guess we'll need to contact again
[19:22] <vorlon> ok
[19:22] <vorlon> #action cyphermox to re-ping the CC regarding the TB nominations and election
[19:22] <meetingology> ACTION: cyphermox to re-ping the CC regarding the TB nominations and election
[19:22] <vorlon> that's it for previous actions
[19:22] <vorlon> #topic Definition of our third party repository policy. See https://docs.google.com/document/d/1apUKR4gtOrfPGCWmtoebaQUhoy-fG8Cyo3VKJyhnpD0/edit
[19:23] <vorlon> that's on the agenda, but is covered by the previous carry-over action for rbasak
[19:23] <vorlon> so I don't think we need to discuss this?
[19:23] <rbasak> Yeah it's the same item
[19:23] <vorlon> #topic Scan the mailing list archive for anything we missed (standing item)
[19:24] <rbasak> "New Official Flavor Process Issues"
[19:24] <rbasak> I think this is on me from the last meeting, and I've been working on this.
[19:24] <vorlon> #link https://lists.ubuntu.com/archives/technical-board/2022-July/002648.html
[19:24] <vorlon> I see you just shared a google doc with me, thanks for that
[19:24] <rbasak> I've shared a draft with the TB and Release Team admins (vorlon and sil2100)
[19:25] <rbasak> Also for ItzSwirlz and Eickmeyer
[19:25] <vorlon> I'd welcome it being shared with other members of the release team if you think it's far enough along to do so, more eyes -> shallow bugs etc
[19:26] <rbasak> (I need a Google account address for Eickmeyer)
[19:26] <vorlon> (to make me less of a bottleneck)
[19:26] <rbasak> Sure - I just need the addresses. The Canonical members I can find.
[19:26] <rbasak> Any other release team members interested, please give me addresses.
[19:27] <vorlon> currently all active release team members are Canonical employees, unfortunately :/
[19:27] <vorlon> (tumbleweed dips in and out occasionally)
[19:27] <rbasak> Not laney
[19:27] <vorlon> he's a member of the launchpad team but not active so I don't think it's worth chasing him on this
[19:27] <rbasak> Oh, "active"
[19:28] <rbasak> But I don't have a list of active members
[19:28] <vorlon> right, I'm saying if you grab the canonical folks on there it's close enough
[19:28] <rbasak> I've just added everyone I have addresses for as it's not up to me to say who is active and who isn't.
[19:29] <vorlon> thanks
[19:29] <vorlon> #link https://lists.ubuntu.com/archives/technical-board/2022-August/002661.html
[19:29] <vorlon> there's also this, which is an invitation for TB members to go to Prague in November
[19:29] <vorlon> I will be in Prague the week prior, but not able to stick around for the Ubuntu Summit
[19:29] <rbasak> I will be there.
[19:30] <vorlon> rbasak: for the summit?
[19:30] <rbasak> I believe sil2100 will also be there.
[19:30] <rbasak> Yes
[19:30] <vorlon> ah, nice
[19:30] <vorlon> cyphermox: do you want to go? :)
[19:30] <vorlon> anyway we don't have to settle that here
[19:30] <cyphermox_> Yeah i think so
[19:31] <vorlon> cyphermox_: nice! I guess you will follow up with Mauro then?
[19:31] <cyphermox_> I'll need to look into it
[19:31] <cyphermox_> Yes I will
[19:31] <vorlon> \o/
[19:31] <Fallen> fwiw from earlier, I had reached out to the CC as well on various elections coming up, I will reping them as well.
[19:32] <vorlon> Fallen: excellent, thank you (and hello!)
[19:32] <cyphermox_> Cool
[19:32] <Fallen> o/
[19:32] <vorlon> #topic Check up on community bugs (standing item)
[19:32] <vorlon> https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard is empty
[19:33] <vorlon> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[19:33] <vorlon> that looks to be sil2100, with cyphermox_ as backup
[19:34] <cyphermox_> Sounds good to me and I shall have my IRC solider before then
[19:34] <vorlon> #agreed next chair: sil2100, backup: cyphermox_
[19:34] <meetingology> AGREED: next chair: sil2100, backup: cyphermox_
[19:34] <vorlon> #topic AOB
[19:34] <vorlon> teh one thing I thought might be AOB was actually covered wrt the mailing list review
[19:35] <rbasak> Great. Thanks for chairing!
[19:35] <vorlon> we do have Fallen here who is Canonical's new manager of the Community Team
[19:35] <vorlon> not sure if he has anything he wants to ask us today, as he was looking to connect :)
[19:36] <Fallen> I've gone through my notes and I think I have a good start to get things rolling. I do have a few things I could chat about
[19:37] <vorlon> we can probably adjourn the meeting and stick around to chat?
[19:37] <Fallen> My first question might be answered, I was wondering how the TB tracks their larger projects - does this happen via the LP link in ubuntu-community?
[19:37] <Fallen> Sure!
[19:37] <vorlon> #endmeeting
[19:37] <meetingology> Meeting ended at 19:37:38 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-08-16-19.10.moin.txt
[19:37] <vorlon> cyphermox_, rbasak: thanks!
[19:38] <cyphermox_> Yes, that and mailing list
[19:38] <vorlon> Fallen: I don't recall ever using the bug link for larger TB-initiated projects, that's generally an entry point for others assigning things to us
[19:38] <vorlon> (often administrative things, like setting up packagesets in Launchpad for the Ubuntu archive)
[19:39] <vorlon> I think https://wiki.ubuntu.com/TechnicalBoardAgenda and the mailing list is really how things are tracked over time
[19:39] <rbasak> Does the TB even have larger projects?
[19:39] <vorlon> well the snap policy question has been ongoing for a while
[19:39] <rbasak> Usually I'd expect larger projects to be done by delegated teams
[19:39] <cyphermox_> Well we have some of these long term documentation things like the third parhy policy
[19:39] <rbasak> Yes that's probably the largest thing
[19:40] <rbasak> I suppose then the answer is that these things are tracked through action items or other standing items in our agenda
[19:40] <cyphermox_> Some of these translate to huge mailing list threads
[19:40] <Fallen> Documentation was my primary thought. Generally though I think it would be great if there is a thing we can point to to show people "this is what <insert council here> is currently working on"
[19:41] <rbasak> That would be useful.
[19:41] <rbasak> "We're working on a way to better track what we're working on"
[19:43] <Fallen> Heh so true :D It might also help move things along a bit quicker, to me if there is a list like this it encourages me to put effort onto the council work that I volunteer on.
[19:43] <sarnold> there was a bit of a longer-term project https://lists.ubuntu.com/archives/technical-board/2021-June/002560.html
[19:43] <Fallen> It seems a launchpad project might be the historically correct way to do this, but I'm also open to other systems. Maybe something to think about until the next TB meeting?
[19:45] <vorlon> I don't know how ingrained the use of ubuntu-community is or how many places there might be documentation pointing people to use that for TB bugs; but it certainly has been an issue in the past that we don't have a clean way to get launchpad email notifications for our ubuntu-community bugs
[19:46] <vorlon> so maybe a separate LP project would be useful, with a committment to continue tracking the existing bug list and whenever we see things there, make sure folks are pointed to the new project and that we fix any documentation?
[19:47] <cyphermox_> +1
[19:47] <rbasak> vorlon: the problem is that ordinary people can't assign an ubuntu-community bug to ~techboard
[19:47] <rbasak> (which was the official process)
[19:47] <vorlon> unfortunately I adjourned the meeting so we can't record actions ;P but I can post to the mailing list suggesting this, to make sure we're all on board before I go changing things in LP
[19:48] <vorlon> rbasak: oh, was assignment the problem? ick
[19:49] <Fallen> I would see this more as a tool for you all to track your work based on the input you receive from others on the list etc, so others directly assigning to ~techboard might actually be counterproductive.
[19:49] <rbasak> +1 for an LP project BTW. Bugs seem like the simplest thing to do that will work, and a separate project will resolve the previous issue.
[19:49] <cyphermox_> A separate project would solve this anwyY
[19:50] <vorlon> Fallen: we know how to unassign ourselves and close bugs ;)
[19:50] <rbasak> And we can track actual stuff that we're committing to using a Triaged state or similar.
[19:50] <rbasak> Now we just need to bikeshed the name?
[19:51] <vorlon> yep - on the mailing list please ;-)
[19:51] <vorlon> Fallen: anything else? fwiw I have a soft stop in 9 minutes for lunch
[19:51] <Fallen> Heh ok, that is fair :) Sounds great!
[19:51] <sarnold> mm lunch
[19:52] <Fallen> Yes, one more, we can keep it brief and continue discussion soon: I wanted to talk a bit about documentation.
[19:53] <Fallen> One thing I'd like the community and Canonical to work on is to improve the documentation about how the community can participate. In your case, also indirectly through subgroups, this might relate to some of the perks people can recieve such as MOTU, and how to become a flavor.
[19:55] <vorlon> improvement of documentation about official flavors is in progress thanks to rbasak, as discussed earlier
[19:56] <Fallen> Yes, very much appreciated! If I can help round up folks to support you I'm very happy to. fwiw I'm working on getting a docs frontend up similar to https://anbox-cloud.io/docs which we can use for documentation of community facing issues.
[19:57] <Fallen> Are there any other areas that you think would be worthwhile to improve documentation on?
[19:57] <vorlon> (fwiw though I agree with improving the documentation, I don't foresee this making a significant difference in the throughput of flavors, both because a flavor is a significant committment over time, and because we don't have infinite capacity to incorporate official flavors into the ecosystem)
[19:58] <vorlon> well it's not specifically under the TB's purview, but I would like for the Ubuntu community collectively to do some work on consolidating and cleaning up the wiki documentation for new contributors
[19:58] <Fallen> I agree, and I think the capacity overhead is something we should consider, and set clear expectations on. Frustrating if someone does put in the effort, but in the end the blocking factor is that we don't believe we have the capacity overhead for it.
[19:58] <vorlon> I think it was mentioned recently that there's still some stuff referencing bzr
[19:59] <Fallen> Yes, that was likely me in the product sprint :)
[20:00] <vorlon> hah
[20:00] <Fallen> Eventually decommissioning the wiki is on my wishlist! Given we are at the hour I'll leave you to the next thing, but if there are any areas of documentation directly in the TB's purview maybe we could talk about that next time.
[20:01] <vorlon> Fallen: cheers. thanks for the chat!
[20:01] <cyphermox_> Ah, interesting, I was just wondering about that given discourse and all
[20:01] <Fallen> Likewise, thank you for the insights!
[20:02] <vorlon> (fwiw actually decommisioning the wiki properly would be a huge project and I'm not on board with it ;)
[20:03] <Fallen> Oh final note, you are all very much invited to #ubuntu-community-team, my team is using this for day to day work discussions, and I've also invited the CC to join :)
[20:03] <cyphermox_> I will join tomorrow when I am not on my phone


[18:53] <ubot2> Nafallo called the ops in #ubuntu-desktop ()
[18:55] <ubot2> EXORCIST called the ops in #ubuntu-desktop ()
[18:55] <ubot2> EXORCIST called the ops in #ubuntu-beginners-team ()
[18:55] <ubot2> EXORCIST called the ops in #ubuntu-bugs ()
[18:55] <Nafallo> ugh
[18:56] <Fuchs> solved.
[18:56] <EXORCIST> !ops
[18:56] <IdleOne> lol
[18:56] <Nafallo> thanks Fuchs and Pricey :-)
[21:05] <Fuchs> AlanBell: since you seem to be around: earlier there was a problem in #ubuntu-nl with no ops around, which made me look at the ACL. I am not sure about your internal policies on these, but maybe you want to adapt it a bit
[21:07] <AlanBell> hi Fuchs
[21:07] <Fuchs> Hi :)
[21:07] <AlanBell> yeah, I will find out what is up with that
[21:07] <Fuchs> Okay
[21:08] <Fuchs> have a nice evening :)
[21:08] <AlanBell> oh JanC is on the ACL for that :)
[21:12] <JanC> eh, I saw earlier that EXORCIST entered in #ubuntu-nl, spewed 12 lines of "insults" and left less than 5 minutes later
[21:13] <JanC> we aren't around every second 24/7  ☺
[21:13] <AlanBell> yeah, which is fine, Fuchs was just pointing out that there was no freenode staff ACL entry
[21:13] <Fuchs> no IRCC entry as well
[21:14] <JanC> ah, I think I have that for #ubuntu-be (certainly IRCC entry)
[21:14] <Fuchs> JanC: yes, he was a bit of an issue in plenty of ubuntu channels due to a personal grudge, and had to be removed from the network entirely,
[21:14] <JanC> I don't think I can manage the #ubuntu-nl* access lists?
[21:14] <Fuchs> I was just a bit surprised by the ACL compared to other ubuntu channels, hence me pointing it out :)
[21:14] <Fuchs> no, you can't
[21:14] <Fuchs> you don't have f or F
[21:15] <AlanBell> JanC: nope, but you are a handy person to talk to :)
[21:16] <AlanBell> SWAT would appear to be the owner, but isn't online I think
[21:16] <JanC> yes, that's Sebastian
[21:17] <JanC> he hasn't been on-line much since his personal server crashed   :-/
[21:18] <AlanBell> ok, well there is no tearing hurry about it, but if you see him around could you point him in the direction of https://wiki.ubuntu.com/IRC/CreatingChannels
[21:19] <AlanBell> we don't insist on anything in particular for channel ACLs, but there are guidelines to add freenode/staff and UbuntuIrcCouncil
[21:19] <JanC> yep, I'll try to remember that
[21:20] <JanC> seems like I already have both of you on #ubuntu-be  ☺
[21:20] <Fuchs> \o/
[21:20] <Fuchs> JanC: it's just, as the website says, good practise, because if we are not on it, we are a bit hesitant to act since we do respect channel owner decisions. But it is entirely up to you, it just hit me as odd :)
[21:21] <Fuchs> s/hit/strike/
[21:22] <JanC> Fuchs: for the record: I don't mind you intervening in case of obvious (server-wide) trolls like that
[21:22] <Fuchs> JanC: that doens't help unless we are on the ACL, I am afraid :(  But anyway, it is in the ubuntu namespace, so in the worst case an ubuntu gc could have us act
[21:23] <JanC> well, I don't know exactly what you can do as freenode staff
[21:23] <JanC> with or withoiut that ACL
[21:23] <JanC> without
[21:24] <Fuchs> we could technically go around it, it's just we rather don't :)
[21:25] <JanC> well, we don't mind if you go around it in case of an emergency
[21:26] <JanC> and I suppose that's the sort of situations you would interfere with—not simple disputes between channel members  ;)


[08:13] <lordievader> Good morning
[09:22] <Onepamopa> question - /proc/sys/kernel/core_pattern is set to /tmp/core.%e.%p.%t, * soft core 500000 & root hard core 1000000 in limits.conf, the application segfaults and no corefile is found anywhere
[09:22] <Onepamopa> ubuntu server 16.04 x64
[09:23] <Onepamopa> so, how do I go about enabling core dump files ?
[10:04] <Genk1> Hello all
[10:04] <Genk1>  what is the fast  way to backup/recover a mysql database using MyISAM engine ?
[10:04] <Genk1> I've found mysqldump to be very slow
[10:04] <ddellav> with myisam thats kinda all you go
[10:04] <ddellav> *got
[10:05] <ddellav> with innodb you can do incremental backups but myisam is not transactional so your only choice is a full table dump
[10:06] <Genk1> ddellav, I see thanks for your your answer
[10:07] <ddellav> you're welcome Genk1
[11:31] <JanC> also depends on database size how fast it is of course...
[12:34] <patdk-lap> and what filesystem your using
[12:35] <patdk-lap> personally, I had always used lvm snapshots to backup mysql myisam
[12:35] <patdk-lap> but it has been awhile, and use innodb for just about everything now
[12:51] <Walex> patdk-lap: even LVM2 snapshots are not that good for consistent MyISAM state, but they usually work.
[12:52] <Walex> Genk1: you should really ask in #MySQL or #MariaDB for faster alternatives to 'mysqldump'. But that's really the right way to do it. If it is slow that may mean that your MyISAM files need compacting
[12:53] <blackflow> depends on the definition of "slow" and considering database size
[12:54] <blackflow> meanwhile, like Walex said, using fs snapshots to back up the database is illadvised as the database has its own regime of syncing states with the underlying fs, so you might be snapshotting incomplete states.
[12:55] <blackflow> postgres has the ability to do WAL archiving. I don't know if that's possible with MySQL. Also, consider using real time replication for backup.
[12:55] <maswan> eh, if it is an atomic snapshot, it is no more unsafe than handling an unscheduled power loss
[12:56] <blackflow> correct, but "unschedules power loss" is not a "consistent backup state" that you want your data BACK UP to be in :)
[12:56] <blackflow> *d
[12:57] <blackflow> and iirc, "unscheduled power loss" with MyISAM tables leads to "lots of corruption and pain". :)
[12:57] <maswan> well, then i'd certainly not use that for any data i'd like to keep. :)
[12:58] <blackflow> if dumps are inadequate, replication is really the best, consistent form of back up.
[13:00] <maswan> dumps were hard for us, so we setup replication, then tuned that to the point that we could get dumps made on the replica so we had both
[13:36] <patdk-wk> hmm, the database doesn't have it's own syning time, that is what a flush command is for
[13:36] <patdk-wk> now if the filesystem supports flushing also, would be requred for lvm snapshot to work
[13:36] <patdk-wk> but if every level is flushed, it's a perfect usable method
[13:37] <patdk-wk> though personally, using a mysql slave database, and doing your backups on there, is better, if your concerned about downtime
[13:48] <JanC> depending on the dependencies, you could possibly dump some tables separately too...
[13:56] <blackflow> patdk-wk: the files are mmaped and there's no guarantee that at every given moment, data in files represents 100% the in-memory state.
[14:01] <patdk-wk> blackflow, did the default change? it was not using mmap by default normally
[14:44] <blackflow> patdk-wk: afaik it mmaps since 5.1. but now that you mention it, I could be wrong, yes.
[14:45] <patdk-wk> I see support for mmap in 5.1
[14:45] <patdk-wk> but it is not enabled, except for packed myisam files, and those are read-only
[17:04] <erick3k> hi
[17:04] <erick3k> can someone help me with a routing problem?
[17:07] <erick3k> anyone in here?
[17:07] <Pici> kinda
[17:07] <erick3k> haha
[17:08] <erick3k> is there a way to force a different subnet gateway to work instead of using the route command or post up?
[17:12] <erick3k> anyone
[17:12] <erick3k> ?
[17:12] <jelly> what's a subnet gateway?
[17:14] <jelly> show an example.  Explain what it's doing, what the actual results are, what you'd want it to do instead
[17:15] <jelly> eg. pastebin current outputs of "ip a" and "ip r" and your network config (/etc/network/interfaces, or whatever else you use)
[17:15] <maxb> Also, don't say "instead of using (some perfectly reasonable options)" without explaining why you propose not to use them
[17:17] <erick3k> well am going to try
[17:17] <erick3k> the ip and gateway are on different subnet
[17:18] <erick3k> so if i put gateway on the /etc/network/interfaces it can not be bring up
[17:18] <erick3k> now if i remove it and add route add default gw (gw ip)
[17:18] <erick3k> as a command it works
[17:19] <erick3k> now i have to through cloud-init add default gateway to the /etc/network/interfaces due to automation
[17:20] <erick3k> so basically a fix could be adding a command before the network starts to delete the line gateway xxx.xxx.xxx.xxx from /etc/network/interfaces before bringing it up on boot
[17:21] <maxb> This sounds a bit scary and broken
[17:21] <erick3k> i know
[17:22] <erick3k> thats why am trying to find a better solution
[17:22] <erick3k> since ubuntu doesnt allow a different subnet gateway on /etc/network/interfaces
[17:23] <maxb> I think you will need to paste the output of "ip route" if we are to have any hope of understanding your network setup
[17:23] <erick3k> ok am gonna show with pics
[17:27] <erick3k> maxb here is not working
[17:27] <erick3k> https://i.imgur.com/z91hKJR.png
[17:29] <erick3k> hold on
[17:30] <maxb> This is not a sensible configuration
[17:31] <maxb> You can't use an address outside the subnet as a default gateway unless there's some other special routing going on
[17:37] <robert45> hi guys, after a dist-upgrade process my server is unbootable, Im getting this on the screen, any advice? http://imgur.com/a/l1hvV
[17:38] <tomreyn> robert45: press enter and examine?
[17:39] <tomreyn> for a (n entirely blind) guess: zfs related
[17:40] <robert45> tomreyn I appreciate the quick reply, Im now inside the shell. I did a service networking status and this is what I get, ifconfig shows correct network setup: http://imgur.com/a/bY7yz
[17:41] <tomreyn> robert45: you should start examingn the cause of the first error, not the last
[17:43] <tomreyn> robert45: on the screen shot you posted, the first error (which has not scroll off screen, i.e. there may have been others before this one) is about systems-tmpfiles-setup.service
[17:43] <tomreyn> the temporary / volatile file storage service did not start up properly.
[17:44] <tomreyn> it is suggested that you should run "systemctl status systems-tmpfiles-setup.service" to examine this issue.
[17:44] <tomreyn> note how the message right before this is about starting ZFS support via FUSE
[17:45] <robert45> tomreyn tx, Im running that command now
[17:46] <tomreyn> also note that ZFS-fuse is considered deprecated
[17:47] <tomreyn> use the native module instead
[17:49] <Curiontice> Hi! I want to cache HTTPS site contents such as Facebook Images and etc. I have added the following https_port 3126 tproxy ssl-bump generate-host-certificates=on dynamic_cert_mem_cache_size=4MB cert=/etc/squid3/lib/ssl_db/certs/myCA.pem connection-auth=off. This gives me errors. Is squid can not be run this way?
[17:49] <Curiontice> Please if anyone know the answer, PM me.
[17:52] <tomreyn> you might want to discuss the errors you get there.
[17:53] <MASM> in logs?
[17:53] <Curiontice> It just crashes. Segfault at xx.xx.xx
[17:54] <Curiontice> Can squid be run with Tproxy target for HTTPS traffic?
[17:54] <Curiontice> \
[17:54] <Curiontice> Can you pls confim me that ^
[17:54]  * tomreyn lacks Squid experience, can't tell
[17:54] <Curiontice> MASM: Can squid be run with Tproxy target for HTTPS traffic?
[17:56] <tomreyn> All I can tell is that caching SSL content contradicts with the idea of end-to-end encryption, it is only possible by creating a man-in-the-middle. Some companies and ... ISPs in some countries ... still do it anyways.
[17:57] <MASM> i don't know men, sorry...
[17:59] <tomreyn> http://wiki.squid-cache.org/Features/HTTPS
[17:59] <tomreyn> i assume "tproxy" stands for 'transparent proxy'.
[18:03] <robert45> tomreyn sorry I had some troubles with the systemctl command, this is what I get: http://imgur.com/a/x7p6l
[18:04] <robert45> I assume its because the filesystem is mounted as readonly
[18:05] <tomreyn> robert45: same here
[18:05] <robert45> Im rebooting it again to see if get why its not mounting properly
[18:05] <tomreyn> robert45: i would check syslog, go back to when you booted, then look through those lines until you hit the first error.
[18:06] <tomreyn> or start with "dmesg -T | less" - sometimes this is faster
[18:07] <robert45> tomreyn tx, doing that now
[18:07] <tomreyn> one (of many) possible explanation might be file system corruption on /etc or / (i do not know your partitioning scheme)
[18:08] <robert45> tomreyn ugh! I hope not, its a production server :(
[18:09] <robert45> tomreyn ok I caught the first error, I dont think it could be related, do you? http://imgur.com/a/p0OXS
[18:09] <tomreyn> apparmor failing could be related, yes
[18:10] <robert45> tomreyn well, its the same error, systemctl shows a read-only filesystem
[18:10] <tomreyn> you surely have current backups, and if it's an important system you surely considered a HA configuration?
[18:10] <robert45> when systemctl apparmor thing
[18:11] <tomreyn> so check dmesg + syslog, find out why it's r/o
[18:31] <robert45> tomreyn tx, I was able to bring it online, few service still failing though
[18:34] <robert45> tomreyn for some reason its mounting /dev/sda1 as ro, but if I use mount -o remount,tw it mounts it ok, any ideas?
[18:36] <robert45> tomreyn nevermind, I was able to fix it, it was all fstab related
[18:36] <robert45> its showing 16.04 instead of 16.10, not sure it didnt upgrade all the way through
[18:38] <tomreyn> robert45: so you upgraded from 16.04 to 16.10 recently, or tried to? appartenly it didn't happen if lsb_release -sd still shows 16.04
[18:39] <robert45> tomreyn I upgraded from 14.04, it shows 16.04 now
[18:39] <robert45> first time
 its showing 16.04 instead of 16.10, not sure it didnt upgrade all the way through
[18:39] <tomreyn> this is contradictionary
[18:40] <robert45> tomreyn not sure if I understood. I was looking to upgrade to 16.10
[18:40] <robert45> tomreyn so I upgraded from 14.04, do I need to run another upgrade?
[18:40] <tomreyn> either you last upgraded from 14.04 to 16.04, or from 16.04 to 16.10
[18:41] <tomreyn> only one of them can be correct
[18:41] <robert45> tomreyn I upgraded from 14.04 to 16.04
[18:41] <robert45> Im looking to upgrade to the latest version 16.10, is it possible?
[18:42] <tomreyn> yes, personally i prefer to run LTS releases on servers, whoever, do not like to have to upgrade every 6 months
[18:42] <tomreyn> s/whoever/however/
[18:42] <tomreyn> also LTS releases tend to be a lot more stable
[18:43] <robert45> tomreyn I see. I ran do-release-upgrade and got "No new release found"
[18:43] <robert45> tomreyn oh I just noticed 16.10 its not a LTS release
[18:44] <robert45> tomreyn so you dont recommend to upgrade from LTS to latest non LTS ?
[18:44] <tomreyn> correct, 16.10 is not LTS. and personally i prefer to only run LTS on servers. in even more so in your case. ;)
[18:44] <tomreyn> correct, 16.10 is not LTS. and personally i prefer to only run LTS on servers. and even more so in your case. ;)
[18:44] <tomreyn> ^typo fixed
[18:45] <tomreyn> first of all, i would suggest you ensure your previous upgrade succeeded, and the system is in a good condition.
[18:46] <tomreyn> !lts | robert45
[18:46] <robert45> tomreyn yes I think I wont upgrade it, Im scary to suffer any other downtime like this one
[18:46] <robert45> tomreyn understood, so far everything looks good! :)
[18:47] <patdk-lp> also be very sure of the non-lts support lifetime
[18:48] <patdk-lp> it used to be 18months, but now is like 9 I think, or maybe 6
[18:48] <tomreyn> and system upgrades mean downtime
[18:49] <tomreyn> robert45: if you like i can check your output of "apt-get update", "apt-cache policy", "apt-get -V -f install", "apt-get -V -y --simulate dist-upgrade" later.
[18:49] <patdk-lp> or worse, a broken package during upgrade
[18:49] <tomreyn> robert45: .. post them to a pastebin if so, e.g. using !pastebinit
[18:49] <tomreyn> !pastebinit | robert45
[18:50]  * tomreyn taking a shower now
[18:50] <robert45> sure, running those now
[18:53] <robert45> tomreyn patdk-lap looks like some errors indeed: http://paste.ubuntu.com/23701740/
[18:53] <robert45> how should I proceed?
[18:56] <erick3k> how can i run post-up command outside of /etc/network/interfaces?
[18:58] <andol> erick3k: cut-n-paste to the shell?
[18:59] <erick3k> andol i meant to run on startup outside interfaces,
[18:59] <erick3k> in shell says command not found
[19:01] <MASM> erick3k maybe put link in bin path
[19:03] <MASM> erick3k, maybe create a shortcuts in local/bin
[19:04] <erick3k> MASM can you link me to an example and a little newbie
[19:05] <MASM> erick3k,  shortcuts : http://unix.stackexchange.com/questions/226315/how-to-use-ln-s-to-create-a-command-line-shortcut
[19:05] <MASM> erick3k, program executable everywhere : http://unix.stackexchange.com/questions/3809/how-can-i-make-a-program-executable-from-everywhere
[19:06] <erick3k> MASM am not sure that would work i want  post-up route add xxx.xxx.xxx.xxx dev eth0 to run outside /etc/network/interfaces file
[19:07] <erick3k> just that command
[19:07] <erick3k> because /interfaces will be modified by cloud-init
[19:08] <maxb> If cloud-init is incorrectly changing your config, then fix that, rather than trying to paper over it elsewhere
[19:09] <erick3k> huh if i knew how
[19:09] <erick3k> i would
[19:09] <erick3k> is it possible to run that command outside interface or not?
[19:10] <erick3k> like on centos
[19:10] <erick3k> you just add route-eth0 file
[19:17] <maxb> Ubuntu's network configuration chooses to give you one readable file rather than littering bits and pieces across multiple files like CentOS
[19:20] <tomreyn> robert45: i don't see errors there. I see a notice, "N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension", and i see a lot of no longer needed (due to changed dependencies) packages which can likely be removed (using apt-get --purge autoremove)
[19:21] <erick3k> maxb so only solution is to have a custom script or have cloud-init run it?
[19:21] <robert45> tomreyn ok do you recommend to --purge autoremove or should I kept those for just inc ase?
[19:21] <maxb> yes
[19:22] <maxb> If you're using cloud-init to configure your networking, it needs to do it *right*
[19:23] <maxb> If it isn't, you need to work on addressing that
[19:24] <tomreyn> robert45: yes maybe dont purge immediately
[19:24] <tomreyn> there's zfs-fuse in there
[19:24] <erick3k> got it, maxb what about if i make a file executable here /etc/network/if-up/ with that command?
[19:25] <erick3k> would that work?
[19:40] <robert45> tomreyn sorry got dc'ed, thanks so much for your help, wish you a happy new year!
[22:15] <erick3k> maxb you still here?
[22:16] <erick3k> remember about the network?
[22:16] <erick3k> found a solution :)


[00:11] <spsalsm> Hello?
[00:24] <spsalsm> It'
[00:25] <spsalsm> It's not Tuesday night
[00:25] <spsalsm> But rather Thursday
[21:57] <danielveazey> greetings, anyone out there today?


[12:06] <phillw> flexiondotorg: ping
[13:35] <flexiondotorg> phillw, pong
[13:36] <phillw> hiyas flexiondotorg will you anytime for a couple l-ppc tests?
[13:36] <flexiondotorg> Not sure.
[13:36] <flexiondotorg> I just tested Ubuntu MATE on PPC and all was good.
[13:36] <phillw> the keyboard bug affecting all flavours is now in progress, there is a work around that works for server and desktop installs.
[13:37] <phillw> provied you have a us keyboard, you mean :P
[13:38] <phillw> Matheiu has pulled the two together, as the underlying issue must be the same with debian installer and ubiquity... https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1549529
[13:50]  * flexiondotorg thinks phillw owes me ;-)
[13:51] <phillw> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 that's an interesting one ... desktop units only..... Never seen that suggested before
[13:53] <flexiondotorg> I can't reproduce that anymore, and that is using computers that previously exhibited the issue.
[13:53] <flexiondotorg> I'm dropping mention of that bug from the Ubuntu MATE release notes.
[13:53]  * flexiondotorg is downloading Lubuntu Desktop.
[13:54] <flexiondotorg> for PowerPC
[13:57] <phillw> flexiondotorg: it has that many dupes, and still shows as live, I'm just going to leave a mention :)
[14:04]  * flexiondotorg is burning lubuntu desktop ppc to DVD
[14:17] <phillw> thnx :)
[14:18] <phillw> 3rd desktop amd64 test underway, 1 to go.
[14:44] <phillw> yikes, there are more red bugs on the tracker than we see at an alpha1 ....
[14:45] <phillw> and ALL seem installer related.... what on earth did they do after Beta-1 ?
[14:56] <flexiondotorg> phillw, https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1561573
[14:58] <phillw> flexiondotorg: thanks, another one the list.... I've now added a "Do NOT upgrade" warning from 15.10 / 14.04 .... http://launchpad.net/bugs/1555237
[14:58] <phillw> that's pretty deadly!!!
[15:00] <phillw> I'll go and blow up a 15.10 install later!
[15:04] <flexiondotorg> phillw, I'm done testing Lubuntu Desktop PowerPC.
[15:04] <flexiondotorg> I've test launching application in live session.
[15:04] <flexiondotorg> And an install.
[15:05] <flexiondotorg> I've add a new bug and noted some that common across architectures.
[15:05] <phillw> thanks, any chance with alternate... just an install will confirm debian installer is as happy as expected.
[15:05] <flexiondotorg> Nope. I'm out of time.
[15:05] <phillw> okies, thanks a lot for your time.
[15:05] <flexiondotorg> You're welcome :-)
[15:06] <phillw> and this http://launchpad.net/bugs/1555237 worked fine earlier in the release, I have  a VM that ! took from 14.04.4 to 16.04
[16:04] <flexiondotorg> wxl, phillw How goes the Lubuntu testing? Any show stoppers?
[16:07] <phillw> flexiondotorg: no, the swap bug is a see it, or do not (and been around a while).... I don't see it. Everything else is on our release notes. Keyboard language has work around.... That's the only one that would concern me.
[16:12] <flexiondotorg> I put that 14.04 upgrade issue in a massive red warning at the top of the release notes. Ever though Ubuntu MATE is not technically affected.
[16:14]  * teward makes a note that keyboard layout selection is likely still borked
[16:17] <phillw> teward: I flagged it for ubuntu-server amd64, there is a simple work around and it, and ubiquity manifestation have been hearded into a room and can expect execution presently.
[16:18] <teward> phillw: right, cypermox is looking into it right now
[16:20] <phillw> teward: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1549529
[16:20] <phillw> he put them both together, the underlying cause is the same.
[16:20] <teward> phillw: yes, i know, remember I poked matsubara who's kept me in the loop
[16:21] <teward> and i had partial tracking in #u-release for some time discussing with cyphermox :)
[16:21] <phillw> that the      work around is the same, the underlying cause is most like the same :)
[16:21] <teward> also tracking the bug too :)
[16:21] <phillw> Yeah, I was on both
[16:21] <teward> phillw: indeed, though it's still a very bad headache - consider those with azerty keyboards, so US/English isn't going to work right
[16:22] <phillw> Nio confirmed by fix also worked for his crazy swedish bug that was driving him mad... A quick command call and it even writes to the config file, so no need to manually edit it... Got to be the easiest work around I've posted up in a long time!!!
[16:24] <teward> heheh
[16:25] <phillw> As soon as I saw it pull up the missing alt-install screen for kybd - I was quite sure I was on a winner :)
[16:26] <phillw> It does back a little further, but Nio had language issue, so no worries about it confirming from that stage :)
[16:46] <wxl> ok, finally taking a breath of fresh air again
[16:46] <wxl> how's it going everyone?
[16:52] <phillw> wxl: all but ppc-alt good to set as ready, flexiondotorg ran out of time.
[16:53] <wxl> phillw: sigh. i wonder how long it will be before ppc dies.
[16:53] <phillw> depends if I can actually source a bloody working one!!!
[16:53] <wxl> heheh
[16:53] <phillw> oops / delete expleteive
[16:54] <wxl> i'm not sure bloody quite counts. maybe i'm wrong. :)
[16:54] <wxl> Unit193: is "bloody" against the language rules? XD
[16:54] <phillw> i use blooming on #phillw
[16:57] <phillw> B2 release notes are also up to date... 14.04.4 --> 16.04 is currently warned against. I'm doing a 15.10 --> 16.04 at present and will amend the notes if it is successful.
[16:58] <phillw> MATE report success for 32 and 64 bit.
[16:58] <wxl> phillw: thanks for all the help. i kind of disappeared due to personal issues. sorry about that.
[17:00] <phillw> It cross my mind where you'd vanished to!!! Hope all is now sorted / in process of being sorted.
[17:00] <wxl> yeah i think we're good now :)
[17:04] <tsimonq2> *yawn*
[17:04] <phillw> morning tsimonq2
[17:04] <tsimonq2> twitter tells me https://twitter.com/omgubuntu/status/712955245777797120
[17:04] <tsimonq2> status?
[17:04] <wxl> woo hoo spring break
[17:04] <tsimonq2> and how can I help?
[17:04] <tsimonq2> yeah totally :D
[17:05] <tsimonq2> (I'm actually building an app for the Ubuntu Touch store, nothing fancy, but still :D)
[17:05] <wxl> i guess i should mark as ready, eh phillw ?
[17:05] <phillw> tsimonq2: I'm not sure, there are a lot of red installer bugs about - not sure what the release team are going to do.
[17:05] <wxl> oic
[17:05] <wxl> we're waiting to hear from them
[17:06] <phillw> wxl: mark ours as, sure.
[17:06] <tsimonq2> I'll read backlogs quick
[17:07] <phillw> wxl there are no bugs specific to B2 ppc-alternate, slide show is ubiquity, language is common to all flavours etc.... I'd be minded to let ppc alt out into the wild - maybe some one would test it?
[17:08] <tsimonq2> wxl: I broke my freaking Pi 3, SD card slot is fcuked up, either that or the SD card itself, I get stuck at rainbow screen and I see some bent connectors looking at the Pi
[17:08] <tsimonq2> *sigh* another $35
[17:08] <tsimonq2> anyways
[17:08] <wxl> phillw: i think i'm just going to do it, with desktop having succeeded
[17:08] <wxl> bummer tsimonq2
[17:08] <phillw> wxl: that would be my mindeset... I'd not do for final, but... what the heck :)
[17:09] <tsimonq2> I'm at mom's if you guys need final QA tests
[17:09] <wxl> heheheh i ktend to agree phillw
[17:09] <tsimonq2> sorry for waking up late, I statrted my app at 3 AM :)
[17:09] <phillw> brb ... DDT
[17:18] <phillw> back
[17:23] <phillw> wxl: when you plough the emails, I emailed Julien to let him know the alts had snook over size... But, so has server iso!!!
[17:23] <wxl> phillw: oh jeez! wtf!
[17:24] <phillw> is okay, I had server ISO as the issue with keyboard needed checking on the other debian-installer system :)
[17:25] <phillw> 15.10 --> 16.04 is working, I'll ammend the notes.
[17:34] <phillw> done
[18:37] <phillw> wxl: do they expect a release today? With the wolf on light-duties, looks like I'm on comms as well !!!
[19:43] <wxl> phillw: we are releasing today!
[19:46] <phillw> okies.... I spent 5 hours solid testing, bugs and wiki ..... I've now opened a bottle of wine, so you will be doing ML announcement and lubuntu.me.... I'll do FB, G+ and as lubuntu follows me on twitter - I can do that one as well.   We will be missing a couple off the list, but it is a milestone test not a full release .... We are borg, we will adapt :)
[19:48] <wxl> phillw: yeah i can take care of that. heck, i can take care of the social media stuff, if you need to conk out.
[19:48] <phillw> is okay... I'm used to that....
[19:48] <wxl> phillw: ok. trying to get logged into the freaking wiki right now.
[19:49] <phillw> Oh, can you check up on the asian contingent complaint, the guy reporting is a good guy and pretty much kick started our translations team for RL.
[19:50] <phillw> wxl: https://wiki.ubuntu.com/XenialXerus/Beta2/Lubuntu
[19:50] <phillw> is notes,
[19:50] <wxl> great, thanks!
[19:51] <phillw> the comment from Keiichi Shiga on Fb does need following up. I've provided the release notes, so if they have queries we will take on board and escalate - it is scary to lose this at this point in the cycle :/
[19:52] <phillw> Julien nailed it last release, but is a full distro cock up.
[19:52] <wxl> these problems affect all flavors, or just us?
[19:53] <phillw> language and keboards seems to be everything from server to desktop Unity
[19:53] <wxl> well that's reassuring, even this late in the cycle
[19:53] <wxl> it means there are many eyes on it
[19:54] <wxl> ubuntu proper has a very vocal international community, so they won't get a release without a lot of serious gnashing of the teeth!
[19:54] <phillw> The work around is kool, and it is being crawled over... but a fix for everyone would have meant re-spining the world... Hence my asking, earlier
[19:56] <phillw> wxl: as to how the messed it up after B1 to B2?..... Pass.... And I've not ranted at anyone, just sent an email to the release team explaining that there was a large elephant in the room that appeared to affect everyone on en-us ..... Which they declined, but it would have been red :P
[19:56] <phillw> *read*
[19:57] <phillw> 14.04.4 --> 16.04 also now kills, it was working earlier in the cycle..... :: SHRUGS ::
[19:57] <wxl> ugh
[19:58] <phillw> wxl:  Not seen so many red bugs on installer mess ups..... ever.... and this is an LTS???? VERY scary
[19:59] <wxl> phillw: needless to say, someone's going to get their hands slapped when the culprit is discovered
[19:59] <phillw> all was working in B1, so some group accepted changes in.
[19:59] <wxl> yep
[20:00] <phillw> AFTER FF
[20:00] <phillw> of is that FF for FFS :P
[20:02] <phillw> wxl: oh, and we gained https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1551446
[20:03] <phillw> which is a bit of a PITA, I've not old Julien the "good news",  I did over sized ALT iso's.... your turn, else he will think all I ever send him is bad news :P
[20:04] <wxl> i think we had that one before though, didn't we, phillw ?
[20:04] <phillw> wxl: as for https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1561573 as the PPC contact for lubuntu, you need to liase with flexio from MATE on this
[20:05] <phillw> wxl: yeah, but it's back....
[20:06] <phillw> from reading the black wallpaper bug, it is start up order... it may be an easy fix for Julien, but he has to be told of it :)......
[21:46] <phillw> flexiondotorg: I had fish finger butties last week, with a 1/2 tin of baked beans.... They are not the same without baked beans!!!!
[21:59] <phillw> wxl: flexiondotorg had a chat with jibel, indeed the keyboard language bug complete with work around is no longer high, but he is happy to have been told of the   bug. I'm still a good boi :D
[22:00] <teward> phillw: you mean the d-i bug?
[22:00] <phillw> Now, let me try that again, in English!!!!
[22:02] <phillw> The language + kbd bug will be rolled out, jibel was no aware of it and appreciates that is can have a major impact on people. He will "quietly" ensure that his attention.
[22:05] <phillw> and I didn't even get kicked from #ubuntu-release - got to chat with one and it was a good day..... Now, food :D :D
[22:11] <phillw> wxl: and flexiondotorg ... been a long day, but THIS has put a smile on my face......
[22:11] <phillw> (22:07:23) stgraber: infinity: desktop belongs to no drupal role, so that means only the release team has admin access to the product
[22:11] <phillw> (22:07:26) infinity: stgraber: Right, I found that.
[22:11] <phillw> (22:07:45) infinity: stgraber: Can't be only the release team, jibel can twiddle it.
[22:33] <drab> anybody around with a suggestion for master configs to lock settings for a mass deployment of lubuntu?
[22:33] <drab> I'm having trouble to figure out where to put a bunch of custom settings to apply system wide on a school computer lab
[22:34] <drab> in the past on ubuntu I could use dconf/gconf and lock settings, but now seeing how to do that with lunbut/lxde/openbox
[22:35] <drab> also I'm trying to customize lxsession-logout, but looking at the code it's not clear to me how to se policy so that students cannot shut down the computer, but just logout, and to make the buttons horizontal (since that's what most kids are used to on windows at home)


 But in any case they shouldn't end up with all 3 series, -generic, -hwe and -oem
[10:58] <alkisg> What's the process for auto-installing oem after the initial installation?Which package/script does that?
[11:13] <luna> New kernels today upstream 1-2 days early
[11:22] <tjaalton> alkisg: the hwe-metapackage is always installed, so that it rolls to the next one. in .0 and .1 it does essentially give the generic kernel
[11:23] <tjaalton> there is no process for auto-installing oem on normal upgrades, so you'd need to look at the apt/dpkg logs to figure out why it would install those. but I suspect some nvidia wonkiness
[11:37] <thefossguy> > <@thefossguy:matrix.org> Hello there, I am experimenting with enabling Rust support in the Linux kernel. So far, I have been able to compile the kernel with Rust support enabled; only in theory. The kernel config options say that Rust support is present but trying to build the out of tree Rust module fails... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/f582bed42f7fd03cce7551c679c81ffb0dec197e>)
[12:14] <alkisg> tjaalton: thanks, I'll ask for remote access to check the logs
[12:23] <alkisg> tjaalton: for iso in *22.04*.iso; do echo -n "$iso: "; mount "$iso" /mnt; mount /mnt/casper/filesystem.squashfs /mnt; chroot /mnt dpkg -l | grep -q hwe && echo -n "YES, " || echo -n "NO, "; umount /mnt; umount /mnt; done 2>/dev/null
[12:23] <alkisg> kubuntu-22.04.2-desktop-amd64.iso: YES, lubuntu-22.04.1-desktop-amd64.iso: NO, ubuntu-22.04.1-desktop-amd64.iso: YES, ubuntu-22.04.1-live-server-amd64.iso: NO, ubuntu-mate-22.04.2-desktop-amd64.iso: YES, xubuntu-22.04.1-desktop-amd64.iso: NO
[12:24] <alkisg> At least in the live CDs, in 22.04 and 22.04.1, there's no -hwe; it starts with 22.04.2
[12:24] <alkisg> But OK that's not important, I'll try to discover why these users are getting the -oem package, thanks
[12:25] <alkisg> Ah, it's there in gnome (which I rarely use) but not in the other flavors; that explains it
[12:28] <alkisg> (although all flavours should really have the same kernel packages...)
[13:26] <arighi> thefossguy, this is with upstream kernel right? not the ubuntu kernel. Also, do you have CONFIG_RUST=y in your kernel .config?


[05:12] <mborzecki> morning
[05:26] <mbeneto> morning
[06:28] <mborzecki> mvo: morning
[06:31] <mvo> mborzecki: good morning!
[06:40] <mborzecki> mvo: shall we land #5122 ?
[06:40] <mup> PR #5122: snap: add support for `snap advise-snap --from-apt` <Created by mvo5> <https://github.com/snapcore/snapd/pull/5122>
[06:45] <mvo> mborzecki: let me quickly double check
[06:45] <mvo> mborzecki: does it have two +1 already?
[06:47] <mborzecki> mvo: yup
[07:46] <mborzecki> mvo: 2.34.2 is tagged but it's not 'released' on github
[07:47] <mvo> mborzecki: yeah, let me fix that, its just test fixes but still let me fix it
[08:18] <mborzecki> google:ubuntu-core-16-64:tests/main/unhandled-task failed on master and journal is basically Jul 23 07:56:56 jul230742-893813 audit[8830]: AVC apparmor="DENIED" operation="accept" profile="snap.network-bind-consumer.network-consumer" pid=8830 comm="python3" laddr=<IP_ADDRESS> lport=8081 family="inet" sock_type="stream" protocol=6 requested_mask="accept" denied_mask="accept" repeated over and over again
[08:18] <mborzecki> thought that the patches cleaning up snap.network-bind-consumer.network-consumer were landed already?
[08:20] <mborzecki> or not, merged #5477 just now
[08:20] <mup> PR #5477: tests: change the service snap used instead of network-bind-consumer <Created by sergiocazzolato> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/5477>
[08:26] <mvo> mborzecki: thank you for this
[08:34] <Chipaca> moin moin
[08:34] <Chipaca> mborzecki: welcome back!
[08:35] <mborzecki> Chipaca: hey
[08:35] <Chipaca> mborzecki: are you appropriately revitalized
[08:35] <mborzecki> Chipaca: i still think that vacation snould be at least 3 weeks long
[08:36] <Chipaca> mborzecki: I see no problem with that
[08:36] <Chipaca> mborzecki: (that's the way nearly everybody does it in Argentina)
[08:38] <mborzecki> Chipaca: here it's usually 2 weeks :(
[08:38] <Chipaca> mborzecki: ah, duration varies, i meant most everybody takes it in a single uninterrupted block
[08:39] <Chipaca> indeed if memory serves the first full year you're working somewhere you get about a week
[08:41] <mvo> hey Chipaca ! good morning
[08:41] <Chipaca> on a completely unrelated note, the person behind https://play.jsgo.io/ just let me know they bumped the limit on git objects, so you can now import snapd in there
[08:41] <mborzecki> Chipaca: the whole yearly allowance here is 26 days, but people usually take at least one 2 weeks block during summer (probablyl because that's also a minimum required by law when you're on permanent contract)
[08:41] <Chipaca> https://play.jsgo.io/375878919304e8143970831774c69ee44f2b204a
[08:42] <Chipaca> ^ that's snapd running in the browser :)
[08:42] <Chipaca> allow me to find the biggest quotes in the uiverse to put around the 'running' word, there
[08:42] <mborzecki> next step, snapd in wasm
[08:43] <mvo> Chipaca: woah, fun
[08:43] <Chipaca> mborzecki: snapd for android watches
[08:43] <mborzecki> on android wear
[08:44] <Chipaca> yus
[08:46] <Chipaca> pedronis: are you around?
[08:50] <pedronis> Chipaca: yes
[08:50] <Chipaca> pedronis: hiya :-)
[08:51] <mborzecki> pedronis: hi
[08:51] <Chipaca> pedronis: I anwered myself already, but just to make sure: managers should no longer have a KnownTaskKinds, and their Ensure/Wait/Stop should no longer call the same thing on the runner, right? (and they shouldn't really be holding on to the runner anyway)
[08:52] <pedronis> Chipaca: yes, no local runner, they should take one in
[08:52] <pedronis> just look at any one
[08:52] <pedronis> Chipaca: also I might do a follow up today that makes Wait/Stop on them optional
[08:52] <Chipaca> yes, I was confused by what's probably a bad merge, but looked at master for a clear picture
[08:53] <Chipaca> pedronis: thanks
[09:51] <mvo> sil2100: mup is currently not working, so I play mup :) https://github.com/snapcore/core18/pull/47 is new and pretty trivial
[09:51] <mup> PR core18#47: hooks: preserve /usr/local/share/fonts <Created by mvo5> <https://github.com/snapcore/core18/pull/47>
[11:04]  * Chipaca wanders off to ponder lunch
[11:14] <pedronis> mvo: Chipaca:    some recent change is making the tests print out squashfs output:   Parallel unsquashfs: Using 4 processors ...
[11:14] <pedronis> that's a bit annoying
[11:15] <pedronis> mvo: Chipaca: try for example the  overlord tetss
[11:15] <pedronis> tests
[11:22] <mvo> pedronis: oh, interessting. I saw this as well but thought it was because I had a locally modified version of squashfs
[11:28] <pedronis> Chipaca: is that an affect of passing -no-progress ?
[12:02] <Chipaca> hmmmm
[12:02] <Chipaca> pedronis: mvo: I'll take a look
[12:03] <Chipaca> it might be we're setting os.Stdout where  before we weren't?
[12:03] <Chipaca> I thought I'd undone those for-testing changes but maybe I missed something
[12:03] <Chipaca> +	cmd.Stdout = os.Stderr
[12:03] <Chipaca> darn
[12:04] <Chipaca> mvo: pedronis: my bad: https://github.com/snapcore/snapd/pull/5494/files#diff-f440ed51e6e7c93f4920731345213192R147
[12:04] <mup> PR #5494: snap/squashfs, tests: pass -n[o-progress] to {mk,un}squashfs <Created by chipaca> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/5494>
[12:09] <mborzecki> Chipaca: some conflicts in #5506
[12:09] <mup> PR #5506: cmd/snap: add a green check mark to verified publishers <Created by chipaca> <https://github.com/snapcore/snapd/pull/5506>
[12:09] <Chipaca> mborzecki: yes. Was hoping to get a second review before deconflicting yet again
[12:10] <Chipaca> mborzecki: HINT HITN NUDGE NUDGE
[12:10] <mborzecki> understood :)
[12:21] <mvo> does "configure: error: C compiler cannot create executables
[12:21] <mvo> See `config.log' for more details" ring any bells? release/2.34 is currently failing with that it seems
[12:22] <mborzecki> mvo: did it come up again?
[12:22] <mvo> mborzecki: yes, in my PR from this morning
[12:30] <mborzecki> mvo: builfing on fedora now
[12:30] <mborzecki> maybe something changes with the deps
[12:31] <mvo> mborzecki: you mean you are trying the build? what is also odd is that master seems to be ok
[12:31] <mborzecki> configure: error: in `/root/rpmbuild/BUILD/snapd-1337.2.34~pre1/cmd':
[12:31] <mborzecki> configure: error: C compiler cannot create executables
[12:31] <mborzecki> heh
[12:32] <mvo> mborzecki: yeah, thats the error I get (my version number is slightly different though)
[12:33] <mborzecki> mvo: running cmd/autogen.sh works though
[12:40] <mborzecki> configure:2740: gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-st
[12:40] <mborzecki> rong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasyn
[12:40] <mborzecki> chronous-unwind-tables -fstack-clash-protection -mcet -fcf-protection  -Wl,-z,relro -z now conftest.c  >&5
[12:40] <mborzecki> annobin: conftest.c: Error: plugin built for compiler version (8.0.1) but run with compiler version (8.1.1)
[12:40] <mborzecki> cc1: error: fail to initialize plugin /usr/lib/gcc/x86_64-redhat-linux/8/plugin/annobin.so
[12:40] <mborzecki> configure:2744: $? = 1
[12:40] <mborzecki> mvo: ^^
[12:42] <mvo> mborzecki: woah, what is annonbin
[12:42] <mborzecki> cachio: can you update fedora 28 image?
[12:43] <mborzecki> mvo: no clue, Son_Goku do you have an idea what that might be?
[12:44] <Son_Goku> is this rawhide?
[12:44] <Son_Goku> also, god damn it annobin
[12:44] <mborzecki> Son_Goku: 28
[12:45]  * Son_Goku growls in anger
[12:45] <Son_Goku> mborzecki, is the f28 image fully up to date?
[12:45] <mborzecki> Son_Goku: i'm afraid not, just pulled in >200MB of updates and retrying the build
[12:45] <Son_Goku> you might be out of sync with gcc + annobin
[12:46] <Son_Goku> mvo, mborzecki: https://fedoraproject.org/wiki/Changes/Annobin
[12:47] <Chipaca> mvo, pedronis: #5547
[12:47] <mup> PR #5547: snap/squashfs: stop printing unsquashfs info to stderr <Created by chipaca> <https://github.com/snapcore/snapd/pull/5547>
[12:47] <Chipaca> heh
[12:47] <Chipaca> pedronis: fastest +1 in the west
[12:47] <Son_Goku> the compiler team has developed a number of plugins to enforce security hardening, expand debuginfo, and include extra information for auditing purposes
[12:47] <Son_Goku> annobin is one of those plugins
[12:48] <mborzecki> Son_Goku: interesting
[12:48] <pedronis> Chipaca: mvo: #5546
[12:48] <mup> PR #5546: many: make Wait/Stop optional on StateManagers <Created by pedronis> <https://github.com/snapcore/snapd/pull/5546>
[12:48] <Chipaca> :-D
[12:48] <mborzecki> mvo: the package builds after dnf upgrade
[12:48] <mvo> pedronis: cool, I check in a bit
[12:48] <mvo> mborzecki: ok, so cachio just needs to update the image?
[12:48] <Son_Goku> annobin has the crappy requirement of being ABI sensitive to gcc
[12:48] <Son_Goku> it has to use the same gcc it was built for
[12:49] <mborzecki> mvo: yes, given what Son_Goku wrote we need to update it each time gcc is updated
[12:49] <cachio> mvo, mborzecki Son_Goku I'll update images today
[12:50] <mvo> cachio: thank you
[12:52] <mborzecki> Son_Goku: hm another intersting thing, annonbin does not seem to depend on gcc
[12:52] <Son_Goku> mborzecki, no, strictly speaking, it's a requirement from redhat-rpm-config
[12:54] <sil2100> mvo: looking! :)
[12:54] <Son_Goku> redhat-rpm-config has the following:
[12:54] <Son_Goku> Requires: (annobin if gcc)
[12:54] <Son_Goku> which is a rich dep that imposes annobin to be installed if gcc is
[12:55] <mborzecki> Son_Goku: but does not seem to enforce any particular version
[13:02] <Son_Goku> mborzecki, yeah, annobin should have a requirement to be run with the gcc it was built from, but it doesn't :/
[13:03] <Son_Goku> hmm, it does
[13:07] <mborzecki> Son_Goku: hm maybe it's implicit when using rich dependency https://paste.fedoraproject.org/paste/2Pdj7r~fbdHIj4jzae6kCA/raw
[13:07]  * zyga waves
[13:08] <Son_Goku> hey zyga
[13:08] <zyga> trying to catch up with my sleep credit
[13:08] <mborzecki> zyga: hey
[13:08] <zyga> anything on fire or can I get back to sleep?
[13:09] <Son_Goku> zyga, you know we only have two weeks until flock, right?
[13:09] <zyga> yes
[13:09] <Son_Goku> I still need to make the presentation and you need to at least make a demo, if not prepare some basic code for plugging base snap building into fedora tools
[13:10] <zyga> I will work on that this week
[13:10] <zyga> next week I'd like to take a week off as that's the last chance for spending any time with my wife without a laptop
[13:11] <Son_Goku> mborzecki, it looks like an error in the annobin packaging means that the version dep is not on annobin itself
[13:11] <Son_Goku> it's on annobin-tests
[13:13]  * zyga returns to slumber
[13:19] <mborzecki> Son_Goku: can you file a bug?
[13:20] <Son_Goku> yep
[13:20] <mborzecki> Son_Goku: thank you
[14:33] <Chipaca> what's up with travis eating logs?
[15:14] <Chipaca> hmm
[15:14]  * Chipaca hmm'ing
[15:16] <Chipaca> master seems broken: if I run the unit tests of cmd/snap, there's a good chance it breaks in the aliases tests
[15:16] <Chipaca> with a connection error
[15:16] <Chipaca> (?!?)
[15:17] <Chipaca> cachio: is this one of the ones you are chasing?
[15:19] <cachio> Chipaca, no
[15:19] <cachio> Chipaca, working with an opensuse repo error
[15:19] <Chipaca> ok
[15:20] <cachio> I see unit tests failing on master now
[15:21] <cachio> Chipaca, https://travis-ci.org/snapcore/snapd/builds/407066445#L2043
[15:22] <cachio> this is the one
[15:22] <cachio> I already updated opensuse image, so it should be gone
[15:26] <mvo> cachio: looking
[15:27] <mvo> cachio: the "E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer" bug has an open PR, one sec
[15:28] <cachio> mvo, I saw this one https://travis-ci.org/snapcore/snapd/builds/407177600#L3637
[15:29] <mvo> cachio: the apt error should be fixed with https://github.com/snapcore/snapd/pull/5548#partial-pull-merging
[15:29] <mup> PR #5548: debian: ensure dependency on fixed apt on 18.04 <Created by mvo5> <https://github.com/snapcore/snapd/pull/5548>
[15:29] <mvo> niemeyer: btw, could you please re-enable mup for our github repos? AIUI github issues are fixed by now
[15:31] <mvo> cachio: hm "... value client.ConnectionError = client.ConnectionError{error:(*url.Error)(0xc820192030)} ("cannot communicate with server: Post http://<IP_ADDRESS>:39530/v2/aliases: read tcp <IP_ADDRESS>:44800-><IP_ADDRESS>:39530: read: connection reset by peer")" is strange, I don't think this has changed in a long time
[15:32] <mvo> cachio: could you please ping me once the f28 images are good again? then I will trigger #5545 again :)
[15:32] <mup> PR #5545:  snapstate: allow setting "refresh.timer=managed" (2.34) <Created by mvo5> <https://github.com/snapcore/snapd/pull/5545>
[15:32] <cachio> mvo, I am gonna update them now
[15:36] <hunterk> mborzecki: Hi there, I was told you may be interested in vulkan+snap testing/examples
[15:37] <mvo> cachio: thank you!
[15:56] <cachio> mvo, fedora 28 is updated
[15:56] <cachio> mvo, running tests now
[15:56] <cachio> I'll check after lunch
[15:56] <cachio> mvo, so far so good
[16:07] <mvo> looks like we need to put the seed.yaml reodering higher on our todo :/ germintae reorder things so our code needs to ensure the right order
[16:12] <cachio> mvo, do you want to check if it is everything ok?
[16:13] <mvo> cachio: yeah, looking
[16:13] <cachio> tx
[16:20]  * Chipaca runs to the shops before they close
[16:20] <Pharaoh_Atem> mborzecki: https://bugzilla.redhat.com/show_bug.cgi?id=1607430
[16:20] <cachio> mvo, tests passed sucessfully on fedora-28
[16:22] <mvo> cachio: nice
[16:22] <mvo> kyrofa: do you know about the current rust snapcraft testsuite failures?
[16:22] <mvo> kyrofa: there is a discussion in #ubuntu-devel right now and whether or not snapd has anything to do with those
[17:26] <pedronis> mvo: ?   for classic or in general? at the moment prepare-image will not even grab bases or default-provider
[17:31] <niemeyer> mvo: Good point, thanks for the reminder
[18:18] <mborzecki> Pharaoh_Atem: thanks, already subscribed to the bug :)
[20:02] <Chipaca> ok, giving up for today
[20:02] <Chipaca> but something is still broken :-(
[20:02] <Chipaca> several somethings actually because the more i try to pin it down the more other things break
[20:03] <Chipaca> grr
[20:03] <Chipaca> anyhow, tomorrow.
[20:07] <shantanoo> hi all, is there a latest clamav snap?
[20:08] <shantanoo> tried building one, but after install got '/snap/clamav/current/usr/local/bin/freshclam: error while loading shared libraries: libclamav.so.7: cannot open shared object file: No such file or directory'