[01:13] <nacc> jbicha: iirc, imagemagick (and others) are stuck because of emacs25?
[01:16] <jbicha> yes
[01:19] <sarnold> are you sure? here I see only 'Pass' and 'Always failed' results http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#imagemagick
[01:20] <nacc> sarnold: in update_output.txt
[01:20] <nacc> sarnold: and the new emacs25 is stuck in z-p, which maybe has the fix (not confirmed yet)
[01:20] <nacc> sarnold: because it failed to build on arm64 :/
[01:20] <nacc> sarnold: so stuck, but in a different place :)
[01:51] <juliank> If people here are interested: I'm currently looking add BLAKE2 for use in the repository (Packages and Release files). I posted some results on deity@l.d.o but really only amd64 so far
[02:07] <sarnold> juliank: nice, thanks
[13:08] <zul> doko: ping can we get them out of binary new as well?
[13:13] <sunweaver> hi! Where can I see what packages from Debian are _not_ pulled into Ubuntu on a regular basis. I.e. I am talking about a package that is in Debian, but not at all in Ubuntu.
[13:23] <jbicha> sunweaver: I don't have an exact answer to that but these packages are prevented from being synced to Ubuntu because either Ubuntu doesn't want them or the packaging differs:
[13:23] <jbicha> https://people.canonical.com/~ubuntu-archive/sync-blacklist.txt
[13:24] <rbasak> sunweaver: anything that has an Ubuntu delta because of "ubuntu" in the package version string.
[13:24] <rbasak> (or for some other reason, for example Ubuntu is "upstream" of Debian)
[13:24] <rbasak> Plus the sync blacklist.
[13:24] <rbasak> (as jbicha mentions)
[13:24] <jbicha> this shows some packages that have been deleted from Ubuntu but still present in Debian unstable
[13:24] <jbicha> https://people.canonical.com/~ubuntu-archive/auto-sync/current.log
[13:24] <rbasak> That's it. Everything else is auto-synced every cycle AFAIK.
[13:32] <sunweaver> jbicha: rbasak: thanks.
[13:32] <sunweaver> funnily, the package was not shown to be in Ubuntu on Debian's DDPO page.
[13:33] <sunweaver> But a closer look on Launchpad revealed, that the package is actually in zesty.
[13:33]  * sunweaver wonders if that is a qa.debian.org bug then.
[15:13] <seb128> wgrant, cjwatson, hey, do you know how are langpack exports enabled? we still don't have any, I think to remember that p_itti said that somebody should set up in the cron on the launchpad side
[15:20] <wgrant> seb128: I can do the LP side on Monday. Do you know how to do the other bits?
[15:21] <seb128> wgrant, I should, I went over that with p_itti before holidays, I think I just need to add a crontab line for zesty to the langpack-o-matic instance once the tarball is there
[15:22] <wgrant> seb128: Sounds plausible. I don't know that side of things well.
[15:22] <wgrant> I'll let you know when we set up the LP cronjob.
[15:25] <seb128> wgrant, thanks, I should be able to figure out the client side changes, let me just know the day you pick for the export so I can do the langpack build on the next day (https://dev.launchpad.net/Translations/LanguagePackSchedule suggest that export on tuesday would be good?)
[15:29] <wgrant> seb128: That sounds ideal, indeed.
[15:29] <seb128> :-)
[19:43] <Unit193> sunweaver: You already got answers, but there's also https://launchpad.net/ubuntu/zesty/+missingpackages
[23:32] <Unit193> bdmurray: Can you provide some context to LP 1667843?
[23:41] <bdmurray> There's a full stacktrace in the Error Tracker for it
[23:43] <Unit193> Right, but that doesn't help me..
[23:44] <bdmurray> Unit193: The stacktrace at the error tracker doesn't help you or you don't have access to the error tracker?
[23:45] <Unit193> Right, sorry.  I don't have access to it, so right now the only useful bit I can see is the title.
[23:46] <bdmurray> Okay I copied the Stacktrace since there wasn't anything private in it.
[23:46] <Unit193> Thanks!
[23:49] <juliank> Do we want to ignore the apt test failure on armhf?
[23:49] <juliank> Tried 5 times or so, does not seem to start working
[23:49] <juliank> Stupid timing-dependent test