Details about package zsv
| Name: | zsv | 
|---|---|
| Uploader: | Azeem Sajid <azeem.sajid@gmail.com> (Debian QA page) | 
| Description: | zsv - tabular data swiss-army knife CLI zsv-dev - world's fastest (SIMD) CSV parser library | 
Package uploads
Upload #2
Information
| Version: | 1.0.1-1 | 
|---|---|
| Uploaded: | 2025-10-31 05:57 | 
| Source package: | zsv_1.0.1-1.dsc | 
| Distribution: | unstable | 
| Section: | utils | 
| Priority: | optional | 
| Homepage: | https://github.com/liquidaty/zsv | 
| Vcs-Browser: | https://github.com/liquidaty/zsv | 
| Vcs-Git: | https://github.com/liquidaty/zsv.git | 
| Closes bugs: | #1119153 | 
Changelog
zsv (1.0.1-1) unstable; urgency=medium . * Initial release (Closes: #1119153)
QA information
- 
        –
        Package uses debhelper-compatDebhelper compatibility level 13
- 
        –
        
Package is the latest upstream versionLocal: 1.0.1 Upstream: 1.0.1 Url: https://github.com/liquidaty/zsv/archive/refs/tags/v1.0.1.tar.gz 
- 
        –
        
Package is not nativeFormat: 3.0 (quilt) 
- 
        –
        "Maintainer" email is the same as the uploader
- 
        –
        Package has lintian informational tagszsv- 
I
spelling-error-in-binary
- errror error [usr/bin/zsv]
- initalize initialize [usr/bin/zsv]
- libary library [usr/bin/zsv]
 
 zsv source- 
X
debian-watch-does-not-check-openpgp-signature
- [debian/watch]
 
- 
O
custom-compression-in-debian-rules
- dh_builddeb -- -Zxz [debian/rules:12] (override comment: On Ubuntu, the default compression used is Zstandard. The `override_dh_builddeb` in rules files overrides this for `xz`.)
 
- 
O
maintainer-manual-page
- [debian/zsv.1] (override comment: For now, the manpage `zsv.1` needs intermediate manual handling. So, it is not meant to be pushed to the upstream.)
 
- 
O
package-does-not-install-examples
- [examples/] (override comment: The examples are not supposed to be installed for the binary. They serve as a sample to work with the zsvlib APIs.)
 
- 
O
very-long-line-length-in-source-file
- 1078 > 512 [data/stack2-2.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 1109 > 512 [app/test/expected/test-stack2.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 1374 > 512 [data/test/buffsplit_quote.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 282431 > 512 [data/loans_1.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 300004 > 512 [data/bigger-than-buff.csv:2] (override comment: There are CSV data and output files with very long line lengths.)
- 3092 > 512 [app/test/expected/test-flatten-2.out:10] (override comment: There are CSV data and output files with very long line lengths.)
- 3933 > 512 [app/test/expected/test-serialize-quoted.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-auto-after-applied.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-auto-after-ignored.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-auto-before.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-csv.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo1.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [app/test/expected/test-2tsv-1.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [app/test/expected/test-flatten.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [app/test/expected/test-merge-select.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/2json.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/2tsv-1.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/desc.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/pretty.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/serialize.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/sql.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4593 > 512 [app/test/expected/test-select-x.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4609 > 512 [app/test/expected/test-select.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4611 > 512 [app/test/expected/test-4-select.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 72941 > 512 [data/stack2-1.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 8171 > 512 [data/loans_1-overwrite.db:1] (override comment: There are CSV data and output files with very long line lengths.)
- 9182 > 512 [app/test/expected/test-sql3.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 9183 > 512 [data/test/select-merge.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
 
 
- 
I
spelling-error-in-binary
- 
        –
        Package closes ITP bug
- 
        –
        Package is not in Debian
- 
        –
        
d/copyright is in DEP5 formatUpstream Contact: Liquidaty <info@liquidaty.com> Licenses: Expat 
Comments
No comments
Upload #1
Information
| Version: | 1.0.1-1 | 
|---|---|
| Uploaded: | 2025-10-29 13:12 | 
| Source package: | zsv_1.0.1-1.dsc | 
| Distribution: | unstable | 
| Section: | utils | 
| Priority: | optional | 
| Homepage: | https://github.com/liquidaty/zsv | 
| Vcs-Browser: | https://github.com/liquidaty/zsv | 
| Vcs-Git: | https://github.com/liquidaty/zsv.git | 
| Closes bugs: | #1119153 | 
Changelog
zsv (1.0.1-1) unstable; urgency=medium . * Initial release (Closes: #1119153)
QA information
- 
        –
        Package uses debhelper-compatDebhelper compatibility level 13
- 
        –
        
Package is the latest upstream versionLocal: 1.0.1 Upstream: 1.0.1 Url: https://github.com/liquidaty/zsv/archive/refs/tags/v1.0.1.tar.gz 
- 
        –
        
Package is not nativeFormat: 3.0 (quilt) 
- 
        –
        "Maintainer" email is the same as the uploader
- 
        –
        Package has lintian informational tagszsv- 
I
spelling-error-in-binary
- errror error [usr/bin/zsv]
- initalize initialize [usr/bin/zsv]
- libary library [usr/bin/zsv]
 
 zsv source- 
X
debian-watch-does-not-check-openpgp-signature
- [debian/watch]
 
- 
O
custom-compression-in-debian-rules
- dh_builddeb -- -Zxz [debian/rules:12] (override comment: On Ubuntu, the default compression used is Zstandard. The `override_dh_builddeb` in rules files overrides this for `xz`.)
 
- 
O
maintainer-manual-page
- [debian/zsv.1] (override comment: For now, the manpage `zsv.1` needs intermediate manual handling. So, it is not meant to be pushed to the upstream.)
 
- 
O
package-does-not-install-examples
- [examples/] (override comment: The examples are not supposed to be installed for the binary. They serve as a sample to work with the zsvlib APIs.)
 
- 
O
very-long-line-length-in-source-file
- 1078 > 512 [data/stack2-2.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 1109 > 512 [app/test/expected/test-stack2.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 1374 > 512 [data/test/buffsplit_quote.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 282431 > 512 [data/loans_1.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 300004 > 512 [data/bigger-than-buff.csv:2] (override comment: There are CSV data and output files with very long line lengths.)
- 3092 > 512 [app/test/expected/test-flatten-2.out:10] (override comment: There are CSV data and output files with very long line lengths.)
- 3933 > 512 [app/test/expected/test-serialize-quoted.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-auto-after-applied.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-auto-after-ignored.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-auto-before.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite-csv.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo-overwrite.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4536 > 512 [app/test/expected/test-echo1.out:5] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [app/test/expected/test-2tsv-1.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [app/test/expected/test-flatten.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [app/test/expected/test-merge-select.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/2json.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/2tsv-1.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/desc.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/pretty.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/serialize.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4591 > 512 [data/test/sql.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4593 > 512 [app/test/expected/test-select-x.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4609 > 512 [app/test/expected/test-select.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 4611 > 512 [app/test/expected/test-4-select.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 72941 > 512 [data/stack2-1.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
- 8171 > 512 [data/loans_1-overwrite.db:1] (override comment: There are CSV data and output files with very long line lengths.)
- 9182 > 512 [app/test/expected/test-sql3.out:1] (override comment: There are CSV data and output files with very long line lengths.)
- 9183 > 512 [data/test/select-merge.csv:1] (override comment: There are CSV data and output files with very long line lengths.)
 
 
- 
I
spelling-error-in-binary
- 
        –
        Package closes ITP bug
- 
        –
        Package is not in Debian
- 
        –
        
d/copyright is in DEP5 formatUpstream Contact: Liquidaty <info@liquidaty.com> Licenses: Expat 
Comments
- 
        
- 
        Hi Alex, Thank you for the review! For `-$(MAKE) clean`, lintian emits the `debian-rules-ignores-make-clean-error`. URL: https://lintian.debian.org/tags/debian-rules-ignores-make-clean-error `$(MAKE) clean` works fine. Could you please confirm the same? 
- 
        Hi Azeem, I can't confirm, dget the .dsc link, then debuild ends with: $ debuild dpkg-buildpackage -us -uc -ui dpkg-buildpackage: info: source package zsv dpkg-buildpackage: info: source version 1.0.1-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Azeem Sajid <azeem.sajid@gmail.com> dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/scratch/mentors/test2/zsv-1.0.1' /usr/bin/make clean make[2]: Entering directory '/scratch/mentors/test2/zsv-1.0.1' Makefile:14: *** Config file config.mk not found. Stop. make[2]: Leaving directory '/scratch/mentors/test2/zsv-1.0.1' make[1]: *** [debian/rules:23: override_dh_auto_clean] Error 2 make[1]: Leaving directory '/scratch/mentors/test2/zsv-1.0.1' make: *** [debian/rules:4: clean] Error 2 dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2 debuild: fatal error at line 1185: dpkg-buildpackage -us -uc -ui failed 
- 
        Alex, Uploaded another revision #2 with the fix. Verified it locally as well. It should work fine now. Thanks! 
- 
        Azeem, You want to devendor zsv (+ds (debian source)), removing libyajl. And build-depend on libyajl-dev. First upload should be -1 (drop the 2nd line from changelog). If you need help tell me. 
- 
        Alex, Sure, I'll update the changelog. Regarding libyajl, its official version is not being used. The official released version of libyajl is 2.1.0. In zsv, it's being used from this fork https://github.com/liquidaty/yajl. Looks like devendoring is not needed here. Let me know how to proceed with this. Thanks! 
- 
        we will have to see if this can be fixed and try to use this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040044 
- 
        Just looked at the forks mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040044. They seem to be doing their own thing. Just to add more context: The fork https://github.com/liquidaty/yajl is by the `zsv` owner from https://github.com/lloyd/yajl. zsv : https://github.com/liquidaty/zsv yajl (fork): https://github.com/liquidaty/yajl This fork has specifically been updated to integrate with `zsv`. See changes: https://github.com/lloyd/yajl/compare/master...liquidaty:yajl:master `zsv` is bundled with this updated yajl version from the fork. 
- 
        maybe try to make the lib not public or https://wiki.debian.org/StaticLinking ? 
- 
        It's already being compiled and linked directly to the binary, not linked as a dynamic library. Here's the output of `ldd`: $ ldd /usr/bin/zsv linux-vdso.so.1 (0x00007ffc641f4000) libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 (0x00007fcfdbd4e000) libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007fcfdbd1c000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fcfdbc35000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fcfdba0c000) /lib64/ld-linux-x86-64.so.2 (0x00007fcfdbfb9000) 
- 
        This issue should be resolved somehow: E: zsv: embedded-library yajl [usr/bin/zsv] either don't provide zsv-dev at all (or do you know anyone wants/uses this?) or if you want to provide it, or build it as shared library (.so), with libzsv-dev/libzsv0 or really get yajl package to use this upstream but making sure these still work: $ apt-cache rdepends libyajl-dev libyajl-dev Reverse Depends: libraptor2-dev libwgdb-dev ruby-ffi-yajl $ apt-cache rdepends libyajl2 libyajl2 Reverse Depends: libyajl-dev tcl-yajltcl yajl-tools collectd xen-utils-4.20 libxenmisc4.20 libwgdb0 uwsgi-core libtulip-core-6.0 siridb-server libraptor2-0 python3-ijson libapache2-mod-security2 libmodsecurity3t64 kcat i3status i3-wm crun collectd-core 
- 
        Thank you for your feedback, Alex! IIUC, this error: E: zsv: embedded-library yajl [usr/bin/zsv] means that it is coming from `zsv` and not `zsv-dev`, right? Regarding providing `zsv-dev`, `zsv` is extensible. It provides an extension model by static/dynamic libraries. AFAIK, it is being used to write custom extensions by other devs. Regarding the shared library: - yes, it can be built i.e. `zsv-dev` with `libzsv.so`, and - `zsv` with the static executable. Would that resolve the above issue? 
- 
        Correction: "static" => "dynamic" `zsv` with the dynamic executable ^^^^^^^
- 
        As suspected, the error is in the `zsv` package, not `zsv-dev`. I am able to reproduce it on my side. zsv: $ lintian zsv_1.0.1-1_amd64.deb E: zsv: embedded-library yajl [usr/bin/zsv] $ echo $? 2 zsv-dev: $ lintian zsv-dev_1.0.1-1_amd64.deb $ echo $? 0 Dropping `zsv-dev` package does not work. I am working on it.
 
                
I had to change debian/rules as following, because the clean target of make would fail: override_dh_auto_install: $(MAKE) install override_dh_auto_test: override_dh_strip: dh_strip --no-automatic-dbgsym override_dh_auto_clean: -$(MAKE) clean