[16:27] <dobey> how does one copy packages from ubuntu archive into a ppa, on launchpad web site? or does one need to use some cli tool?
[17:08] <sidi> Hitting an issue with a slightly weird package which I suspect might be LP specific. I need one of my packages to have a file in /usr/local/bin/ (can explain why if necessary). I'm currently adding the file to my *install files, overriding dh_usrlocal so it doesn't complain, and dh_gencontrol is failing my package because I have files in /usr/local (build log: https://launchpadlibrarian.net/220540588/buildlog_ubuntu-trusty-i386.libpreload-logger_0.23_BUI
[17:08] <sidi> LDING.txt.gz). Works fine on my machine with debuild so not sure why LP refuses it (other than files in /usr/local being very very bad)
[17:08] <sidi> hm, silly IRC client... https://launchpadlibrarian.net/220540588/buildlog_ubuntu-trusty-i386.libpreload-logger_0.23_BUILDING.txt.gz
[17:10] <dobey> why do you need that in /usr/local/bin?
[17:12] <sidi> dobey, i'm using a library for data collection on ubuntu systems (part of a scientific study), that library is incompatible with internals of Chrome's NativeClient and seccomp2 sandboxes (for a lot of reasons, some of which we haven't figured out yet). I'm adding a /usr/local/bin/chromium-browser script that turns the library off and then calls the real chromium
[17:12] <sidi> we can provide support to study participants if that doesn't work for them, but I need to start that study before the end of the week or I'm losing some of my funding, so I don't have time to do things the proper way
[17:13] <sidi> and running my own chromium-browser package means lots more admin work since it's a package that is often updated, with the risk that participants update their packages before I get to update my own PPA package, go back to the real chromium and end up with a browser that doesn't work any more
[17:17] <dobey> i don't know why launchpad builder gives you an error if sbuild works fine locally (you did build with sbuild locally, right?), as i don't know enough about the builder configuration to answer
[17:17] <sidi> it does work locally with "debuild"
[17:22] <sidi> cjwatson, i'm curious if you know the way out of that one... ^ (TLDR: need a file installed in /usr/local but LP specifically refuses to build packages with files in there)
[20:55] <cjwatson> dobey: it's not discoverable, but you can do it from https://launchpad.net/ubuntu/+archive/primary/+copy-packages
[20:57] <cjwatson> sidi: NO_PKG_MANGLE=1 dh_builddeb, although that will have some other effects like suppressing changelog stripping and png optimisation
[20:57] <cjwatson> sidi: you would be able to reproduce it locally if pkgbinarymangler were in your chroot
[20:58] <cjwatson> sidi: there's another approach though, you could install /usr/bin/chromium-browser and use dpkg-divert in your maintainer scripts to divert the real one aside - a little harder to get right but not by very much, and more reliable in the face of things like different PATH ordering
[21:05] <sidi> cjwatson, i am totally positive that i didnt understand your last suggestion
[21:06] <cjwatson> sidi: https://www.debian.org/doc/debian-policy/ap-pkg-diversions.html
[21:06] <cjwatson> I appreciate you're in a rush, just it may be worth knowing of better approaches
[21:08] <sidi> ok, that sounds like the proper way to do things, i'm actually pleased there is a mechanism for it
[21:08] <sidi> but let me try the "easy" way first, though
[21:10] <sidi> cjwatson, are you saying I should change my rules to override the dh_builddeb step and make sure NO_PKG_MANGLE is set to 1, or I should locally build packages this way and then upload binary packages?
[21:12] <cjwatson> sidi: Launchpad will never accept binary package uploads
[21:12] <cjwatson> sidi: so I mean the former
[21:13] <sidi> Alright, let me try that
[21:17] <dobey> you could just "export NO_PKG_MANGLE=1" in debian/rules i guess, no?
[21:18] <cjwatson> you could, but I wouldn't.
[21:19] <cjwatson> better to be narrow.
[21:19] <cjwatson> that variable does things to other stages as well.
[21:20] <cjwatson> (notably dh_strip / debugging symbols)
[21:33] <dobey> oh
[21:35] <sidi> i'm sometimes genuinely amazed by the amount of knowledge you have of debian packaging...
[21:37] <sidi> I must've done something stupid, but https://launchpadlibrarian.net/220563791/buildlog_ubuntu-trusty-amd64.libpreload-logger_0.25_BUILDING.txt.gz is what I get with NO_PKG_MANGLE=1
[21:37] <sidi> "dpkg-deb: error: failed to open package info file `debian/libpreload-logger1/DEBIAN/control' for reading: No such file or directory"
[21:40] <sidi> Do I need to manually move my control files in my install step?
[21:52] <cjwatson> sidi: wuh what
[21:52] <cjwatson> sidi: I'll look in a bit, you have a disastrously broken rules file somehow
[21:52] <cjwatson> dh_builddeb being called waaaaaay too early
[21:54] <cjwatson> sidi: override_dh_builddeb not override dh_builddeb
[21:54] <cjwatson> underscore not space
[21:56] <cjwatson> if you ever find yourself having to muck about in .../DEBIAN/ directly during a build then you have done something wrong :-)
[21:58] <sidi> oh god did I do that again?
[21:58] <sidi> cjwatson, i sincerely apologise, i'm not exactly sober at this time of day
[22:15] <sidi> cjwatson, seems it's working properly
[22:16] <sidi> thank you for being up this late :-)
[23:39] <cjwatson> sidi: cool cool