[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#607873: FTBFS: dpkg-gencontrol: error: error occurred while parsing Suggests field



found 607873 1:3.0.1-3
retitle 607873 FTBFS: "dpkg-gencontrol: error: error occurred  while parsing Suggests field" when more, different libdb-dev existing.
thanks

On Thu, Dec 23, 2010 at 01:42:31PM +0100, Lionel Elie Mamane wrote:
> Source: openoffice.org

> Severity: serious
> Justification: Policy 7.7

The policy doesn't say anything about broken, misconfigured systems. Neither
does it say anything about filing it against sids version when history also
is affected. (since 1:3.0.1-3)

> Version: 1:3.2.1-10

So this is wrong, and you bogusly blocked a important bugfix from entering
testing.

> Package `libavalon-framework-java' is not installed.
> Use dpkg --info (= dpkg-deb --info) to examine archive files,
> and dpkg --contents (= dpkg-deb --contents) to list their contents.
> Package `libavalon-framework-java' is not installed.
> Use dpkg --info (= dpkg-deb --info) to examine archive files,
> and dpkg --contents (= dpkg-deb --contents) to list their contents.

Not relevant here.

> dpkg-gencontrol: warning: can't parse dependency libdb4.6-dbg libdb4.8-dbg

This is the problem.

What OOo does is the following:

        BUILD_DEPS += , libdb-dev
        DBG_DBG_SUGGESTS += , $(shell apt-cache show libdb-dev | grep Depends | awk '{ print $$2 }' | sed -e s/dev/dbg/)

to find out what db it builds against to add the correct suggests. No,
hardcoding it is no way, and there's no libdb-dbg.

>   APT prefers testing
>   APT policy: (600, 'testing'), (600, 'stable'), (500, 'stable'), (300, 'unstable'), (1, 'experimental')

... and the above works unless someone has such a broken mix (what has "stable"
to do here?!) which results in two different libdb-devs pointing to different
lidbX.Ys on his system...

In any case, I am not going to change this.

Grüße/Regards,

René



Reply to: