Bug#352051: works on sid?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this seems to work for me on current sid... Can you confirm that? Screenshot of my attempt: (2.0.2-2 + 2.0.2-3 parts): http://people.debian.org/~rene/352051-works.png Regards, Rene -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux)

Re: 2.0.3 Sarge Backport: agg pyuno compat

Hello, > Rene Engelhard wrote: > > > SYSTEM_AGG=n (no package libagg-dev in sarge) > > > > Already there. Look in the DebianSarge section. ... and also the first Mail. I think I had not understood some constuctions. Thanks for the answers. Ciao, Joo [ OOo 2.0.2, Debian Sarge, i386,

Re: 2.0.3 Sarge Backport: agg pyuno compat

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rene Engelhard wrote: > > SYSTEM_AGG=n (no package libagg-dev in sarge) > > Already there. Look in the DebianSarge section. Correction: It even *IS* disabled globally. Just enabled only for sid. So I don't see what problem you should have

Re: 2.0.3 Sarge Backport: agg pyuno compat

Joo Martin wrote: > I have had a look to the debian rules for Sarge Backport. > I suggest to change some variables to: > > BUILD_PYUNO=n (no package python-central in sarge) wrong. When we build on sarge we build with sarge's policy. There *is* conditionals for that. So we don't need

2.0.3 Sarge Backport: agg pyuno compat

Hello, I have had a look to the debian rules for Sarge Backport. I suggest to change some variables to: BUILD_PYUNO=n (no package python-central in sarge) SYSTEM_AGG=n (no package libagg-dev in sarge) And the query: ifeq "$(BUILD_PYUNO)" "y" BUILD_DEPS += , python-

Processed: notfound 320047 in 1.1.4-7

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.19 > notfound 320047 1.1.4-7 Bug#320047: openoffice.org: Don't install, dependencies problem Bug#317762: openoffice.org-bin: broken dependencies with libmyspell3 and libwpd8 Bug#318340: op