=== santa is now known as Guest22632
[03:58] -queuebot:#ubuntu-release- Unapproved: python-fitsio (zesty-proposed/universe) [0.9.10+dfsg-1build1 => 0.9.10+dfsg-1ubuntu1] (no packageset)
[03:59] -queuebot:#ubuntu-release- Unapproved: accepted python-fitsio [source] (zesty-proposed) [0.9.10+dfsg-1ubuntu1]
[04:52] -queuebot:#ubuntu-release- Unapproved: blacs-mpi (zesty-proposed/universe) [1.1-37ubuntu3 => 1.1-38] (no packageset) (sync)
[04:52] -queuebot:#ubuntu-release- Unapproved: accepted blacs-mpi [sync] (zesty-proposed) [1.1-38]
[04:52] -queuebot:#ubuntu-release- Unapproved: xbase64 (zesty-proposed/universe) [3.1.2-11 => 3.1.2-12] (no packageset) (sync)
[04:53] -queuebot:#ubuntu-release- Unapproved: accepted xbase64 [sync] (zesty-proposed) [3.1.2-12]
[06:41] -queuebot:#ubuntu-release- Unapproved: node-mocha (zesty-proposed/universe) [1.20.1-2 => 1.20.1-7] (no packageset) (sync)
[06:42] -queuebot:#ubuntu-release- Unapproved: accepted node-mocha [sync] (zesty-proposed) [1.20.1-7]
[06:59] <rbasak> o/
[07:00] <rbasak> I'm going to swap my SRU day to today as I'll be busy with the sponsorship party on Wednesday
[07:00] <rbasak> infinity: ^
[07:04] <rbasak> apw: when you're in, please could you take a look at releasing mysql-5.7 to xenial-updates please? I think it's ready. The dep8 failure looks like it's an intentional environment thing?
[07:57] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (precise-proposed) [2.3.1-89ubuntu3]
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (trusty-proposed) [2.3.1-93ubuntu2~ubuntu14.04.1]
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (xenial-proposed) [2.3.1-93ubuntu2~ubuntu16.04.1]
[08:01] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (yakkety-proposed) [2.3.1-93ubuntu2~ubuntu16.10.1]
[08:13] <jbicha> rbasak: ostree/yakkety is not an autopkgtest regression: http://autopkgtest.ubuntu.com/packages/f/flatpak/yakkety/s390x http://autopkgtest.ubuntu.com/packages/f/flatpak/yakkety/armhf
[09:07] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.10.0-14.16~16.04.1] (no packageset)
[09:45] -queuebot:#ubuntu-release- Unapproved: gnome-dvb-daemon (zesty-proposed/universe) [1:0.2.91~git20170110-2 => 1:0.2.91~git20170110-2build1] (no packageset)
[09:46] -queuebot:#ubuntu-release- Unapproved: accepted gnome-dvb-daemon [source] (zesty-proposed) [1:0.2.91~git20170110-2build1]
[09:51] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.10.0-14.16~16.04.1]
[09:54] <flexiondotorg> Please unblock mate-desktop/1.18.0-0ubuntu2
[09:54] <flexiondotorg> Please unblock mate-settings-daemon/1.18.0-0ubuntu2
[09:55] <flexiondotorg> Please unblock caja-dropbox/1.18.0-0ubuntu2
[10:28] <Laney> flexiondotorg: There is no block, just a queue freeze which is reviewed regularly. I'm about to do a pass.
[10:32] <flexiondotorg> Ah, OK. Thanks Laney
[11:18] -queuebot:#ubuntu-release- Unapproved: accepted snapd-glib [source] (zesty-proposed) [1.9-0ubuntu1]
[11:26] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (zesty-proposed) [1:45.8.0+build1-0ubuntu1]
[11:28] <rbasak> Laney: are you able to stop phasing of cups 2.1.3-4ubuntu0.2 in xenial-updates please?
[11:28] <Laney> rbasak: I think you probably need an AA
[11:29] <rbasak> Looks like there are a ton of reports so the fix to bug 1642966 didn't work.
[11:29] <ubot5> bug 1642966 in cups (Ubuntu Yakkety) "package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1" [High,Fix committed] https://launchpad.net/bugs/1642966
[11:29] <rbasak> Laney: ah. I thought you were!
[11:29] <rbasak> apw: ^
[11:29] <rbasak> xnox: ^
[11:29] <Laney> assuming that the SRU team can't do it themselves
[11:29] <Laney> nope!
[11:29] <rbasak> I believe we can't.
[11:31] <Laney> When do you unphase vs. removing the package?
[11:31] <Laney> Just OOI
[11:31] <rbasak> No sure.
[11:31] <rbasak> Not sure.
[11:31] <rbasak> In this case removal might be appropriate I think.
[11:36] -queuebot:#ubuntu-release- Unapproved: adplug (zesty-proposed/universe) [2.2.1+dfsg3-0.3 => 2.2.1+dfsg3-0.4] (no packageset) (sync)
[11:37] -queuebot:#ubuntu-release- Unapproved: accepted adplug [sync] (zesty-proposed) [2.2.1+dfsg3-0.4]
[11:38] -queuebot:#ubuntu-release- Unapproved: apt-dpkg-ref (zesty-proposed/universe) [5.3.1+nmu1 => 5.3.1+nmu2] (no packageset) (sync)
[11:39] -queuebot:#ubuntu-release- Unapproved: accepted apt-dpkg-ref [sync] (zesty-proposed) [5.3.1+nmu2]
[11:39] -queuebot:#ubuntu-release- Unapproved: boxer-data (zesty-proposed/universe) [10.5.14 => 10.5.15] (no packageset) (sync)
[11:40] -queuebot:#ubuntu-release- Unapproved: accepted boxer-data [sync] (zesty-proposed) [10.5.15]
[11:44] <xnox> rbasak, Laney - removal is still a regression, as people will not get the other fix, which is ultimately causing the upgrade failures......
[11:50] <rbasak> xnox: I don't follow. The bug that causes the maintainer script failure (a race?) is not fixed. Correct?
[11:53] <xnox> cups in xenial-release prematurely shutsdown preventing people from accessing the web interface https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300
[11:53] <ubot5> Ubuntu bug 1598300 in cups (Ubuntu Xenial) "CUPS web interface stops responding after a while" [Undecided,Fix committed]
[11:53] <xnox> when attempting to fix that, it was discovered that upgrade scripts fail because systemd units end up being silly
[11:55] <xnox> not everyone is affected by either upgrade bug; or the web interface bug.
[11:56] <xnox> we never got a reliable reproducer for the upgrade failure
[11:56] -queuebot:#ubuntu-release- Unapproved: accepted gnome-dictionary [source] (zesty-proposed) [3.24.0-0ubuntu1]
[11:58] <rbasak> xnox: OK, but given the SRU resulted in further reports, the bug still exists, right?
[11:58] -queuebot:#ubuntu-release- Unapproved: accepted xfdashboard [source] (zesty-proposed) [0.6.1-0ubuntu1]
[11:58] <rbasak> By "the bug" I mean the systemd problem.
[11:58] <xnox> correct
[11:59] <xnox> or at least a similar issue is still manifesting itself elsehow.
[11:59] <rbasak> By removing the latest SRU we'll stop people hitting the systemd problem, which they are right now.
[11:59] <xnox> e.g. i still think it's correct to keep what was done in .2 but further fixes are needed.
[11:59] <rbasak> They then won't get the web interface fix
[11:59] <xnox> true
[11:59] <rbasak> But from the point of view of users unaffected by the web interface problem, it's a "regression" they won't hit then.
[12:00] <rbasak> So IMHO, we should do that pending a full fix for the systemd issue.
[12:01] <Laney> IIUC you could copy .1 back into -updates
[12:01] <rbasak> I don't think that'll help.
[12:01] <xnox> .1 never made into -updates because of failure to upgrade
[12:01] <Laney> Help whajt?
[12:01] <Laney> Oh
[12:01] <rbasak> *Any* update to cups has the race that leads to the maintainer script failure.
[12:01] <Laney> I thought that one was released
[12:01] <xnox> nope mark hit upgrade failure and kindly makred it block-proposed =)
[12:01] <xnox> or some suhc
[12:02] <Laney> Then I think killing this one is right
[12:04] -queuebot:#ubuntu-release- Unapproved: accepted mir [source] (zesty-proposed) [0.26.2+17.04.20170322.1-0ubuntu2]
[12:08] <Laney> flexiondotorg: Could I trouble you to include patch headers please?
[12:08] <Laney> and the changelog is most uninformative
[12:09] <flexiondotorg> This is for mate-desktop and mate-settings-daemon right?
[12:09] <Laney> Yeh
[12:12] -queuebot:#ubuntu-release- Unapproved: wmaker (zesty-proposed/universe) [0.95.7-7 => 0.95.7-8] (no packageset) (sync)
[12:12] -queuebot:#ubuntu-release- Unapproved: accepted wmaker [sync] (zesty-proposed) [0.95.7-8]
[12:17] <Laney> flexiondotorg: and https://launchpadlibrarian.net/312618974/caja-dropbox_1.18.0-0ubuntu1_1.18.0-0ubuntu2.diff.gz <- did you mean to remove 2003_execute_via_dbus_launch.patch?
[12:17] <Laney> (also, Popen has an env= argument)
[12:18] <flexiondotorg> Ah, yes. 2003_execute_via_dbus_launch.patch should have been dropped.
[12:18]  * Laney invokes the reject-o-tron
[12:18] <flexiondotorg> I'll resubmit mate-desktop, mate-settings-daemon and caja-dropbox later with the changes you've suggested.
[12:19] <Laney> If you want to fix nautilus-dropbox as well, I wouldn't complain :-)
[12:19] <flexiondotorg> Laney Can I upload with the same versions, now that are being rejected, or should I bump them to -0ubuntu3?
[12:19] <Laney> You can re-use
[12:20] <flexiondotorg> OK, I'll do nautilus-dropbox too.
[12:20] <Laney> Fanx
[12:20] -queuebot:#ubuntu-release- Unapproved: rejected caja-dropbox [source] (zesty-proposed) [1.18.0-0ubuntu2]
[12:21] -queuebot:#ubuntu-release- Unapproved: rejected mate-desktop [source] (zesty-proposed) [1.18.0-0ubuntu2]
[12:21] -queuebot:#ubuntu-release- Unapproved: rejected mate-settings-daemon [source] (zesty-proposed) [1.18.0-0ubuntu2]
[12:21] <Laney> also communicating with Dropbox about their borkedness would be good, but not strictly required
[12:21] <flexiondotorg> I've tried.
[12:22] <Laney> (for nautilus-dropbox you would presumably look at XDG_CURRENT_DESKTOP and only do this hack if it is Unity)
[12:23] <Laney> "Unity" in os.environ.get("XDG_CURRENT_DESKTOP", "").split(":") or something
[12:24]  * Laney gets hungry
[12:28] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-system-settings [sync] (zesty-proposed) [0.4+17.04.20170324-0ubuntu1]
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted youker-assistant [source] (zesty-proposed) [2.2.7-0ubuntu1]
[12:39] <flexiondotorg> Laney, Yes. For nautilus-dropbox I check it required for Unity.
[12:39] <Laney> Neato wheetos
[12:39] -queuebot:#ubuntu-release- Unapproved: rejected indicator-china-weather [source] (zesty-proposed) [2.2.1-0ubuntu1]
[12:41] -queuebot:#ubuntu-release- Unapproved: accepted lirc [sync] (zesty-proposed) [0.9.4c-8]
[12:42] <Laney> I left a package in the queue for someone else to enjoy
[12:42] -queuebot:#ubuntu-release- Unapproved: accepted budgie-desktop [source] (zesty-proposed) [10.2.9-3ubuntu4]
[12:52] <jibel> could someone review ubuntu-ui-extras in the unapproved queue? it goes with ubuntu-system-settings that has just been approved
=== _salem is now known as salem_
[13:14] <apw> jibel, in zesty ?
[13:14] <jibel> apw, yes
[13:14] <apw> jibel, /me hates on syncs
[13:19] <rbasak> apw: see cups discussion above please. Are you able to do a phasing stop or delete from xenial-updates?
[13:21] <apw> i can delete that, what version was there before ?
[13:22] <rbasak> I believe there was nothing in xenial-updates. I'll check.
[13:22] <apw> jibel, the diff here is vast, ugg
[13:23] <rbasak> Yeah, AFAICS 2.1.3-4 only in the release pocket.
[13:24] <apw> rbasak, is there a bug for the regression
[13:24] <apw> so i can ref it
[13:29] <rbasak> Yes, one moment
[13:29] <rbasak> apw: let's use 1676380 to track today's "regression".
[13:33] <apw> rbasak, gone modulo the publisher
[13:36] <rbasak> Thank you! I'll sort out the bugs.
[13:37] <ginggs> anyone know of something that changed in armhf and s390x autopkgtesters between 2017-01-29 and 2017-03-02?  varnish now fails its autopkgtests  - Port "6081" should be listening with tcp
[13:38] <ginggs> ^ blocks pcre3 migration
[13:39] <xnox> ginggs, firewall upgrades? =)
[13:40] <infinity> xnox: I assume that's a local loopback.
[13:41] <infinity> Certainly looks like it should be.
[13:41] <infinity> So, something lxc/lxdish is going on there.
[13:42] <infinity> Laney: ^
[13:42] <Laney> Yes?
[13:42] <Laney> Did someone run it locally?
[13:43] <ginggs> Laney: not on the affected architectures
[13:43] <xnox> ginggs, locally on amd64 but with e.g. lxd runner
[13:43] <infinity> Oh.  Or.
[13:44] <infinity> ginggs: It could be as simple as the test not depending on net-tools, and those chroots being "cleaner"?
[13:44] <infinity> Since the tests uses 'netstat' to determine if the port is open, and netstat was demoted out of essential.
[13:45] <ginggs> ah, ok, let me try locally with lxd runner
[13:45] <infinity> On 2017-01-27
[13:45] <infinity> Which would sort of match your timeline.
[13:47] <xnox> oooooh
[13:48] <infinity> Of course, I'm having a heck of a time finding the string netstat here now. :P
[13:51] <infinity> Ah-ha.
[13:51] <infinity> Found it.
[13:56] <infinity> ginggs: Assuming it's not LXC screwing with you, but just the net-tools demotion, then my ruby-specinfra upload will fix it.
[13:57] -queuebot:#ubuntu-release- Unapproved: ruby-specinfra (zesty-proposed/universe) [2.66.0-1 => 2.66.0-1ubuntu1] (no packageset)
[13:57] <infinity> ginggs: https://launchpad.net/ubuntu/+source/ruby-specinfra/2.66.0-1ubuntu1
[13:58] -queuebot:#ubuntu-release- Unapproved: accepted ruby-specinfra [source] (zesty-proposed) [2.66.0-1ubuntu1]
[13:58] <ginggs> infinity: ta!
[13:59] <infinity> (If it is an LXC issue, my upload is still correct, it just might not fix your bug :P)
[14:02] <Laney> https://paste.ubuntu.com/24260974/
[14:02] <LocutusOfBorg> hello apw, or any AA, can you please move libboost-filesystem-dev to main?
[14:02] <LocutusOfBorg> I'm working to remove boost1.61 and mir is unhappy
[14:02] <infinity> Laney: Kay, so it's LXC not letting us bind to some ports?
[14:03] <Laney> No
[14:03] <infinity> Oh, I misread.
[14:03] <infinity> It's net-tools.  Check.
[14:03] <infinity> So, we have an inverse bug that some of our testing chroots aren't clean enough.
[14:04] <infinity> Laney: I somehow read the second run as a failure.  In my defense I just woke up. ;)
[14:04] <LocutusOfBorg> BTW boost-default is already in main, not sure why it is half in universe
[14:05] <infinity> LocutusOfBorg: Reference to mir unhappiness?
[14:05] <LocutusOfBorg> mirtest-dev/amd64 unsatisfiable Depends: libboost-filesystem-dev
[14:05] <infinity> It being half in universe is correct, as only the bits with deps end up in main.
[14:05] <LocutusOfBorg> oh indeed
[14:06] <LocutusOfBorg> my bad, to make mir less pita during boost transitions, we ended up in depending on the -dev package
[14:06] <LocutusOfBorg> instead of the runtime one
[14:06] <LocutusOfBorg> http://launchpadlibrarian.net/312291835/mir_0.26.2+17.04.20170322.1-0ubuntu1_0.26.2+17.04.20170322.1-0ubuntu2.diff.gz
[14:06] <LocutusOfBorg> such stuff -         libboost-filesystem1.61.0 | libboost-filesystem1.58.0 | libboost-filesystem1.55.0,
[14:06] <LocutusOfBorg> is unmaintainable
[14:06] <LocutusOfBorg> +         libboost-system-dev, <-- this is really better to me
[14:07] <LocutusOfBorg> so, at the end just the -dev package needs promoting
[14:07] <LocutusOfBorg> to make the whole Borg community happy
[14:07]  * LocutusOfBorg BTW nice article on slashdot wrt Ubuntu Beta!
[14:07] <infinity> That should show up on component-mismatches-proposed.  Did that change *just* get uploaded?
[14:08] <infinity> Yeah, it did.
[14:08] <infinity> So, our reports should yell at us shortly.  I might wait on that to see if they say something else.
[14:08] <LocutusOfBorg> as you wish :) yes, I'm working on removing boost1.61 from main/archive
[14:08] <philroche> infinity: RE. gce-compute-image-packages lp:1668327 Patches for all suites in -proposed have been verified. GCE are eager to get this released, would you be able to move these from -proposed to -updates? https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327
[14:09] <ubot5> Ubuntu bug 1668327 in gce-compute-image-packages (Ubuntu Yakkety) "Startup scripts get run when guest packages are updated" [Medium,Fix committed]
[14:22] <infinity> philroche: Sure thing.
[14:22] <philroche> infinity: Thanks
[14:24] <infinity> LocutusOfBorg: Err, that mir upload is still wrong.
[14:25] <infinity> LocutusOfBorg: If your goal is to remove all boost << 1.62, not removing the versioned deps won't get you far. :P
[14:25] <infinity> LocutusOfBorg: Oh.  OR I MISSED THE '-' in the diff.
[14:25] <infinity> Man, I really need to wake up before I type.
[14:25] <infinity> Nevermind me. :P
[14:26] <mapreri> man, I was already yelling :|
[14:26] <mapreri> infinity: don't do it again! :>
[14:26] <infinity> I think I should find some breakfast and/or coffee before I continue.
[14:27] <infinity> Two "I can't read" moments within half an hour isn't a good record.
[14:27] <mapreri> coffee that way -------->
[14:33] <jbicha> any Archive Admin interested in reviewing switcheroo-control in the Zesty new queue? it's a small pkg required for GNOME 3.24's dual gpu feature
[14:38] <ginggs> infinity: your ruby-specinfra upload did indeed fix varnish autopkgtests, thanks
[14:47] <infinity> ginggs: \o/
[14:57] -queuebot:#ubuntu-release- Unapproved: binutils-m68hc1x (zesty-proposed/universe) [1:2.18-8 => 1:2.18-9] (no packageset) (sync)
[14:57] -queuebot:#ubuntu-release- Unapproved: accepted binutils-m68hc1x [sync] (zesty-proposed) [1:2.18-9]
[15:07] -queuebot:#ubuntu-release- Unapproved: lvm2 (zesty-proposed/main) [2.02.167-1ubuntu2 => 2.02.167-1ubuntu5] (core)
[15:08] <LocutusOfBorg> lol infinity <3
[15:08] <LocutusOfBorg> the problem is not ENOCOFFEE
[15:08] <LocutusOfBorg> but EMONDAY
[15:08] <LocutusOfBorg> you are not alone
[15:09] <LocutusOfBorg> in Italy we just had daylight saving time switch, and I did woke up one hour before today, so my body has a two hours "jet lag" right now :)
[15:12] -queuebot:#ubuntu-release- Unapproved: s390-tools (zesty-proposed/main) [1.37.0-0ubuntu2 => 1.37.0-0ubuntu3] (core)
[15:15] <xnox> oh we are in the full frozen mode now.... horum.
[15:19] <infinity> xnox: A cherrypick that adds the new version to the changelog doesn't seem like a cherrypick?  What's the difference between this and just updating to the point release?
[15:20] <infinity> stgraber: That lvm2 upload is a bit wonky.  It seems to entirely scrub the previous versions from history?
[15:20] <infinity> stgraber: http://launchpadlibrarian.net/312918372/lvm2_2.02.167-1ubuntu4_2.02.167-1ubuntu5.diff.gz
[15:21] <xnox> infinity, 342 files changed, 3778 insertions(+), 3688 deletions(-) of refactor; rewriting of argument parsing; whitespace changes; and header includes reordering.
[15:21] <xnox> https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1671497/comments/4
[15:21] <ubot5> Ubuntu bug 1671497 in s390-tools (Ubuntu) "[17.04 - FEAT] Upgrade s390tools to version 1.37.1" [Low,In progress]
[15:21] <xnox> and minor renames of files and/or macros
[15:21] <infinity> xnox: Ahh, so maybe the bit here that's rubbing me the wrong way is you adding "1.37.1" news items to README, which implies this is 1.37.1
[15:22] <infinity> xnox: When really, it's 1.37.0 with a couple of upstream cherrypicks.
[15:22] <xnox> well i've cherrypicked all the worthy fixes.... all of which are described by the changelog entry, hence the pick up of the changelog entry too.
[15:23] <infinity> xnox: Yeah, but the way you've rewritten the readme says "this is 1.37.1", which it isn't.
[15:23] <infinity> Not even close.
[15:23] <xnox> true
[15:24] <infinity> This is what patch headers are for.  Don't muck with the upstream README, IMO.
[15:24] <xnox> i could take those changelog entries out of the patch; and stick them into debian/changelog instead?!
[15:24] <xnox> patch header is not end-user visible....
[15:24] <infinity> The debian changelog being more verbose also is never a bad idea.
[15:25] <infinity> Patch headers should record origin (assuming this was from a VCS, not just a diff of a tarball), and debian/changelog can absolutely document the bugs fixed.
[15:25] <xnox> public VCS :`(
[15:26] <xnox> there is this java webapp one has to click through to get to the tarball and accept GPL EULA
[15:26] <infinity> Mucking with the upstream readme would be more acceptable to me if you documneted the changes under "1.37.0 + Ubuntu patches" or something, but it still seems gross to document it there.
[15:26] <infinity> Hahahaha.  Have you told them that's BS?  We've done so in the past (with IBM even, I think), and won the argument.
[15:27] <infinity> Since the GPL explicitly places no burden on people downloading, only people redistributing.
[15:27] <infinity> Thus it's not an EULA at all.
[15:27] <xnox> i have. and they started to download the tarball and attach it to a launchpad bug reports for me.
[15:27] <infinity> *cough*
[15:27] <infinity> I'm laughing too hard to type.
[15:27]  * xnox now feels for real to be back from vacation
[15:28] <xnox> There was cause and effect and change of behaviour.... but an enterpice solution with a personal butler service.
[15:29] <infinity> Wow.  You win the creative spelling of the day award.
[15:29] <infinity> apw: Sorry, xnox's "enterpice" beats anything you'll come up with today.
[15:29] <rbalint> hi, who should be pinged for binary package removals? LP: #1671423
[15:29] <ubot5> Launchpad bug 1671423 in kineticstools (Ubuntu) "Please remove i386 binaries" [Undecided,New] https://launchpad.net/bugs/1671423
[15:30] <philroche> infinity: Thanks for the gce-compute-image-packages work :)
[15:32] <infinity> rbalint: A quick investigation looks like that bug should be titled "bcftools is FTBFS on 32-bit arches"?
[15:33] <xnox> infinity, i have not been typing on a keyboard for a whole week. (there was no wifi at the slope of the resort, where i was staying) my words per minute are way down.
[15:33] <infinity> Or... Some arches.
[15:33] <xnox> infinity, i already talked today about the release meetings at bluefun with pat as well.
[15:34] <rbalint> infinity: well it looks unlikely to be fixed #819617
[15:35] <rbalint> infinity: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819617  FTBFS: any-i386 - floating point idiosyncracies
[15:35] <ubot5> Debian bug 819617 in src:bcftools "FTBFS: any-i386 - floating point idiosyncracies" [Important,Open]
[15:35] <rbalint> rbalint: rbalint more patience :-)
[15:37] <rbalint> rbalint: infinity and kineticstools does not migrate due to the missing build
[15:38] <infinity> rbalint: Well, that was a long read.  Tempted to go read the upstream report too, but I have better things to do. ;)
[15:39] <rbalint> infinity: did not want to push you that far :-)
[15:41] <mapreri> apw: should I suppose you didn't manage to push the armhf timeout change to autopkgtest workers?  (re: diffoscope timeouting)
[15:41] <infinity> rbalint: Done.
[15:42] <rbalint> infinity: thanks!
[15:42] -queuebot:#ubuntu-release- Unapproved: rejected s390-tools [source] (zesty-proposed) [1.37.0-0ubuntu3]
[15:44] <infinity> jibel: Ugh.  That ubuntu-ui-extras upload is very not feature-freeze friendly.
[15:45] <stgraber> infinity: hmm, I wonder what's going on here... I uploaded 0ubuntu2 a couple weeks back and nothing since
[15:46] -queuebot:#ubuntu-release- New sync: ubuntu-filemanager-app (zesty-proposed/primary) [0.4+17.04.20170323-0ubuntu1]
[15:46] <infinity> stgraber: https://launchpad.net/ubuntu/+source/lvm2/+publishinghistory
[15:46] <stgraber> infinity: and rmadison tells me the only lvm2 in zesty right now is 2.02.167-1ubuntu2 (nothing in zesty-proposed)
[15:46] <infinity> stgraber: publishing history shows some upload and the deletion action?
[15:47] <infinity> s/the/then/
[15:47] <infinity> stgraber: By you, even. :P
[15:47] <infinity> stgraber: So, okay, let me diff against ubuntu2 to get something more readable.
[15:47] <stgraber> infinity: ah, yeah, almost forgot about that. It was a mistargeted PPA upload that made it to proposed and that I wiped from the archive before it had a chance to build
[15:48] <infinity> stgraber: Yep, the diff against ubuntu2 is indeed much more readably sane.  Accepting.
[15:48] -queuebot:#ubuntu-release- Unapproved: isso (zesty-proposed/universe) [0.10.6-2 => 0.10.6-2ubuntu1] (no packageset)
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted isso [source] (zesty-proposed) [0.10.6-2ubuntu1]
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted lvm2 [source] (zesty-proposed) [2.02.167-1ubuntu5]
[15:50] <infinity> slangasek: When the personal/unity8/whatever session landed in the default install, did we also do away with their blanket exception to abuse freezes?  I suspect we should have, not sure if we explicitly did?
[15:51] <infinity> (Asking because of a current landing that is very freeze-unfriendly)
[15:51] <infinity> (Which only affects the unity8 session)
[15:51] <infinity> (More stuff in brackets)
[15:58] <jibel> infinity, agreed it is not freeze friendly at all
[15:59] <jibel> infinity, hence my question last week if we could have an overlay for zesty, a blanket exception would work too
[16:00]  * infinity fixed ubuntu-archive-tools a bit better for powerpc removal.
[16:00] <davmor2> ( infinity ) thought I'd put you in () being as you loved them so much
[16:00] <infinity> jibel: My preference would be for removing the unity8 session from the default install, but I suspect I'd lose that argument. :/
[16:01] <jibel> infinity, right, that would stay your preference
=== MapspaM is now known as SpamapS
[16:12] -queuebot:#ubuntu-release- Unapproved: chrome-gnome-shell (zesty-proposed/universe) [8.2-0ubuntu1 => 8.2-0ubuntu2] (ubuntugnome)
[16:39] -queuebot:#ubuntu-release- Unapproved: update-manager (trusty-proposed/main) [1:0.196.22 => 1:0.196.23] (core)
[16:40] <slangasek> infinity, jibel: what's freeze-unfriendly about it?  unity8 is supposed to have strong upstream CI such that the release team should feel comfortable granting exceptions
[16:41] <infinity> slangasek: Did you look at the diff before making that statement?
[16:41] <slangasek> no, of course not
[16:41] <slangasek> what's in the diff? :)
[16:42] <infinity>  127 files changed, 6353 insertions(+), 1101 deletions(-)
[16:42] -queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (trusty-proposed) [1:0.196.23]
[16:42] <infinity> http://paste.ubuntu.com/24261929/
[16:43] <bdmurray> rbasak: I fix update-manager thanks for spotting that!
[16:43] <infinity> slangasek: I'm sure their CI is lovely, but that's a whole lot of change.
[16:43] <slangasek> infinity: ok. does it change the packaging?
[16:44] <infinity> And I don't buy the "upstream's CI is so good we don't care about freezes anymore" argument, or we'd take new versions of a lot more software than we do.
[16:44] <infinity> slangasek: No, it doesn't change the packaging.  How's that relevant?
[16:45] <slangasek> lots of upstreams have CI.  not a lot of upstreams have CI that it's been worth our time to grant exceptions around
[16:46] <slangasek> it's relevant because we should be able to trust upstream to be the authority on the quality of their code, and we should only have to get involved for integration questions
[16:47] -queuebot:#ubuntu-release- Unapproved: xorg-server (zesty-proposed/main) [2:1.18.4-1ubuntu9 => 2:1.19.3-1ubuntu1] (desktop-core, xorg)
[16:47] <jibel> slangasek, it adds printing support to ubuntu-system-settings
[16:47] <jibel> ie not a bug fix
[16:48] <jibel> OTOH, it has CI + manual verification of the silo
[16:48] <infinity> slangasek: So, I understand that's the argument we used for ci-train landings, I don't think we EVER used it for freeze exceptions.  The exception they had previously was based on the code not being delivered with the regular distro cadence.
[16:48] <infinity> slangasek: And I still don't buy the "Canonical upstreams are unique snowflakes wrt CI" argument.  Saying it doesn't make it true.
[16:49] <slangasek> I didn't say they were unique snowflakes
[16:49] <slangasek> what I'm saying is that if there are other upstreams with strong CI that are worth our effort to develop exceptions for, I would be ok with that
[16:50] <infinity> So, you'd be happy with new systemd upstream versions breaking freezes?
[16:54] <slangasek> I'm not sure I would consider systemd upstream's CI "strong", the coverage might be a bit weak
[16:55] <slangasek> I do actually in principle prefer having that package in a state that we can rely on the CI instead of constantly worrying about what may have broken with a package update
[17:01] -queuebot:#ubuntu-release- Unapproved: neutron (zesty-proposed/main) [2:10.0.0-0ubuntu3 => 2:10.0.0-0ubuntu4] (openstack, ubuntu-server)
[17:09] -queuebot:#ubuntu-release- Unapproved: linux-signed (zesty-proposed/main) [4.10.0-14.16 => 4.10.0-15.17] (core, kernel) (sync)
[17:09] -queuebot:#ubuntu-release- Unapproved: linux (zesty-proposed/main) [4.10.0-14.16 => 4.10.0-15.17] (core, kernel) (sync)
[17:10] -queuebot:#ubuntu-release- Unapproved: linux-meta (zesty-proposed/main) [4.10.0.14.16 => 4.10.0.15.17] (core, kernel) (sync)
[17:11] <infinity> rtg: Aww, crap.  Did my request just miss a new upload? :P
[17:11] <infinity> Oh well.
[17:11] -queuebot:#ubuntu-release- Unapproved: neutron-lbaas (zesty-proposed/universe) [2:10.0.0-0ubuntu1 => 2:10.0.0-0ubuntu2] (openstack)
[17:11] <rtg> infinity, well, -15 was already built in the PPA. It'll show up in -16
[17:12] <infinity> rtg: Off-by-1 error?  That's 14.
[17:12] <rtg> infinity, I just promoted -15 to -proposed
[17:12] <infinity> rtg: Oh, off-by-dumb error, I was reading the left side of queuebot's messages. ;)
[17:13] <rtg> infinity, your patch will make kernel freeze (in -16)
[17:13] <infinity> rtg: Ta.  It's currently making my tools lie, so I'm hoping to see that clear up.
[17:20] <nacc> infinity: would you be willing to process the src:vm-builder removal for 17.04? I think it would also require removing src:sandbox-upgrader and I'm not sure if the latter is used by the release team or not (i'm assuming not given that it's in universe)
[17:21] <nacc> infinity: LP: #1618899
[17:21] <ubot5> Launchpad bug 1618899 in vm-builder (Ubuntu) "vmbuilder fails with dist-upgrade with release xenial; remove vm-builder from zesty" [Low,Triaged] https://launchpad.net/bugs/1618899
[17:23] <infinity> rtg: Due to powerpc removal, the config/ changes are unreviewable (as expected).  Can you swear on a stack of bibles that nothing actually changed beyond "remove powerpc && updateconfigs"?
[17:25] <infinity> Oh, I guess I could review the final configs from the binaries instead.  I might do that to be paranoid.
[17:45] -queuebot:#ubuntu-release- Unapproved: munin (trusty-proposed/main) [2.0.19-3ubuntu0.3 => 2.0.19-3ubuntu0.4] (ubuntu-server)
[17:48] <rbalint> is there anything to be done for LP: #1672941 ?
[17:48] <ubot5> Launchpad bug 1672941 in cyrus-sasl2 (Ubuntu) "FTBFS with older versions of OpenSSL" [High,New] https://launchpad.net/bugs/1672941
[17:54] -queuebot:#ubuntu-release- Unapproved: stress-ng (zesty-proposed/universe) [0.07.26-1 => 0.07.27-1] (no packageset) (sync)
[17:55] -queuebot:#ubuntu-release- Unapproved: accepted stress-ng [sync] (zesty-proposed) [0.07.27-1]
[18:00] <rtg> infinity, only one config change other then powerpc, "UBUNTU: [Config] CONFIG_PINCTRL_GEMINILAKE=m"
[18:02] -queuebot:#ubuntu-release- Unapproved: neutron (xenial-proposed/main) [2:8.4.0-0ubuntu1 => 2:8.4.0-0ubuntu2] (openstack, ubuntu-server)
[18:04] -queuebot:#ubuntu-release- Unapproved: neutron (yakkety-proposed/main) [2:9.2.0-0ubuntu1 => 2:9.2.0-0ubuntu2] (openstack, ubuntu-server)
[18:06] <infinity> rtg: Kay, I'm diffing config-$(uname -r) from the binaries to confirm.
[18:29] -queuebot:#ubuntu-release- Unapproved: mate-desktop (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[18:31] -queuebot:#ubuntu-release- Unapproved: neutron-lbaas (xenial-proposed/main) [2:8.3.0-0ubuntu2 => 2:8.3.0-0ubuntu3] (openstack, ubuntu-server)
[18:31] -queuebot:#ubuntu-release- Unapproved: mate-settings-daemon (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[18:44] <tjaalton> i've uploaded xorg-server update to zesty, it was acked by Laney
[18:44] <mapreri> http://people.canonical.com/~ubuntu-archive/transitions/html/html/boost1.62.html
[18:44] <mapreri> this was last generated the 21st.  What happened?
[18:53] <barry> any thoughts on what we should do about emacs25.1+1-3ubuntu3?  It's been held up for several weeks due to failing/crashing tests on arm64  all other arches are fine.
[18:55] <nacc> barry: dannf has been looking into it
[18:55] <nacc> barry: but it's not easily reproducible, unfortunately
[18:55] <dannf> yeah, i haven't been able to reproduce it all for weeks now
[18:55] <nacc> barry: and it appears that it may have been happening for some time
[18:56] <barry> nacc, dannf thanks for looking into it.  have either of you looked to see if upstream has a bug on that?  i could look if you haven't yet.
[18:57] <dannf> barry: i did at the time and didn't see one. i also tried to reproduce w/ all usptream code back when i could reproduce it, and i couldn't break upstream
[18:58] <nacc> barry: i've not done any digging beyond what dannf has done -- i just have packages blocked by it :)
[18:58] <barry> dannf: that's interesting.  so perhaps it's a debian or ubuntu delta?
[18:58] <barry> nacc: :)
[18:59] <dannf> barry: my hope was that i could reproduce it in debian and get a bug filed there - iirc, the build failure is correlated with the REL_ALLOC=no change in debian
[18:59] <barry> i don't see anything in a quick search of gmame.emacs.bugs
[19:02] <barry> dannf: gotcha.  well, if i can help in any way, please do ping.  i don't have direct access to arm64 h/w tho.
[19:03] <dannf> barry: there's a canonical porterbox, but when i could reproduce it, it was only in a vm
[19:04] <barry> dannf: yep
[19:04] <dannf> barry: i'm sure we could provide you with hw access though
[19:04] <barry> dannf: that would be great
[19:07] <dannf> doko: is the mcdivitt you have deployed from our maas shareable?
[19:42] -queuebot:#ubuntu-release- Unapproved: rejected xorg-server [source] (zesty-proposed) [2:1.19.3-1ubuntu1]
[19:53] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (zesty-proposed) [4.10.0-15.17]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted mate-desktop [source] (zesty-proposed) [1.18.0-0ubuntu2]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted neutron-lbaas [source] (zesty-proposed) [2:10.0.0-0ubuntu2]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted mate-settings-daemon [source] (zesty-proposed) [1.18.0-0ubuntu2]
[19:58] -queuebot:#ubuntu-release- Unapproved: accepted chrome-gnome-shell [source] (zesty-proposed) [8.2-0ubuntu2]
[19:58] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (zesty-proposed) [2:10.0.0-0ubuntu4]
[20:06] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (zesty-proposed) [4.10.0.15.17]
[20:06] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (zesty-proposed) [4.10.0-15.17]
[20:12] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.10.0-15.17] (core, kernel)
[20:19] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.10.0-15.17]
[20:19] -queuebot:#ubuntu-release- New: accepted nama [sync] (zesty-proposed) [1.208-1]
[20:19] -queuebot:#ubuntu-release- New: accepted sdpb [sync] (zesty-proposed) [1.0-3]
[20:19] <rbalint> barry: you probably also saw in #842852 that emacs25.1+1-3 seems to fix crashes on amd64
[20:21] <rbalint> barry: letting it migrate manually seems to be a better state for zesty, maybe we hit a VM bug on arm64?
[20:22] <infinity> Letting it migrate "manually" breaks a ton of rdeps.
[20:22] -queuebot:#ubuntu-release- New binary: sdpb [ppc64el] (zesty-proposed/none) [1.0-3] (no packageset)
[20:22] -queuebot:#ubuntu-release- New binary: sdpb [s390x] (zesty-proposed/none) [1.0-3] (no packageset)
[20:22] -queuebot:#ubuntu-release- Packageset: 70 entries have been added or removed
[20:22] <infinity> emacs isn't exactly a leaf package.
[20:23] -queuebot:#ubuntu-release- New binary: sdpb [arm64] (zesty-proposed/none) [1.0-3] (no packageset)
[20:23] -queuebot:#ubuntu-release- New binary: sdpb [i386] (zesty-proposed/none) [1.0-3] (no packageset)
[20:23] <infinity> As much as I wish it were, so I could remove it from the archive and tell barry to just snap it instead. :P
[20:24] -queuebot:#ubuntu-release- New binary: sdpb [amd64] (zesty-proposed/universe) [1.0-3] (no packageset)
[20:24] -queuebot:#ubuntu-release- New binary: sdpb [armhf] (zesty-proposed/universe) [1.0-3] (no packageset)
[20:24] <barry> >:-|
[20:25] <infinity> :)
[20:26]  * barry joins forces with rbalint 
[20:31] <barry> rbalint: it looks like 842852 might already be fixed with -3 so we should try to get that through proposed first
[20:32] <infinity> Is it possible that it's the backtrace code that's choking, and fixing the warnings spit out in the build would paper over it?
[20:33] <infinity> Curiously, the Debian build doesn't throw warning on that same .el file (though it does on later ones).
[20:33] <infinity> That's a bit WTF.
[20:33] <barry> infinity: i was thinking something similar
[20:33] <barry> yeah
[20:38] <nacc> infinity: yeah, that's what made it a bit confusing
[20:38] <nacc> infinity: iirc, dannf's debugging
[20:39] <nacc> infinity: and we were trying to guess if the parallel=1 fix just papered over it before, but don't anymore (at least not consistently)
[20:39] <infinity> I also wonder if building on real hardware would fix it.
[20:39] <nacc> right
[20:39] <infinity> Cause we still have the power to do that.
[20:40] <infinity> Err, I might have the power to do that.  Maybe not.
[20:40] <nacc> i think that would be worth trying, if its possible :)
[20:42] <dannf> infinity: i think it is likely that real hw woudl fix it
[20:43] <infinity> That's disconcerting.
[20:43] <barry> indeed
[20:51] -queuebot:#ubuntu-release- Unapproved: xorg-server (zesty-proposed/main) [2:1.18.4-1ubuntu9 => 2:1.19.3-1ubuntu1] (desktop-core, xorg)
[20:53] <tjaalton> Laney: new attempt ^
=== salem_ is now known as _salem
[21:04] -queuebot:#ubuntu-release- Unapproved: julia (zesty-proposed/universe) [0.4.7-6 => 0.4.7-6ubuntu1] (no packageset)
[21:04] -queuebot:#ubuntu-release- Unapproved: accepted julia [source] (zesty-proposed) [0.4.7-6ubuntu1]
[21:25] -queuebot:#ubuntu-release- Unapproved: eject (zesty-proposed/main) [2.1.5+deb1+cvs20081104-13.1 => 2.1.5+deb1+cvs20081104-13.1ubuntu1] (core)
[21:32] -queuebot:#ubuntu-release- Unapproved: debian-installer (zesty-proposed/main) [20101020ubuntu500 => 20101020ubuntu501] (core)
[21:53] <tsimonq2> infinity: Is there any chance you would let a new Lubuntu slideshow package in to Zesty within the next... idk... week? that would fix some glaring problems
[21:54] <infinity> tsimonq2: Yup.
[21:54] <infinity> tsimonq2: Slideshows kinda get a pass for obvious reasons.  You can't take screenshots of your finished product until post-freeze, when it's finished.
[21:55] <infinity> cyphermox: Which reminds me, do we have a slideshow update for Ubuntu for zesty, or is that going to be the usual last-minute panic?
[21:56] <infinity> Wow, it's had three revisions in zesty!
[21:56] <infinity> A miracle.
[21:56] <tsimonq2> infinity: bug 1633148 and another bug which shows our incorrect website is in a screenshot (lubuntu.net which someone is squatting versus lubuntu.me, our new one)
[21:56] <ubot5> bug 1633148 in ubiquity (Ubuntu) "Lubuntu 16.10 slideshow still incorrectly showing Lubuntu Software Center" [Undecided,New] https://launchpad.net/bugs/1633148
[21:56] <tsimonq2> infinity: That would be the main fixes.
[21:56] <tsimonq2> infinity: But I'm glad for the ack, thank you. :)
[21:56] <infinity> tsimonq2: Yeah, all good.
[21:59] <tsimonq2> infinity: Yeah, gilir was having doubts about uploading a slideshow at this point because of FF, I'll let him know you gave it an ack ;)
[22:09] <tsimonq2> infinity: He still hasn't gotten back to me on lubuntu-next yet, fyi
[22:21] -queuebot:#ubuntu-release- Unapproved: runc (zesty-proposed/universe) [1.0.0~rc2-0ubuntu3 => 1.0.0~rc2+docker1.12.6-0ubuntu1] (no packageset)
[22:22] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (zesty-proposed) [1.0.0~rc2+docker1.12.6-0ubuntu1]
[22:24] <bdmurray> infinity: Are you doing any SRU work today? I've a couple of uploads I'd prefer not to self-approve.
[22:24] <infinity> bdmurray: rbasak was taking my day, but I can look at a couple, I suspect he's EOD by now.
[22:25] <bdmurray> infinity: its update-manager & update-notifier in T and X, somebody already approved Y.
[22:28] <infinity> bdmurray: Way to look out for 2038 in a punctual manner.
[22:31] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (trusty-proposed) [1:0.196.23]
[22:33] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (trusty-proposed) [0.154.1ubuntu3]
[22:34] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.4]
[22:35] <infinity> bdmurray: Done.
[22:35] <bdmurray> infinity: thanks
[22:35] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (xenial-proposed) [1:16.04.6]
[22:36] -queuebot:#ubuntu-release- Unapproved: caja-dropbox (zesty-proposed/multiverse) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[22:43] <cyphermox> infinity: it's still a panic
[22:43] <cyphermox> infinity: I'm mangling the translations right now, about to test it
[22:43] <infinity> cyphermox: I dunno, I see an upload 7 days ago that looks promising.
[22:43] <cyphermox> it looks promising except for all the places where it still says 16.10.
[22:44] <infinity> \o/
[23:28] -queuebot:#ubuntu-release- Unapproved: zfs-linux (zesty-proposed/main) [0.6.5.9-5ubuntu1 => 0.6.5.9-5ubuntu2] (core)
[23:38] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (zesty-proposed) [0.6.5.9-5ubuntu2]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (zesty-proposed) [20101020ubuntu501]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted eject [source] (zesty-proposed) [2.1.5+deb1+cvs20081104-13.1ubuntu1]
[23:40] <infinity> flexiondotorg: That caja XDG_CURRENT_DESKTOP change will have a lot of knock-on effects.  Can you not just yell at dropbox instead?
[23:41] <infinity> flexiondotorg: Or is that somehow limited to only being in the environment when dealing with dropbox itself?
[23:42] <flexiondotorg> infinity So I discussed this with Laney earlier.
[23:43] <flexiondotorg> I've also prepare a debdiff for nautilus-dropbox, that checks if XDG_CURRENT_DESKTOP includes 'Unity' before exporting a modified environment.
[23:43] <flexiondotorg> I've tried, and am still trying, to get the attention of Dropbox.
[23:44] <infinity> flexiondotorg: Okay, maybe I'm mireading this.  Is the environment here limited to running some dropbox binary, and not being pushed back to the user's desktop environment?
[23:44] <flexiondotorg> The caja-dropbox changes is deliberately made this way so all DE can benefit.
[23:44] <flexiondotorg> LXDE, XFCE and MATE have been using my patched caja-dropbox for about a year now.
[23:44] <infinity> Question not being answered. :)
[23:45] <flexiondotorg> The environment change it just in the content of the Dropbox binary, not the whole session.
[23:45] <infinity> Right, okay.  Then it's fine.  I mean, super gross, but fine.
[23:45] <infinity> It was that context I was missing.
[23:45] <flexiondotorg> I was getting there :-)
[23:45] <infinity> Cause in the desktop session, claiming to be another DE ends up doing VERY WEIRD THINGS.
[23:45] <flexiondotorg> Indeed.
[23:46] <flexiondotorg> Laney asked me to fix nautilus-dropbox, the debdiff is ready and the approach used there was agreed with Laney.
[23:46] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1559249/comments/7
[23:46] <ubot5> Ubuntu bug 1559249 in nautilus-dropbox (Ubuntu) "Dropbox indicator is broken on non-Unity environments" [High,Triaged]
[23:46] <infinity> Oh, you no can upload that?
[23:46] <flexiondotorg> I have no super powers.
[23:46] <infinity> Slacker.
[23:47] <flexiondotorg> Says you. It's 00:45 here ;-)
[23:47] <flexiondotorg> infinity So if you can take a look at the debdiff for nautilus-dropbox that would be grand.
[23:48] <flexiondotorg> http://www.webupd8.org/2017/03/fix-dropbox-indicator-menu-not-working.html
[23:48] <infinity> flexiondotorg: So, I like the nautilus diff better, from my paranoid POV.
[23:48] <flexiondotorg> Yep.
[23:48] <infinity> flexiondotorg: As you're clearly only applying that env to the Popen.
[23:48] <infinity> flexiondotorg: Don't suppose that same clarity could be applied to the caja one?
[23:49] <flexiondotorg> Like I say, caja-cropbox is being used by XFCE and LXDE users too.
[23:49] <infinity> Yes...
[23:49] <infinity> I just mean, use the env.copy, then pass new_env trick.
[23:49] <infinity> Since changing os.env directly is less obviously not a leak.
[23:49] <flexiondotorg> And, in my testing, without passing a faux XDG_CURRENT_DESKOP recent Dropbox just doesn't work.
[23:50] <flexiondotorg> So use the say limit for just MATE in caja-dropbox?
[23:50] <infinity> I don't need you to explain the fix any more.  I get it.  I'm just asking it to look like the nautilus fix.
[23:51] <infinity> (minus the if)
[23:51] <flexiondotorg> Ah, right.
[23:51] <flexiondotorg> Can do.
[23:51] <infinity> ie: new_env = os.environment.copy(); new_env['XDG_CURRENT_DESKTOP'] = 'Unity'; sub.Popen(blah, env=new_env)
[23:52] <flexiondotorg> Wilco
[23:52] <infinity> Thanks.  I'm not an expert on python and os.env, but altering the environment directly when you really care about the env of a fork makes me twitch a bit.
[23:52] <infinity> So, better safe than lolz.
[23:53] <infinity> And I'll sponsor the nautilus fix for you, looks sane enough.
[23:53] <flexiondotorg> infinity Cheers. I'll let Laney know in the morning. I'll rework the caja-dropbox patch.
[23:54] <infinity> Ta.
[23:55] -queuebot:#ubuntu-release- Unapproved: rejected caja-dropbox [source] (zesty-proposed) [1.18.0-0ubuntu2]
[23:57] <infinity> flexiondotorg: Please use update-maintainer to update maintainers on Ubuntu changes, rather than setting the maintainer to yourself. ;)
[23:58] <infinity> flexiondotorg: Fixed that and the version number, and uploaded.
[23:58] <flexiondotorg> infinity OK. Noted. First time doing a change like that.
[23:58] -queuebot:#ubuntu-release- Unapproved: aptdaemon (yakkety-proposed/main) [1.1.1+bzr982-0ubuntu16.1 => 1.1.1+bzr982-0ubuntu16.2] (kubuntu, ubuntu-desktop)
[23:58] <flexiondotorg> infinity Thanks.
[23:59] -queuebot:#ubuntu-release- Unapproved: nautilus-dropbox (zesty-proposed/multiverse) [2015.10.28-1 => 2015.10.28-1ubuntu1] (xubuntu)