On 2024/9/27 14:06, Helmut Grohne wrote:
Package: trippy Version: 0.11.0+dfsg-1+b1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + vasttrafik-clitrippy has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/bin/trip is contained in the packages * trippy/0.11.0+dfsg-1+b1 as present in unstable * vasttrafik-cli/1.11-2 as present in trixie|unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file.
Thanks Helmut for bringing this to attention.In hindsight, "trip" is a largely generic name. I kinda overlooked it when packaging trippy. OTOH, vasttrafik-cli only serves a specific county (first level of administrative divison) of Sweden, namely Västra Götaland, which IMHO doesn't quite fit either (something with a global coverage could, for example).
Replaces is inappropriate: trippy is mtr (ping + traceroute) in TUI, while vasttrafik-cli is a client for some (physical!) public transport service. Conflicts kinda works, but it's totally possible someone from that county wants to use both. And I don't really want to resort to diversion.
Salvo, I suggest we both "take a step back"; the executable of trippy could be renamed to, well, trippy (upstream is very cooperative so it shouldn't be a problem); I imagine vasttrafik-cli could use something like vt-trip or vttrip, but that's your call. What do you think?
-- Sdrager, Blair Noctis
OpenPGP_signature.asc
Description: OpenPGP digital signature
