Package zxing-cpp-tools
trixie (Debian 13 (Trixie)) (utils): Utilities provided by ZXing library
2.3.0-4: amd64 arm64

debian package index
Packages published for Debian 13 (Trixie) and its configured repositories.
Open a package to inspect every retained build, dependency relationship, checksum, file list, and source observation.
trixie (Debian 13 (Trixie)) (utils): Utilities provided by ZXing library
2.3.0-4: amd64 arm64
Source: zxing-cpp
trixie (Debian 13 (Trixie)) (devel): fast and lightweight x86/x86-64 disassembler library - tools
4.1.1-1: amd64 arm64
Source: zydis
trixie (Debian 13 (Trixie)) (sound): Realtime software synthesizer for Linux
3.0.6-7: amd64 arm64
trixie (Debian 13 (Trixie)) (sound): Realtime software synthesizer for Linux (data)
3.0.6-7: all
Source: zynaddsubfx
trixie (Debian 13 (Trixie)) (sound): dssi plugin of zynaddsubfx
3.0.6-7: amd64 arm64
Source: zynaddsubfx
trixie (Debian 13 (Trixie)) (sound): lv2 plugin of zynaddsubfx
3.0.6-7: amd64 arm64
Source: zynaddsubfx
trixie (Debian 13 (Trixie)) (sound): vst plugin of zynaddsubfx
3.0.6-7: amd64 arm64
Source: zynaddsubfx
trixie (Debian 13 (Trixie)) (admin): command line software manager using libzypp
1.14.89-1: amd64 arm64
trixie (Debian 13 (Trixie)) (admin): command line software manager using libzypp (common files)
1.14.89-1: all
Source: zypper
trixie (Debian 13 (Trixie)) (doc): command line software manager using libzypp (documentation)
1.14.89-1: all
Source: zypper
trixie (Debian 13 (Trixie)) (sound): Easy to use, tracker-inspired music sequencer
0+git20250217+ds-2+b1: arm64
Source: zytrax
trixie (Debian 13 (Trixie)) (utils): library providing read access on ZIP-archives - binaries
0.13.78+dfsg.1-0.1: amd64 arm64
Source: zziplib
trixie (Debian 13 (Trixie)) (devel): transparent application fuzzer
0.15-5+b1: amd64 arm64
Source: zzuf
This operating-system view preserves native package policy. Versions, architecture labels, suites, dependency operators, patches, and maintainer fields mean what the publishing repository says they mean. A similarly named package in another system is not treated as identical.
Where two package records cite the same authoritative upstream homepage, the catalog can link them to one software project. That mapping never replaces the native package page and name matching by itself is not enough to merge projects.