[SOLVED] upgradepkg installed package as new
by zdolar from LinuxQuestions.org on (#56AVV)
Hi!
For a long time I'm using Code:upgradepkg --reinstall --install-new for upgrade of packages I compiled.
For others (system, alien, ktown..) I use slackpkg+.
Recently I was surprised when I found:
/var/lib/pkgtools//packages/zoneminder-1.34.14-x86_64-GIT-20200520_ZD
/var/lib/pkgtools//packages/zoneminder-1.34.15-x86_64-GIT-20200522_ZD
/var/lib/pkgtools//packages/zoneminder-1.35.4-x86_64-GIT-20200604_ZD
/var/lib/pkgtools//packages/zoneminder-1.35.5-x86_64-GIT-20200730_ZD
on my test machine.
What could be the reason for the above? Does upgradepkg consider a minor package version change as a new package and so install a new version as a totally different program?
So far I did not notice such behavior of upgradepkg.
Using oldpkg%newpkg notation would be unnecessary complication.
For a long time I'm using Code:upgradepkg --reinstall --install-new for upgrade of packages I compiled.
For others (system, alien, ktown..) I use slackpkg+.
Recently I was surprised when I found:
/var/lib/pkgtools//packages/zoneminder-1.34.14-x86_64-GIT-20200520_ZD
/var/lib/pkgtools//packages/zoneminder-1.34.15-x86_64-GIT-20200522_ZD
/var/lib/pkgtools//packages/zoneminder-1.35.4-x86_64-GIT-20200604_ZD
/var/lib/pkgtools//packages/zoneminder-1.35.5-x86_64-GIT-20200730_ZD
on my test machine.
What could be the reason for the above? Does upgradepkg consider a minor package version change as a new package and so install a new version as a totally different program?
So far I did not notice such behavior of upgradepkg.
Using oldpkg%newpkg notation would be unnecessary complication.