[16:38] <szxzx> running into an issue trying to backport a couple of packages to xenial – "Depends: debhelper (>= 9) but it is not going to be installed" – even though I've enabled xenial-backports on the PPA and it seems to have a newer version (https://packages.ubuntu.com/xenial-backports/debhelper). any help would be appreciated!
[16:38] <cjwatson> That means that your PPA or its dependencies have something that makes the newer debhelper version uninstallable
[16:39] <cjwatson> Baseline xenial has debhelper >= 9 anyway
[16:40] <cjwatson> ("is not going to be installed" is apt's way of saying "I tried the requested version and it was available but its dependencies weren't satisfiable in combination with everything else you asked for"
[16:40] <cjwatson> )
[17:10] <szxzx> cjwatson: I see, how would I go about debugging it? is there anything that could help in the build log, or would I need to build it locally?
[17:11] <cjwatson> szxzx: I usually find "chdist" (in ubuntu-dev-tools) helpful - lets you set up a lightweight apt environment matching what your PPA is building with, and then you can try "chdist apt-get name-of-environment build-dep your-source-package-name"
[17:12] <cjwatson> see if that reproduces it, then convert it into a similar apt-get install line, and then you can add packages to that to force apt to eventually give you a more helpful message
[17:12] <cjwatson> if you can't figure it out then point me at the build and I can see if I can
[17:18] <kyrofa> Hey, do we have arm back? I'm starting to get emails about build failures again
[17:19] <nacc> kyrofa: see /topic
[17:20] <kyrofa> nacc, ah, thank you. So easy to miss those when you have a bouncer
[17:20] <nacc> kyrofa: :)
[17:23] <cjwatson> The queues are still draining, but they should only take another day or so now
[17:48] <szxzx> cjwatson: installing debhelper in chdist fails with "dpkg: dependency problems prevent processing triggers for systemd: systemd depends on libsystemd0 (= 229-4ubuntu21); however: Version of libsystemd0:amd64 on system is 229-4ubuntu4." – would appreciate help deciphering!
[17:49] <cjwatson> szxzx: um, I perhaps should have said, you aren't meant to actually continue with the install
[17:49] <cjwatson> szxzx: just purely running apt's dependency checks and then saying no.  you'll need to revert any installations that happened
[17:50] <szxzx> sorry, using webchat and it timed out and cleared the logs... had to improvise from memory :)
[17:50] <cjwatson> szxzx: so this will have actually installed stuff on your dev system, which was not at all the intent of my recommendation :)
[17:50] <cjwatson> szxzx: could you point me at the failing build, please?
[17:51] <szxzx> cjwatson: no worries, running in a throwaway docker container
[17:51] <szxzx> cjwatson: https://launchpad.net/~szxzx/+archive/ubuntu/caffe/+build/14255673
[18:00] <cjwatson> szxzx: OK, so xenial-backports isn't relevant here because this PPA has debhelper in it directly.  Did you have to copy that in for some other package?
[18:01] <cjwatson> szxzx: https://paste.ubuntu.com/26438883/ shows the problem - the version of debhelper you have in your PPA depends on other things that aren't available
[18:01] <cjwatson> (slightly mangled paste on line 6, sorry)
[18:01] <szxzx> cjwatson: nope, I'll go ahead and remove backports
[18:01] <cjwatson> szxzx: that won't do anything
[18:02] <cjwatson> szxzx: it's not about whether you have backports enabled; it's the fact that you have an uninstallable version of debhelper *in your PPA*
[18:02] <cjwatson> https://launchpad.net/~szxzx/+archive/ubuntu/caffe/+packages
[18:02] <szxzx> cjwatson: yeah, just replying to your first comment asking about backports. I realize that's not what's causing the issue
[18:02] <cjwatson> backports may make a difference down the line, I don't know, but it's not the problem here
[18:02] <cjwatson> OK
[18:04] <szxzx> cjwatson: so if I just delete debhelper from my PPA that would be a good start, right? started this last week and I can't remember why I added it TBH
[18:05] <cjwatson> szxzx: Right, if you don't know then that's probably a reasonable response.  If you do need to put it back then you'll need to make sure that those of its dependencies that aren't in xenial{,-security,-updates} are also included
[18:05] <cjwatson> szxzx: (you'll need to wait for a PPA publisher cycle before retrying the build - make sure debhelper actually disappears from the PPA)
[18:18] <szxzx> cjwatson: ok, now I see why I added debhelper in the first place. the actual package I was trying to build wants debhelper >= 10, and at that point I wasn't aware that it exists in backports
[19:29] <milki> hi, im getting a 503 from the 1.0 api saying its being upgrade?
[19:30] <milki> is there a different api i should be using?
[19:50] <milki> cjwatson: hi
[19:50] <milki> cjwatson: i see in the logs you helped someone earlier today
[19:52] <nacc> milki: which api?
[19:53] <milki> nacc: im hitting https://api.staging.launchpad.net/1.0
[19:53] <nacc> milki: hrm, that does not 503 for me
[19:53] <milki> hm
[19:53] <milki> ok
[19:53] <nacc> milki: that url itself 503s for you?
[19:53] <nacc> milki: in a browser, e.g
[19:53] <milki> so maybe the rest of the url is wrong now
[19:53] <milki> yeah
[19:54] <milki> https://api.staging.launchpad.net/1.0/~git-core/+archive/ubuntu/ppa/?ws.op=getPublishedBinaries\&status=Published\&distro_arch_series=https://api.staging.launchpad.net/1.0/ubuntu/trusty/amd64\&binary_package_name=git\&exact_match=true
[19:54] <milki> is the original url
[19:54] <milki> so... im going to munge that and see what im getting wrong now
[19:54] <nacc> milki: yeah that also errors for me so it's somethig in the suffix
[19:55] <milki> cjwatson: nvm, nacc helped me out
[19:57] <milki> aha
[19:57] <milki> dropping staging worked
[19:57] <milki> >.>
[19:57] <milki> api.launchpad.net
[19:59] <milki> nacc: thanks for rubber ducking with me
[19:59] <nacc> milki: np :)
[20:50] <jfmcarreira> heyyy guys
[20:50] <jfmcarreira> any help with this error? https://launchpadlibrarian.net/354303990/buildlog_ubuntu-bionic-amd64.playuver_0.18.1-1-201801221931~ubuntu18.04.1_BUILDING.txt.gz
[20:51] <nacc> jfmcarreira: do those files exist?
[20:53] <jfmcarreira> nacc: it shows "-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/lib/libPlaYUVerLib.so"
[20:53] <jfmcarreira> nacc: this is a app that i am trying to split into different  pkgs
[20:53] <jfmcarreira> without luck
[20:53] <jfmcarreira> nacc: i trying to run debuild -us -uc -b and it worked on a ubuntu machine
[20:54] <nacc> jfmcarreira: do you have a link to the srcpkg?
[21:36] <cjwatson> milki: right, staging's weekly restore from the production DB hit a snag so it's down at the moment
[21:37] <milki> o, its related. ok
[21:37] <milki> thanks for the update
[21:37] <cjwatson> nacc: note that I pointed jfmcarreira at https://wiki.debian.org/Multiarch/Implementation#CMake (specifically the include(GNUInstallDirs) stuff) a few days ago for a similar problem.  Perhaps somebody with more time can work through the details of that with them
[21:39] <jfmcarreira> cjwatson: I implemented it the way the link pointed out
[21:39] <jfmcarreira> nacc: what you mean by srcpkg? source code?
[21:40] <cjwatson> jfmcarreira: OK, you didn't actually say that, you just repeated a very similar-looking question a while later, so it was hard to tell
[21:40] <nacc> cjwatson: thanks
[21:41] <nacc> jfmcarreira: a source package is the ... source that builds binary packages :)
[21:41] <nacc> jfmcarreira: if you have a link, i can try and see what's going wrong
[21:42] <jfmcarreira> nacc: let me do another test and I found out that I was not building the code after changes that cjwatson recommended
[21:42] <cjwatson> nacc: FWIW a handy trick (and it's way too opaque) is that you can try the number after PACKAGEBUILD- in the log and tack it onto the end of https://launchpad.net/builders/+build/
[21:42] <cjwatson> which then redirects to https://launchpad.net/~jfmcarreira/+archive/ubuntu/ppa/+build/14262379
[21:42] <jfmcarreira> nacc: this output comes from launchapad recipes so idk where I can find the srcpkg
[21:43] <nacc> jfmcarreira: well, i mean you must be building something yourself, right? ... what are you building, basically :)
[21:43] <nacc> cjwatson: ah thanks!
[21:43] <nacc> cjwatson: never knew that, but that is very helpful!
[21:44] <cjwatson> I'd rather that build logs just had a link to the build, but never got round to that ...
[21:44] <nacc> yeah there are a few links like that (relatively well-defined) that would be nice to have
[21:47] <jfmcarreira> cjwatson: nacc trying to build again with the latest code
[21:52] <cjwatson> hmm, GNUInstallDirs is supposed to set CMAKE_INSTALL_LIBDIR to have ${CMAKE_LIBRARY_ARCHITECTURE} at the end of it if it's set, but it's not obvious that it's doing so
[21:52] <cjwatson> might be worth cranking up cmake's debug output to see exactly what variables are being set
[21:54] <cjwatson> might also be worth seeing if there are any ordering requirements on when GNUInstallDirs is included - maybe it needs to come after some kind of compiler-detection code in the CMakeLists?
[21:57] <kugel> Hello. I can't log in to launchpad. I get a server error after passing ubuntu one login
[22:02] <cjwatson> kugel: do you get an OOPS ID?
[22:03] <cjwatson> kugel: (are you seeing what I wrote?  this is the third time I've replied to you)
[22:10] <kugel> cjwatson:  (Error ID: OOPS-0cf2cb01ee21acc5364a0ab6258bfa2a)
[22:11] <kugel> cjwatson: hm, looks like irssi's awayproxy didn't notify me
[22:18] <cjwatson> kugel: fix on its way, try again in a few minutes
[22:20] <kugel> cjwatson: thanks, good now. was this problem specific to my account?
[22:20] <cjwatson> kugel: yes and no; https://bugs.launchpad.net/launchpad/+bug/1607242
[22:21] <cjwatson> we'd imported a comment on some bugzilla or other from your email address in 2014
[22:21] <cjwatson> so there was a sort of placeholder record that conflicted
[22:21] <kugel> alright. thank you anyway
[22:21]  * cjwatson taps fingers waiting for the cron job to run
[22:22] <kugel> so now I can post on the glibc bug that's bugging me hard
[22:22] <cjwatson> kugel: there we go, should work now
[22:24] <kugel> I'm talking about https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1732550, it affects me on two systems. Is there anything I can do to bump it?
[22:25] <kugel> it's fixed upstream long ago, and should be backported into 2.26
[22:27] <kugel> kugel-e-merged was merged into my account? Never heard about kugel-e-merged
[22:27] <nacc> kugel: the bug question should be somewhere else (it's not really a LP question)
[22:29] <nacc> kugel: e.g, ubuntu-devel, or probably the lxd-relevant channel
[22:38] <cjwatson> kugel: "kugel-e" was the autocreated placeholder I mentioned earlier, and it got a "-merged" suffix a few minutes ago when it was merged
[22:38] <kugel> ah, ok
[22:38] <cjwatson> (merging was how we gave control of that email address to your account)
[22:38] <kugel> so, I would expect my account details list two email addresses, but it's still just the one I use to log in
[22:39] <cjwatson> why would you expect that?
[22:40] <kugel> cjwatson: because I misread your comment (I read other email address)
[22:40] <kugel> nevermind
[22:40] <cjwatson> ok :)
[23:42] <szxzx> hi there, I have an issue with backportpackage repeatedly timing out uploading a large-ish file. (my connection is solid AFAIK.) is there any way to retry/resume the upload without restarting the whole process?
[23:54] <jfmcarreira> still the same error https://launchpadlibrarian.net/354313578/buildlog_ubuntu-bionic-amd64.playuver_0.18.1-1-201801222211~ubuntu18.04.1_BUILDING.txt.gz