[00:00] <slangasek> nacc: ok.  I think this is something that ought to be filed as a bug against pkg-php-tools as well
[00:00] <nacc> slangasek: yep, i'll take it as  followup
[00:21] <nacc> slangasek: ok, just subscribed you to my last set for the day
[00:21] <nacc> by my count, we've only got 22 more revdeps
[00:21] <nacc> jgrimm: --^
[00:27] <slangasek> ah, of course, a fix for operator precedence change; I remember all the work we had to do when C99 support came out that we had to do to update our operator precedence rules, it stands to reason the same thing would apply to php7
[00:28] <nacc> slangasek: :)
[00:28] <nacc> php was ... inconsistent before? i guess
[00:29] <nacc> so they are now consistent, but means that the implicit way things work before is not true anymore
[00:29] <nacc> from waht i could gather, "good" php code never shoudl have been affected... :)
[00:29] <slangasek> so it's getting better?  ok, I guess I can allow them that
[00:31] <nacc> :)
[02:06] <nacc> slangasek: have a great weekend! looking forward to being done with php5 next week :)
[08:29] <TJ-> Can anyone make sense of this potentially serious security/DoS issue after installing/enabling libapache2-mod-php5? A user reported this early hours of today in #ubuntu+1. User's 'sudo' group membership was somehow removed. Captured in http://pastebin.ubuntu.com/15585996/
=== [yas] is now known as Guest28156
[14:58] <Unit193> Is anyone currently active?  Newsbeuter that was uploaded into Debian now covers the delta we have (memleak fix) plus an additional segfault fix or two.  It'd really benefit a sync at little to no cost as it's not seeded.
[15:01] <Unit193> If not, well the memleak was pretty awful so that fix is good, and one segfault is only in translations so if you're American no problem. :>
[15:07] <ginggs> Unit193: requestsync please
[15:09] <Unit193> ginggs: Heh, was worth a shot.  Sure, will do.
[15:10] <ginggs> Unit193: at least you know there's someone who might look at it now.
[15:10] <Unit193> \o/
[15:19] <ginggs> Unit193: I see your name on LP: 1406825
[15:19] <ubottu> Launchpad bug 1406825 in xscreensaver (Ubuntu) "xscreensaver complains "This version of xscreensaver is VERY OLD!"" [Medium,Fix released] https://launchpad.net/bugs/1406825
[15:20] <Unit193> ginggs: Old report, yeah.  I suppose you've seen all the noise in Debian then. :P
[15:21] <ginggs> yeah :) so how did you fix it in ubuntu?
[15:23] <Unit193> I don't remember if we just ended up updating it or adding the patch, but last time I merged it there was no patch.
[15:25] <Unit193> So, Lubuntu users are going to hit it half way through Xenial. :/
[15:34] <ginggs> ah, ok and 5.15 in trusty doesn't have the time bomb yet
[15:35] <Unit193> Not sure if it was lost or what, I remember looking into it.  Also, https://build.opensuse.org/package/view_file/openSUSE:13.2:Update/xscreensaver.4176/xscreensaver-disable-upgrade-nagging-message.patch
[17:35] <Bluefoxicy> Bah, no BFQ in Xenial :(
[18:27] <Bluefoxicy> libenchant1c2a:amd64 depends on libhunspell-1.3-0v5 (>= 1.3.3) Xenial
=== StaffUnicorn is now known as nhandler
[20:10] <Laney> doko: I'm not that happy with skipping glib2.0's testsuite - and it wasn't a first build (if it was then it would have migrated).
[20:10] <Laney> Something external obviously broke it and now we don't have visibility of that problem
[23:19] <Unit193> ginggs: There we go, finally picked up: #1565370.