[03:18] If a bug turned out not to really be a bug and just something in the user's home directory, should the status be Invalid? === tasdomas_afk is now known as tasdomas [06:57] hello, can I get some help? [07:05] people are here at different times [07:05] please state your problem and have a little patience for people to respond [07:25] I added a new directory to my repo (copy and paste) but when I commit it doesn't list the new dir in the list. do I need to do something else before commiting? [07:30] "a new directory"? [07:30] you mean a new PPA? [07:31] sudheera: how did you call the new ppa? maybe any special character that could be a problem? [07:31] * pmjdebru1jn is just thinking out loud [07:32] nope I think I got it. I just executed "bzr add" and now it get the new dir. [07:32] oh, bzr repo [07:33] * pmjdebru1jn thought you mean a package repo :D [07:33] meant* [07:34] my bad [08:16] hi [08:18] I was wondering if someone could point me to the rifght direction - I have a package revipe on launchpad. When i use pbuilder on my machine to test build the package it goes fine - no problems. When I request build on Launchpad it fails: [08:18] dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 7) autotools-dev zlib1g-dev [08:19] what am I missing? [08:21] the dependancies are in the control file. Whe i test it with pbuilder it builds fine (on precise) and I can install the package no problem. [08:23] are you pushing the package for precise as well? [08:23] could you put the control file on a pastebin? and maybe the last entry of the changelog [08:26] pevma: particularly the last (the topmost) debian/changelog entry is of relevance [08:26] pevma: please post the +build link to the failing build on Launchpad [08:27] https://launchpadlibrarian.net/145325339/buildlog.txt.gz [08:27] That's much quicker than playing twenty-questions asking for specific details about the build [08:27] yes, i request build it on precise [08:28] hm, that's useful but not quite what I asked for [08:29] there should be a URL somewhere in your failure mail that contains the substring /+build/ [08:29] * State: Failed to build [08:29] * Recipe: oisf/suricata-libhtp-0.5.x-daily [08:29] * Archive: oisf/suricata-beta [08:29] * Distroseries: precise [08:29] * Duration: 3 minutes [08:29] * Build Log: https://launchpadlibrarian.net/145325339/buildlog.txt.gz [08:29] * Upload Log: [08:29] * Builder: https://launchpad.net/builders/charichuelo [08:30] is this what you had in mind? [08:30] No, but it allows me to find it [08:30] It was +recipebuild in fact - https://launchpad.net/~oisf/+archive/suricata-beta/+recipebuild/503159 [08:31] here is the control file - http://pastebin.com/0jrLr7ec [08:32] The build-dependencies look very overspecified to me, so it's possible that you've managed to confuse apt by giving it too many constraints [08:32] generally you don't need to specify runtime libraries there in addition to -dev [08:33] and [08:33] Depends: , [08:33] typically you'd some variables there [08:34] However, it seems to work locally ... [08:34] pevma: um - http://pastebin.com/0jrLr7ec doesn't match http://bazaar.launchpad.net/~oisf/suricata-daily-git-test/suricata-packaging-git/view/head:/debian/control which is what the recipe seems to be using? [08:35] hmm my chnage log looks wired - could that be the issue? - http://pastebin.com/fXng8fXB [08:35] Ah, never mind, I'm looking in the wrong place [08:35] pevma: no [08:35] By all means fix it but it doesn't matter here [08:35] ok [08:37] the package tha i am trying to build is from a git branch import, so i run dh_autoreconf as well in the rules file. However when i build it from source (not from git import) with the very same control file it works both locally and on Launchpad PPA [08:37] oh, I see [08:38] pevma: There is a blank line at the start of debian/control - remove it [08:38] nooooooooooooo [08:38] :) [08:38] don't tell that is it [08:38] :) [08:38] Curiously it doesn't appear in http://bazaar.launchpad.net/~oisf/suricata-daily-git-test/suricata-packaging-git/view/head:/libhtp/debian/control - I had to check out the branch locally to see it [08:39] i will give it a try now.. brb [08:39] regarding your Depends, you probably want libhtp1 to Depends: ${shlibs:Depends} [08:39] in fact, Depends: ${shlibs:Depends}, ${misc:Depends} [08:39] That would be usual [08:43] aaand i can't request more builds ! exceeded the quota .. [08:43] for the day [08:43] crap [08:47] ok, well I will try tomorrow again. Thanks a bunch guys ! [08:52] cjwatson: regarding " Depends: ${shlibs:Depends}, ${misc:Depends}" - what woudl that mean (forgive the silly question if such) ? [08:54] ${shlibs:Depends} - automatic dependencies for any shared libraries you link against. ${misc:Depends} - various miscellaneous dependencies generated by debhelper (should generally go in Depends for all binary packages in sources that use debhelper) [08:54] 10x [08:55] pmjdebru1jn: FWIW, this is why I always ask for the build link from LP rather than a pastebin of the control file - in this case the pastebin lost the information about the blank line at the start of the file, and generally it's far too easy to hide mistakes by accident that way [08:58] right [08:58] fair enough [08:59] cjwatson: http://bazaar.launchpad.net/~oisf/suricata-daily-git-test/suricata-packaging-git/view/head:/libhtp/debian/control - looks better ? [09:00] pevma: Yes. I'd recommend adding ${misc:Depends} to libhtp-dev's Depends too, but that won't block building [09:01] ok, thank you === tasdomas is now known as tasdomas_afk === tasdomas_afk is now known as tasdomas === tasdomas is now known as tasdomas_afk === mpt_ is now known as mpt === cyphermox_ is now known as cyphermox === matsubara is now known as matsubara-lunch === matsubara-lunch is now known as matsubara