drt-tools-nmu-transition(1)

πŸ“¦
version 0.3.5 Β· 2 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– drt-tools-nmu-transition(1) β€” the nmu-transition page, bestie edition πŸ’–

okay so. this is a General Commands Manual page, and it's all about drt-tools-nmu-transition. sit down, grab a boba, we're doing binNMUs. πŸ§‹βœ¨


✨ NAME ✨

drt-tools-nmu-transition β€” prepare and schedule binNMUs for a transition. that's it, that's the whole job. binNMU queen behavior. πŸ‘‘


🌸 SYNOPSIS 🌸

drt-tools nmu-transition <-m|--message> [--bp] [--dw] [--extra-depends]
[-v|--verbose]... [-q|--quiet]... [-s|--suite] [-a|--architecture]
[-h|--help] [INPUT]

like, the <|> vibe is mandatory for -m, everything else is just vibing along. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Prepare and schedule binNMUs for a transition. no cap. 🫢

This command expects a list of packages with their respective versions from ben. Each line should look like this:

haskell-pandoc-citeproc    [build logs] (0.17.0.1-1)    ✘    ✘    ✘    ✘    ✘    ✘    ✘    ✘    ✘

not me reading the little ✘ row like a mood board 😭

Note that any information from ben except the source package and the version are ignored. so all those ✘s? decoration. the drama. the aesthetic. Per default, binNMUs are scheduled with ANY in unstable. πŸŽ€

The list of packages can be either given on the standard input or they are read from a file. your call, bestie. 🌈


πŸ’… OPTIONS πŸ’…

  • -m, --message <MESSAGE> β€” Message for binNMUs. it's giving "you literally cannot skip this one". πŸ’–
  • --bp <BUILD_PRIORITY> β€” Build priority.

If specified, the binNMUs are scheduled with the given build priority. Builds with a positive priority will be built earlier. positive = front of the line, main character energy ✨

  • --dw <DEP_WAIT> β€” Dependency-wait.

If specified, the builds will wait until the given dependency relation is satisfied. they're just standing there. patiently. waiting for their dep to text back. πŸ™ˆ

  • --extra-depends <EXTRA_DEPENDS> β€” Extra dependencies.

If specified, the given dependency will be installed during the build. little treat for the build. a lil snack. πŸ“

  • -v, --verbose β€” Increase logging verbosity. more words. more lore. πŸ“’
  • -q, --quiet β€” Decrease logging verbosity. shhh. library voice. 🀫
  • -s, --suite <SUITE> [default: unstable] β€” Suite for binNMUs. the default is literally unstable, it's already in its unhinged era. 😌
  • -a, --architecture <ARCHITECTURE> β€” Architectures for binNMUs.

If no architectures are specified, the binNMUs are scheduled with ANY. Otherwise, the architectures specified here are taken. The option supports the special architecture ANY as well as removing architectures from ANY by specifying -$arch. yes you can subtract an arch, it's math but make it fashion. πŸ’…

  • -h, --help β€” Print help (see a summary with -h). self-care: read the docs. 🫢
  • [INPUT] β€” Input file with a list of packages.

If not specified, the list of packages will be read from the standard input. no file? no problem, stdin has your back fr fr. πŸ’œ


⭐ friendly reminder bestie: the only info from ben that survives the vibe check is the source package and the version. everything else gets ignored. periodt. πŸ’€

and that's the whole page!! πŸŽ‰ slay. this was nmu-transition, from the drt-tools-nmu-transition(1) page in the General Commands Manual β€” footer says nmu-transition on the left and drt-tools-nmu-transition(1) on the right, and honestly? iconic. go schedule something. πŸŽ€πŸ¦‹βœ¨

πŸ“¦ where this page comes from