[00:27] <slangasek> nacc: ok; so I can't reproduce your build failure, but I am seeing annoying behavior where if I try to simplify the rules, I'm getting (empty) binary packages spit out for all the stanzas listed in debian/control.  It seems like the -a option is somehow taking precedence over the -p options; I'll futz with this some more to try to figure it out
[00:35] <slangasek> looks like the grep-dctrl might be the simplest solution anyway :/
[00:36] <nacc> slangasek: yeah, i tried to find better ways, but settled on that. I can take it as an action item to try and clean it up further
[13:37] <yofel> so, I'm a bit confused. Why was an autopkgtest run for a superseded version here? http://autopkgtest.ubuntu.com/packages/p/plasma-framework/xenial/s390x/
[13:46] <mitya57> This may be because someone restarted the previously failed job
[18:26] <nacc> slangasek: fyi, the php-cache-lite regressions seems to be due to deprecation, i can see if i can silence that warning so the tests pass
[18:26] <nacc> slangasek: looking at php-html-safe, might be a real issue, but checking
[18:38] <nacc> slangasek: ok, php-html-safe is failing because of a bug in php-xml-htmlsax3, fixed in debian, will request a sync
[18:41] <nacc> slangasek: and i see why php7.0/php-defaults is hung up, that version of php-defaults needs a more current version of php7.0 than we have. I can do another merge, but would like your input as to what level you'd like to go to? Latest Debian (7.0.4-5) or the last 7.0.3 version (7.0.3-13)
[18:44] <nacc> slangasek: whichever way you decide, i think we can clear out the rest of the php stuff (I've filed bugs for several) from excuses page at that point