DAPTUP(8)
π DAPTUP β the plugin for apt[itude] and cupt that lists repo changes π
okay so bestie, listen. this is the manual page for daptup, section 8 of the System Manager's Manual. it's a little script that keeps you in the loop about what's actually happening in your repos. let's go π¦
β¨ SYNOPSIS β¨
daptup ( --pre | --post | --last ) [ -h | --help ] [ --nocolor ]
that's it. that's the whole vibe. three main modes, two little extras. π
πΈ OPTIONS πΈ
--preβ does only the 'pre' stage: it collects the info that's gonna be used as the 'old' stuff. you usually only need to pass this in apt hooks, like it's not a thing you type yourself fr.--postβ does only the 'post' stage: it collects the 'new' info and β but only if the appropriate option is enabled in the config file β outputs the changes. again, usually only specified in apt hooks. π«Ά--lastβ outputs the changes only. this is the one you want when you're like "what happened in the last update??" heads up though: the list of outdated packages, if daptup is configured to output it, will get rebuilt. so it's not just a peek, it does a lil work. π-h --helpβ prints the help. iconic. simple. we love her.--nocolorβ disables color output, which is useful for scripts or when the output isn't going to a terminal. right now it only works with the--lastoption, however, you can disable color globally in the configuration file if that's your thing.
so like, real talk, daptup is a script that outputs the list of packages recently entered to the repo, the list of packages which got new updates, the list of changes in 'watched' packages and, optionally, the list of outdated packages. yes, that's a lot of lists. she's thorough. π
and starting with 0.8.0 version, daptup uses apt hooks so you literally don't need to explicitly call it. it will be called automatically by all the supported package managers. no cap. you just live your life and daptup does its thing in the background. main character energy honestly. β¨
π©Ή TROUBLESHOOTING π©Ή
okay so this is the part where things can get a lil messy, and I need you to pay attention bestie.
if daptup was interrupted while building the lists, the cached lists can stay in an inconsistent state. which is not it if you want to use the --last option before the new update. π
there is nothing to do if the interrupt occurred at the moment when the old lists were building β besides running the new update, that is. like, that's the only move.
however!! if the interrupt occurred when the new lists were building, you can easily redo this stage by calling:
daptup --post
see? fixable. we stay calm. π§
π FILES π
/etc/daptup.confβ the self-documented configuration file. yes she documents herself. confident queen./var/spool/daptup/outdatedβ the cached file with info about outdated packages.
π SEE ALSO π
apt-get(8), aptitude(8), cupt(1)
go read those too, iykyk. π
π AUTHOR π
daptup was written by Eugene V. Lyubimkin.
this manual page was written by Eugene V. Lyubimkin <jackyf@debian.org>, for the Debian project (but may be used by others). generous king behavior honestly. π
and that's the whole page!! this version came from the System Manager's Manual, dated Jan 5, 2013, and it's the DAPTUP(8) page. mwah. go read your repo changes bestie π
π¦ where this page comes from
- debian bookworm: daptup 0.12.7+nmu1
- debian trixie: daptup 0.12.7+really0.12.7-0.1 Β· GPL-3.0-or-later
- ubuntu jammy: daptup 0.12.7+nmu1
- ubuntu noble: daptup 0.12.7+nmu1
- ubuntu questing: daptup 0.12.7+really0.12.7-0.1
- ubuntu resolute: daptup 0.12.7+really0.12.7-0.1build1 Β· GPL-3.0-or-later
- ubuntu stonking: daptup 0.12.7+really0.12.7-0.3 Β· 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