acpid-doc and bacula-doc: dump contents to the root of the /usr/share/doc hierarchy, (may) clobber each other in the process
While attempting to install every single package in the Alpine v3.17 main and community repos in a virtual machine (entirely for meme reasons) using apk
, I encountered this warning:
WARNING: bacula-doc-13.0.1-r0: overwriting usr/share/doc/README owned by acpid-doc-2.0.34-r0.
This, in itself, is a problem. This same conflict does happen in a non-meme VM, so it's not the pure force of my Science™ causing apk to break.
oops:~# apk add acpid-doc
(1/1) Installing acpid-doc (2.0.34-r0)
OK: 52 MiB in 50 packages
oops:~# apk add bacula-doc
(1/1) Installing bacula-doc (13.0.1-r0)
ERROR: bacula-doc-13.0.1-r0: trying to overwrite usr/share/doc/README owned by acpid-doc-2.0.34-r0.
1 error; 52 MiB in 51 packages
The fact that they're clobbering each other's usr/share/doc/README files is also very suspect. Why are these 2 doc packages installing to /usr/share/doc directly, and not under their own folders within the hierarchy? That doesn't seem right.
To more precisely demonstrate this, here's the output of apk manifest acpid-doc
:
sha1:075d599585584bb0e4b526f5c40cb6b17e0da35a usr/share/doc/COPYING
sha1:339a28465a901e321a81403dacb637983fba4ba9 usr/share/doc/Changelog
sha1:b04de9409f065ea39619b899f30860ce312e2a2e usr/share/doc/README
sha1:45c94374b5a6df4a7b4e85dc091a671b5482809c usr/share/doc/TESTPLAN
sha1:3327b0be482c8076e4ccd6a3174e6725636b3c0a usr/share/doc/TODO
sha1:aa4872e0f99ef93d37a14110ad206f0a6aec3de0 usr/share/man/man8/acpi_listen.8.gz
sha1:d306c468af5bb066d4b1b0f0d6db26735f5cdbfe usr/share/man/man8/acpid.8.gz
sha1:5c8015db98ef60f9fe90f4014c63f602140fce89 usr/share/man/man8/kacpimon.8.gz
On an install without acpid-doc
installed, performing apk manifest bacula-doc
:
sha1:928575ad4b9a18e0a76d798f3bd853bb4b42b46e usr/share/doc/ChangeLog
sha1:96658e73578d8b9ca94b430833ff58161cd76799 usr/share/doc/INSTALL
sha1:72c5b51c522eaa1819d12f12bf7a9c7a74047706 usr/share/doc/LICENSE
sha1:ccc7343c8a9d663ffacb0402c879d5653514834f usr/share/doc/LICENSE-FAQ
sha1:7afcc86fc1c9ee302cf1e7410f111c3a5d5dbcc5 usr/share/doc/LICENSE-FOSS
sha1:7f60076b681be6ec7cc223af53972cddfdc77265 usr/share/doc/README
sha1:06b21222367271d3cd591a82f8b8b1cbfc27bf2f usr/share/doc/ReleaseNotes
sha1:31569eb8cafca0bb8d00c7370b7d908325e59fa5 usr/share/doc/VERIFYING
sha1:5fd458890f2be0623d4e29811c17961dc7513530 usr/share/man/man1/bat.1.gz
sha1:eb4f50c272e31aeb185e4eff77e89a383c2d77d4 usr/share/man/man1/bsmtp.1.gz
sha1:35315e8d28b80967066d405f0c22d9eb90c81bbe usr/share/man/man8/bacula-dir.8.gz
sha1:15819aeb5d27090da22c82080d58734568336b92 usr/share/man/man8/bacula-fd.8.gz
sha1:7c22ee14eb3d64e45c1f08bef47c784dfae0b7e8 usr/share/man/man8/bacula-sd.8.gz
sha1:8c072a855018cd139ca0c1fc0979ce8cca413814 usr/share/man/man8/bacula.8.gz
sha1:e9a8aba9319efba7cfd1d0390a9392e675599d18 usr/share/man/man8/bconsole.8.gz
sha1:b7266818a19b40143a848358b6abb9a49e96ff00 usr/share/man/man8/bcopy.8.gz
sha1:3529a4dfa66c2074223c599dcc5dbfd6a3ea0bb8 usr/share/man/man8/bextract.8.gz
sha1:9e37ab489012bfd757e2076daa55bbbf78fe71be usr/share/man/man8/bls.8.gz
sha1:6793c3a75506ef342be333fb83a30bc8661f179f usr/share/man/man8/bregex.8.gz
sha1:6add9d372f1bc0e95433f6bde53c1ac7fd93a51b usr/share/man/man8/bscan.8.gz
sha1:5e4f96a8f4ccfca781c363752fbd9bcd7727290a usr/share/man/man8/btape.8.gz
sha1:497ebf685003c0461cb76e208cfc675bb7040d38 usr/share/man/man8/btraceback.8.gz
sha1:3021ac84f143d9b45e73cede9831cd733a04458d usr/share/man/man8/bwild.8.gz
sha1:9df95554cfa6809345a6484b7beeb9c7cf1f89bc usr/share/man/man8/dbcheck.8.gz
Reviewing the APKBUILDs for bacula
and acpid
(and not being confident enough to write a patch against them), their man prefixes appear to be sane, but the doc prefixes end up placing their docs under the hierarchy bare.