[00:00] This is part of the source itself [00:01] https://launchpad.net/~surveymonkey/+archive/surveymonkey/+packages [00:01] Thats the package I built, libmemcached [00:01] in the .tar.gz there is a libmemcache-1.0 folder not being included [00:02] What is the .install file for? [00:02] the normal packaging is use upstream buildsystem to install into DESTDIR=debian/tmp [00:02] dh_install then installs from there into debian/package-name/ via the info in the .install files [00:03] those folders are then turned into packages [00:04] This is the folders in the package folder: http://paste2.org/LZ7yUvgA [00:04] Its installing libmemcached/ but not libmemcached-1.0/ [00:04] and same, libhashkit/ but not libhashkit-1.0/ [00:04] whats the install file? [00:05] http://paste2.org/DX9VL0Ws [00:05] so does each .install file represent a folder in the package? [00:06] so if I created a libmemcached-1.0.install, it'd autodetect? [00:06] no it are text files [00:07] Yeah, but inside they just have destination folders [00:07] they can [00:07] relative to debian/ [00:07] but its optional [00:09] I don't understand then. What is required to get the libmemcached-1.0 and libhashkit-1.0 directories shipped into /usr/include/ with libmemcached/ and libhashkit/ [00:10] they have to be installed by the buildsystem into debian/tmp [00:10] then you just list the path in the install file [00:11] I don't have a debian/tmp folder [00:11] it is created during the build [00:11] normally [00:11] the package can override it to a different name [00:11] or not have one if its a single binary package [00:11] I did debuild -S [00:12] debuild -S does not build a binary package [00:12] only a source package [00:12] that will not contain any build sources [00:12] binary packages are build without the -S argument [00:13] But when I put it on a PPA, I think they only want a source package [00:13] and then their build server builds the binary packages [00:13] yes [00:13] but you should build locally first [00:14] ok, so just run debuild? [00:14] for testing [00:14] yes [00:14] http://paste2.org/Z9D9XHHd [00:14] thats the error I get when running locally [00:15] you need to install build dependencies [00:15] I have build-essential [00:15] the best way is running. sudo mk-build-deps -ir [00:18] Looks like its working [00:22] ok, when I did it locally a libmemcached-1.0 folder is there in debian/tmp/usr/include/libmemcached-1.0 [00:22] so why doesn't the source package that was built on the build servers have it? [00:25] ls debian/tmp/usr/include/ [00:25] libhashkit libhashkit-1.0 libmemcached libmemcached-1.0 libmemcachedprotocol-0.0 libmemcachedutil-1.0 [00:26] ls -d /usr/include/libmem* /usr/include/libhash* [00:26] /usr/include/libhashkit /usr/include/libmemcached [00:26] you see, the installed package is missing all the header directories === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === j_f-f_ is now known as j_f-f [08:22] wgrant: I'm afraid that the comparison to Sid isn't working properly in MDT... can you take a look? [08:22] For example, the first package in the list (among many others) is in Sid, but it's marked as not found. [08:23] Also, the "universe" page stopped working. [08:47] Logan_: Ah, I didn't have the new signing key installed. [09:07] wgrant: Thanks for fixing it! :) [12:10] somebody around for some sponsoring ? [12:10] https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1252254 [12:10] Ubuntu bug 1252254 in opensc (Ubuntu) "OpenSC fails to authendicate with firefox" [Undecided,Confirmed] [13:21] seems quite silent here :( [13:21] :) === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === paddy_ is now known as paddy