[ooo-build] patching issues

Andreas Radke a.radke at arcor.de
Thu Aug 6 08:48:43 PDT 2009


Am Thu, 6 Aug 2009 16:02:43 +0200
schrieb Petr Mladek <pmladek at suse.cz>:

> On Thursday 06 August 2009, Andreas Radke wrote:
> > Am Thu, 6 Aug 2009 00:40:47 +0200
> >
> > schrieb Rene Engelhard <rene at debian.org>:
> > > Did you change that? The patch is included in upstream and thus
> > > it's only applied for < ooo310-m16.
> > >
> > > Regards,
> > >
> > > Rene
> >
> > no. didn't change anything to my last alpha2 build. had to add
> > --with-tag=ooo310-m17 or it automatically took m14.
> 
> Does it mean that it helped you to force ooo310-m17 with
> --with-tag=ooo310-m17 or do you still see the problem?
> 
> It is strange because I see DEFAULT_TAG=ooo310-m17 in 
> ooo-build-3.1.0.99.2/configure.in.
> 
> 

I'm using the provided download tarball:

_mirror="http://download.go-oo.org/"
source=(${_mirror}/${_go_tree}/ooo-build-${_GOver}.tar.gz

and I don't run autoconf stuff again. Guess what's in configure...

DEFAULT_TAG=ooo310-m14
# For the upstream packages it is like:
# DEFAULT_TAG=OOO310_m1



-Andy


More information about the ooo-build mailing list