/srv/irclogs.ubuntu.com/2016/07/19/#ubuntu-meeting.txt

xiaohongaiwenohello02:25
=== PerfM_ is now known as PerfM
=== Guest73831 is now known as med_
=== aaron is now known as Guest65680
=== Guest65680 is now known as ahoneybun
coreycbhey all16:00
coreycb#startmeeting ubuntu-server-team16:00
meetingologyMeeting started Tue Jul 19 16:00:20 2016 UTC.  The chair is coreycb. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:00
meetingologyAvailable commands: action commands idea info link nick16:00
=== 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 | ubuntu-server-team Meeting | Current topic:
tewardo/16:00
powersjo/16:00
coreycbJust going to hang tight for a few minutes and let people show up16:00
jgrimmo/16:01
rbasako/16:01
smbo/16:02
nacco/16:02
coreycbalright looks like we have a decent number of folks so let's get started16:02
rharpero/16:02
coreycb#topic Review ACTION points from previous meeting16:02
=== 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 | ubuntu-server-team Meeting | Current topic: Review ACTION points from previous meeting
naccsorry, i'm bad and haven't updated the wiki; i think there was just hte one for jgrimm to review the qemu bug(s)16:03
coreycbnacc, ok jgrimm do you have status on that?16:03
* jgrimm goes looking for the bug16:03
jgrimmcoreycb, ask me again during free discussion, i'll have looked up what the bug is by then16:04
coreycbjgrimm, ok sounds good16:04
coreycb#topic Yakkety Development16:05
=== 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 | ubuntu-server-team Meeting | Current topic: Yakkety Development
coreycb#link https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule16:05
naccjgrimm: https://launchpad.net/bugs/156101916:05
jgrimmthanks nacc16:05
ubottuLaunchpad bug 1561019 in libvirt (Ubuntu) "copied cpu flags don't match host cpu" [Medium,New]16:05
coreycbAlpha 2 is in 9 days16:05
coreycbAnd we're about a month away from Feature Freeze16:05
tewardnginx is probably going to get a merge for Yakkety, it'll include the dynamic modules that Debian adds.  Test packages are being built on my side now, then in a PPA, and a call for testing install/upgrade will go out16:07
coreycbkeep feature freeze in mind  as new features and new packages will need FFEs after that point16:07
tewardassuming I don't get another case of the lazies :)16:07
tewardthat should land for Yakkety then before FeatureFreeze16:07
teward('tis all for me today)16:07
coreycbthanks teward16:07
coreycbanything else for yakkety development?16:08
jgrimmotherwise, generally... merges and bugs have been making good forward progress16:08
coreycbjgrimm, great16:08
coreycb#subtopic Release Bugs16:09
coreycb#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-x-tracking-bug-tasks.html#ubuntu-server16:09
coreycb#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-y-tracking-bug-tasks.html#ubuntu-server16:09
jgrimmcoreycb, i'll jump in here with status on bug 1561019 action item16:09
ubottubug 1561019 in libvirt (Ubuntu) "copied cpu flags don't match host cpu" [Medium,New] https://launchpad.net/bugs/156101916:09
jgrimmhallyn and smb seems to be making progress on that atm.  my action was to find someone to work on it.. so done. :)16:10
coreycbjgrimm, :)16:10
smbyeah... ugly16:11
smbjgrimm, thought that was actually worked around16:11
jgrimmsmb, fair enough16:12
jgrimmsmb, my response was about action item i took last week, to make sure someone took a look at it.16:13
smbjgrimm, guess at some point I'd have to check whether this was actually pused anywhere16:13
jgrimmsmb, ack!16:13
coreycbas for other bugs, based on a quick scan, it looks like all the high importance bugs have someone from the server team who's been working on them or communicating at least16:13
coreycband some triage is needed for others16:14
coreycbdoes anyone have anything else for bugs?16:14
coreycb#topic Server & Cloud Bugs (caribou)16:15
=== 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 | ubuntu-server-team Meeting | Current topic: Server & Cloud Bugs (caribou)
coreycbhey caribou16:15
jgrimmcoreycb, unable to attend today16:15
rbasakcaribou sends his apologies16:15
coreycbapology accepted16:15
coreycb:)16:15
coreycb#topic Weekly Updates & Questions for the QA Team16:15
=== 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 | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the QA Team
jgrimmpowersj, ^^16:16
powersjWorking with IS to get Jenkins updated to latest LTS version due to a known Jenkins defect, cpaelzer and I are meeting re: 390, and pinged IS on getting torkoal (baremetal system) added and up to Jenkins.16:16
powersjTurning focus back to Jenkins CI and integration jobs for cloud-init while waiting on Jenkins fix and slave additions.16:16
coreycbpowersj, thanks for the update.  any questions for powersj?16:17
coreycbalrighty, on we go16:18
coreycb#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)16:18
=== 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 | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
smbNo news, sorry (at least no bad news).16:18
coreycbsmb, ok thanks16:19
coreycbsmb, same story for the other kernel folks?16:19
smblikely16:19
argesyup16:19
coreycbalright thanks guys16:20
coreycb#topic Upcoming Call For Papers16:20
=== 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 | ubuntu-server-team Meeting | Current topic: Upcoming Call For Papers
coreycbjumped the gun. any questions for kernel folks?16:20
rharperwell, not now16:20
rharper=)16:20
coreycblol16:20
jgrimmall good16:20
coreycbany conferences coming up that have a call for papers?16:21
coreycbI know openstack summit deadline was last week16:21
coreycb#topic Ubuntu Server Team Events16:22
=== 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 | ubuntu-server-team Meeting | Current topic: Ubuntu Server Team Events
coreycbany events coming up?16:23
rharperhttp://containersummit.io/city-series/2016/austin16:24
rharpertonight16:24
rharperif you're in Austin16:24
coreycbrharper, nice, and look at that mug shot!16:25
rharperlol16:25
coreycbrharper, what's your talk on?16:25
rharperfire-side chatting about containers and lxd16:25
coreycbrharper, awesome16:26
coreycb#topic Open Discussion16:26
=== 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 | ubuntu-server-team Meeting | Current topic: Open Discussion
coreycbjgrimm, did you want to discuss that libvirt bug?16:27
coreycbor was it qemu bugs16:27
jgrimmcoreycb, we already covered it during release bugs16:28
=== JanC is now known as Guest39320
=== JanC_ is now known as JanC
jgrimmalll good16:28
coreycbjgrimm, ah, that was it.  good so no actions to carry over as far as I can tell.16:28
jgrimmagreed!16:29
coreycbjgrimm, I still owe you a reply on your email about subscriptions to openstack packages16:29
coreycb#topic Announce next meeting date, time and chair16:30
=== 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 | ubuntu-server-team Meeting | Current topic: Announce next meeting date, time and chair
coreycbthe next meeting will be the same time next week16:30
jgrimmcoreycb: james took care of it16:30
coreycbjgrimm, oh, great, thanks jamespage!16:31
coreycbgaughen is up next week to chair16:31
jgrimmcoreycb, indeed.. i owe him (yet another) beer for his kindly assistance. :)16:31
gaughencoreycb, I will be at the sprint16:31
coreycbgaughen, ok16:31
coreycbnext in line is arosales, smoser, rbasak.  any of you not at the sprint next week?16:32
jgrimmsmoser or rbasak should be around16:32
coreycbjgrimm, alright, it'll be one of them16:32
coreycb#topic Assigned merges/bugwork (rbasak)16:32
=== 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 | ubuntu-server-team Meeting | Current topic: Assigned merges/bugwork (rbasak)
rbasako/16:32
coreycbo/16:32
rbasakI've been doing some catching up16:33
rbasakI've mainly been focusing on unblocking existing assignments right now.16:33
rbasakcpaelzer isn't here, but AFAICT he's mainly blocked on me reviewing his ntp and dovecot merges, so I'll get on with those ASAP.16:33
arosalescoreycb: I am at sprint next weeek16:33
rbasak(I sponsored a ton of uploads today, more tomorrow)16:34
arosalesrbasak: or smoser could I trade with you?16:34
rbasakjgrimm and rharper, I think you should be unblocked?16:34
jgrimmrbasak, i am! thank you16:34
coreycbarosales, yep it's going to be one of them. I'll nag them.16:34
rharperrbasak: yes, just need to work the bugs you've assigned16:34
rbasaknacc, your only assignment right now is the bacula thing according to my sheet. I think I'm waiting on you to tell me when you're ready for upload. Is that right?16:34
arosalescoreycb: smoser rbasak thanks :-)16:34
naccrbasak: yep, i think we're pretty close16:34
naccrbasak: i need to verify the yakkety changes are good again (some stuff got sent to debian)16:35
rbasakmagicalChicken: around? I've been catching up on your bugs, I think some probably need unassigning perhaps.16:35
naccrbasak: did you get a chance to look at hte puppet bug?16:35
rbasaknacc: OK, I'll wait for you, thanks.16:35
naccrbasak: LP: #157047216:35
magicalChickenrbasak: Yeah16:35
rbasaknacc: not in detail, sorry I didn't reply to the puppet bug yet. I'm reluctant though. I don't understand why we can't invert the logic using existing functionality.16:35
ubottuLaunchpad bug 1570472 in puppet (Ubuntu) "Set systemd as default service provider" [Medium,In progress] https://launchpad.net/bugs/157047216:35
rbasakmagicalChicken: where are we with bug 1394403 right now please?16:36
ubottubug 1394403 in apache2 (Ubuntu Trusty) "RewriteRule of "^$" is broken" [Medium,Incomplete] https://launchpad.net/bugs/139440316:36
naccrbasak: oh we could; but upstream has already taken that change; it won't affect the SRU -- and upstream may chagne the logic altogether (they're working on adding a new extension that may allow for calling arbitrary conditional functions16:36
magicalChickenrbasak: Still unable to reproduce with the first patch that went in16:36
naccrbasak: but if we change first, then we're diverging from upstream's change, which seems less than ideal16:37
naccrbasak: i agree with you for 16.1016:37
naccrbasak: i disagree with you for 16.04 :)16:37
naccrbasak: if that makes sense :)16:37
magicalChickenrbasak: I did LP: #1534538, but I need to redo it because a security update went into repos first16:37
ubottuLaunchpad bug 1534538 in apache2 (Ubuntu Trusty) " AliasMatch directive does not accept long URI" [Medium,Triaged] https://launchpad.net/bugs/153453816:37
rbasaknacc: right, but we need to fix 16.10 first for the SRU. And I don't want to upload a change I know will be broken in three months.16:37
naccrbasak: ok, i'll work on upstream then16:38
rbasaknacc: I'd be happy for us to fix Yakkety with a temporary delta that we know is right, even if that isn't upstream.16:38
rbasaknacc: unless that's particularly awkward? Then that would unblock the SRU.16:38
naccrbasak: right, i was thinking the opposite direction, but the same result16:38
rbasaknacc: otherwise we're defeating the object of fixing development rist.16:38
rbasakfirst16:38
naccrbasak: in that, yakkety gets the current fix, and then i fix upstream and yakkety16:39
naccrbasak: fix the fix, i guess16:39
naccrbasak: either way, one delays the sru more :)16:39
naccrbasak: and takes more of my time :-P16:39
rbasakI'm not sure I follow.16:39
naccrbasak: i have to learn ruby :)16:39
rbasakWhat I'm asking for is to fix Yakkety and then to fix Xenial. The Xenial fix can be minimal.16:39
naccwell, enough ruby :)16:39
rbasakI'm sayingi that the Yakkety fix must not be known broken, but it can be a delta.16:40
rbasakIs that OK?16:40
rbasakIf upstream are planning a big picture fix, then the Yakkety delta can also be minimal I think.16:41
rbasakAs long as it's not autombroken.16:41
naccrbasak: well, given that i'm the one who will probably have to fix upstream; that's what i was trying to say. I will work on fixing upstream and yakkety. But the fix we have now, which is minimal, works for both, right now. The future fix will just be future-proof (which doesn't matter for the current releases). But I will just work on it instead of yammering furhter16:42
rbasakmagicalChicken: for 4403, it's not clear to me that you can't reproduce from reading the bug.16:42
rbasakmagicalChicken: am I missing something, or else could you please update the bug?16:42
magicalChickenrbasak: Sure, I'll redo the verification and post logs16:42
magicalChickenI had been able to reproduce before the first patch I submitted, but after that patch the duplicate rewrite message isn't present in apache's log16:43
rbasakmagicalChicken: sorry, I don't follow. What do we need to do to resolve the bug?16:43
rbasakAre we stuck because unreproducible?16:44
magicalChickenrbasak: Yes. I had submitted a patch earlier that fixed it for me, but the user said that it did not fix it for them16:44
rbasakmagicalChicken: but the user has since provided a reproducer, right?16:44
magicalChickenrbasak: I posted logs of me running the test case they provided with the patch in place, and the bug doesn't show up in them16:45
magicalChickenrbasak: I haven't heard from the user since then16:45
rbasakSorry, I know I'm confused here.16:45
rbasakAh, OK.16:45
rbasakI think I follow. I didn't read your comment as there being a problem.16:45
magicalChickenrbasak: Right yeah, I need to rewrite that to clarify16:45
rbasakOK, thanks.16:45
magicalChickenI'll go ahead and try to reproduce 1 more time too16:45
rbasakI saw the security team trump your progress in 538.16:46
rbasakCan I leave that to you to redo, please?16:46
magicalChickenrbasak: Sure, it shouldn't take long, it was a simple patch16:46
rbasakOK, thanks!16:47
rbasakmagicalChicken: next, in bug 1511222, it looks like the reporter hasn't replied.16:47
ubottubug 1511222 in apache2 (Ubuntu Trusty) "Incorrect trusted proxy match test in mod_remoteip" [Medium,Triaged] https://launchpad.net/bugs/151122216:47
rbasakmagicalChicken: would you prefer to drive it anyway and SRU verify yourself, or drop it?16:47
rbasakIt looks like only one person has reported affected since October.16:48
rbasakSo I don't mind which you prefer - depends on your confidence in the fix and your view on the impact of the bug on other users.16:48
magicalChickenrbasak: I had tested out the patch and it worked okay for me. I can go ahead and rerun that test and post the logs. I don't think the user is going to reply16:48
rbasakmagicalChicken: OK, so would you like to continue with landing the fix, or forget about it until someone replies?16:48
magicalChickenrbasak: It might be good to wait for someone to reply, since I may have been wrong about a patch working on the RewriteRule bug earlier16:49
magicalChickenrbasak: If anyone else reports they're affected, I can ask them to test out the patched version and see if it fixes it for them16:50
rbasakOK, that's fine. Please could you note this in a comment on the bug, and then I'll treat it as unassigned? If you could stay subscribed in case the user does reply, that would be helpful.16:50
magicalChickenSure, thanks16:50
magicalChickenYeah, I'll pick it up again if anyone replies to it16:50
rbasakmagicalChicken: OK great! Next, bug 1296835 needs SRU verification. Are you planning on doing that, or is the bug stalled because you're waiting on a reporter to do it?16:51
ubottubug 1296835 in pptpd (Ubuntu Trusty) "status_of_proc lacks a "-p" in /etc/init.d/pptpd" [Medium,Fix committed] https://launchpad.net/bugs/129683516:51
magicalChickenrbasak: I can go ahead and do the verifiction for that16:52
rbasakOK great. Thanks!16:52
magicalChickenrbasak: Thanks16:52
rbasakAlmost there :)16:53
magicalChickenhaha16:53
rbasakJust one more - any progress on the logwatch bugs please?16:53
rbasakI realise this is quite a few bugs you have on at once, so no worries if not. Just trying to update my spreadsheet :)16:53
magicalChickenI hadn't been aware of a logwatch bug16:54
magicalChickenI can handle that this week, it just had slipped my mind, sorry16:54
rbasakNo worries. It's a whole collection of bugs - various messages. Looks like mostly regexp updates needed, each small individually.16:55
magicalChickenrbasak: Cool, shouldn't be too hard to get fixed then16:55
rbasakhttps://bugs.launchpad.net/ubuntu/+source/logwatch is the list - I mean the "unmatched" and "not being reported" type bugs.16:55
rbasakGreat. Thank you!16:55
magicalChickenThanks16:55
rbasakmagicalChicken: and thank you for your patience. I'm focusing on getting rid of the bugs from my spreadsheet - it's fine if they aren't making progress because of reporter silence - as long as we communicate what they need to do, I'm happy to drop them from my tracking. As long as I can forget about them :)16:56
magicalChickenrbasak: No problem, I'll stay subscribed to the ones we're waiting on so that I can pick them up again when the reporter replies16:57
rbasakI'm done for today, thanks all. I think everyone has something to get on with, possibly with the exception of cpaelzer until I unblock him.16:57
rbasakI intend to triage more this week and get a backlog of assignments again.16:57
rbasakAny other comments or questions?16:57
naccrbasak: feel free to put more on my plate again, i'm mostly caught up now that you've sponsored stuff16:58
rbasaknacc: thanks. And thank you for all the uploads! I need to do that endorsement :)16:58
rbasakcoreycb: #endmeeting please16:58
coreycb#endmeeting16:58
=== 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 Tue Jul 19 16:58:42 2016 UTC.16:58
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-07-19-16.00.moin.txt16:58
coreycbthanks all16:58
naccrbasak: i'm trying to figure out the ftbfs you found; as it works on amd64; and it's not clear why my chnage owuld have broken anything16:58
rbasaknacc: looking at the build failure, I suspect it's a latent bug in debian/rules trigerred by building using a Yakkety dpkg-buildpackage or something.16:59
naccrbasak: yep, that sems likely, i'm digging into it16:59
naccthanks!16:59
rbasaknacc: IIRC, it said something about build-arch not existing? Debian policy probably requires that.16:59
rbasaknacc: sorry I didn't dig further - I was trying to get through as much of the sponsorship queue as possible.17:00
naccrbasak: eyp, i think so -- and np, of course!17:00

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