Man page - deb-check-file-conflicts(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
DEB-CHECK-MISSING-BREAKS-REPLACES-CONFLICTS
NAMESYNOPSIS
DESCRIPTION
OPTIONS
OUTPUT
EXAMPLES
AUTHOR
SEE ALSO
NAME
deb-check-file-conflicts - check for missing Breaks/Replaces in Debian packages
SYNOPSIS
deb-check-file-conflicts [ --debug ] [ --changes-file = FILE ] [ -o OUTPUT ] [ --output = OUTPUT ]
DESCRIPTION
deb-check-file-conflicts checks produced binary packages for conflicting files against packages that are not declared with Breaks and Replaces relationships.
The tool helps identify potential upgrade issues where files from one package might conflict with files from other packages during installation.
Note that the results depend on what apt repositories are enabled. If you want to prevent upgrade issues across Debian releases, you need to have both unstable and the previous release repositories enabled in the apt sources configuration.
OPTIONS
--debug
Enable debug output
--changes-file= FILE
Specify the changes file to check (defaults to CHANGES_FILE environment variable)
-o , --output = FILE
Write output to FILE (defaults to $EXPORT_DIR/missing_breaks_replaces.xml or ./missing_breaks_replaces.xml)
OUTPUT
The tool generates a JUnit XML format report containing test results for each binary package checked. Each test case indicates whether missing Breaks/Replaces relationships were found.
EXAMPLES
# Check a
changes file for missing relationships:
$ deb-check-file-conflicts --changes-file
foo_1.0-1_amd64.changes
# Write results
to a specific output file:
$ deb-check-file-conflicts -o results.xml --changes-file
foo_1.0-1_amd64.changes
AUTHOR
deb-check-file-conflicts and this manual page were written by Maximiliano Curia <maxy@gnuservers.com.ar>.
Both are released under the GNU General Public License, version 2 or later.
SEE ALSO
dpkg (1), apt-file (1)