You only applied one of the two fixes, correct?
--martin

> -----Original Message-----
> From: [email protected] [mailto:sipx-dev-
> [email protected]] On Behalf Of Douglas Hubler
> Sent: Thursday, September 09, 2010 8:41 AM
> To: sipXecs developer discussions
> Subject: Re: [sipx-dev] RPM build failure in master-4.2
> 
> thx, applied
> 
> On Wed, Sep 8, 2010 at 9:45 PM, Martin Steinmann <[email protected]>
> wrote:
> > diff --git a/sipXcommserverLib/Makefile.am
> b/sipXcommserverLib/Makefile.am
> >
> > index 3c15754..40cedff 100644
> >
> > --- a/sipXcommserverLib/Makefile.am
> >
> > +++ b/sipXcommserverLib/Makefile.am
> >
> > @@ -1,8 +1,7 @@
> >
> >  ## Process this file with automake to produce Makefile.in
> >
> >  include config/project.am
> >
> >
> >
> > -RPMS = $(DEFAULT_RPMS) $(DEBUG_RPM) \
> >
> > -
> > $(DEST_RPM)/sipxcommserverlib-doc-
> $(SIPX_VERSION).$(RPM_TARGET_ARCH).rpm
> >
> > +RPMS = $(DEFAULT_RPMS) $(DEBUG_RPM)
> >
> >
> >
> >  EXTRA_DIST = \
> >
> >      config/sipX-config.in \
> >
> > diff --git a/sipXconfig/sipxconfig.spec.in
> b/sipXconfig/sipxconfig.spec.in
> >
> > index b761fb8..38d5aaf 100644
> >
> > --- a/sipXconfig/sipxconfig.spec.in
> >
> > +++ b/sipXconfig/sipxconfig.spec.in
> >
> > @@ -31,7 +31,6 @@ BuildRequires: jakarta-commons-collections
> >
> >  BuildRequires: ruby-devel
> >
> >  BuildRequires: rubygems
> >
> >  BuildRequires: rubygem-rake
> >
> > -BuildRequires: sipx-jasperreports-deps
> >
> >  BuildRequires: sipxcommons >= %version
> >
> >  BuildRequires: asciidoc
> >
> >  %if %{_vendor} == suse
> >
> >
> >
> >
> >
> > _______________________________________________
> > sipx-dev mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/
> >
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to