=== JanC_ is now known as JanC === _salem is now known as salem_ [01:13] jbicha: iirc, imagemagick (and others) are stuck because of emacs25? [01:16] yes [01:19] 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] sarnold: in update_output.txt [01:20] sarnold: and the new emacs25 is stuck in z-p, which maybe has the fix (not confirmed yet) [01:20] sarnold: because it failed to build on arm64 :/ [01:20] sarnold: so stuck, but in a different place :) [01:51] 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 === maxb_ is now known as maxb === JanC_ is now known as JanC [02:07] juliank: nice, thanks === maclin1 is now known as maclin === salem_ is now known as _salem === rumble is now known as grumble === marcusto_ is now known as marcustomlinson_ === marcustomlinson_ is now known as marcustomlinson === Foxtrot is now known as foxtrot === _salem is now known as salem_ === salem_ is now known as _salem === _salem is now known as salem_ === hikiko is now known as hikiko|ln [13:08] doko: ping can we get them out of binary new as well? [13:13] 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] 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] https://people.canonical.com/~ubuntu-archive/sync-blacklist.txt [13:24] sunweaver: anything that has an Ubuntu delta because of "ubuntu" in the package version string. [13:24] (or for some other reason, for example Ubuntu is "upstream" of Debian) [13:24] Plus the sync blacklist. [13:24] (as jbicha mentions) [13:24] this shows some packages that have been deleted from Ubuntu but still present in Debian unstable [13:24] https://people.canonical.com/~ubuntu-archive/auto-sync/current.log [13:24] That's it. Everything else is auto-synced every cycle AFAIK. [13:32] jbicha: rbasak: thanks. [13:32] funnily, the package was not shown to be in Ubuntu on Debian's DDPO page. [13:33] 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. === hikiko|ln is now known as hikiko === jamespage_ is now known as jamespage [15:13] 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] seb128: I can do the LP side on Monday. Do you know how to do the other bits? [15:21] 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] seb128: Sounds plausible. I don't know that side of things well. [15:22] I'll let you know when we set up the LP cronjob. [15:25] 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] seb128: That sounds ideal, indeed. [15:29] :-) === JanC is now known as Guest36981 === JanC_ is now known as JanC === pavlushka is now known as KindThree === KindThree is now known as pavlushka [19:43] sunweaver: You already got answers, but there's also https://launchpad.net/ubuntu/zesty/+missingpackages [23:32] bdmurray: Can you provide some context to LP 1667843? [23:32] Launchpad bug 1667843 in icecast2 (Ubuntu) "/usr/bin/icecast2:11:source_shutdown:source_main:source_client_thread:source_fallback_file:_start_routine" [Undecided,New] https://launchpad.net/bugs/1667843 === salem_ is now known as _salem [23:41] There's a full stacktrace in the Error Tracker for it [23:43] Right, but that doesn't help me.. [23:44] Unit193: The stacktrace at the error tracker doesn't help you or you don't have access to the error tracker? [23:45] Right, sorry. I don't have access to it, so right now the only useful bit I can see is the title. [23:46] Okay I copied the Stacktrace since there wasn't anything private in it. [23:46] Thanks! [23:49] Do we want to ignore the apt test failure on armhf? [23:49] Tried 5 times or so, does not seem to start working [23:49] Stupid timing-dependent test