Re: Error in determine_new_packagename()

Sorry for my late reply, tested OK. Great job. On Mon, Feb 24, 2014 at 4:42 AM, Andrea Pescetti wrote: > On 22/02/2014 LOH KOK HOE wrote: > >> @pescetti, >> I notice that the revision number of the fixed you sent to me is rather >> old because when I issue the command `svn info | grep "Revision"

Re: Error in determine_new_packagename()

On 22/02/2014 LOH KOK HOE wrote: @pescetti, I notice that the revision number of the fixed you sent to me is rather old because when I issue the command `svn info | grep "Revision"`, I have this output `Revision: 1568993`. Well, what I meant is: - We had a similar problem with another configure

Re: Error in determine_new_packagename()

Dear all, I have the problem solve by using @Kay Schenk's suggestion, download the EPM source, build it (there was a guideline included in the source), and then set the --with-epm to the newly created EPM binary. @pescetti, I notice that the revision number of the fixed you sent to me is rather ol

Re: Error in determine_new_packagename()

On 21/02/2014 Oliver-Rainer Wittmann wrote: On 21.02.2014 15:11, LOH KOK HOE wrote: I have this: $ ./configure --with-epm-url=http://epm.sourcearchive.com/downloads/3.7-1/epm_3.7.orig.tar.gz This looks like as if your system epm is used instead of the needed epm 3.7 one. Unfortunately, I hav

Re: Error in determine_new_packagename()

Hi, On 21.02.2014 15:11, LOH KOK HOE wrote: I have this: $ ./configure --with-epm-url=http://epm.sourcearchive.com/downloads/3.7-1/epm_3.7.orig.tar.gz configure:11566: checking whether to enable EPM for packing configure:11577: checking for epm configure:11595: found /usr/bin/epm configure:1

Re: Error in determine_new_packagename()

I have this: $ ./configure --with-epm-url= http://epm.sourcearchive.com/downloads/3.7-1/epm_3.7.orig.tar.gz configure:11566: checking whether to enable EPM for packing configure:11577: checking for epm configure:11595: found /usr/bin/epm configure:11608: result: /usr/bin/epm configure:11633: che

Re: Error in determine_new_packagename()

Hi, On 21.02.2014 13:26, LOH KOK HOE wrote: @Oliver I did `source` every time I make a build, without `source`, there will be compile error complaining that build command not found. don't mind. I just want to be sure that this step is not forgotten. What does your configure 'tells' you about

Re: Error in determine_new_packagename()

@Oliver I did `source` every time I make a build, without `source`, there will be compile error complaining that build command not found. On Fri, Feb 21, 2014 at 4:10 PM, Oliver-Rainer Wittmann < orwittm...@googlemail.com> wrote: > Hi, > > > On 20.02.2014 14:39, LOH KOK HOE wrote: > >> During th

Re: Error in determine_new_packagename()

Hi, On 20.02.2014 14:39, LOH KOK HOE wrote: During the build, there was an error happen in instsetoo_native module where a function call determine_new_packagename causing the build stop. As I trace back the bug, I have this link and they ment

Re: Error in determine_new_packagename()

On 02/20/2014 05:39 AM, LOH KOK HOE wrote: During the build, there was an error happen in instsetoo_native module where a function call determine_new_packagename causing the build stop. As I trace back the bug, I have this link and they ment

Error in determine_new_packagename()

During the build, there was an error happen in instsetoo_native module where a function call determine_new_packagename causing the build stop. As I trace back the bug, I have this link and they mention this was cause by the epm module. The modul