install then upgrade issue with non default RPM locations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: install then upgrade issue with non default RPM locations

Hello Everyone,

I encountered an issue (rpm-4.1.1 RH9/YD3) when installing then upgrading a package using non-default RPM locations (relocating with --prefix). This is to test install, upgrade procedure without messing up with existing installation/database.

When I'm trying to upgrade (rpm -Uvh --nodeps --prefix ... --dbpath ... ...) previously installed (rpm -ivh --nodeps --prefix ... --dbpath ... ...) package, the RPM database reflects the change, however the actual files/directories get deleted from the file system.

This does not happen if the above is done using default RPM locations, no '--prefix ...'.

Is this something that anybody encountered before or has solution for?

Note, the package itself is not really much but one simple shell script file in /bin directory. Two different versions of same packages are not really different, it is only the spec release number that has changed.

Thanks in advance.

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux