Your message dated Mon, 17 Jun 2019 23:18:43 +0000
with message-id <[email protected]>
and subject line Bug#930091: fixed in bison 2:3.4.1+dfsg-1
has caused the Debian Bug report #930091,
regarding bison is wrongly marked Multi-Arch: foreign
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
930091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930091
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 options
to fix it.

A. Depend on libbison-dev explicitly. We consider that a dependency on
   bison does not include libbison-dev. Not every user of bison needs
   libbison-dev and only those that do need it, need the dependency.
   This change is quite simple: Drop the libbison-dev dependency from
   bison. It makes a pile of packages FTBFS until they add the
   dependency. bison has around 540 build-rdeps. I haven't examined how
   many need libbison-dev. flex went this way.

B. Reverse dependencies. This is the "tricky multiarch fix". It may take
   a while to understand, but we can fix the whole issue with a single
   upload of bison:

   * Drop the dependency on libbison-dev from bison.
   * Rename bison to bison-bin.
   * Update the description of bison-bin (formerly bison) to explain
     that this package is an implementation detail and people should
     continue depending on bison.
   * Rename libbison-dev to bison.
   * Make the new bison (former libbison-dev) depend on bison-bin
     (formerly bison).
   * Add Provides: libbison-dev to the new bison (formerly
     libbison-dev).

   After performing these changes, a Build-Depends: bison will result in
   the build architecture bison executable together with the host
   architecture liby.a. Things will just work without any need for
   modifying downstream packages. People won't have to be aware of the
   distinction between the library and the code generator.

Comparing these approaches I see the following trade-offs:

 * A makes a ton of packages FTBFS and will need possibly hundreds of
   uploads.
 * A is consistent with flex.
 * A is slightly better for cross building. Given the experience with
   flex, I expect that the majority of rdeps won't need libbison-dev.
   For cross building this means that bison doesn't have to be available
   for the host architecture.

We need a decision on which approach to take. Preferrably soon. I'm
happy to implement either. I'm also happy to take care of the MBF if we
opt for A. This bug should not be fixed for buster. If you ask me, I'd
slightly preferred option B, but since flex did A, I favour consistency
and thus A. What is your (maintainer) preference? Do we need to know how
many packages would ftbfs before deciding?

Helmut

--- End Message ---
--- Begin Message ---
Source: bison
Source-Version: 2:3.4.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
bison, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chuan-kai Lin <[email protected]> (supplier of updated bison package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 17 Jun 2019 14:56:07 -0700
Source: bison
Binary: bison bison-dbgsym libbison-dev
Architecture: source amd64
Version: 2:3.4.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Chuan-kai Lin <[email protected]>
Changed-By: Chuan-kai Lin <[email protected]>
Description:
 bison      - YACC-compatible parser generator
 libbison-dev - YACC-compatible parser generator - development library
Closes: 930091
Changes:
 bison (2:3.4.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version.
   * Stop depending on libbison-dev. (Closes: #930091)
   * Install examples (which are DFSG-free).
   * Add autopkgtest configuration.
   * Use mk-origtargz for source repacking.
   * Use +dfsg version suffix (lintian dfsg-version-with-period).
   * Various lintian fixes and overrides.
Checksums-Sha1:
 467d299b00ec6176af3df6ad6c72868fb5b82a10 1908 bison_3.4.1+dfsg-1.dsc
 e2054d746ae46283ec24129c9599e1829d92e35f 2021584 bison_3.4.1+dfsg.orig.tar.xz
 e5cb2972b087ea9afc46f2974b1fbede62fb13f2 10512 bison_3.4.1+dfsg-1.debian.tar.xz
 5645c7af8afbd4deaef90e4e00a3d280d40f603b 530836 
bison-dbgsym_3.4.1+dfsg-1_amd64.deb
 2f0dd87bd7d8155375621f9b9c5a38e95ad83204 5854 
bison_3.4.1+dfsg-1_amd64.buildinfo
 01f30d12da26b210f2f357a728a6160bd863e91f 923468 bison_3.4.1+dfsg-1_amd64.deb
 8fabebee6000775131c787e9cfb67dbe28d6a79e 521616 
libbison-dev_3.4.1+dfsg-1_amd64.deb
Checksums-Sha256:
 3d996c59d7a5536f967d9e788a0a2cf46e1e487b7cbb4e408bfe3bb57a78eb34 1908 
bison_3.4.1+dfsg-1.dsc
 15aa21a6123fefba13acd206b3a3f77306d7056fbc3a225b2bc088cb61dac6f5 2021584 
bison_3.4.1+dfsg.orig.tar.xz
 09d0a82dd717dc74ab3846593f1d10990a8a1a8afcdc652fe498b64687d515cd 10512 
bison_3.4.1+dfsg-1.debian.tar.xz
 54d8b2ca458e749d0fbd9b686b9e9bc0941d67f0fe730f8f197adb6e470797a4 530836 
bison-dbgsym_3.4.1+dfsg-1_amd64.deb
 cca50f33effbfc69f6f2d592625d37ccf5c1fa3ea957350e03537650ec68694d 5854 
bison_3.4.1+dfsg-1_amd64.buildinfo
 c22a176a04b6d365544069c40959069d013af968badfd628195c1870810916cf 923468 
bison_3.4.1+dfsg-1_amd64.deb
 e7089e08a8448224acaa342fe7771daf070144fde61554fdff79a0a1507c616d 521616 
libbison-dev_3.4.1+dfsg-1_amd64.deb
Files:
 b52ec0795f1133ee07d1ca2648f12077 1908 devel optional bison_3.4.1+dfsg-1.dsc
 186615a583b42fc0734e5e31a6f848bf 2021584 devel optional 
bison_3.4.1+dfsg.orig.tar.xz
 5dfdb68f2d614de5a8455ecda5196440 10512 devel optional 
bison_3.4.1+dfsg-1.debian.tar.xz
 6ec410355f76dceb670adf12172e74b7 530836 debug optional 
bison-dbgsym_3.4.1+dfsg-1_amd64.deb
 3ea2135bac2bd6bed4e7e6bccacf5daf 5854 devel optional 
bison_3.4.1+dfsg-1_amd64.buildinfo
 bebc5662a23853eebb6a40ddf42f4987 923468 devel optional 
bison_3.4.1+dfsg-1_amd64.deb
 097eba711c7ab6017024d183c900176b 521616 libdevel optional 
libbison-dev_3.4.1+dfsg-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEEpjo/UW6i/KKi+2ONAbOplSquRxMFAl0IG/sRHGNrbGluQGRl
Ymlhbi5vcmcACgkQAbOplSquRxNylQ/+Px4OvnT+gRPDaae1tTWmyqvTltR5W03K
6hCMzIvJvIAHITEBQmKjnM9l/dYkINN/o/qoICfP1Le0ebIwqhWKTTJOCeunETPG
e08yEBj8XhVECVKLMQwcT1nmyiXCXNgt4h10eEV06WGJ6P04gDtJ030ymHGUJMnc
3yYFdFNAYTcfHT+V9xqK/9clmJ7vZr3KsJVNgeWDbKMHZ1UiK70YRTz9R1PkuMQ+
U4e1IejpM19z0krJFWZhyzx3pVAeLZ/6LCshJtAyO0lFVXXphJX5JggG9AaWxPQG
O66fjgaU/QEFfK0YTUXT94i8isQW8iLnUx4IYFVB7wRcCIWo2fLnvvSm8cwZxhyL
qMnO4OiOUO80NVbEyzPZDlAIqwqlSjJZKgOl9x75SlIam9vj8Bsenaa8GBBPRYG2
UbBXe/Do1vIXhWUeu2e23TXVftB77EzGUzjwzDUSBLirE5bIUvoZDpvKqSlz9N/z
qOXS8dlJpN53Zd31nZxJ/MDMxXR2XnWp/OlbeQxM4HjSXq9WRv8agcevniFOSA+H
K6K6m2ZVpleUBYvoqUH/4NVOodiUtSmLWYMphUXPlS/U/0EK4vBklG1VPsFNiyS8
++0Hk1H6RLTCeZap5DytpMUYWRNQ9PTv/jF3dwar1CsDIDq52DmLCw9pZhM5WpiG
l3tyTY0Nvr4=
=WWxz
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to