Package upgrade outside of slackpkg using pip confuses package database
by silverlining from LinuxQuestions.org on (#4Y456)
This is my first post. I have Slackware 14.2 64-bit. I needed to have pip, which for some reason isn't included with the full install. I downloaded pip 9.0.3 from SlackBuilds and installed it using Slackpkg. When I ran 'pip list' to check, it suggested I upgrade to version 19.3.1 via the 'pip install --upgrade pip' command. I did that and a message said that it deleted pip 9.0.3 and installed the new version.
However, running pkgtool showed pip 9.0.3 still installed. Just for curiosity, I used pkgtool to remove the pip 9.0.3 package, which it said it did. But come to find out, it really removed the upgraded one. So pip evidently didn't update the install log (didn't delete the old version and didn't add the new version to the log) but yet the upgraded version 19.3.1 was actually tied to the old version that pkgtool saw and removed. Is there a more correct way to do this so that the package database stays accurate?
However, running pkgtool showed pip 9.0.3 still installed. Just for curiosity, I used pkgtool to remove the pip 9.0.3 package, which it said it did. But come to find out, it really removed the upgraded one. So pip evidently didn't update the install log (didn't delete the old version and didn't add the new version to the log) but yet the upgraded version 19.3.1 was actually tied to the old version that pkgtool saw and removed. Is there a more correct way to do this so that the package database stays accurate?