[07:02] leave === JanC is now known as Guest51396 === JanC_ is now known as JanC === infinity changed the topic of #ubuntu-devel to: Zesty Released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: [09:23] infinity: Yay. I assume auto syncs don't run yet? Want to fix bug 1681231 (sync package, and upload it as an SRU to yakkety) [09:23] bug 1681231 in cracklib2 (Ubuntu) "package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed" [Undecided,Triaged] https://launchpad.net/bugs/1681231 [09:23] ...Is there a way to mark a package as expected to fail to build on an arch? [09:23] Unit193: Let it fail? [09:24] juliank: autosyncs probably won't be on for a day or two while people do some manual merges first. [09:24] Right, but it keeps emailing me... [09:24] Great. I synced manually now, and will prepare an SRU for yakkety shortly. [09:24] Also I'm not sure how we can have a reproducible test case here [09:25] s/yakkety/zesty/ [09:25] Or well, both even it seems [09:26] Although: If we only see the issue in zesty, probably no need to work around it in yakkety too [09:27] no artful template yet in /usr/share/python-apt/templates/Ubuntu.info [09:27] I know it's a bit early to nag about that :P [09:27] acheronUK: It's not been that long :D [09:28] but it did just break our CI builds [09:28] juliank: yep. I know. :) [09:29] Oh well, I'll SRU cracklib2 to both yakkety and zesty it seems, one of the linked bug reports complains about yakkety [09:36] If no one is working on the python-apt thing, I can do this quickly [09:37] juliank: if you have the time, that would be great [09:46] Actually, if I'm looking at this correctly then the issue should be fixed with golang 1.8 [10:07] Change is committed, upload is coming [10:10] acheronUK: Uploaded [10:10] juliank: thank you :) [11:01] Hmm, I guess I should just SRU (more parts of) cracklib 2.9.2-4 to xenial (2.9.2-1) too. (-2 fixes a CVE, -3 fixes a buffer overflow) [12:13] do programs written in java make it onto the ubuntu repos? or is it usually just c and python? [12:18] lol [12:33] cpaelzer, will you take care of strongswan please? :) (I'm listed as last uploader, but I just did a no change rebuild) [12:57] juliank: test regression on python-apt against update-notifier on s390x [12:58] acheronUK: retried it [12:58] thx. hoping it is just random weirdness of s390x [12:58] It's definitely not a python-apt regression [12:58] Could not connect to localhost:52117 (127.0.0.1). - connect (111: Connection refused) [12:59] Ah no, that happens everywhere [12:59] Anyway, no downloading changes anywhere [13:00] ooh. new retry button http://autopkgtest.ubuntu.com/packages/u/update-notifier/artful/s390x [13:00] yeah, just saw that too [13:03] acheronUK: And it passed [13:03] juliank: yep. just saw :) [14:22] acheronUK: Oh well, now snapcraft failed, but no new regression, already happened in prev build too (for squashfs-tools) [14:24] juliank: can that get through then? [14:26] Some tests are still in progress AFAICT [14:28] juliank: I meant the snapcraft fails being badtested [14:29] as at the moment looks like they would hold it back, regression or not [14:30] It looks like snapcraft itself regresses on armhf [14:30] On amd64 the upload run worked, but the python-apt caused one failed. [14:31] on armhf the upload run failed, with different errors than on amd64 [14:31] fun! [14:39] ok. if python-apt is going to be stuck in proposed for a bit, will have to start thinking about workarounds for our CI === mnepton is now known as mneptok [23:20] ginggs: I don't suppose you're around?