[00:00] The warning about data.tar.xz is unrelated; that dpkg-deb invocation runs on the host, which uses an old version of dpkg that doesn't have xz binary support. [00:00] If you look at the precise build (eg. https://launchpadlibrarian.net/178105061/buildlog_ubuntu-precise-amd64.inkscape_0.48.5%2B31~ubuntu12.04.1_UPLOADING.txt.gz) you'll see that it has some files, but not many. [00:01] The build is successful. It just doesn't install any binaries into the package. [00:01] installing pt.gmo as /build/buildd/inkscape-0.48.5+31~ubuntu12.04.1/debian/inkscape-trunk/usr/share/locale/pt/LC_MESSAGES/inkscape.mo [00:02] LiamW: There's your problem. You've asked it to install itself to debian/inkscape-trunk, but your binary package is named "inkscape", not "inkscape-trunk". [00:02] ahh [00:03] # Add here commands to install the package into debian/inkscape. [00:03] /usr/bin/make install DESTDIR=/build/buildd/inkscape-0.48.5+31~ubuntu12.04.1/debian/inkscape-trunk [00:08] I don't see the words "trunk" anywhere important grepping through the packaging branch [00:08] $ grep -r trunk [00:08] changelog: * Renamed package to inkscape-trunk [00:08] control:Vcs-Browser: https://code.launchpad.net/~inkscape.dev/inkscape/trunk [00:08] control:Vcs-bzr: https://code.launchpad.net/~inkscape.dev/inkscape/trunk [00:08] control:Conflicts: inkscape-trunk [00:08] control:Description: vector-based drawing program (trunk build) [00:08] and no, it's the right branch [00:13] wgrant: where might that line appear in the packaging branch? [00:13] would it even be in the packaging branch? [00:31] did I accidentally flood? [00:31] my bouncer is normally supposed to prevent that, but hey [00:32] /tmp/recipe-0.48.5+{revno:packaging}$ grep -r inkscape-trunk [00:32] debian/changelog: * Renamed package to inkscape-trunk [00:32] debian/control:Conflicts: inkscape-trunk [00:32] debian/rules: $(MAKE) install DESTDIR=$(CURDIR)/debian/inkscape-trunk [00:33] Which is weird, since the packaging branch's debian/rules looks nothing like that. [00:33] I suspect some part of the upstream inkscape build system is clobbering debian/rules. [00:33] Or something? [00:33] I grepped around for the words "trunk" and "DESTDIR" in the stable branch [00:33] didn't find anything [00:34] well, anything relevant [00:34] Oh! [00:34] http://bazaar.launchpad.net/~inkscape.dev/inkscape/debian-packaging-stable/revision/32 [00:34] That's a few hours after the latest recipe build. [00:35] And it fixes debian/rules. [00:35] But the recipe hasn't been rebuilt since. [00:35] let me do that now [00:36] done [00:36] https://code.launchpad.net/~inkscape.dev/+recipe/inkscape-stable [01:12] build score over 90000? https://code.launchpad.net/~inkscape.dev/+archive/ubuntu/stable/+build/6206934 [01:12] I want to see if it works now :) [01:24] wgrant: on a different (but related) branch, precise always fails to build: https://launchpadlibrarian.net/180616225/buildlog.txt.gz [01:24] "make: dh: Command not found" [01:24] it has the same build-deps as the stable and trunk recipe builds [01:24] but it only fails in precise [01:25] dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting. [01:25] dpkg-buildpackage: warning: (Use -d flag to override.) [01:25] dpkg-buildpackage: warning: This is currently a non-fatal warning with -S, but [01:25] dpkg-buildpackage: warning: will probably become fatal in the future. [01:25] Look in the log for "The following packages have unmet dependencies:" [01:26] I found this: [01:26] "No packages found matching linux-image-[0-9]*." [01:26] That's unrelated. [01:26] The following packages have unmet dependencies: [01:26] pbuilder-satisfydepends-dummy [01:26] ... [01:26] "Unable to resolve dependencies! Giving up..." [01:27] LiamW_: precise only has libcairo 1.10 [01:27] You build-depend on 1.12 [01:29] hmm, that will mean no gradient meshes [01:29] even though I had them working on precise before (maybe I had newer cairo?) [01:29] I don't know [01:29] http://packages.ubuntu.com/precise/libcairo2 [01:30] I'll be looking way back through my IRC logs, just a moment [01:34] on precise, I had 1.12.2 [01:35] libcairo2-dev | 1.10.2-6.1ubuntu2 | precise | amd64, armel, armhf, i386, powerpc [01:35] libcairo2-dev | 1.10.2-6.1ubuntu3 | precise-updates | amd64, armel, armhf, i386, powerpc [01:35] I have a code with some .a files, launchpad ignores they when it is building a package? [01:35] sergio-br2: build logs? [01:35] sergio-br2: Launchpad just runs dpkg-buildpackage, which does whatever your debian/rules tell it to do. [01:36] funny, with the same code, i can build it here with sbuild, but launchpad complains about some libraries [01:37] Are you sure it's using exactly the same library packages? [01:37] LiamW, https://launchpadlibrarian.net/180616209/buildlog_ubuntu-trusty-amd64.ppsspp_0.9.9-0ubuntu2~ubuntu14.04.1_FAILEDTOBUILD.txt.gz [01:37] i think so [01:37] augh that makefile [01:39] sergio-br2: You don't build-depend on any of those libraries. [01:40] So they're not going to be installed. [01:40] those libraries are embedded in the code [01:40] oh dear [01:40] sergio-br2: consider cleaning up the Makefile.am for that package [01:41] automake is perfectly capable of generating a simple "CXX" compared to showing the full compiler invocation [01:41] while at the same time being verbose about the link [01:42] Anyway, I don't see libavcodec being built in that build. [01:42] So your debian/rules probably isn't building it. [01:47] no, libavcodec and others are already compiled in the source code [01:47] sergio-br2: your debian/rules is a little complicated [01:47] (upstream approach ...) [01:47] sergio-br2: will a simple "../configure && make" build everything on your machine? [01:48] yeah, i need to improve it [01:48] but works in my machine [01:48] ok [01:48] then a few lines rules file will work [01:49] sergio-br2: http://bazaar.launchpad.net/~inkscape.dev/inkscape/debian-packaging-stable/view/head:/rules [01:49] base your rules off of that, maybe, since nothing complicated is going on there [01:52] in that case, you don't even need to override dh_auto_configure since a simple ../configure will work [01:53] humm, OK [01:53] so basically, this [01:53] %: [01:53] dh $@ --with bash-completion,python2 --parallel [01:53] or if your package doesn't have bash completion or need python to build, it's easier [01:53] dh $@ --parallel [01:59] sergio-br2: http://bazaar.launchpad.net/~inkscape.dev/inkscape/debian-packaging-stable/revision/32#rules [02:00] this project, ppsspp, I have to run qmake first, it does not use ./configure [02:01] then override dh_auto_configure [02:01] override_dh_auto_configure: [02:01] like export NOCONFIGURE=true && qmake [02:01] ? [02:01] qmake . [03:32] wallyworld, get a bouncer dude [03:35] LiamW: it's only freenode, nfi what its problem is [03:36] constant disconnects? If your connection is unstable (mine is) it's probably a good idea to have one [03:40] LiamW: i've not ever set up one before, nor do i know how to do it. i'll ask google :-) === s8321414_ is now known as s8321414 [17:36] anyone help with this error: http://launchpadlibrarian.net/180529917/q-launchpad-z-q-gears-paul.log I've rewrite the git history using those python functions and still get this error :( === JanC_ is now known as JanC