Bug#607873: FTBFS: dpkg-gencontrol: error: error occurred while parsing Suggests field
On Mon, Dec 27, 2010 at 12:25:56PM +0100, Rene Engelhard wrote:
> 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.
I don't see how my system is broken and/or misconfigured. At the end
of the email, you seem to imply that the "broken, misconfigured" part
is that I'm mixing stable and testing/unstable. My understanding is
that this has always been supported / allowed (and more generally,
mixing/upgrading from release N and/to release N+1, of which testing
is an "alpha / beta version"), albeit not very well tested. What is
not supported is mixing/upgrading oldstable with/to testing/unstable,
nor release N and/to release N+2.
> Neither does it say anything about filing it against sids version
> when history also is affected. (since 1:3.0.1-3)
One reports bugs with the information one has. I determined that the
sid version was affected, and had no information on whether older
versions were, and which ones.
>> Version: 1:3.2.1-10
> So this is wrong, and you bogusly blocked a important bugfix from
> entering testing.
No, this is not wrong. It states that this bug is present in version
1:3.2.1-10, and it is. It does not state anything about past versions,
it does not say past versions don't have this bug, and it does not
state that past versions have this bug.
>> 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...
No, they are not "on the system", but available for installation. One
could even have a non-Debian repository in /etc/apt/sources.list, that
offers yet another libdb-dev, with a higher (or lower) pin and/or
version number. Then one would also have two different libdb-dev
available for installation.
--
Lionel
Reply to: