RC-ALERT(1)
π RC-ALERT(1) π
ok so like. bestie. this is a General Commands Manual page for the command rc-alert. it's giving "let me tell you which of your installed packages are in trouble" and honestly? iconic. let's get into it π¦
β¨ NAME β¨
rc-alert β check for installed packages with release-critical bugs π₯
πΈ SYNOPSIS πΈ
rc-alert [inclusion options] [--debtags [tag[,tag ...]]] [--popcon]
[package ...]
rc-alert --help|--version
like, you can hand it a bunch of inclusion options, you can do the whole --debtags thing with a comma list of tags, you can --popcon it, and you can also just name packages directly at the end. OR you can do the short lil --help / --version run. choose your fighter π
π DESCRIPTION π
rc-alert goes and downloads the list of release-critical bugs off the Debian BTS webpages, and then spits out a list of packages that are installed on your system β or the ones you named on the command line β which show up in that list. so it's basically a vibe check for your packages, but the vibe is "are you broken" π
and here's the tea on caching: if the directory $XDG_CACHE_HOME/devscripts/rc-alert already exists, OR you pass the --cache option, then that (sizable, lowkey thicc) downloaded list gets cached. which means the next time you run it, it only re-downloads if the thing actually changed. efficient queen π
π OPTIONS π
--cacheβ forces the creation of the$XDG_CACHE_HOME/devscripts/rc-alertcache directory. like, make the folder, bestie, i said what i said.--help,-hβ shows you a lil summary of the options. the appetizer. the trailer. π--version,-vβ shows version and copyright info. receipts, basically.
okay so ALSO β plot twist β you can filter which bugs get reported based on the tags and distributions attached to the package. the filtering options are:
--include-tags,-fβ a list of tags the bug must have, in the same format used for output. for example, to include bugs taggedsecurityorhelp wanted, you'd use"SH". yes it's letters. yes it's cryptic. yes it slays.--include-tag-op,-tβ if you set this toand, then a bug has to have all of the tags you gave--include-tags. all of them. no skipping. π--exclude-tagsβ a list of tags the bug must not have, same format as--include-tags.--exclude-tag-opβ if you set this toand, then a bug must have none of the tags you gave--exclude-tags. by default though, the bug gets excluded if any tag matches. default is messy-girl energy, ngl.--include-dists,-dβ a list of distributions the bug must apply to, in the format used for output. for example, to include bugs affectingtestingorunstable, use"TU". π--include-dist-op,-oβ if you set this toand, a bug has to apply to all of the distributions you listed before it gets included.--exclude-distsβ a list of distributions the bug must not apply to, same format as--include-dists.--exclude-dist-opβ if you set this toand, a bug must apply to all of the listed distributions in order to be excluded. by default the bug gets excluded if it applies to any of the listed distributions.
and THEN, because we weren't done, you can also only list bugs that have specific debtags set. β οΈ but heads up: you need to have debtags installed, AND it's not mandatory for maintainers to set proper debtags, so the list you get will probably be incomplete. fr fr. don't come for me.
--debtagsβ match packages based on the listed tags. each package is matched only if it has all the listed tags. but β plot twist β if there are multiple tags within the same facet, a package is matched if it has any of the listed tags within that facet. multi-tag, multi-facet, multi-drama.--debtags-databaseβ use a non-standard debtags database. the default is/var/lib/debtags/packages-tags.
so, popularity-contest collects data about installation and usage of Debian packages. and you can additionally sort the bugs by the popcon rank of the related packages. bougie behavior, love that for you π
--popconβ sorts bugs by the popcon rank of the package the bug belongs to.--pc-voteβ by default, packages are sorted by how many people have the package installed. this option instead sorts by how many people are regularly using the package. note: this option has no effect when combined with--pc-local. it simply does not show up to that party. π--pc-localβ instead of requesting remote data, it uses the info from the last popcon run, which lives at/var/log/popularity-contest. locally sourced, artisanal, farm-to-table data π§
π EXAMPLES π
--include-dists OSthe bug must apply to at least one ofoldstableorstable.--include-dists TU --include-dist-op andthe bug must apply to bothtestingandunstable.--include-dists O --include-tags S --exclude-tags +the bug must apply tooldstable, be taggedsecurity, but notpatch.--exclude-dists SOT --include-tags Rthe bug must apply to onlyunstableorexperimental(or both), and be taggedunreproducible.--debtags implemented-in::perl,role::plugin,implemented-in::pythonthe bug must apply to packages matching the specified debtags β i.e. the match will only include packages that have therole::plugintag and that have either of the tagsimplemented-in::perlorimplemented-in::python.--popcon --pc-localreads/var/log/popularity-contestand sorts bugs by your personal popcon ranking (which is basically the atime of your packages' binaries). your atime. your ranking. main character energy π«Ά
π BUGS π
it is not possible to say "does not apply only to unstable".
that's it. that's the bug. the syntax just won't let you say it. the audacity.
π¦ SEE ALSO π¦
debtags(1) popbugs(1) popularity-contest(8)
π AUTHOR π
rc-alert was written by Anthony DeRobertis and modified by Julian Gilbey <jdg@debian.org> and Adam D. Barratt <adam@adam-barratt.org.uk> for the devscripts package. the Debtags and popcon functionality was added by Jan Hauke Rahm <info@jhr-online.de>. absolute legends, every single one πΈ
and that's the whole page bestie π this one ships under DEBIAN, in the Debian Utilities corner of the manual, filed as RC-ALERT(1). now go check your packages, they might be going through something πβ¨
π¦ where this page comes from
- debian bookworm: devscripts 2.23.4+deb12u2 Β· GPL-2.0-or-later
- debian trixie: devscripts 2.25.15+deb13u1 Β· GPL-2.0-or-later
- epel 10: devscripts 2.25.5-1.el10_1 Β· GPL-2.0-or-later
- epel 9: devscripts 2.25.5-1.el9 Β· GPL-2.0-or-later
- fedora 43: devscripts 2.25.19-2.fc43 Β· GPL-2.0-or-later
- fedora 43: devscripts 2.25.33-1.fc43 Β· GPL-2.0-or-later
- fedora 44: devscripts 2.26.5-1.fc44 Β· GPL-2.0-or-later
- opensuse-leap 16.0: devscripts 2.22.2-160000.2.2 Β· (Artistic-1.0 OR GPL-1.0-or-later) AND Artistic-2.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND GPL-3.0-only AND SUSE-Public-Domain AND ISC
- opensuse-leap 16.0: devscripts 2.22.2-160000.2.2 Β· (Artistic-1.0 OR GPL-1.0-or-later) AND Artistic-2.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND GPL-3.0-only AND SUSE-Public-Domain AND ISC
- opensuse-leap 16.0: devscripts 2.22.2-160000.2.2 Β· (Artistic-1.0 OR GPL-1.0-or-later) AND Artistic-2.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND GPL-3.0-only AND SUSE-Public-Domain AND ISC
- opensuse-leap 16.0: devscripts 2.22.2-160000.2.2 Β· (Artistic-1.0 OR GPL-1.0-or-later) AND Artistic-2.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND GPL-3.0-only AND SUSE-Public-Domain AND ISC
- ubuntu jammy: devscripts 2.22.1ubuntu1 Β· GPL-2.0-or-later
- ubuntu jammy: devscripts 2.22.1ubuntu1.2 Β· GPL-2.0-or-later
- ubuntu noble: devscripts 2.23.7 Β· GPL-2.0-or-later
- ubuntu noble: devscripts 2.23.7ubuntu0.2 Β· GPL-2.0-or-later
- ubuntu questing: devscripts 2.25.19ubuntu2
- ubuntu resolute: devscripts 2.26.7 Β· GPL-2.0-or-later
- ubuntu stonking: devscripts 2.26.11ubuntu1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms