/srv/irclogs.ubuntu.com/2017/02/23/#ubuntu-meeting.txt

=== JanC is now known as Guest31516
=== JanC_ is now known as JanC
=== maclin1 is now known as maclin
=== gaughen_ is now known as gaughen
sil2100o/16:00
* slangasek waves16:00
robru\o16:01
slangasek#startmeeting16:02
meetingologyMeeting started Thu Feb 23 16:02:17 2017 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:02
meetingologyAvailable commands: action commands idea info link nick16:02
slangasek[TOPIC] Lightning round16:02
=== meetingology changed the topic of #ubuntu-meeting to: Lightning round
slangasek$ echo $(shuf -e barry doko bdmurray slangasek caribou infinity sil2100 robru cyphermox tdaitx xnox chiluk mwhudson)16:02
slangasekchiluk sil2100 cyphermox infinity tdaitx doko barry mwhudson xnox slangasek bdmurray caribou robru16:02
robruwooohooo!16:03
slangasekchiluk: hi, anything for this week?16:03
chiluklp 1647389 .. is all ..  It's being a real bear to track down16:04
ubottuLaunchpad bug 1647389 in qemu (Ubuntu) "Regression: Live migrations can still crash after CVE-2016-5403 fix" [High,Confirmed] https://launchpad.net/bugs/164738916:04
chiluk-done-16:04
sil2100- Landing team work, silo coordination16:04
sil2100- SRU reviews16:04
sil2100- Reviewing the xenial linux-hwe kernel SRU (urgent)16:04
sil2100- Writing up a script to inform me of any kernel SRU actions required16:04
sil2100- Further examination of failing xenial-i386 builds for touch16:04
sil2100  * Resolved with latest qtmir landing16:04
sil2100- walinuxagent:16:04
sil2100  * Discussion with upstream about the configuration split concept16:04
sil2100  * Waiting on: final upstream decision and test results16:04
sil2100- ubuntu-image:16:04
sil2100  * Removing any hard-coded sector-size values16:04
sil2100  * Looking into ubuntu-image CI - e.g. how it's done16:05
sil2100(done)16:05
slangasekcyphermox:16:06
sil2100cyphermox sent an e-mail he might be late16:08
cyphermoxSorry, around but on my cell, can't really past summary16:08
slangasekok16:08
slangasekno infinity16:08
slangasektdaitx:16:08
sil2100...or that :)16:08
tdaitx* 1 day off (or, more precisely, 2 half-days if anyone cares)16:08
tdaitx= OpenJDK16:08
tdaitx  * Going through their contribution policy now that we have OCA (thanks steve!)16:08
tdaitx  * Reviewing patches that we can (re)submit16:08
tdaitx= Other16:08
tdaitx  * Checking and learning about debhelper 9 tools (and changes since 5)16:08
tdaitx  * Going through a few OpenJDK (7 and 8) LP bugs (LP: #1573673, Debian: #855686, Debian: #853758, LP: #1548434, Debian: #855858, ...)16:08
tdaitx  * Merging open-vm-tools (LP: #1651608)16:08
ubottuLaunchpad bug 1573673 in openjdk-8 (Ubuntu) "package openjdk-8-jre-headless:amd64 8u77-b03-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2" [High,Incomplete] https://launchpad.net/bugs/157367316:08
tdaitx= OpenJDK 7 (low priority, thus taking longer than usual)16:08
ubottuDebian bug 855686 in src:icedtea-web "icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met" [Serious,Open] http://bugs.debian.org/85568616:08
ubottuDebian bug 853758 in openjdk-8 "openjdk-8: Please cherry-pick 8dfbb002197a / fix for JDK-8164293 [memory leak in hotspot]" [Serious,Fixed] http://bugs.debian.org/85375816:08
ubottuLaunchpad bug 1548434 in openjdk-8 (Ubuntu) "jmap -heap broken since update to 7u95-2.6.4-0ubuntu0.14.04.1" [Undecided,Confirmed] https://launchpad.net/bugs/154843416:08
tdaitx  * Testing new package changes on OpenJDK 7u131, simplifying build16:08
ubottuDebian bug 855858 in openjdk-8-jre "[openjdk-8-jre] jexec'ing .jar-files through binfmt doesn't work" [Normal,Open] http://bugs.debian.org/85585816:08
ubottuLaunchpad bug 1651608 in open-vm-tools (Ubuntu) "please rebase open-vm-tools to version 10.1.0" [Undecided,New] https://launchpad.net/bugs/165160816:08
tdaitx  * Testing mauve16:08
tdaitx= AOB16:08
tdaitx  * My beloved router is now a brick unless I manage to write directly to flash, will fetch a replacement today16:08
tdaitx(done)16:08
slangaseksil2100: removing hard-coded sector-size values> how is that going to work? is this for planning to support 4096 disks?16:09
slangasekdoko:16:09
barryslangasek: LP: #166731316:10
ubottuLaunchpad bug 1667313 in Ubuntu Image "Stop hard-coding sector size to 512" [Low,New] https://launchpad.net/bugs/166731316:10
sil2100slangasek: not as deep like that for now, but will open up to possibilities like that in the future - for now I want to get rid of hard coding and just trust the sector size that parted gives us16:10
doko- was on vacation last Thu and Fri16:10
doko- prepare rust packaging, backports for trusty and xenial16:10
doko- toolchain updates for zesty16:10
doko- new processing, MIRs, ...16:10
doko- GCC 7 updates16:10
doko(done)16:10
sil2100slangasek: since that's what we use for all paritioning right now16:10
sil2100slangasek: but on the bug I did mention we should maybe make sector size configurable16:10
cyphermox+116:11
cyphermoxDefault to a sane value and make it configurable. I'm not sure if it was with parted that we sometimes has weird behavior for 4k drives16:12
sil2100Bug for tracking: LP: #166731316:12
ubottuLaunchpad bug 1667313 in Ubuntu Image "Stop hard-coding sector size to 512" [Low,New] https://launchpad.net/bugs/166731316:12
sil2100Now the question would be: should this be in the gadget.yaml or an explicit option in ubuntu-image? Since to me it's more the former16:13
barrysil2100: fwiw, i commented on the bug with my thoughts16:14
tdaitxbtw, if someone knows stuff that should really *not* be used in debhelper (bad idea, doesn't work/scale well, ...), I'm all ears16:15
sil2100barry: ah, I see now, thanks! :)16:16
barryshort week due to usa holiday16:16
slangasekbarry: your turn16:16
barryubuntu-image: LP: #1665014; LP: #1666173; LP: #1666580; LP: #1631156; 1.0 bug triaging; LP: #166714016:16
ubottuLaunchpad bug 1665014 in ubuntu-image (Ubuntu Yakkety) "SRU 0.15 tracking bug" [High,Fix committed] https://launchpad.net/bugs/166501416:16
barrydebuntu: LP: #1647031 - i re-cherry-picked the network-manager resolved patch, but apparently some people are still having trouble.  should discuss re-reverting for zesty; flufl.bounce 3.0 for python 3; LP: #1647204; gpgme1.0 still blocked (due to beta1 freeze?)16:16
ubottuLaunchpad bug 1666173 in Ubuntu Image "Failed to create an image by using ubuntu-image (0.15+snap3)" [Undecided,Invalid] https://launchpad.net/bugs/166617316:16
ubottuLaunchpad bug 1666580 in Ubuntu Image "sfdisk crash when pc-boot.img is too big" [High,Fix committed] https://launchpad.net/bugs/166658016:16
ubottuLaunchpad bug 1631156 in Ubuntu Image "flake8.extension entry point has global ramifications" [High,Fix committed] https://launchpad.net/bugs/163115616:16
ubottuLaunchpad bug 1667140 in Ubuntu Image "Change d/tests to use -O instead of -o" [Medium,In progress] https://launchpad.net/bugs/166714016:16
ubottuLaunchpad bug 1647031 in systemd "systemd-resolved’s 127.0.0.53 server does not follow CNAME records" [Unknown,New] https://launchpad.net/bugs/164703116:16
ubottuLaunchpad bug 1647204 in gpgme1.0 (Ubuntu) "1.8.0-2 FTBFS in zesty 17.04" [High,Confirmed] https://launchpad.net/bugs/164720416:16
barryother: subiquity testing16:16
barry--done--16:16
slangasekbarry: wrt > 440B mbrs... is that in the gadget.yaml spec?  It had been in one iteration when the docs were in ubuntu-image, I think16:17
slangasekand xnox is away16:18
slangasek * short week due to swap last Friday16:18
slangasek * processing of old Debian removals as of FF16:18
slangasek * worked with infinity to get the ball moving on powerpc removal16:18
slangasek * continued focus on cloud-image builds16:18
slangasek(done)16:18
bdmurrayworked with mvo regarding receiving snap crashes at errors16:18
bdmurraywrote a database query to find snap reports16:18
bdmurrayworked on snapping apport (crash reports being created)16:18
bdmurraydiscovered snappy bugs LP: #1613971, LP: #166575616:18
ubottuLaunchpad bug 1613971 in Snappy "using oneshot results in failed service" [Undecided,New] https://launchpad.net/bugs/161397116:18
ubottuLaunchpad bug 1665756 in Snappy "environment variable setting issue" [Undecided,Fix committed] https://launchpad.net/bugs/166575616:18
bdmurrayupdated bug bot for 16.04.2 ISO checksums and recommends16:18
bdmurrayreview of foundations-bugs16:18
bdmurraysubmitted some MIR bugs16:18
bdmurrayuploaded vlc SRU for LP: #163975016:18
ubottuLaunchpad bug 1639750 in vlc (Ubuntu Xenial) "subtitle downloads hang" [Medium,Fix committed] https://launchpad.net/bugs/163975016:18
bdmurray✔ done16:18
caribouLP: #1638695 - python performance regression in Xenial16:18
ubottuLaunchpad bug 1638695 in python2.7 (Ubuntu) "Python 2.7.12 performance regression" [High,Confirmed] https://launchpad.net/bugs/163869516:18
caribouworking with doko on this one16:19
caribou  VPN reconfiguration16:19
caribou  Sosreport 3.3 trusty SRU16:19
caribou  Sponsor ceph and sssd SRU16:19
caribou(done)16:19
slangasekrobru:16:19
robru* britney email notifications almost complete (thanks to Laney for some gpg example code)16:19
robru* some archive maintenance mentoring from cyphermox16:19
robru(done)16:19
slangasekemail notifications> nice!16:20
sil2100\o/16:20
slangasekany questions over status?16:20
bdmurrayrobru: what does almost complete mean in terms of rollout? what will we see?16:20
barryslangasek: the bug someone saw had a proper size in the gadget.yaml but accidently produced a .img contents that was 512 bytes, so it blew up on them.  while investigating i saw an XXX comment about how we should actually check that the contents of an 'image:' specified partition should actually check that it fits in the partition size. ;)  that's the bug i'm fixing (i.e. not specifically mbr related, just any partition with contents >16:20
barrygadget.yaml specified size)16:20
robrubdmurray: the code is basically complete. all I need is to write some unit tests, and maybe iterate on the wording of the emails that get sent out (they're pretty terse at the moment). I expect to submit for code review tomorrow then roll out monday or tuesday once somebody approves it16:21
gaughenslangasek, are we done with status?16:21
gaughenthat's my question about status16:21
slangasekbarry: ok.  does the documentation also state that mbr is enforced to 440B?16:22
slangasek(if you don't know offhand, that's fine)16:22
barryslangasek: 446B to be exact16:22
barryslangasek: and yes, we enforce that in the parser16:22
slangasekyeah, mine was a question of the documentation16:23
slangasekanyway16:23
barryslangasek: yep, it's documented here: https://github.com/snapcore/snapd/wiki/Gadget-snap#gadget.yaml16:23
slangasekok, great16:23
slangasek[TOPIC] AOB16:23
=== meetingology changed the topic of #ubuntu-meeting to: AOB
slangasekgaughen: your turn :)16:23
gaughenso my status less status and more questions16:24
gaughensubquity - please give feedback16:25
cyphermoxAh yes, thanks for mentioning16:26
barryslangasek: we may have to roll back that network-manager change again :(16:26
barryslangasek: and can you check if gpgme1.0 -proposed block is explicit or tied to beta 1 freeze?16:26
cyphermoxBarry provided some good feedback, some of it is due to the run being a dry run16:27
cyphermoxAnd to exit subiquity : ctrl-x16:27
gaughenthanks barry!16:27
barrycyphermox: on the nm cherry pick?16:27
cyphermoxNo, for subiquity16:27
barrycyphermox: ah16:27
cyphermoxWhy revert nm again?16:28
slangasekbarry: because of the DNSSEC thing?16:28
gaughenand my other question is how do we look regarding 17.0416:28
barryslangasek: yep16:28
gaughenfeature freeze was last week16:28
barryslangasek: it works fine for me, but there have been reports of problems16:28
slangasekbarry: you can check this directly in lp:~ubuntu-release/britney/hints-ubuntu/ for the rationale, and if it says 'block request by freeze' that always means freeze16:29
barryslangasek: ack16:30
slangasekbarry: I'd really not like to roll it back yet again; maybe this is something cyphermox can look at16:30
slangasekto see if we can sort out the DNSSEC problem on the systemd-resolved side sooner?16:30
barryslangasek, cyphermox +1 - let's talk after the meeting.  i haven't had time yet to investigate, but i'm fairly confident the cherry pick went okay ;)16:31
slangasekyes, it's clear to me this is unrelated to the first issue we were backing out for16:31
* sil2100 needs to go and play with the cat16:31
sil2100It demands attention badly16:31
sil2100o/16:31
slangasekbut gaughen asked a question16:31
slangasekhow do we look regarding 17.0416:32
slangasekgaughen maybe wants to expand on this :)16:32
bdmurraywe look smashing16:32
barrytremendous16:32
barrybest release ever, believe me16:33
slangaseknobody has better binaries than us16:33
bdmurraywe've made it great again16:33
slangaseketc16:33
barryobquote: yooge16:33
slangasekdid we get where we needed to be on merges of new upstream versions from Debian before FF?16:34
slangasekI know infinity is still working on glibc16:34
* barry feels pretty good about the packages he's watching16:34
gaughenslangasek, any major items that still need to be done? I know about glibc16:35
slangasekgaughen: there's your answer, everybody feels good16:35
gaughenand slangasek you've been doing package removals, do you need help?16:35
gaughenis there any other sorts of things like that which needs to be done now16:36
bdmurrayI'd like to help removing packages16:36
dokodpkg merge?16:36
slangasekI'm done with the removals that I think were reasonable for this cycle16:36
gaughenslangasek, everbody = barry?16:36
dokoand decisions about pie on arm64?16:36
slangasekand we talked about wanting a report view of process-removals output (bdmurray?)16:36
dokoalthough again a bit late for this cycle16:36
slangasekdoko: infinity mentioned dpkg merge in his email; I'm not sure there's any justification for doing that as an FFe though16:37
dokoprobably not16:37
bdmurrayslangasek: is there a time to have it done by for it to be useful this cycle?16:37
slangasekpie on arm64> I still have the action to follow up with andrewc, we should get an answer on the overall strategy but I think we can safely assume it's not critical for 17.0416:38
bdmurrayit'd be helpful if xnox looked at bug 165162316:39
slangasekbdmurray: I think it provides some utility at any point ... scanning the list for "stale and ancient things without revdeps that could be removed" can be done whenever someone has a free moment16:39
ubottubug 1651623 in apport (Ubuntu Yakkety) "adt tests fail on zesty for apport" [Undecided,New] https://launchpad.net/bugs/165162316:39
bdmurraythe upstream maintainer of unattended-upgrades hasn't merged a couple of my patches, I guess I should just stick them in zesty now?16:40
barryslangasek: looks like gpgme1.0 is listed in the freeze file.  is there any record of the rationale for that?16:40
slangasekbarry: any rationale is listed in comments in that file16:40
barrythe only comment in that file says "# generate-freeze-block ubuntukylin ..."16:41
barrythen "block a11y-..."16:41
slangasekbarry: essentially, though, our freezes are governed by momentum, where we continue to apply the same process we always have even though this is now opt-in and it penalizes flavors that have opted out but are /derived from/ by flavors that opt in (namely, ubuntu-desktop -> ubuntukylin)16:41
slangasekyes, the comment tells you which flavors are frozen for16:41
slangasekfrom there you can look at the Task: field on the binary package to see which flavor is directly responsible, if you care16:42
slangasekbut if it's in the freeze file, it's because it's part of a milestone freee16:42
barryslangasek: cool, that's what i wanted to know.  and that's fine, we can wait until after milestone freeze is lifted (or if prudent, just say it's too late for zesty, or do a ffe)16:43
slangasekbarry: wait for what exactly?16:43
slangasekbarry: anything that's uploaded to zesty-proposed today is already a candidate for inclusion and doesn't need an FFe16:44
barryit was uploaded several days ago16:44
slangasekyes, I'm saying if it's *in* -proposed today, there's nothing you should be filing an FFe about unless you should have filed one before you uploaded it16:44
slangasekbut filing the FFe or not has no effect on whether the package will make it into the release from -proposed16:45
barrycool16:45
slangasekthere is, in any case, a lot of work to be done to work through the set of packages blocked in -proposed16:46
barryyep16:46
slangasek(not gpgme1.0, that will go in as soon as the freeze lifts, which should be today)16:46
slangasekok - anything else today?16:46
barrycool.  yeah, fixing that package's build problems on arm, etc. was, um, fun16:47
slangasekunaligned access? :P16:47
barryentropy exhaustion and compiler flags (two separate problems)16:47
slangasekah :)16:48
slangasek#endmeeting16:49
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Feb 23 16:49:26 2017 UTC.16:49
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-23-16.02.moin.txt16:49
slangasekthanks, everyone!16:49
barrythanks!16:49
xnoxbdmurray, hey, at least mdadm/xenial is now sorted (in -proposed) =)19:39
bdmurraywell that's something!19:39
=== lamont` is now known as lamont

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!