while xbps 0.60 did fix some issues with having the new package replace the transitional one, it only seems to work if the transitional one was already installed
reproducer:
mkdir A B root
touch A/file
xbps-create -A noarch -n A-1.0_1 -s "test pkg" --replaces "B>=0" A
xbps-create -A noarch -n B-1.0_1 -s "test pkg (transitional dummy package)" -D "A>=1.0_1" B
xbps-rindex -a *.xbps
xbps-install -R . -r root B
expected: if the transaction contains both package B and the package that replaces B (A), B should not be installed
actual:
Name Action Version New version Download size
A install - 1.0_1 -
B install - 1.0_1 -
Space available on disk: 26GB
Do you want to continue? [Y/n]
[*] Verifying package integrity
A-1.0_1: verifying SHA256 hash...
B-1.0_1: verifying SHA256 hash...
[*] Collecting package files
A-1.0_1: collecting files...
B-1.0_1: collecting files...
[*] Unpacking packages
A-1.0_1: unpacking ...
B-1.0_1: unpacking ...
[*] Configuring unpacked packages
A-1.0_1: configuring ...
A-1.0_1: installed successfully.
B-1.0_1: configuring ...
B-1.0_1: installed successfully.
0 downloaded, 2 installed, 0 updated, 2 configured, 0 removed, 0 on hold.
while xbps 0.60 did fix some issues with having the new package replace the transitional one, it only seems to work if the transitional one was already installed
reproducer:
expected: if the transaction contains both package
Band the package that replacesB(A),Bshould not be installedactual: