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