18:58:58 #startmeeting 18:58:58 Meeting started Wed Apr 27 18:58:58 2016 UTC. The chair is jmw. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:58:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:59:01 guten abend 18:59:19 #chair nthykier 18:59:19 Current chairs: jmw nthykier 19:00:07 o/ 19:00:37 my dinner's just finished cooking, so I'm around but need to grab and eat that 19:00:52 adsb: ok, we'll highlight if there's anything for you 19:00:59 did pochu make it back? 19:02:11 hum, might be just us then 19:02:48 fun 19:04:23 So, I can say I hope to have Britney fixed 19:04:38 explodey cron! 19:05:37 nthykier: shall we crack on with some admin stuff and see if anyone else shows up? 19:05:48 sure 19:05:56 #topic Admin/Previous minutes/Apologies 19:06:24 previous minutes are http://meetbot.debian.net/debian-release/2016/debian-release.2016-03-23-18.58.html and don't appear to have been controversial 19:06:50 #info Previous minutes: http://meetbot.debian.net/debian-release/2016/debian-release.2016-03-23-18.58.html 19:07:09 of the usual suspects, jcristau isn't expected here tonight, pochu is MIA and adsb is eating 19:07:43 #topic Mysql variants in Stretch 19:08:14 so the only update here is that pkg-mysql-maint are on the case and have some details to iron out internally, but are working on a plan 19:08:27 did anything go to -devel yet? I don't read it 19:08:42 Don't remember seeing it any thing either on d-d 19:08:57 #info Latest developments: http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2016-April/008918.html 19:09:00 ok 19:09:30 we are just playing the waiting game for now then, and maybe in a couple of weeks I will poke the list if nothing has happened 19:09:41 #info jmw monitor mysql developments 19:09:48 moving on? 19:10:17 pochu had an action item related to this 19:10:24 do we know of the status of that? 19:10:27 . 19:10:46 yes, pochu mailed pkg-mysql-maint to get them started on planning the transition 19:11:05 the mail I linked is the response 19:11:27 cool - wasn't sure if it was done with that or not 19:11:32 yup 19:11:47 I think deciding what to do with libmysqlclient.so.18 is the blocker from the pov 19:12:08 ok 19:12:15 (also ok to moving on) 19:12:24 #topic Sprint at Suncamp 19:12:49 so, some releasers will join DSA and FTP masters at suncamp in a few weeks time 19:12:56 though I cannot for the life of me find the wiki page now 19:13:11 And we got a sprint sponsored by the DPL 19:13:14 erh, ex-DPL 19:14:00 ah yes, on his outgoing spending spree 19:14:13 o/ 19:14:14 so that looks healthy and on going (the sprint that is) 19:14:16 wonder how well wiki.d.o's search works 19:14:22 hey pochu 19:14:40 ah here it is 19:14:53 #info Some members of the release team will join DSA and FTP at Suncamp 19:14:59 #link https://wiki.debian.org/DebianEvents/Europe/2016/DSC?action=show&redirect=SunCamp 19:15:11 #info Sprint focus: split of release tools from ftp-master.debian.org 19:15:24 I don't think there's much else to say 19:15:32 nope 19:15:37 #topic Transitions check 19:15:54 as usual, pochu is charging away at transitions and I don't think there's anything controversial in progress 19:16:13 png happned? 19:16:21 finally 19:16:23 oh it did, yes 19:16:26 6 years on 19:16:39 pochu: is everything healthy? 19:16:46 #info libpng transition is complete 19:16:55 and there was much rejoicing 19:17:13 (and removal enthusiasm...) 19:18:04 do we have any news on the "jasper" removal? 19:18:24 I haven't seen any 19:18:42 but https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=jasper-rm;users=jmm@debian.org has many bugs 19:19:02 including several key packages 19:19:26 I wonder if jmm_ is around 19:20:39 There is also guile-1.8-rm, which survived Jessie 19:20:42 sorry 19:20:49 because lilypond? 19:20:52 yes, things are good :) 19:20:52 (lilypond being the only rdep still) 19:21:03 yes lilypond is blocking guile-1.8's removal 19:21:27 right, that is not new - though I was hoping we might finish it for Stretch 19:21:28 upstream is slowly working on that. I suggested an upload to experimental so it could be tested but nothing happened 19:21:33 from memory don was going to fix it, one day, honest 19:22:04 and none of us could bring ourselves to remove it, yes 19:22:09 yeah. I wasn't sure whether to get it out of stretch now to put some pressure, or if we would not mind releasing Stretch with it for lilypond's shake 19:22:33 if we won't release it with it no matter what, then we should remove it from stretch *now* 19:23:27 removing it from stretch isn't a death sentence either of course, it'll still be in unstable and could re-enter 19:23:36 I'm tempted, I must say 19:23:43 lilypond or guile-1.8? 19:23:56 lilypond, once it doesn't use guile-1.8 19:24:00 lilypond surely could... right 19:25:28 I am also okay with setting a deadline for the guile-1.8 removal 19:25:32 (from testin) 19:25:35 testing* 19:25:50 lilypond is the only thing left depending on guile-1.8, right? (I don't have my keys on me to check franck) 19:26:04 in testing, yes 19:26:13 (according to ben) 19:26:14 yes, see https://release.debian.org/transitions/html/guile-1.8-rm.html 19:26:53 maybe an RC bug against lilypond saying that guile-1.8 will be removed is the way to go. interested people will get a reasonable amount of notice, and britney will just do it when the time comes 19:27:12 sgtm 19:27:21 anyone want an action? :) 19:27:34 I can do that 19:27:43 #agree guile-1.8 should be removed from testing before Stretch 19:27:47 pochu: thanks 19:28:00 #info lilypond is the last remaining package dependent on guile-1.8 19:28:17 mmm 19:28:23 #action pochu file RC bug against lilypond to start an auto-removal timer 19:28:24 nack 19:28:30 oh? 19:28:33 lilypond has rdeps 19:28:37 oh yay 19:28:38 #undo 19:28:38 Removing item from minutes: 19:28:41 # Broken Depends: 19:28:41 songwrite: songwrite 19:28:43 #undo 19:28:43 Removing item from minutes: 19:28:44 # Broken Build-Depends: 19:28:45 denemo: lilypond 19:28:53 thought I would mention it before we continued 19:29:01 (not sure they are blockers) 19:30:24 songwrite has a popcon of 85 19:30:25 ok, got a happy dak with: dak rm -nR -s testing guile-1.8 lilypond songwrite denemo 19:30:38 denemo has ~500 19:30:46 lilypond ~2500 19:30:57 I'm still ok (just wanted to check the rdep list ) 19:31:23 FTR, there is #746005 (re: RC bug against lilypond) 19:31:29 (currently not RC) 19:31:42 yes, that was RC and got downgraded 19:31:54 so we'd just have to bump it :) 19:32:00 maybe we should file/upgrade anyway, and at least get some discussion going 19:32:11 yes 19:32:14 ok with me 19:33:02 #info lilypond is the last remaining package dependent on guile-1.8 but has reverse dependencies of its own (low-ish popcon) 19:33:30 #action pochu upgrade #746005 against lilypond to get the ball rolling on removal, or at least a discussion 19:33:35 how's that? 19:33:38 ack 19:33:45 yep 19:33:54 how about jasper? 19:34:10 an action to me on nagging the sec team for a status? 19:34:48 if you like 19:34:58 #info removal of jasper has been proposed but we could do with an update 19:35:19 oh btw there's an uncoordinated Ada transition going on atm 19:35:21 #action nthykier follow up jasper with security team for a status update 19:35:24 oh happy fun 19:35:46 I love how well coordinated those are 19:35:49 #info An uncoordinated Ada transition has started 19:35:58 last one took several months to complete 19:36:13 fortunately it's rather self-contained 19:36:14 not me ... 19:36:25 pochu: is that the libgtkada tracker? 19:36:32 jmw: that's a part of it yes 19:36:41 doko: yeah gnat got uploaded with a new default 19:36:42 and libxmlada? 19:36:54 jmw: also libtemplates-parser, libgnatcoll 19:36:59 yikes 19:37:08 but that's just a part of it 19:37:26 https://lists.debian.org/debian-ada/2016/04/msg00003.html 19:37:31 is this worth a gentle reminder about larger transitions to somewhere like d-d-a? (because everybody reads that, I hear) 19:39:04 jmw: we could do it. whether that helps... 19:39:09 quite 19:39:25 or maybe just to the ada list 19:39:27 though I'm pretty happy how people are handling transitions, for the most part 19:39:42 yes, I think it's been working well on the whole 19:40:17 (and I don't mind small transitions being uncoordinated) 19:40:58 from memory ada transitions tend to be icky but self-contained 19:41:08 maybe we should just wait and see then 19:41:30 mehh GCC 6.1 release day, and GCC trunk already ftbfs on mips and mips64el ... 19:41:37 icbw though, been a while since I've poked 19:41:46 #info Other transitions are healthy, and permitting self-contained transitions to be started autonomously has been working well 19:41:49 yeah last time the biggest annoyance was to have several trackers in ben for months IIRC 19:42:16 any others to note? 19:42:38 I suppose we'll have a ghc transition soon 19:42:50 and that will allow us to remove llvm-toolchain-3.5 19:43:12 there will be a mini perl transition (minor version bump) 19:43:13 gcc-6 introduces new symbols in runtime libs, and will block packages until it migrates 19:43:19 that's probably all I have to highlight :) 19:43:38 doko: ok 19:44:02 #info Forthcoming; gcc-6 introduces new symbols in runtime libs, and will block packages until it migrates 19:44:35 right, moving on: any other business? wave for a slot 19:44:36 * jmw waves 19:44:59 ok probably just me then 19:45:04 #topic Wheezy EoL 19:45:12 adsb: ^ could you use any help co-ordinating that? 19:46:06 #info Some binaries are still missing from security uploads 19:46:09 potentially. we need to work out what we're doing with the packages that are left in opu-new 19:46:26 carnil's done sterling work recently catching us up 19:47:02 other than typo-3, we're basically in sync. openjdk-6/mipsel has version sad because experimental 19:47:41 oh the missing builds are also missing on security-master? 19:47:48 jmw: which ones? 19:48:02 I'm looking at oldstable.html 19:48:16 https://release.debian.org/oldstable/missing-security.html is the difference between security and ftp-master. icewasel is a FP because it was released since dinstall 19:48:31 so if it's not on that list, then yes it's also missing on security-master 19:48:34 aha 19:48:41 that's a much better list 19:48:54 would negotiating a target date be helpful at this point? 19:48:57 it is now, yes 19:49:04 #undo 19:49:04 Removing item from minutes: 19:49:05 looking at them would be helpful 19:49:19 #info Nearly all missing builds have been caught up from security uploads 19:49:24 #info Target date needed 19:49:36 #action jmw start negotiating Wheezy EoL target date 19:49:56 I suspect we also still end up with packages where opu > stable, however. and possibly opu > pu, because of differing build failures for openjdk-7 at least 19:49:59 it's all horrid 19:50:16 we could fudge version bumps in stable if it really came to it 19:50:33 dpkg and highlight are pending, are they just to be processed as normal? 19:51:25 oh dpkg had an opu bug I think I saw 19:51:46 I believe dpkg already got uploaded? 19:51:46 they both do 19:51:53 okiedoke 19:52:04 nthykier: uploaded, yes. that's why jmw's asking about it :P 19:52:09 ah 19:52:18 it just stood out on the page 19:52:30 long live wheezy 19:52:33 right, aob? 19:53:26 going.... 19:53:29 ... gone 19:53:32 #topic Next meeting 19:53:44 according to my calendar the next meeting is 25th May 19:53:51 ack 19:53:53 is 1900UTC a better time? 19:54:00 ok with me 19:54:07 (don't care either way) 19:54:20 object now or forever hold... 19:54:29 that will be the start of SunCamp 19:54:30 1800UTC is a stretch for me in BST 19:54:41 oh hm, suncamp 19:54:48 they have summer in UK? :P 19:54:49 hmm, no it's not. nvm 19:54:56 oh, nthykier made a funny 19:54:57 we could delay a few days and get a suncamp report 19:55:21 nthykier: you hush. it's been snowing for three days. 19:55:27 same here actually 19:55:31 its crazy 19:55:32 "april" 19:55:33 lol 19:55:36 so warm in here :P 19:56:05 Skipping the IRC meeting in favor of SunCamp seems fine 19:56:31 how about the week after, 1st June? though that might not work for adsb 19:57:04 might it not? did I forget something? 19:57:15 my calendar claims you have a significant date 19:57:29 hehe 19:58:01 * nthykier .oO( info: jmw knows adsb calender better than adsb! ) 19:58:01 yes. but that won't impact my availability 19:58:06 ok 19:58:10 I move 1st June then 19:58:28 no, adsb knows, it just wasn't relevant. but jmw apparently wasn't sure :) 19:58:33 moved to 1st of June 19:58:43 nthykier: more like jmw knows half the facts only, and therefore makes caution 19:58:45 cool 19:59:00 #info Next meeting: 1st June 2016 1900UTC (time change from normal) 19:59:07 #endmeeting