Trying to install fq fails for me as follows: Preparing to unpack .../archives/fq_0.0.4-2_amd64.deb ... Unpacking fq (0.0.4-2) ... dpkg: error processing archive /var/cache/apt/archives/fq_0.0.4-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/fq_0.0.4-2_amd64.deb As these two "fq" seem to have completely different purposes, please either rename one of the commands (or both) or add a Conflicts header to conflict with the other package.
We believe that the bug you reported is fixed in the latest version of
fq, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1005961@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Milde <daniel@milde.cz> (supplier of updated fq package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 19 Feb 2022 23:12:58 +0100
Source: fq
Architecture: source
Version: 0.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Changed-By: Daniel Milde <daniel@milde.cz>
Closes: 1005961
Changes:
fq (0.0.5-1) unstable; urgency=medium
.
[ Xentripetal ]
* initial work for avro OCF files
* Hook into registry, add codecs
* Cleanup
* Change avro codec to funcs
* Regenerate docs
* Cleanup for linting
* Use existing scalar description helper
* Initial pass on logical types
* Undo change to doc/file.mp4. I have no idea how
this got changed in the first place? Maybe some macos shenanigans.
* cleanup some docs, change enum to mapper, error zigzag on more than 8 bytes
* Update linting
* Parse header using avro decoders. Still not certain
this is the best idea. Will get opinions before finalizing.
* Add test case with all data types
.
[ Mattias Wadman ]
* goreleaser: Use zip for macos
* doc: Add macOS security notes and move supported format up a bit
* id3v2: Should assert not validate magic
* zip: Assert signature not validate
* interp: Fix handling of group decode error from stdin
* pcapng,fuzz: Fix infinite loop by fatal error on block length <= 0
* mp4,fuzz: Fatal error on infinite sgpd box entries
* mpeg_spu: Fatal error on infinite loop
* fuzz: Fuzz all formats
* interp: Use correct sym color
* interp: Add grep_by/1 to recursively match using a filter
* mp3: Decrease max sync seek length between frames to 4k
.
[ bump ]
* Update make-golangci-lint from 1.43.0 to 1.44.0
* Update github-golangci-lint from 1.43.0 to 1.44.0
.
[ Mattias Wadman ]
* lint: Fix typeassert and case exhaustive warnings
* github: Add basic issue template
.
[ Joel Rangsmo ]
* Polish of problem template and clarifying questions
* Remove redudant question and fix typo
.
[ Mattias Wadman ]
* fq: Add arch and os to --version
* doc: Use f($a; $b) instead of jq f/2 notation
* decode,scalar: Add scalar.Str{Uint/Int/F}ToSym to parse numbers
* interp: Cleanup display aliases, now: d, da, dd, dv, ddv
* interp: Add Platform() method to OS interface
* doc: Add per format documentation
* doc,matroska: Fix filesname in example
* doc,interp: Add some example usages to cli help
* make: Cleanup some not very used targets
* doc: Document display and some more jq hints
* doc: More display alias leftover fixes
* protobuf: Add note about sub message decoding
* decode: Add scalars args to FieldRootBitBuf
* doc: Color edges in diagram based on dest
* bitio,decode: Refactor bitio usage and make buffer slicing more correct
* bitio: Cleanup documentation a bit
* mp4: Add video preview (pnot) and JPEG 2000 (jP) signatures
* interp: Support force decode as -o force=true
* doc: Add format links to format table
* fuzz: List seed numbers and make it build again
* decode: Rename LenFn() to LimitedFn, add FramedFn and document
* asn1_ber: Add decoder
* mp4: Add stz2 support
* aac_frame: Only try decode object types we know about
* interp: Add missing default opts for tovalue
* asn1_ber: Add more doc and multiple outputs for frompem
.
[ Xentripetal ]
* Change tests to use new verbose syntax
* Support snappy and deflate codecs
* Fix lint
.
[ Mattias Wadman ]
* binary,decode,doc: Rename buffer to binary and add some documentation
* bitio: More doc cleanup
* bitio,doc: Even more cleanup
* doc: Cleanup and add more decode value and binary documentation
.
[ Xentripetal ]
* Timestamps should be UTC
* Cleanup snappy
* Lint and add basic doc
* Take heading off doc to match make doc format
.
[ Thushan Fernando ]
* Adds Windows Scoop instructions for fq.
.
[ Mattias Wadman ]
* doc: Add more license details
.
[ Xentripetal ]
* Dates need to specify UTC too
* Comment on snappy decompression
.
[ Mattias Wadman ]
* interp: Refactor radix* into toradix($base)/fromradix($base)
* interp: Use absolute path in errors
.
[ bump ]
* Update docker-golang from 1.17.6 to 1.17.7
* Update github-go-version from 1.17.6, 1.17.6 to 1.17.7
.
[ Mattias Wadman ]
* interp: Add paste function to allow pasting text into REPL etc
* repl: Fix completion of non-underscore extkeys
* repl,interp: Make stdio work during completion
* fuzz: Make it compile again and run one format per fuzz
* gojq: Rebase fq branch
* mpeg_spu: Fatal error on unknown cmd
* doc: Add inital decoder API documentation
.
[ Xentripetal ]
* simplify scalar usage
* make doc
.
[ Mattias Wadman ]
* doc: Unbreak formats_digaram.jq since radix change
* bump: Add snappy config
* doc: Add snappy license
* doc: More decode API details and polish
* doc: Add CHANGES.md documenting release changes
* fq: Update version to 0.0.5
.
[ Daniel Milde ]
* d/control: fq conflicts with nq (Closes: 1005961)
Checksums-Sha1:
dac63ff90f37e9c3932f6d813c761afaa5fbef81 2190 fq_0.0.5-1.dsc
90bfcca4ed30fceabd9e56c2a16f8f01a614ab0a 2164165 fq_0.0.5.orig.tar.gz
0e44c80d2252af4df85052ea7b18634be34c65b1 5036 fq_0.0.5-1.debian.tar.xz
f0bb21e57316fb0f11525cad214737ff31707a9b 6857 fq_0.0.5-1_source.buildinfo
Checksums-Sha256:
f7df796027b659551958b55b11156927b4cc0675928a945931795c65c490d6ac 2190 fq_0.0.5-1.dsc
50116ed8f627258cd49b45cd474f98f1a9256229e17524e9626f64df18a86190 2164165 fq_0.0.5.orig.tar.gz
5a32446998e0f8ebb1516dfd0079604bf172b68d1f54efdf67e1c2aa9da5c16e 5036 fq_0.0.5-1.debian.tar.xz
280202367bbc0ce23e0122e944a92bf4d98d3256f986a410bde80028b04cebfd 6857 fq_0.0.5-1_source.buildinfo
Files:
ca4ebfb5d815e4ce3abbf147cef036e9 2190 utils optional fq_0.0.5-1.dsc
4c1edfda8a512fd3e288db4046987426 2164165 utils optional fq_0.0.5.orig.tar.gz
db68c72ed8e665f3094cf5013ca4e346 5036 utils optional fq_0.0.5-1.debian.tar.xz
2f9ce93b80e908c479cf93e7698c0c8d 6857 utils optional fq_0.0.5-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCgAuFiEENgtlhwehpEylf7Z+7wuhxPOZAQMFAmIRbosQHGRhbmllbEBt
aWxkZS5jegAKCRDvC6HE85kBA5wpD/9reRvt/CHds25j8AxXygp5nHCpSk4B33am
LRYaCajHVbbPDeO9ndKLCi8hlobWalEaf7fFes+WNmO4QW5Bq9fe27Na53DwKcV8
LXYPkYvTXSgiWmXMgLzDMGrDbVMCuRWCBCtWklXrIYkQnzwxLdlxsQ19UP4eNvKM
arWWoU+8hyAMHdl0Ob0M+oD4o/bhtozRs3mSP+g4z2VMq6v+VvtQb50hBeZij+Kv
5p+97qyfSaXqS2Rp5VxRJPBBzRmiCrTJ7aviJ1LemDbw6t4ODc8Z6dRnJ7qNRfrY
3Twj/fK+JbRWI7aIgyHimXz3vTcpQEWi9ROpW3H8zrV0fH3lZcA2PP2ddcBbBT37
3b5ynHUgh8iapE5+s7Fc2ZrTH0f7cjNLGHsLhysOLQQhqvahBRvhkrku7yLe7Yqr
iLgwIWiykF14i0/gy1YVlNsMGCgROuXmxoHY9HzRntEOa1oBkZrWT73A2XpBb+QJ
W93XZx5j3EJieapXz14M0lMB9G3aCvhG3gKliKqtZndk7lH0bPfip427Z0d/dux/
9GKUlm0oyFqX7Qt3Lof+QCDyOBVJjYhFb5nbzvJp60ICatQgQjq05ynWQCQLvxNr
D0s/cUBUVVYx1YAYSem8kl059ArempbzE4ObPjXPIx4ZuhGZbrf35Rsjq0WThaal
gW16G8IgLQ==
=ALXR
-----END PGP SIGNATURE-----
On 18.02.2022 08:39, Axel Beckert wrote: Hello, While preparing a NMU for nq Christoph Biedl pointed out, that the issue was solved the wrong way. According to the policy [1] "Two different packages must not install programs with different functionality but with the same filenames. (...) If this case happens, one of the programs must be renamed. The maintainers should report this to the debian-devel mailing list and try to find a consensus about which program will have to be renamed. If a consensus cannot be reached, both programs must be renamed." For now I reopen the bug, not 100% sure how to proceed. I'm not the maintainer of nq and I won't be able to make a strong decision like renaming a binary in the nq package. Hilmar [1] https://www.debian.org/doc/debian-policy/ch-files.html
I suggest fq renames the binary because it was introduced over 4 years later and has only been in one release so far.
Both packages have very low usage acc to popcon, but for fq the fq binary is the entire point of the package, whereas for nq, the fq binary seems to only be a small part of the functionality of the package. Therefore, I think that nq should rename the fq binary. Stephen
Hi, which contains only the binary /usr/bin/tq (+ man page) and argue that it has the right keep that name b/c it is the only binary in it. ;-) I rather follow the argumentation of Bastian: new packages should better care if they introduce file conflicts w/ existing packages, especially if the names of the programs are rather short. I had a look if there are packages, which needs nq or fq for building, i.e. if renaming could cause FTBFS bugs: currently there are none for both. So, we only will generate frustrated end users. Hilmar -- sigfault
Hi, nq maintainer here. I propose to make a new release 1.0, where fq is renamed to nqtail, and by default I will install a symlink fq -> nqtail. Debian (and other distros) are free to remove this symlink. Since fq is widely packaged now (https://repology.org/project/fq-inspect-binary-data/versions) I hope this will resolve the issue. Thanks,
Great, that would be perfect if you’re willing to do so! Just let me know when that’s done and I can work with the nq debian maintainer to get that uploaded. Thanks, Stephen
Stephen Gelman <ssgelm@debian.org> writes: nq 1.0 has been release without conflicting names.
We believe that the bug you reported is fixed in the latest version of
nq, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1005961@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hilmar Preuße <hille42@debian.org> (supplier of updated nq package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 06 Jul 2024 15:34:34 +0200
Source: nq
Architecture: source
Version: 1.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: nicoo <nicoo@debian.org>
Changed-By: Hilmar Preuße <hille42@debian.org>
Closes: 1005961 1038937
Changes:
nq (1.0-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
* New upstream version (Closes: #1038937).
- Incompatible change: The fq utility has been renamed to nqtail.
- Incompatible change: The tq utility has been renamed to nqterm.
This should solve the file conflict with the fq package
(Closes: #1005961).
.
* Bump Standards and dh compat version, no changes needed.
* Add upstream metadata file.
.
[ Christoph Biedl ]
* Add autopkg test.
Checksums-Sha1:
d647c9a560f828471d4ff4efbd2f85a1b2d89540 1912 nq_1.0-0.1.dsc
5aad55c59385d4f9e7fedd076f4fc90a1b2f98ee 11596 nq_1.0.orig.tar.xz
199c033ee1b0ee5367d0770af46be44699f29036 4188 nq_1.0-0.1.debian.tar.xz
a57f6c22eb32b790dad596a152daf09ccab8cc9b 5984 nq_1.0-0.1_source.buildinfo
Checksums-Sha256:
4f72ff24fb0e77f2e1b4ca82127de612f0c69afa40601abfc4786a79fe07a10f 1912 nq_1.0-0.1.dsc
756d410537abd2ca1c202c4dd09fe2d7c4bbd5e17d43f075afce36042f29339e 11596 nq_1.0.orig.tar.xz
60cf2e9cf5abb40802b677ff4d2440145714e864a2c433905f525ef9c733e7fd 4188 nq_1.0-0.1.debian.tar.xz
3d19ccdce028f293969c071bfabf9852a6924fd22a898b0301c59eab51e536f1 5984 nq_1.0-0.1_source.buildinfo
Files:
1188989343c3ede89a86b3e1d5192c41 1912 utils optional nq_1.0-0.1.dsc
44e60b0bd10268393f3486d9163ad6c5 11596 utils optional nq_1.0.orig.tar.xz
934d587c4082b32f1fd3045466735b4a 4188 utils optional nq_1.0-0.1.debian.tar.xz
343d424764f24b075ce2af68d71d300f 5984 utils optional nq_1.0-0.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmaJSNxfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIs84RAAn4TlNKkjiNbWiYj6i9n34SrceicT+C3oO5m/GvjyoWq0Dzib8yanuARO
0q6IQcBuV7M6ZRQQ2/1Ga6UycJ7x8HCBfeRkZ+1fUvI7enxtWt65tZpO+B0t9fYV
zKuLTkbXjigs46zripPf1KAuJS5tuJBse9qKvqMWSeIHOIDkQpOPTspxU8XUtxMm
iX4TybKVLUQjA0PgGZ5X6sepn3Y7UO79UKXRv/tEMgDtHokUUhXiOaWV2RI//KZ6
lKfqJROKphHUinwsWbvN4VRAU1vdIzrPYu7Emdmt0VeYVe0+Qvb+WGHM0GU8/dTU
+DK6ok5KL4H2tQi7iXi0O7OxUCBEpZbF96NbhJHAcMlGS1x+unB2+7WKFGKpz1gt
XYoboAivIqsZjbV75DwpmU1MH7LtbizhEgU3rE/aODfwZCmS3QZbjAwdsctA/g4J
TKV8po0L4JGf5sZSb5OHEm0dZVWDN0haaZDwKmffYQ0Y905ZBkJWMgTlQphCv7JI
c9bSNJSafBmk29844N1CbxIW6MBQOmfi2t31q97CvVomDHmQ3P+zpe9aTQdH71wh
UeS5HFIMvJFn4Qff1dNeTq67xUvMNQv8IZpYhEWms/5c0yxob3Xnlz/pjCr+nh6M
SJKJbUxSYBjNEcJNiLnXC7WEv7/M+6J5/xYYF/oNiKR9HzSL2l8=
=ZNFB
-----END PGP SIGNATURE-----
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran, Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun. Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie für weitere Details.
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran, Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun. Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie für weitere Details.
Es gibt eine Familienspende in Höhe von 1.850.000,00 USD von Cheng Charlie Saephan. Bitte antworten Sie für weitere Informationen. Denken Sie daran, Ihrer Familie und den Bedürftigen in Ihrer Umgebung Gutes zu tun. Dies ist bereits der zweite Versuch, Sie zu erreichen. Bitte antworten Sie für weitere Details.