1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • Lintian and Dpkg's :any multiarch acceptor

    From Felix Lechner@21:1/5 to All on Thu Nov 4 00:00:01 2021
    Hi,

    For a brief time between October 1 and October 15, Lintian gave
    potentially confusing advice on some build prerequisites. [1]

    The :any multiarch acceptor—a rarely used feature some other tools
    call the "muliarch qualifier"—was originally not implemented at all
    [2] and then implemented incorrectly. [3] Many people do not even know
    about the feature. To my knowledge it works now.

    Here are two questions:

    1. Did anyone find the latest Lintian versions (2.109.0 and up)
    confusing as to whether the :any should be included? The material you
    would have encountered includes both the context offered by Lintian
    (the extra information after the tag) and any relevant tag
    descriptions.

    2. Should Lintian issue any advice when it sees the :any multiarch
    acceptor? If so, for which packages? It might allow maintainers to
    undo erroneous advice they may have been given, although many folks
    use the feature legitimately, as well.

    Thank you!

    Kind regards
    Felix Lechner

    [1] The affected versions were 2.107.0 and 2.108.0.
    [2] https://bugs.debian.org/994902
    [3] https://bugs.debian.org/995981

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johannes Schauer Marin Rodrigues@21:1/5 to All on Thu Nov 4 10:40:02 2021
    Hi,

    Quoting Felix Lechner (2021-11-03 23:34:17)
    For a brief time between October 1 and October 15, Lintian gave potentially confusing advice on some build prerequisites. [1]

    The :any multiarch acceptor—a rarely used feature some other tools call the "muliarch qualifier"—

    it seems the only tool that calls :any an "acceptor" is lintian while the rest of the world calls it a qualifier. I filed a MR to fix this:

    https://salsa.debian.org/lintian/lintian/-/merge_requests/378

    was originally not implemented at all [2] and then implemented incorrectly. [3] Many people do not even know about the feature. To my knowledge it works now.

    Here are two questions:

    1. Did anyone find the latest Lintian versions (2.109.0 and up)
    confusing as to whether the :any should be included? The material you
    would have encountered includes both the context offered by Lintian
    (the extra information after the tag) and any relevant tag
    descriptions.

    2. Should Lintian issue any advice when it sees the :any multiarch
    acceptor? If so, for which packages? It might allow maintainers to
    undo erroneous advice they may have been given, although many folks use the feature legitimately, as well.

    which wording do you need advice on? I grepped the Lintian git for tags containing the string :any and still wasn't sure what you are exactly asking about.

    Thanks!

    cheers, josch
    --==============765172131573511205=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

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

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmGDqVMACgkQ8sulx4+9 g+E0Zg/9G9nZUYsnBK724RvZt0Xy2nyMyNAIhIivyt1f2IfYwxOc6tFyN9nmDS/9 zKaFD0T7N5BiMOnbAwzdkSWbOmn53Ya2f4AkjyV0Dkd2U03N/7B4eBwtvHkps3z0 Fe/IkR0AAA8Yjhl5yweTWwPKZjMU5JUHFlvuRcoO4DkDMChR1gxnVFN7mYCATzBh lFSLe2mja2Sz3CJ71R8YDZK61PGS9Z5KiTU0yZPnMz2zuPB8Ot6z0U68j1nkqE5e z3gg/iQ3q31+Mb0myLdUZGOAJBh6wCCyheOZOVVHpku38kEwta4P4dvA4gmsqfMt V/+Jn0qa4+LrjOzWI5/Tja36hbprCi7clhk1poUMlFmE9zvSYuVFpVFMJR6Vfed4 kfP/JgCSRzDENZCHnN+RQI/sO0QJkWZ238+uyEHj+z/sX/fq6ExR2oSpnjb6vMcL 68yEdrVt0DOew/PqjP+Y2N144XK6ZhTjaabVW/LG4vaN5LVAbSqI3cPK7hENK907 Edo/x2+RIaZVbBVwVohns1b9DP4o0Nkh/n7g/qd0nHZDvhcl75Ab5q5cgBmG8iYW 7aExjfPAe6CgtUej4H2AbBufi2h+TjnjB6/97GAAbDev3T6Z1kHUZI9MpYA3xrGn 5k8CscpEN9/wvj5YBtKJ+vOWwWx+TP5EXo7RDWAnHHxtITXYakQ=
    =qkpy
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johannes Schauer Marin Rodrigues@21:1/5 to All on Thu Nov 4 21:00:02 2021
    Hi Felix,

    Quoting Felix Lechner (2021-11-04 20:25:28)
    On Thu, Nov 4, 2021 at 2:35 AM Johannes Schauer Marin Rodrigues <josch@debian.org> wrote:
    it seems the only tool that calls :any an "acceptor" is lintian

    I think the multiarch spec is confusing because of its terminology.
    It's been a hurdle for many people.

    I think inventing new terminology that is not used anywhere else just adds confusion. I agree that terminology can be confusing but this can be fixed by either

    * adding better documentation for the existing terminology, for example to
    wiki pages, Debian policy or the upcoming Multiarch Specification shipped by
    dpkg [1] or by

    * changing the terminology such that all the involved tools use the same
    terminology

    I don't think just Lintian starting to use new terminology that is not used by dpkg, apt or the wiki pages is helpful at all. Quite the opposite. I think this just makes the status quo worse.

    Thanks!

    cheers, josch

    [1] https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/tree/doc/multiarch.txt?h=pu/doc-multiarch-spec
    --==============%23437138118830520=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

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

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmGEOkAACgkQ8sulx4+9 g+HQsRAAj5Yfdxy5IyA6nkQg6MtLFB66EQSWAl/u+lsitO+0nhte5krB8oS942Pc 76+argKXdHoaXyC0nlEIARPRaP/yIiPlolcsqpDeffQuijVwZvf8OUi0bZFLn8wq 9AVGi+yPSXpqwv6VT15oAI7bwlc0ZBjNOv+IYCz20Jfkb1ULgQyvbnnVdSVuihEb HvEtVi+B0bm9qP1XKq9uATgQEioH/caII017D1E6l7XdzEgNW0R78H05ufJYal61 hbP8WXRis5XlJhi4jIYsB7X/LATXLNGWZ8R+7B2hIHQ4tC4VxXxbiEM1b1tPZMCH yUBZpdvWBo6Rrvd87EV3L8ENQLHlTFzRnYbATwgiaqV3xYEMDUzBHPQdNniqC4dv VLgS7ubzlW0RxgxT3nhv1vcHUl8UmUZK+x1O93znoqB5MPBhNIS73hDnRSftkaTV zUhnu/WcyLr9DoQCq9sCaXRJVMrzAeZwLM6s4XLxul3U7jdop4CFQzpmPOhQgknI fyTD9XbIpgPXXfhcU6a//JKS8SU7756VPFlpKAd3TVAA4jRi6lzqFg1uLEs+hXSs 2cKYbwQBZThMslTmafBy3bkeVsE8X6xw0MT77AqR49XUCY+SwtfiCXT71r7wdy8b AuHCKZI70sjmXl+tqrr4ZoHb3N0Z2C2wwVYfqVo64Jg8Fcq10zw=
    =HDsy
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Felix Lechner@21:1/5 to josch@debian.org on Thu Nov 4 20:50:02 2021
    Hi Johannes,

    On Thu, Nov 4, 2021 at 2:35 AM Johannes Schauer Marin Rodrigues <josch@debian.org> wrote:
    it seems the only tool that calls :any an "acceptor" is lintian

    I think the multiarch spec is confusing because of its terminology.
    It's been a hurdle for many people.

    still wasn't sure what you are exactly asking

    No worries! You were not affected. Thanks for writing!

    Kind regards
    Felix Lechner

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?IOhannes_m_zm=c3=b6lnig_=@21:1/5 to All on Fri Nov 5 00:20:01 2021
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------UQhrhMKjYUHsf0xMTPjqTh0F
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    T24gMTEvMy8yMSAyMzozNCwgRmVsaXggTGVjaG5lciB3cm90ZToNCj4gMS4gRGlkIGFueW9u ZSBmaW5kIHRoZSBsYXRlc3QgTGludGlhbiB2ZXJzaW9ucyAoMi4xMDkuMCBhbmQgdXApDQo+ IGNvbmZ1c2luZyBhcyB0byB3aGV0aGVyIHRoZSA6YW55IHNob3VsZCBiZSBpbmNsdWRlZD8g VGhlIG1hdGVyaWFsIHlvdQ0KPiB3b3VsZCBoYXZlIGVuY291bnRlcmVkIGluY2x1ZGVzIGJv dGggdGhlIGNvbnRleHQgb2ZmZXJlZCBieSBMaW50aWFuDQo+ICh0aGUgZXh0cmEgaW5mb3Jt YXRpb24gYWZ0ZXIgdGhlIHRhZykgYW5kIGFueSByZWxldmFudCB0YWcNCj4gZGVzY3JpcHRp b25zLg0KDQpiZWluZyB0aGUgb25lIHdobyBpbml0aWFsbHkgdHJpZ2dlcmVkICM5OTU5ODEg YnkgYmxpbmRseSBmb2xsb3dpbmcgDQphZHZpY2Ugb2YgbGludGlhbiAoeWVzIGkga25vdzog Km5ldmVyKiBibGluZGx5IGZvbGxvdyBsaW50aWFuJ3MgYWR2aXNlKSwgDQppIHRoaW5rIGkg Y2FuIHNheSB0aGF0IGkgaW5kZWVkIGZvdW5kIHRoZSBkZXNjcmlwdGlvbiBvZiB0aGUgDQoi cnVsZXMtcmVxdWlyZS1idWlsZC1wcmVyZXF1aXNpdGUiIHRhZyBoaWdobHkgY29uZnVzaW5n Lg0KDQppbiBnZW5lcmFsIGkgdGhpbmsgdGFnIGRlc2NyaXB0aW9ucyBzaG91bGQgb255IHVz ZSAibWFjaGluZS1wYXJzYWJsZSANCmFkdmljZSIgaWYgdGhlIG1hY2hpbmUtcGFyc2FibGUg aXMgbWVhbnQgdG8gYmUgdXNlZCBhcy1pcywgYW5kIHVzZSBodW1hbiANCmxhbmd1YWdlIGlu IGFsbCBvdGhlciBjYXNlcy4NCnRoYXQgaXM6IHJhdGhlciB0aGFuIHVzaW5nIGEgc3RyaW5n IGxpa2UgInB5dGhvbjM6YW55IHwgcHl0aG9uMy1hbGw6YW55IA0KfCBweXRob24zLWRldjph bnkgfCBweXRob24zLWFsbC1kZXY6YW55IHwgZGgtc2VxdWVuY2UtcHl0aG9uMyIgKHdoaWNo IA0KbG9va3MgdmVyeSBtdWNoIGxpa2UgY29kZSkgdXNlIHNvbWV0aW5nIGxpa2UgInRoZSBw YWNrYWdlIHNob3VsZCANCnByb2JhYmx5IGJ1aWxkIGRlcGVuZCBvbiBvbmUgb2YgcHl0aG9u My1kZXY6YW55IG9yIGRoLXNlcXVlbmNlLXB5dGhvbjMgDQpvciBbLi4uXSIuDQoNCnRoZSBw b2ludCBpJ20gdHJ5aW5nIHRvIG1ha2UgaXMgbm90IGFib3V0IHRoZSBjb3JyZWN0bmVzcyBv ZiB0aGUgYWR2aWNlIA0KaXRzZWxmLCBidXQgdGhhdCBhbiBleHBsYW5hdGlvbiB0aGF0IGxv b2tzIGxpa2UgYSBjb2RlLWV4YW1wbGUgaXMgDQpwcm9iYWJseSBnb2luZyB0byBiZSB1bmRl cnN0b29kIGFzIHN1Y2guDQpzbyBpZiB0aGUgdGV4dCBpcyBub3QgdG8gYmUgY29weSBhbmQg cGFzdGVkIGludG8gY29kZSwgaXQgc2hvdWxkbid0IGxvb2sgDQpsaWtlIHRpdCBjb3VsZC4N Cg0KZm1kc3QNCklPaGFubmVzDQo=

    --------------UQhrhMKjYUHsf0xMTPjqTh0F--

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

    wsF5BAABCAAjFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmGEXj8FAwAAAAAACgkQtlAZxH96NvjX ww//UTTMYHiYq1ZxHu3w/tWhruPcYsIPqvgRfzMq42EYSNb05fHn6nHfgO2TNA6kKdDvh8xiSWme zc5hGoeRVeZejpW7Hnd/5MX/wwJ3g1hZJD0mMt5i2hu8K/Woi0Aiea1U2d7CQ97Gx5YhdH8gkxOr EPIkb/niyf6mRs7e2RGz3tAGaViGlP7ncI3fHgZY1mU7zvCt0ywKxwU+68ch/IM+KcgKgzQ8Sjgw ce6gqGp5B3vj/7jIyI4Z6/WnOkaVRnYJbE6f0fmmRS4G3i6Ig9XTd1hmaVc/3zToi66Vi9XLy67E NbCHsvYcPrfDjFQlOOgSMJzu5LaeYIGkUjwXYW6OUkW3qagpFfuFpL3Ggk/jWrNIhiFcvE2lzF9F fhbBM+0m0J98Kn9Is0gS31NNooVP2DZQZUgQG9+KlemrDSUJx6htYEgn5KBkiArSqUXyE4ceRb61 Y5H8NLli3ZXGK46mh0aOwON379nMuO9WdLidQKoSBz+hoUmCi3vbj5e3gfdFssf6Y9XuVdYbkyAE ldfXjo7klWTScMqmRgmg6izfXB/J8XJdIrzdv4AcVPqqTnCiUAV/0SyqBU8ZzWXZ3wcurVvNuRZ/ VDpVvQbT3e2LzLVz7FcmdNBV5L9KupnkCm66xHcteAf+5tRxC7uqrsvdPhFL3+HK3OOqfYpO1Z2f XlM=
    =a7OX
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)