How to report bug in build-deps?

[Colin Law]

On 11 September 2011 22:25, Ric Moore <wayward4now at gmail.com> wrote:
> On Sun, 2011-09-11 at 20:45 +0100, Colin Law wrote:
>> On 11 September 2011 19:40, Ric Moore <wayward4now at gmail.com> wrote:
>> > On Sun, 2011-09-11 at 11:59 +0200, Bruce Pieterse wrote:
>> >> On Sun 11 Sep 2011 11:51:14 SAST, Colin Law wrote:
>> >> > On 11 September 2011 10:45, Bruce Pieterse<octoquadza at gmail.com>  wrote:
>> >> >> On 11/09/2011 01:12, Patton Echols wrote:
>> >> >>>
>> >> >>> On 09/10/2011 09:16 AM, Colin Law wrote:
>> >> >>>>
>> >> >>>> On 10 September 2011 16:41, Bruce Pieterse<octoquadza at gmail.com>    wrote:
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>> Bruce
>> >> >>>>>
>> >> >>>>> On Sep 10, 2011 5:20 PM, "Colin Law"<clanlaw at googlemail.com>    wrote:
>> >> >>>>>>
>> >> >>>>>> When one does
>> >> >>>>>> sudo apt-get build-dep<some_app>
>> >> >>>>>> it should install all the packages to allow that app to be built.  How
>> >> >>>>>> do I report a bug in the build dependencies list for an app (there are
>> >> >>>>>> some deps missing).
>> >> >>>>>>
>> >> >>>>>> Do I just report it against the app itself?
>> >> >>>>>>
>> >> >>>>>> Google has failed me, or perhaps more accurately I have failed to
>> >> >>>>>> persuade google to help.
>> >> >>>>>>
>> >> >>>>> Hi Colin,
>> >> >>>>>
>> >> >>>>> What application are you trying to install and what does apt-get say for
>> >> >>>>> the
>> >> >>>>> dependencies?
>> >> >>>>
>> >> >>>> I think you have misunderstood my problem.  I am not attempting to
>> >> >>>> install an app, but install the *build* dependencies for the app, and
>> >> >>>> the build dependencies have missing packages.  So I want to report
>> >> >>>> that as a bug.
>> >> >>>>
>> >> >>>
>> >> >>> I am far from an expert, and can't even tell you where to look.  But I see
>> >> >>> this as a logic problem.
>> >> >>>
>> >> >>> the build-dep switch reads the<some-app>  source, finds the dependencies
>> >> >>> and installs them, right?
>> >> >>>
>> >> >>> One of two things is going on.  Either the source correctly lists the
>> >> >>> missing packages as dependencies and build-dep is missing them, or the
>> >> >>> source does not correctly list them.  It seems to me you need to figure out
>> >> >>> which.
>> >> >>>
>> >> >>> Someone with more knowledge of how such things work may give a better
>> >> >>> answer.
>> >> >>>
>> >> >> I'll be honest, I'm no expert to. lol. You can install gnucash with sudo
>> >> >> apt-get install gnucash. Is there a reason why you are building it from
>> >> >> source when it is already in repo?
>> >> >
>> >> > So that I can contribute to development of the software.
>> >> >
>> >> > Colin
>> >> >
>> >>
>> >> Ah, now I get it, my apologies! Well, let me grab the source code
>> >> myself and see if I can help out :)
>> >
>> > He'll need all of the .dev files that it needs in order to compile
>> > it. :) Ric
>>
>> Just to re-iterate, I am not building the Ubuntu version, but the
>> original project source ( git://github.com/Gnucash/gnucash.git) which
>> is why I ran into the problem, as the build-deps provide the packages
>> for building the Ubuntu version, not the original version.
>
> I thought that was a given, and that you understood.
>
> When you're compiling a source build you're on your own, regarding the
> dependencies. Watching the console will provide hints as you attempt tp
> compile it, as to what you are missing. USUALLY some .dev package, as I
> said.  If you were building an source .deb package it would pull in the
> depends for you.
>
> Again, that is a given, "just to re-iterate".

I know, I was re-iterating as I thought that maybe you had not picked
that up as I have known which dependencies I need right from the very
first post.  My confusion was that I thought the build-deps should
have automatically picked them all up, but I was wrong.  Anyway the
problem is no more and as I said I have marked the bug as invalid.

I am not sure what a .dev file is though.

Colin


-- 
gplus.to/clanlaw