[02:44] <dragonbite> I have a problem when trying to run the Ubuntu-SDK...
[02:45] <dragonbite> It comes up with updates available for my kits and the option to select "ubuntu-sdk-15.04-amd64"
[02:48] <dragonbite> I check it, let it run and get the following error message
[02:48] <dragonbite> "You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies:
[02:48] <dragonbite> qtdeclarative5-ubuntu-ui-toolkit-plugin : Depends: libubuntugestures5 (= 1.3.1795+15.04.20160106-0ubuntu1)
[02:48] <dragonbite> E: Unmet dependencies. Try using -f.
[02:48] <dragonbite> Command returned 100: schroot -u root -c source:click-ubuntu-sdk-15.04-amd64 -- apt-get dist-upgrade --yes
[02:48] <dragonbite> ---Click exited with errors, please check the output---"
[02:48] <dragonbite> qtdeclarative5-ubuntu-ui-toolkit-plugin is already installed
[02:49] <dragonbite> libubuntugestures5 it cannot find  to install
[03:18] <Son_Goku> does Unity 8 have a hard dependency on Mir, or is that dependency abstracted out through its usage of Qt and QML?
[04:18] <RAOF> Son_Goku: I think it's still capable of being run without Mir, yes.
[04:19] <RAOF> There was certainly a time where you could run a Unity8 session under X11; I don't think we're making any particular effort to preserve that, though, so it might not work anymore :)
[05:46] <hallyn> hm, so both 'shut down' and 'restart' from the menu lead to the same popup with the two 'restart' and 'shut down' options
[06:31] <pitti> Good morning
[06:47] <cpaelzer> good morning
[06:53] <slangasek> morning ;)
[06:54] <ginggs> Pharaoh_Atem, nacc: I sync'd pcre3 from Debian. Is someone going to look at php?
[07:00] <slangasek> ginggs: once pcre3 has been built in xenial-proposed, we can try to build https://launchpad.net/ubuntu/+source/twig/1.23.1-1ubuntu3/+build/9275887 again and see if it's fixed
[07:04] <slangasek> pitti: problems creating nova instances for ppc64el autopkgtests this morning? http://autopkgtest.ubuntu.com/running.shtml
[07:04] <pitti> slangasek: yes, see #is
[07:04] <slangasek> ok :)
[07:04] <pitti> slangasek: buildds are down too
[07:04] <pitti> slangasek: I just filed bug #89226
[07:04] <pitti> slangasek: err, RT #89226
[07:04] <slangasek> pitti: got it, thanks
[07:05] <pitti> I suppose they saw the 30.000 test rebuild requests, cried, and died
[07:06] <slangasek> I don't imagine I should wait up for the test results, then
[07:06] <pitti> I can temporarily disable ppc64el in britney
[07:06] <pitti> that doesn't help with getting builds on ppc64el, but might unblock at least some stuff
[07:13] <pitti> slangasek: force-skiptest php-zend-code> it's more elegant to re-run the test against all of -proposed
[07:13] <pitti> slangasek: run-autopkgtest --all-proposed [...]; or specify both packages as --trigger, but --all-proposed is simpler
[07:13] <pitti> as you can just copy&paste it from ALL_PROPOSED=1 retry-autopkgtest-regressions
[07:14] <slangasek> pitti: oh, you can pass --trigger multiple times; that's the thing I forgot.  Would love to have an example of that on the wiki page :)
[07:15] <pitti> slangasek: I did document --all-proposed
[07:15] <slangasek> yeah, but I don't like --all-proposed ;)
[07:18] <pitti> slangasek: https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure?action=diff&rev2=57&rev1=56
[07:19] <pitti> ppc64el autopkgtests temporarily disabled
[07:23] <slangasek> nacc: looks like phpunit, php-defaults, php7.0 are now wedged in -proposed because of the missing php7.0-zip; what's the plan for getting that restored?
[08:01] <loop> guys why you do not  write anything?
[08:02] <loop> anyone is active?
[08:03] <loop> Guys wake up. I want to share with you my advice and opinion about ubuntu as regular user.
[08:07] <dholbach> good morning
[08:07] <loop> yo
[08:07] <loop> I suggest: Make the new app store (that will operate on the principle of Steam and will be the most important program in the system). With him will could download any application (eg. steam, vokoscreen, audacity ...). There will be no need to add the repo when u want install sth. Only each application exists on Linux will be there to download. Now, after the installation of ubuntu then you have big problems with the installation o
[08:08] <loop> Go on askubuntu and see how many different problems people have with installing steam (omg: /). Close to ~ 80% of the problems of people with askubuntu is installation problems with the program - which will solve the new ubuappstore. Remember that the majority of users are simple people in matters of IT - as I do. All is more difficult cuz of model-behavior of the system.
[08:08] <loop> Get rid of the .deb file type and substitute is an  .uni typ file that will be associated with the shop and it will be installed as 2 clicks in windows. You have a problem with the quality and popularity of software, bugs, and causing it lack of the store (model: Play Store, Steam) and install with performance based management system through apt - which are outdated and fit into the shell text.
[08:08] <loop> To graphical shell fits only app store and the type of executable file .uni. Listen to me and soon show the streamergamers, YouTubers who are you doing free advertising and will promote your free system as for Valve tournaments esports promoted the CS GO which in 2012 was at the bottom. Now it is no. 1 eSports on world. For example look at YT gamers scene in EU at the moment.
[08:09] <infinity> loop: This not a channel for complaints and walls of suggestion text.
[08:10] <loop> I leave your system. By the described disadvantages. You want to start gaining users, in first care in order for the players and the people who use specialized software, creators programmed into .uni. I know that the closed software does slowly in digital society  slaves of men, but I will sit on the windows  if you really are idiots and do not see that what i wrote.
[08:10] <loop> The small things make the difference, and those I have described are enough to your system was popular, like Windows is now popular.
[08:10] <loop> I leave your chat too bye.
[08:10] <loop> ban me :)
[08:11] <dholbach> nobody said they'd like to ban you... this is just not a good way of making yourself heard
[08:11] <infinity> loop: As a general rule, wandering into a room with a bunch of people and suggesting that they're all idiots if they don't immediately implement your idea is likely not the best way to be heard.
[08:12] <infinity> loop: For the record, we're toying with new appstore models (see: snappy), and indeed, some third party software will be delivered that way in the near future.
[08:13] <infinity> loop: You'll be happier to know that we read your comment, were appropriate shamed by your tone, invented a time machine, and started working on it a year ago.
[08:13] <infinity> s/appropriate/appropriately/
[08:14] <loop> I ll read about yout work.
[08:14] <loop> Have politely :) Have fun.
[08:14] <loop> bb
[08:17] <dholbach> @pilot in
[10:25] <mapreri> dholbach: fancy syncing libeatmydata ? :)
[10:25] <mapreri> i did an upload yesterday in debian
[10:25] <dholbach> mapreri, taking a look
[10:28] <darkxst> pitti, vmware no longer gets "splash" on the kernel command line, was that intended?
[10:28] <pitti> darkxst: I don't know, but I doubt that's vmware specifc
[10:29] <pitti> darkxst: it should be specific to the kind of image (cloud/server/desktop)
[10:29] <dholbach> mapreri, done
[10:29] <darkxst> pitti, it happend on installed xenial ubuntu-gnome's
[10:29] <mapreri> dholbach: ♥
[10:29] <darkxst> but not on my laptop
[10:29] <dholbach> :)
[10:54] <pitti> xnox: hmm, is https://launchpadlibrarian.net/243987535/buildlog_ubuntu-xenial-amd64.upstart_1.13.2-0ubuntu20_BUILDING.txt.gz due to a new coreutils or something such?
[10:54] <pitti> not ok 38 - with single-line command that writes 1 line to stderr
[10:54] <pitti> wrong content in file 0x7f0d28045740 (output), expected '0 bytes (0 B) copied,*
[10:54] <pitti> ' got '0 bytes copied, 2.9651e-05 s, 0.0 kB/s
[11:01] <ogra_> at least it is fast
[11:18] <darkxst> pitti, it doesnt seem to affect the live images
[11:27] <Odd_Bloke> xnox: Does the latest kernel (with its modified initrd handling) mean that we can drop your s390x-specific hack from livecd-rootfs?
[11:46] <davmor2> cyphermox, seb128: upgrade from 14.04 → 16.04 really hates us, it broke again bug #1551198
[11:46] <LocutusOfBorg> what did happen to ppc64el buildds?
[11:59] <cpaelzer> LocutusOfBorg: for ppc64el see this channel around 5h before now between pitti and slangasek as well as #is
[12:13] <LocutusOfBorg> thansk cpaelzer
[12:17] <LocutusOfBorg> please seb128 can you retry https://launchpad.net/ubuntu/+source/inkscape/0.91-7ubuntu2/+build/9276902 ?
[12:17] <LocutusOfBorg> :)
[12:22] <seb128> LocutusOfBorg, why is there no build log?
[12:26] <seb128> LocutusOfBorg, retried
[12:34] <LocutusOfBorg> seb128, ppc64el disabled
[12:34] <LocutusOfBorg> so it will be retried when they will become online again, and thanks BTW
[12:34] <seb128> LocutusOfBorg, yw
[12:35] <seb128> ppc64el disabled? do we know what's the issue?
[12:35] <LocutusOfBorg> scroll above ^^
[12:35] <LocutusOfBorg> :)
[12:36] <seb128> I looked to the logs and I didn't see much useful
[12:36] <seb128> oh, well, let's wait then
[12:50] <rbasak> If using dh_install with --fail-missing to better manage a complex package (mysql-5.7), how should we handle files that we deliberately don't want installed? dh_install -X, or some other way?
[12:51] <rbasak> Also, Skuggen reports that --list-missing is reporting manpages installed correctly by dh_installman, and so needs to explicitly exclude those too.. Is that expected?
[12:58] <dholbach> @pilot out
[12:58] <xnox> pitti, looks like it. open a bug and assign to me?!
[12:58] <xnox> Odd_Bloke, possibly, needs testing. I'll spin a rebuild in my ppa and see what happens.
[13:06] <jibel> stgraber, Hi, could you have a look at bug 1551150? lxc is a primary suspect.
[13:55] <cjwatson> pitti: is ppc64el happier for you now?
[13:56] <cjwatson> ah yes, the RT was updated too
[14:01] <pitti> cjwatson: it is indeed, thanks
[14:02] <pitti> l
[14:07] <cyphermox> davmor2: it says module-init-tools in unauthenticated, does it come from some other testing?
[14:12] <davmor2> cyphermox: nope default install of 14.04.4 + updates and then running update-manager -d in atl+F2
[14:41] <tjaalton> anyone know what changed the default monospace font?
[14:41] <tjaalton> in xenial
[14:41] <tjaalton> it's much wider than the old
[14:43] <rbasak> tjaalton: https://lists.ubuntu.com/archives/ubuntu-devel/2016-February/039224.html maybe?
[14:44] <tjaalton> rbasak: exactly
[14:53] <tjaalton> before I had a split terminator instance with four columns, 125+94+94+94 wide (roughly). Now they are 125+94+64+64..
[14:53] <tjaalton> unusable :/
[14:53] <tjaalton> smaller font size is not an option
[14:57] <pitti> xnox: I pushed http://bazaar.launchpad.net/~ubuntu-core-dev/upstart/ubuntu/revision/1628 now, this seems to work fine
[14:58] <xnox> pitti, cool!
[14:58] <pitti> xnox: while I'm at it, do you have an idea about that flaky test:
[14:58] <pitti> not ok 26 - with single-line script that is killed
[14:58] <pitti>  wrong value for WIFSIGNALED (status), expected TRUE got FALSE
[14:58] <pitti>  at tests/test_job_process.c:1760 (test_start).
[14:58] <pitti> 1..153
[14:58] <pitti> FAIL: test_job_process
[14:58] <pitti> xnox: this seems to fail in most autopkgtset runs
[14:59] <pitti> and currently we force-badtest the entire thing, which is a shame
[14:59] <pitti> as we don't hear about other regressions that way
[14:59] <xnox> pitti, yes -> it is possible that a short lived process exits faster than we manage to kill it, and catch the signal.
[14:59] <pitti> xnox: would it be okay to disable that particular test for now, so that the others become useful again?
[14:59] <xnox> i wonder if we should "loop" / re-attempt the test a few times before giving up.
[14:59] <xnox> ok.
[15:03] <pitti> xnox: I think the rest of the test is okay, so http://paste.ubuntu.com/15244176/
[15:04] <xnox> doko, please RM unity-scope-snappy as per bug #1542451 which also fixes bug #1542376 and bug #1534346
[15:04] <xnox> pitti, yeap, looks good.
[15:04] <pitti> xnox: thanks
[16:05] <nacc> ginggs: hey, pcre3 question for you, when you have a moment
[16:16] <ginggs> nacc: just ask
[16:19] <nacc> ginggs: ok, we've deduced that the twig testsuite is failing with php7 due to a pcre bug. Thanks to Pharaoh_Atem's debugging with the SCL maintainer, we know that FC23 doesn't have this problem, but both SCL and Ubuntu do. I'm trying to understand how Debian/Ubuntu pull in the fixes normally? There are a lot of upstream bugfixes since 8.38 that Debian & Ubuntu seem to be missing. I just noticed you did
[16:19] <nacc> the last merge, and wasn't sure if you had more context.
[16:25] <ginggs> nacc: i would say normally fixes come in upstream releases, which get packaged in debian and then make their way into ubuntu. sometimes, a bug may be filed in debian (e.g. debian #815921) and it may be important enough for the maintainer to upload a new debian release.
[16:32] <ginggs> nacc: do you know which bug it is? http://vcs.pcre.org/pcre/code/trunk/ChangeLog?view=markup
[16:32] <nacc> ginggs: ok, thanks -- I figured that was the case, but wasn't sure, I might just have hit a window where the debian bug wasn't fixed yet.
[16:33] <nacc> ginggs: sadly not yet :/ i'm trying with all of fc23's patches applied just to get a bseline, but i know it's just not the abvoe-mentioned issue
[16:34] <nacc> ginggs: it's something to do with the jit (as if we disable pcre.jit in PHP, it goes away)
[16:45] <nacc> ginggs: the tricky part is i have to rebuild php7 to test :)
[17:34] <seb128> bdmurray, you said that https://code.launchpad.net/~seb128/software-properties/newtab-enable-proposed/+merge/286626 looked fine to you, could you comment on it saying so?
[17:37] <bdmurray> seb128: Yep
[17:37] <seb128> bdmurray, thanks
[17:41] <jderose> cyphermox: so i'm taking a stab at https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1508865 today... sometime during the 15.10 cycle this was introduced. something is different about how the first-run DM is setup compared to the normal installation DM... any ideas?
[17:41] <jderose> cyphermox: i've been looking the the changes in bzr, but nothing has stood out to me yet
[17:46] <xnox> jderose, the networking page steps got re-arranged, maybe that affected things?! (e.g. the step that oem-config starts from should be like -1 or some such?!)
[17:46] <xnox> jderose, however i thought networking is generally not enabled at all during user config.
[17:47] <jderose> xnox: it used to be, because that's how ubiquity could guess your timezone using your IP
[17:47] <xnox> ok.
[17:47] <jderose> xnox: happen to know where in the ubiquity code said networking setup happens?
[17:48] <xnox> it's a separate page/plugin.
[17:48] <xnox> a stand-alone file i believe.
[17:49] <cyphermox> jderose: what do you mean by "DM" ?
[17:50] <ginggs> cjwatson: where can I find the specs of the powerpc buildds sagari, denneed* and fisher* please?
[17:50] <jderose> cyphermox: my terminology might be wrong... i'm looking at, for example, bin/ubiquity-dm
[17:50] <cyphermox> this isn't a new change; oem-config needs to get rid of any oem-specific networking config; NM would re-write new config files as necessary
[17:51] <cyphermox> but I see what might be wrong
[17:52] <cyphermox> for wired you probably need to go an click on nm-applet and pick the wired device for it to connect, and it's not doing so automatically
[17:52] <jderose> cyphermox: i do recall a bug about prepare for shipping to end user should delete stuffs in /etc/NetworkManager/system-connections/... could that have resulted in networking being completely disabled during the user first-run?
[17:53] <cjwatson> ginggs: What in particular are you trying to figure out?
[17:53] <cyphermox> not disabled, but NM gets confused because "Ethernet 1" gets deleted and it won't just automatically recreate it, because reasons
[17:53] <jderose> cyphermox: in my experience, th nm applet is only shown when on wifi... otherwise it silently connects to ethernet without displaying the nm applet
[17:54] <ginggs> cjwatson: still trying to figure out the openmpi failures with powerpc LP: #1550863 / Debian #814183
[17:54] <jderose> ubiquity also no longer prompts to connect to wifi during the user first-run
[17:54] <cjwatson> ginggs: they're all POWER7; sagari is bare metal, denneed*/fisher* are VMs
[17:54] <cyphermox> jderose: no, the applet should always show
[17:54] <cyphermox> jderose: wifi should not try to connect automatically to anything
[17:55] <cjwatson> ginggs: the usual relevant difference is that sagari has something like 15GB of RAM while the VMs have somewhat less (don't know exactly how much)
[17:55] <cjwatson> ginggs: for more details ask infinity
[17:55] <jderose> cyphermox: it didn't do it automatically... when there was no ethernet, it would prompt you to connect to wifi. it still does this during the initial install, but doesn't anymore during the first-run user config
[17:56] <cyphermox> I'm not sure it ever did in the oem context
[17:56] <ginggs> cjwatson: thanks (again)
[17:56] <cyphermox> but that should be easy enough to fix
[17:57] <cjwatson> ginggs: (something more like denneed*/fisher* should be considered future direction, though we can adjust available RAM a bit just as we recently did on ppc64el)
[17:57] <cyphermox> jderose: I'll look as soon as I'm done eating lunch :)
[17:58] <jderose> cyphermox: i'm 100% certain it used to do this during the oem first-run user setup. this is a bug that flexiondotorg found just prior to the 15.10 release during his ISO testing
[17:59] <ginggs> cjwatson: I was just looking for a pattern, in Debian it appeared that things FTBFS on POWER8, but built on PPC970FX
[17:59] <jderose> cyphermox: no rush, enjoy your lunch! :)
[18:35] <jderose> cyphermox: just confirmed to make sure i'm not talking crazy... when no ethernet is plugged it but you have a wifi card, 14.04.4 prompts you to join a wifi network during oem first-run user config on the 2nd page; 15.10 and xenial go directly to the timezone selection page, without networking enabled
[18:36] <nacc> ginggs: another question, if you happen to know, does libpcre3 allow for runtime disabling of JIT?
[18:42] <cyphermox> jderose: sounds like maybe the network screen crashes when running in oem
[18:43] <cyphermox> jderose: that would show up in /var/log/syslog, or /var/log/installer/debug (or /var/log/ubiquity/debug, I think)
[18:43] <jderose> cyphermox: for wired, 14.04.4 automatically connects to the network, but doesn't show the nm applet; 15.10 and xenial never show the nm applet, neither for wireless nor weired
[18:44] <jderose> okay, i'll check the logs...
[18:44] <cyphermox> well, much of this is wrong then, nm-applet should always show
[18:45] <cyphermox> jderose: please file bugs for each different thing, and I'll get to them as soon as I can
[19:28] <nacc_> Pharaoh_Atem: hrm, so i built a version of pcre3 that compile-time had jit disabled. still get a segfault unless i tell php pcre.jit=0 (which all it does is not call pcre_study, afaict).
[19:33] <ginggs> nacc_: don't know, sorry
[19:34] <vooze> Hello dear devs ;) I have reported this bug, but I can't figure what what package is responsible to setting the wallpaper. https://bugs.launchpad.net/ubuntu/+bug/1550815 - The issue is it changes the colors on the wallpaper from the original image
[19:34] <nacc_> ginggs: np, i'm figuring it out as i go ... it is a pcre bug, but i think one that may not yet have been found upstream (as i can reproduce it with the latest svn)
[19:34] <nacc_> Pharaoh_Atem: --^ which is confusing to me that fc23 works at all
[19:35] <nacc_> Pharaoh_Atem: fc23 doesn't happen to use the php7 src pcrelib, does it?
[19:43] <nacc_> Pharaoh_Atem: but in more positive news, i've reduced the twig segfault to a one line change in the testcase, so i know *why* it's failing (as in what particular test in the testcase)
[19:58] <cjwatson> nacc_: sorry if you've talked about this already, but I keep seeing you talking about pcre3, is there a reason you aren't using the (newer!) pcre2?
[19:58] <cjwatson> if upstream only works with pcre3 then that's a valid reason of course
[19:58] <Pharaoh_Atem> nacc_: that's awesome
[19:59] <Pharaoh_Atem> and horrifying
[19:59] <Pharaoh_Atem> maybe Fedora is optimizing out the issue with its more aggressive gcc flags?
[19:59] <Pharaoh_Atem> cjwatson: someone needs to kill that soversion mutation in Debian for pcre
[19:59] <Pharaoh_Atem> it *should* be pcre1
[20:02] <ginggs> Pharaoh_Atem: hopefully pcre3 will disappear soon, and then we'll only have pcre2
[20:03] <dobey> hmm, why is "do-release-upgrade -d" complaining that it can't authenticate module-init-tools from us.archive.u.c on my laptop?
[20:04] <nacc_> cjwatson: php7 only supports building against pcre3 (afaict) ... i guess i could try and move the build-dep, but i think that's how upstream is too
[20:05] <dobey> vooze: what ubuntu is that?
[20:05] <vooze> dobey: on the images: ubuntu 14.04 (unity) but I have found the "bug?" in Linux Mint, Ubuntu Gnome 15.10, Ubuntu 16.04 and Xubuntu as well.
[20:06] <nacc_> Pharaoh_Atem: it could be ... it does sound like php & pcre have had issues int he past, i'm filing a pcre bug now to see if they can help debug
[20:06] <dobey> vooze: what resolution is your screen?
[20:06] <vooze> dobey: 1920x1080 on laptop and 2560x1440 on desktop (bug present on both)
[20:07] <vooze> Also Laptop uses Intel GPU and Desktop Nvidia
[20:10] <dobey> vooze: nautilus is what renders the background; i moved the bug there; but when i open the image in eog on my computer, it is not as orange as you claim it should be
[20:10] <cjwatson> Pharaoh_Atem: about a decade too late
[20:11] <cjwatson> Pharaoh_Atem: no point going through a painful transition when we want to end up on pcre2 anyway
[20:12] <vooze> dobey: maybe a different color profile (or just different tuned monitor?) Would it be possible for you to set it as wallpaper while having it open in eog to see if there is a difference?
[20:13] <dobey> vooze: this is intel with a dell 4k monitor that is 100% rgb
[20:13] <vooze> It is different from image to image "how much" it changes I think. That is just the "best" image I could find to show the difference.
[20:16] <vooze> dobey: okay. Could you possible try to apply it as wallpaper? Also thanks for taking the time to help me.
[20:17] <dobey> vooze: for me it seems slightly more orange there when applied as a wallpaper; perhaps due to a different scaling method used for the background, versus for eog
[20:18] <dobey> granted, i also have redshift running
[20:19] <vooze> dobey: Could be. But at least now the bug is open and maybe some nautilus-devs? (But thats gnome devs I guess? Can take a look at it. Otherwise I will just have to wait for Unity 8 :)
[20:20] <vooze> Maybe that will handle it differently with mir.
[20:20] <dobey> well, if you want gnome devs to look at it, probably also needs to be forwarded upstream
[20:20] <vooze> dobey: Well, I checked on Ubuntu Gnome and the issue is there as well, so could not hurt I guess.
[20:25] <vooze> dobey: is this something I can do from the bugtracker on launchpad or should I post elsewhere and link it on launchpad?
[20:26] <dobey> i don't recall the exact procedure for pushing bugs upstream, sorry
[20:26] <dobey> ask in #ubuntu-bugs perhaps
[20:26] <vooze> dobey: Okay, I will try to figure it out. Thank you again for your time.
[20:49] <stefanct> hm, is there a lp: containing the xenial package that i can use for a nest-part packaging directive in a recipe?
[20:50] <stefanct> i have seen lp:debian/sid which is almost as good, but referring to the "real" thing seems better
[20:50] <cjwatson> not in general, the bzr importer was creakingly bad and we haven't turned it on for xenial
[20:50] <dobey> stefanct: there are no source imports of xenial packages, no
[20:50] <dobey> ah i see cjwatson is still here :)
[20:51] <cjwatson> I'm three hours west of usual this week
[20:52] <dobey> ah
[20:52] <dobey> at the ols sprint?
[20:52] <cjwatson> yep
[20:53] <stefanct> ok thanks
[20:53] <dobey> cool. bet the weather is nice there :)
[20:58] <sarnold> coreycb: congratulations :)
[20:58] <coreycb> sarnold, thanks!
[21:35] <slangasek> nacc_: hi, did you see my follow-up on bug #1549942 yesterday?
[21:35] <slangasek> nacc_: I believe that's the last blocker for getting php7.0/phpunit/php-defaults migrated now
[22:02] <stefanct> is there an easy way to exclude a directory (e.g. debian/patches) when using nest-part?
[22:48] <ScottK> caribou: If you care about armv5 at all (not sure if Ubuntu does, but its derivatives might) you should definitely merge clamav again.
[22:49] <teward> ScottK: I don't think there's any Ubuntu supporting anything less than armv7 right now?  Unless I misread the architectures documentation
[22:49] <ScottK> I think that's right, but I don't know about derivatives.
[22:50] <ScottK> That or sparc, which is definitely at most a derivative's concern.
[22:52] <teward> ScottK: i hate to be argumentative, but with Xenial sparc's not even on our arch list - at that point would it not be up to the derivatives alone to provide support/fixes for those patches?  (And I am excluding officially recognized flavors of *buntu from "derivatives")
[22:52] <teward> s/our arch/the arch/
[22:53] <teward> (basically, how much do we need to provide support for unsupported archs for derivatives)
[22:53] <teward> my two cents though, i have no say ultimately :)
[22:53] <ScottK> Since Debian's already fixed the bug and all it takes is a merge, meh.
[22:53]  * teward shrugs
[23:10] <Pharaoh_Atem> cjwatson: then someone should probably port php to use pcre2 :/