FS#67565 - [lua53-lgi] shoud have a "replaces"entry for lua-lgi
Attached to Project:
Arch Linux
Opened by Stefan Husmann (stefanhusmann) - Wednesday, 12 August 2020, 20:06 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 22:14 GMT
Opened by Stefan Husmann (stefanhusmann) - Wednesday, 12 August 2020, 20:06 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 22:14 GMT
|
Details
Description: After the lua 5.4 rollout the lua53-lgi package
was added to the repos, but without a "replaces" field. This
leads to strange messages if one runs pacman -Qi awesom, for
instance, claiming that awesome needs lua-lgi, which is no
longer true. See
https://bbs.archlinux.org/viewtopic.php?id=258099
for a discussion
Additional info: * package version(s): 0.9.2-3 * config and/or log files etc.: see https://bbs.archlinux.org/viewtopic.php?id=258099 * link to upstream bug report, if any Steps to reproduce: pacman -Qi awesome (or any other package depending on "old lua-lgi" |
This task depends upon
Comment by
Eli Schwartz (eschwartz) -
Wednesday, 12 August 2020, 20:37 GMT
Comment by
Axel Schroeder (danran) - Tuesday,
03 November 2020, 18:56 GMT
Comment by Vinh Vu (Vinhvu95) -
Monday, 14 December 2020, 21:59 GMT
Comment by
Balló György (City-busz) - Thursday,
08 June 2023, 22:14 GMT
- Field changed: Status (Unconfirmed → Assigned)
- Task assigned to Levente Polyak (anthraxx), Felix Yan (felixonmars)
The bigger issue is automatically guaranteeing -Syu results in
replacing one with the other and the upgrade succeeding, vs.
default-fail conflicting packages that break awesome and therefore
the upgrade if you just type <ENTER> or use --noconfirm
Any ETA for this? My arch upgrade keeps failing b/o this and I
don't know a workaround (sorry, newbie...)
For other newbies like me, you can fix the problem by using the
pacman -Rdd command to remove lua-lgi. Hopefully other people can
correct me if I am wrong. The extra -dd command will ignore
dependencies.
Both lua53-lgi and lua-lgi are available in the repositories, and
they have no conflicting files, so I assume it was fixed.