BOTCH-MULTIAR...PRETER-PROBLEM(1)
π BOTCH-MULTIARCH-INTERPRETER-PROBLEM π
okay so bestie, welcome to botch-multiarch-interpreter-problem, a lil tool from the botch tools collection and honestly? it's giving detective energy πβ¨
β¨ NAME β¨
botch-multiarch-interpreter-problem β find all arch:all packages that allow switching architectures π¦
πΈ SYNOPSIS πΈ
botch-multiarch-interpreter-problem [-h] [-v] graph.xml
π DESCRIPTION π
So you hand this program a package graph, and it hands you back a page β plain text format, no frills β listing every Architecture:all package that is NOT Multi-Arch:foreign and that sits on a dependency path between two Architecture:any packages. no cap, that's the whole gig π
More precisely (because we love precision in this house π): dose-ceve creates a graph where the nodes are binary packages and source packages, and the edges are their dependency and provides relationships. This program prints all nodes (or packages) that fulfill these criteria:
- the package is not
Multi-Arch:foreignπ - the package is
Architecture:all - the package has a (possibly transitive) predecessor in the dependency graph that is either an
Architecture:anybinary package or a source package that buildsArchitecture:anypackages - the package has a (possibly transitive) successor in the dependency graph that is
Architecture:anyand notMulti-Arch:foreign. lowkey important: traversal of the successors stops atMulti-Arch:foreignpackages π
π OPTIONS π
-v,--verboseβ be verbose. spill the tea, tell me everything π£οΈ-h,--helpβ print help message. the classic cry for help, we've all been there π«Ά--packagesβ Packages file to retrieve binary package size π¦-H,--htmlβ output HTML document with additional statistics πβ¨
π EXAMPLE π
okay so listen, there's a vibe check here and it's important:
The graph created bydose-cevemust not containBuild-Depends-Indepdependencies because source packages do not have to be cross-built to create theirArchitecture:allpackages. These can always be retrieved by native compilation.
Also:
The graph does not have to includebuilds-fromrelationships because theArchitecturefield of source packages is used to determine whether a source package buildsArchitecture:anybinary packages.
Now the actual run, bestie:
dose-ceve --deb-drop-b-d-indep --deb-native-arch=amd64 -G pkg -T grml deb://Packages.gz debsrc://Sources.gz > graph.xml
botch-multiarch-interpreter-problem --packages=Packages.gz graph.xml > out.html
w3m out.html
and boom, you're browsing your own lil html report in w3m π (iconic honestly)
π BUGS π
See <http://bugs.debian.org/botch>.
π¦ SEE ALSO π¦
Debian doc-base Manual /usr/share/doc/botch/wiki/Home.html π
π AUTHOR π
This man page was written by Johannes Schauer. Botch is written by Johannes Schauer and Pietro Abate. absolute legends, we stan π«Ά
β COPYRIGHT β
Copyright 2012-2014 Johannes Schauer, Pietro Abate
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. A special linking exception to the GNU Lesser General Public License applies to this library, see the COPYING file for more information. π
and that's the whole page bestie!! this was rendered with perl v5.36.0, dated 2023-02-17, under the manual name BOTCH-MULTIAR...PRETER-PROBLEM(1) from botch tools. go forth and multiarch, periodt π β¨π¦
π¦ where this page comes from
- debian bookworm: botch 0.24-2 Β· LGPL-3.0-or-later WITH OCaml-linking exception
- ubuntu noble: botch 0.24-2 Β· LGPL-3.0-or-later WITH OCaml-linking exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms