drt-tools-nmu-list(1)
π drt-tools-nmu-list β the manual, but make it cute
okay so bestie, you found yourself in the drt-tools-nmu-list(1) page from the General Commands Manual, and honestly? you're about to have a great time. this little icon binNMUs a whole list of packages for you and it is not playing around. π
β¨ NAME β¨
drt-tools-nmu-list β BinNMU a list of packages π¦
πΈ SYNOPSIS πΈ
drt-tools nmu-list <-m|--message> [--bp] [--dw] [--extra-depends]
[-v|--verbose]... [-q|--quiet]... [-s|--suite] [-a|--architecture]
[-h|--help] [INPUT]
π DESCRIPTION π
BinNMU a list of packages. periodt.
so here's the vibe: this command reads a list of source packages from stdin or from a file you hand it, and it takes all of that as input to produce/schedule commands that binNMU those very packages. she's a hard worker, no cap. π₯
and the way she handles both version-less lists and versioned source packages formatted as source_version? yeah. ate. π
one thing you gotta know, and this is important so listen up: if you specify an architecture, but the package that's gonna be rebuilt produces a Multi-Arch: same binary, then a binNMU for ANY gets scheduled instead. that's just how it is, iykyk. π
π OPTIONS π
-m,--message<MESSAGE>β the message for the binNMUs. yeah you gotta give her one, she's not gonna write it herself bestie βοΈ--bp<BUILD_PRIORITY>β build priority. if you specify it, the binNMUs get scheduled with that build priority you gave. and lowkey important: builds with a positive priority will be built earlier. main character builds go first, obviously πβοΈπ¨--dw<DEP_WAIT>β dependency-wait. if you specify it, the builds will wait until the given dependency relation is satisfied. she's patient, she's not gonna rush in there π--extra-depends<EXTRA_DEPENDS>β extra dependencies. if you specify it, the given dependency will be installed during the build. little bonus snack for the build process π-v,--verboseβ increase logging verbosity. she will tell you EVERYTHING π’-q,--quietβ decrease logging verbosity. she will tell you nothing, respectfully π€«-s,--suite<SUITE>[default:unstable] β the suite for the binNMUs. default isunstableand honestly? iconic behaviour β-a,--architecture<ARCHITECTURE>β architectures for the binNMUs. okay so here's the tea: if you don't specify any architectures, the binNMUs are scheduled withANY. otherwise, the architectures you specify here are the ones that get taken. and this option supports the special architectureANY, plus it supports removing architectures fromANYby specifying-$arch. yes you can subtract. she contains multitudes π§-h,--helpβ print help (see a summary with-h) π«Ά[INPUT]β input file with a list of packages. if you don't specify it, the list of packages will be read from the standard input. no file? no problem, she'll read fromstdinπ
π friendly reminder that this is drt-tools-nmu-list(1) β you're in the right place, bestie, and you're doing amazing.
and that's the whole page!! you made it to the bottom, so here's your little sign-off: this one lives under the name nmu-list and it's part of the drt-tools-nmu-list(1) family. mwah, go binNMU something. π
β¨ππ¦
π¦ where this page comes from
- ubuntu resolute: drt-tools 0.3.5-2 Β· GPL-3.0-or-later
- ubuntu stonking: drt-tools 0.3.5-3build1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms