[SOLVED] RPi4 luajit issues

[unformatted]

I just upgraded a RPi4 and running package-query -Au I get the following message:

$this->bbcode_second_pass_code('', '
[user@PC61 ~]$ package-query -Au
aur/luajit-git v2.1.0.beta3.r201.gdd5032ed-1 -> 2.0.5.25.g61464b0-1
')

I did not install that package explicitly myself so I tried removing it:

$this->bbcode_second_pass_code('', '
[user@PC61 ~]$ sudo pacman -Rns luajit-git
[sudo] password for user:
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing luajit-git breaks dependency 'luajit' required by gegl
:: removing luajit-git breaks dependency 'luajit' required by mpv
')

So I tried installing it from AUR:

$this->bbcode_second_pass_code('', '
[user@PC61 builds]$ git clone https://aur.archlinux.org/luajit-git.git
[user@PC61 luajit-git]$ makepkg -srci
==> ERROR: luajit-git is not available for the 'aarch64' architecture.
')

How do I get rid off this package or should I do something else?

[graysky]

$this->bbcode_second_pass_quote('unformatted', '
')$this->bbcode_second_pass_code('', '
[user@PC61 ~]$ package-query -Au
aur/luajit-git v2.1.0.beta3.r201.gdd5032ed-1 -> 2.0.5.25.g61464b0-1
')

[unformatted]

Not that I'm aware of.

$this->bbcode_second_pass_code('', '
[user@PC61 ~]$ cat /etc/pacman.conf
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = aarch64

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =

#NoUpgrade =
#NoExtract =

# Misc options
#UseSyslog
#Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
#ParallelDownloads = 5

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux ARM
# packagers with `pacman-key --populate archlinuxarm`.

#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

[alarm]
Include = /etc/pacman.d/mirrorlist

[aur]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
')

[graysky]

Are you using an official image? You or someone must have built and installed the git package.

Post the output of pacman -Qm

In any case, you have the git package installed. If you want to build a later version of the git package, add the -A switch to your makepkg call like this:
$this->bbcode_second_pass_code('', 'makepkg -srciA')

Or replace it with the non-git package assuming nothing depends on the git package:
$this->bbcode_second_pass_code('', '# pacman -S luajit')

If you want to remove it, remove the packages that require it. That can be complex but you have mpv and gegl for sure. Perhaps others. You can start with:
$this->bbcode_second_pass_code('', '# pacman -Rs mpv gegl luajit-git')

Then see what pacman tells you/if it finds more.

[unformatted]

I'm using an official image.

$this->bbcode_second_pass_code('', '
[user@PC61 ~]$ pacman -Qm
luajit-git v2.1.0.beta3.r201.gdd5032ed-1
package-query 1.12-1
')

$this->bbcode_second_pass_code('', '
[user@PC61 ~]$ sudo pacman -S luajit
[sudo] password for user:
resolving dependencies...
looking for conflicting packages...

Packages (1) luajit-2.1.0.beta3.r384.g1d7b5029-1

Total Installed Size: 0.76 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
luajit: /usr/bin/luajit exists in filesystem (owned by luajit-git)
luajit: /usr/bin/luajit-2.1.0-beta3 exists in filesystem (owned by luajit-git)
..and a lot more..
')

Besides mpv and gegl, gimp is also involved, so

$this->bbcode_second_pass_code('', '
sudo pacman -Rns mpv gegl gimp luajit-git
')

Now luajit-git is gone.

Reinstalling mpv and gimp did not introduce it again, so problem solved.

I'm running 2 more RPi4's, same architecure, which have luajit-git installed but not from AUR. So I'm keeping an eye on those when upgrading. At least I now know how to deal with it. Thanks for helping out.

[graysky]

Glad you got things sorted out. My brain was not functioning when I replied. Turns out we did provide the git package, see here. So no mystery around where it came from for you.