On Sat, 2024-08-10 at 20:22 -0400, Kusoneko wrote: > Aug 10, 2024 20:18:48 David C. Rankin <drankinatty@xxxxxxxxx>: > > > Devs, > > > > I was surprised trying to install a python-tqdm package to get > > the error: > > > > (2/2) checking for file conflicts > > [######################################] 100% > > error: failed to commit transaction (conflicting files) > > python-tqdm: /usr/bin/tqdm exists in filesystem > > Errors occurred, no packages were upgraded. > > > > The package is there: > > > > $ l /usr/bin/tqdm > > -rwxr-xr-x 1 root root 206 Jul 8 2021 /usr/bin/tqdm > > > > I check with pacman to find the owning package -- and there is > > none: > > > > $ pacman -Qo /usr/bin/tqdm > > error: No package owns /usr/bin/tqdm > > > > How can I check how it got there and what may depend on it? I > > don't install stray packages, and especially not to /usr/bin, so > > this is a surprise. I don't want to just willy-nilly remove it > > either and have something unknown break. > > > > Best course of action? > > > > -- > > David C. Rankin, J.D.,P.E. > You can probably just delete it and any other file that conflicts for > this. It was likely installed through `pip install -g` which is why > pacman isn't tracking it or what package it's from, if you're > replacing it with python-tqdm from the pacman repository, whatever > installed it through pip shouldn't be able to tell the difference. > > -- > Kusoneko > GPG: https://kusoneko.moe/gpg.txt > https://kusoneko.moe And if you're really worried about something breaking, you can always rename the file, install python-tqdm, and see if anything breaks. If anything does then you can easily revert by just renaming the binaries. Perhaps the tqdm versions are the same and you won't even need to do anything. -- Best regards, Brian
Attachment:
publickey - brianrobt@pm.me - 0x688B900B.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
