FS#41854 - install replacement package right after the previous package is removed

Attached to Project: Pacman
Opened by Damian Nowak (Nowaker) - Sunday, 07 September 2014, 14:34 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 07 September 2014, 14:41 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

root@nowaker ~ # pacman -Syu
<< sync snipped >>
:: Replace lzo2 with core/lzo? [Y/n]
resolving dependencies...
looking for inter-conflicts...

Packages (69): << snipped >> lzo-2.08-3 lzo2-2.08-1 [removal] << snipped >>

Total Download Size: 246.14 MiB
Total Installed Size: 720.32 MiB
Net Upgrade Size: 24.47 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages ...

<< downloads snipped >>

(1/1) removing lzo2 [#############################################################################] 100%
( 1/68) upgrading bash [#############################################################################] 100%
New optional dependencies for bash
bash-completion: for tab completion
( 2/68) upgrading ca-certificates-java [#############################################################################] 100%
( 3/68) upgrading openssl [#############################################################################] 100%
^C
Interrupt signal received
( 4/68) upgrading coreutils [#############################################################################] 100%
pacman -Syu 34.59s user 4.27s system 72% cpu 53.284 total
root@nowaker ~ # pacman -Syu --ignore oraclejdk7-64
pacman: error while loading shared libraries: liblzo2.so.2: cannot open shared object file: No such file or directory


Yeah, I hit ^C, my fault. Manually copied liblzo2 binaries back and all works.

I'd just want to suggest improving how package replacements are handled by Pacman. What I see from the output is that lzo2 package was removed without a replacement being installed right after that. It would be installed at some later point I guess. If lzo package was installed right after lzo2 was removed, it would be really hard to get system to the state I encountered.

Thanks.
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 07 September 2014, 14:41 GMT
Reason for closing:  Duplicate
Additional comments about closing:  FS#23011

Loading...