15:03:40 #startmeeting third-party 15:03:41 Meeting started Mon Apr 17 15:03:40 2017 UTC and is due to finish in 60 minutes. The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:44 The meeting name has been set to 'third_party' 15:04:01 o/ 15:04:42 #topic Open Discussion 15:04:57 hi asselin 15:05:24 hi mmedvede 15:06:30 asselin: are you running zuul by any chance? 15:07:06 mmedvede, yes 15:08:22 which version? I am pinning it before 2.5.1 tag, and it stopped working due to voluptious package update last week 15:08:36 we're on a very old version 15:09:02 asselin: ok, then heads up - do not update python packages and restart zuul, you could lose it 15:09:28 :( ok...is upstream affected as well? 15:09:37 I am still investigating, maybe a newer version can be used 15:09:51 asselin: I assume master is patched 15:10:23 so upstream does not appear to be affected 15:11:48 or they haven't restarted in a while.... 15:11:55 there is that https://review.openstack.org/#/c/456270/ 15:12:03 fairly recent 15:12:11 "Handle dict extras in Voluptuous Schema" 15:12:14 yes, Voluptuous made things stricter 15:12:31 so, if you have the latest Voluptuous is will break zuul < 2.5.2 15:12:53 hi pabelanger, what do you think the best course of action? downgrade voluptuous? 15:13:17 downgrading is likely safest fix, but need to see why it was upgraded first 15:13:26 otherwise, you should be able to use 2.5.2 15:14:55 I'll give 2.5.2 a go, thanks pabelanger 15:18:20 any other topics? 15:18:35 I don't have any 15:19:24 one thing to note, you should be able to safely use 2.5.2 if using 2.5.1 now 15:20:14 yes, it appears that zuul 2.5.2 is working well after I upgraded it (at least I see a job in the queue) 15:22:05 so if you pin zuul to an old version and it stops adding jobs after a restart, upgrade to 2.5.2 15:24:01 thanks for attending 15:24:07 #endmeeting