I finished rebuilding all reverse build dependencies of bison. And I
found that removing libbison-dev as a dependency of bison (option A)
does not cause any additional FTBFS errors. All the build failures I
observed were due to existing FTBFS bugs, or due to problems (such as
tests hanging) that
On 06.06.19 20:08, Helmut Grohne wrote:
> Package: bison
> Version: 2:3.3.2.dfsg-1
> Severity: important
>
> bison is marked Multi-Arch: foreign and Depends on libbison-dev.
> Packages Build-Depend on bison and expect a libbison-dev (for the host
> architecture). This is broken.
>
> We had this
Status update. The ratt run is still in progress, having built 152
out of 547 reverse dependencies. Out of those 152 only 1 fails to
build (libbonobo), and that package is already FTBFS for reasons
entirely unrelated to bison.
So I think A is the way to go, and it is likely that very few
On Thu, Jun 06, 2019 at 10:34:21PM -0700, Chuan-kai Lin wrote:
> Personally I would go for A. The reason being the following paragraph
> from Bison documentation [1]:
>
> "The Yacc library contains default implementations of the yyerror and
> main functions. These default implementations are
On Thu, Jun 6, 2019 at 9:50 PM Helmut Grohne wrote:
> And the question now is: Where to move that dependency? Either the
> consumers must explicitly depend on libbison-dev (A) or bison is
> restructured in a way that still provides the library for the right
> architecture when issuing a
Hi Chuan-kai,
On Thu, Jun 06, 2019 at 07:42:48PM -0700, Chuan-kai Lin wrote:
> 1. bison (the executable) being marked Multi-Arch: foreign is not
> inherently broken, since in a cross-build situation we are running the
> bison binary in the host (instead of the target) architecture.
> 2. The
Hi Helmut,
Thank you for the bug report! Let me see if I understand the
situation correctly:
1. bison (the executable) being marked Multi-Arch: foreign is not
inherently broken, since in a cross-build situation we are running the
bison binary in the host (instead of the target) architecture.
2.
Package: bison
Version: 2:3.3.2.dfsg-1
Severity: important
bison is marked Multi-Arch: foreign and Depends on libbison-dev.
Packages Build-Depend on bison and expect a libbison-dev (for the host
architecture). This is broken.
We had this problem earlier with flex and I can provide the same
8 matches
Mail list logo
