Man page - debftbfs(1)
Packages contains this manual
- devscripts.conf(5)
- build-rdeps(1)
- whodepends(1)
- checkbashisms(1)
- annotate-output(1)
- namecheck(1)
- transition-check(1)
- debrsign(1)
- dpkg-genbuilddeps(1)
- deb-reversion(1)
- ltnu(1)
- debbisect(1)
- cowpoke(1)
- dscextract(1)
- list-unreleased(1)
- getbuildlog(1)
- debclean(1)
- chdist(1)
- rc-alert(1)
- mk-origtargz(1)
- deb2docker(1)
- edit-patch(1)
- what-patch(1)
- dd-list(1)
- tagpending(1)
- suspicious-source(1)
- bts(1)
- deb-why-removed(1)
- devscripts(7)
- plotchangelog(1)
- uscan(1)
- mergechanges(1)
- debsnap(1)
- debftbfs(1)
- hardening-check(1)
- dscverify(1)
- dget(1)
- who-uploads(1)
- debrepro(1)
- git-deborig(1)
- deb-janitor(1)
- deb2apptainer(1)
- dep-14-convert-git-branch-names(1)
- dep3changelog(1)
- wnpp-alert(1)
- pts-unsubscribe(1)
- sadt(1)
- debc(1)
- debdiff-apply(1)
- nmudiff(1)
- add-patch(1)
- dpkg-depcheck(1)
- rmadison(1)
- debsign(1)
- deb2singularity(1)
- diff2patches(1)
- debi(1)
- mk-build-deps(1)
- origtargz(1)
- debrebuild(1)
- deb-check-file-conflicts(1)
- reproducible-check(1)
- mass-bug(1)
- debootsnap(1)
- salsa(1)
- svnpath(1)
- debrelease(1)
- pts-subscribe(1)
- debdiff(1)
- dch(1)
- debcheckout(1)
- wrap-and-sort(1)
- wnpp-check(1)
- manpage-alert(1)
- dcmd(1)
- who-permits-upload(1)
- debchange(1)
- archpath(1)
- debuild(1)
- grep-excuses(1)
- debcommit(1)
- uupdate(1)
apt-get install devscripts
Manual
DEBFTBFS
NAMEDESCRIPTION
options:
NAME
debftbfs - list packages that have FTBFS bugs filed
DESCRIPTION
usage: debftbfs [-h] [-d] [-v]
[--distribution {stable,testing,unstable,experimental}] [--source {auto,udd-mirror.d.n,udd.d.o,bugs.d.o}]
Query udd or bugs.debian.org for all source packages which currently have FTBFS bugs filed against them for a given distribution (default: unstable) in "main". If the psql utility is installed, the data will be queried from udd-mirror.debian.net. Otherwise it will come from udd.debian.org. Querying the former is a bit faster but the data might be not 100% up to date. The result is a line-based list of source package names, their FTBFS bug and the bug title, separated by a space. Only bugs tagged ’ftbfs’ and with a severity greater or equal to ’serious’ are selected. The result is sorted by source package name, alphabetically ascending.
The three available data sources differ in how fast it is to retrieve the data, how up-to-date the data is and in the chosen heuristic to decide which ftbfs bugs affect which source package in a given distribution. The fastest two data sources are udd-mirror.debian.net and udd.debian.org with the former being around 20% faster than the latter but either finish in under a second. The former will be more outdated than the latter though at is is only a mirror. The slowest method is directly querying bugs.debian.org via its SOAP interface. While querying bugs.debian.org will retrieve the most up-to-date information, the heuristics chosen to decide whether a source package is affected by an ftbfs bug slightly differs to the heuristic used by udd. Differences mostly occur for bugs that were re-assigned to different source packages or have otherwise missing or incorrect metadata stored.
options:
-h , --help
show this help message and exit
-d , --debug
Enable output of debugging messages
-v , --verbose
Print verbose output
--distribution {stable,testing,unstable,experimental}
Pick the distribution affected by the FTBFS issue
--source {auto,udd-mirror.d.n,udd.d.o,bugs.d.o}
Choose the UDD source between udd-mirror.debian.net, udd.debian.org and bugs.debian.org.