[04:40] <tachyons> cjwatson, dobey if you are not busy can you help me to find why this package failed to build in amd64
[04:40] <tachyons> https://launchpad.net/~aboobackervyd/+archive/apertium/+build/5393470
[04:48] <saiarcot895> tachyons: I think I can explain this; liblttoolbox3-3.2.so.0 is located in debian/lttoolbox/usr/lib, but not in /usr/lib, which is where it is expected to be.
[04:50] <tachyons> saiarcot895, thanks for your input, but I didn't got your point :-(
[04:50] <tachyons> debian/lttoolbox/usr/lib is the path while packaging isn't it?
[04:51] <saiarcot895> The shlibdeps is trying to find the libraries on which the applications are dependent on, and then include them as dependent packages. There are a set of paths that shlibdeps (anything, actually) looks in to find libraries; debian/lttoolbox/usr/lib isn't one of them
[04:52] <saiarcot895> It is the path for the packaging, but it's not included in the list of paths to check, in the same way that debian/lttookbox/usr/bin is not included in PATH
[04:53] <tachyons> saiarcot895, means I have to edit rules files to add it?
[04:53] <saiarcot895> In this case, I think you can just set the LD_LIBRARY_PATH here to include debian/lttoolbox/usr/lib, and shlibdeps will work fine
[04:53] <tachyons> BTW it works without any problem in i386
[04:53] <saiarcot895> tachyons: interesting, let me check that
[04:55] <tachyons> saiarcot895, https://launchpad.net/~aboobackervyd/+archive/apertium/+packages check this all i386 builds are success full
[04:55] <tachyons> but none of the amd64 build succeeded
[04:58] <tachyons> export DH_OPTIONS
[04:58] <tachyons> %:
[04:58] <tachyons> 	dh $@ --with autoreconf
[04:59] <tachyons> this my current rules file , I don't know how to configure dh-shlibdeps
[05:04] <saiarcot895> tachyons: ok, I'm not sure what it is; according to the i386 builds, it seems that the usr/lib folder is indeed included in the list of paths to check, so I'm not sure what the problem could be on amd64.  The only thing I can think of is that, on amd64, shlibdeps is expecting the library to be in usr/lib/x86_64-linux-gnu instead of /usr/lib (which should probably be true for everything except Precise), but in the case of Precise, then, it shouldn
[05:04] <saiarcot895> 't fail
[05:06] <tachyons> not only for precise, same output for precise to trusty
[05:06] <tachyons> 12.04 to 14.04
[05:07] <tachyons> saiarcot895, how can I tell to check usr/lib/x86_64-linux-gnu
[05:08] <saiarcot895> Well, it shouldn't fail on Precise because Precise didn't have the concept of multi-arch, so the libraries should be installed in /usr/lib instead of /usr/lib/x86_64-linux-gnu
[05:08] <tachyons> saiarcot895, what about other distros?
[05:09] <saiarcot895> tachyons: On that, I'm not entirely sure. If you're using cmake, I  think it's handled automatically by cmake. If you are installing manually, I think there's a way to check if the distro version is multi-arch
[05:10] <saiarcot895> tachyons: if you mean other distros as in outside of Ubuntu, no idea
[05:10] <tachyons> I mean other ubuntu versions
[05:10] <tachyons> it is using gnu make not cmake
[05:10] <saiarcot895> Quantal and up are multi-arch and so use usr/lib/x86_64-linux-gnu in amd64
[05:11] <tachyons> how to specify it in .install file?
[05:12] <saiarcot895> tachyons: I meant the build system itself, and the autoreconf switch tells me it's using autoconf
[05:12] <tachyons> saiarcot895, change build system to cmake?
[05:14] <saiarcot895> tachyons: I wouldn't change the build system to cmake just for this; at the moment I'm not sure what the problem could be, so I would wait for cjwatson or dobey to respond
[09:41] <dennis__> Hi there, I would like to provide ppa packages for both 12.04 and 13.10. Now the ppa only builds for 13.10. What do I have configure in this case? Is it possible to add the supported series in the changelog? Now it only contains 'saucy'.
[17:52] <tachyons> can any one help me on this issue , still not fixed :-(
[17:53] <tachyons> cjwatson, dobey
[18:00] <cjwatson> tachyons: I can't spend much time on this.  If multiarch is being a problem for this backport then you may need to apply http://wiki.debian.org/Multiarch/Implementation in reverse
[18:01] <tachyons> cjwatson, sorry for the disturbance , build failed in precise too
[18:01] <tachyons> afaik precise do not have multi-arch
[18:02] <dobey> precise has multiarch support
[18:03] <cjwatson> it does indeed#
[18:03] <cjwatson> but maybe not for all the build-dependencies
[18:03] <dobey> and your package isn't being built with multiarch anyway
[18:03] <cjwatson> dunno, I didn't really look hard at this build failure
[18:03] <cjwatson> maybe it's one of those that doesn't notice that it failed to actually build the library until it gets round to trying to install it
[18:04] <dobey> though the library package is named incorrectly-ish
[18:05] <tachyons> cjwatson, reading multi-arch documentation , I hope it will solve the issue
[18:05] <cjwatson> multiarch is clearly a red herring, having looked at this a bit harder
[18:05] <cjwatson> don't bother reading those docs
[18:05] <cjwatson> I wonder if it's depending on a feature of newer dpkg
[18:06] <dobey> the library did build and appears to have installed to the usr/lib/ dir as expected. no idea why shlibdeps isn't finding it. doing override_dh_shlibdeps isn't helping, surely
[18:06] <cjwatson> I vaguely recall dpkg-shlibdeps having been made nicer in this area recently-ish
[18:07] <dobey> Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
[18:07] <cjwatson> you might need:
[18:08] <cjwatson> override_dh_shlibdeps:
[18:08] <dobey> adding a .symbols file for the library should solve it
[18:08] <cjwatson>         dh_shlibdeps -ldebian/tmp/usr/lib
[18:08] <cjwatson> or similar
[18:08] <tachyons> let me try
[18:09]  * cjwatson -> out
[18:30] <tachyons> dobey, https://launchpadlibrarian.net/161105754/buildlog_ubuntu-raring-amd64.lttoolbox_3.2-1ubuntu9_FAILEDTOBUILD.txt.gz
[18:30] <tachyons> build failed again
[18:44] <tachyons> .
[18:58] <tachyons> dobey, are you there? :-)
[18:59] <tachyons> I took diff of two results
[18:59] <tachyons> debian/rules build-arch
[18:59] <tachyons> dh build-arch --with autoreconf
[18:59] <tachyons>    dh_testdir -a
[18:59] <tachyons>    dh_autoreconf -a
[19:00] <tachyons> debian/rules build
[19:00] <tachyons> dh build --with autoreconf
[19:00] <tachyons>    dh_testdir
[19:00] <tachyons>    dh_autoreconf
[19:00] <tachyons> why this difference?
[19:18] <Dudytz> hi all! I am noob in launchpad ... how to list all branches of a project with the "bazaar heads" command? eg: the project https://launchpad.net/~webupd8team/+archive/themes
[19:19] <Dudytz> I tried: bzr heads --tips lp:~webupd8team/ubuntu/raring/themes/master
[19:19] <Dudytz> and bzr heads --tips lp:~webupd8team/ubuntu/raring/themes
[19:19] <Dudytz> and bzr heads --tips lp:~webupd8team/themes
[19:19] <Dudytz> but always I get an error: You need to run this command either from the root of a shared repository,
[19:19] <Dudytz> or from a branch.
[19:21] <tachyons> Dudytz, you may have to use cd
[19:21] <tachyons> to source directory
[19:22] <Dudytz> but I dont have the source project ... I need a initial import
[19:22] <Dudytz> like a git clone
[19:25] <Dudytz> I need to clone this project: https://launchpad.net/~webupd8team/+archive/themes ... specifically the faience-azur-dark package .. for the ubuntu raring
[19:25] <Dudytz> how to do this with bazaar?
[19:27] <TheLordOfTime> i'm not sure git or bzr work very well with the PPAs...
[19:28] <TheLordOfTime> at least in terms of being able to "get" the source of something published inside a PPA (not sure though, don't take this as an answer)
[19:29] <Dudytz> ???
[19:29] <Dudytz> but bazaar is the version control of launchpad
[19:30] <Dudytz> I believe that all launchpad developers uses the bzr commands to clone, pull and push files to launchpad
[19:30] <JanC> packages aren't built from version control
[19:30] <Dudytz> like github
[19:30] <Dudytz> with the git command
[19:31] <JanC> are those themes in LP version control or elsewhere?
[19:32] <JanC> and you can get the source package using apt-get, of course
[19:32] <Dudytz> in lp
[19:32] <Dudytz> Yes, I can
[19:33] <Dudytz> But I need to learn to use launchpad .. to create branches of projects
[19:33] <JanC> you will have to ask the PPA maintainer(s) where the bzr repositories for those themes are then
[19:34] <Dudytz> oh god ...
[19:34] <Dudytz> the project is hosted in launchpad with bazaar
[19:37] <JanC> Dudytz: it seems to me like many of those themes were downloaded from gnome-look.org, deviantart.com & such?
[19:37] <Dudytz> JanC ... this is an example! I need to learn to "clone" a launchpad project
[19:39] <JanC> Dudytz: PPA & source repository are two separate parts of a LP project, they don't have to be used both, and in this case only PPA seems to be used for the themes
[19:41] <Dudytz> ok, thanks ... but I need to learn HOW TO CLONE A PROJECT
[19:41] <JanC> and 'themes' isn't a project, just a PPA of the user group 'webupd8team'
[19:41] <Dudytz> NOT THEMES GOOOOD
[19:42] <Dudytz> ITS AN EXAMPLE
[19:42] <Dudytz> GOOOOOD
[19:45] <JanC> ...
[19:46] <tachyons> cjwatson, dobey thanks issue resolved