You are not logged in.

#1 2023-08-10 08:21:12

Bluboy234
Member
Registered: 2020-06-10
Posts: 15

Packages not in AUR

Why does this show packages not in AUR? I feel this has something to do with the new git migration. I am updating my system after some months now. I merged the pacman.conf file and also updated the mirrors.

[iwantroca@alkalimetals ~]$ yay
:: Synchronizing package databases...
 core is up to date
 extra                                           8.3 MiB  5.72 MiB/s 00:01 [##########################################] 100%
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
 -> Packages not in AUR: js78  libopenaptx  python-pep517  xorg-server-xdmx
:: 12 packages to upgrade/install.
12  core/linux-firmware          20230625.ee91452d-5 -> 20230804.7be2766d-2
11  core/linux-firmware-whence   20230625.ee91452d-5 -> 20230804.7be2766d-2
10  core/systemd                 254-1               -> 254.1-1
 9  core/systemd-libs            254-1               -> 254.1-1
 8  core/systemd-sysvcompat      254-1               -> 254.1-1
 7  extra/python-cryptography    41.0.2-1            -> 41.0.3-1
 6  extra/python-distlib         0.3.6-3             -> 0.3.7-1
 5  extra/python-more-itertools  10.0.1-1            -> 10.1.0-1
 4  extra/python-pygments        2.15.1-1            -> 2.16.1-1
 3  extra/python-virtualenv      20.21.0-1           -> 20.24.2-1
 2  aur/citra-git                r9140.bae1c3140-1   -> r9708.335fb78c5-1
 1  aur/citra-qt-git             r9140.bae1c3140-1   -> r9708.335fb78c5-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems

I have merged the pacman.conf with pacman.conf.pacnew by commenting out the community repo.
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 = auto

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

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists
#ParallelDownloads = 5
#ILoveCandy

# 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
# packagers with `pacman-key --populate archlinux`.

#
# 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.

#[testing]
#Include = /etc/pacman.d/mirrorlist

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

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

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

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

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
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

Offline

#2 2023-08-10 08:34:55

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,358
Website

Re: Packages not in AUR

Because it's an AUR helper?

Mod note: moving to AUR Issues.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2023-08-10 08:43:52

mpan
Member
Registered: 2012-08-01
Posts: 1,583
Website

Re: Packages not in AUR

Bluboy234:
All four packages are no longer in the repos, but you have them installed in your system. You can confirm by issuing:

pacman -Qmq

It seems there is a bug in yay, which would explain the misleading message.


Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!

Offline

#4 2023-08-10 09:22:19

hcjl
Member
From: berlin
Registered: 2007-06-29
Posts: 330

Re: Packages not in AUR

The output of yay is correct, as these installed packages are neither in the official repos nor in the AUR.

Offline

#5 2023-08-10 10:10:18

philo
Member
Registered: 2015-01-26
Posts: 275

Re: Packages not in AUR

Those 'missing' packages are probably not needed  any more and can be safely be removed.

Uninstalling yay would be a good idea also, even though unrelated to your original issue.

Offline

#6 2023-08-10 13:00:38

mpan
Member
Registered: 2012-08-01
Posts: 1,583
Website

Re: Packages not in AUR

hcjl wrote:

The output of yay is correct, as these installed packages are neither in the official repos nor in the AUR.

They are also not on the Moon. And not in infinitely many other places. Let’s make yay write “Packages not in Antarctic: js78 libopenaptx python-pep517 xorg-server-xdmx”.

The message is misleading: it suggest the situation bears some connection to AUR, while there is no such connection. AUR is completely out of picture there. yay simply fails to distinguish between packages it manages and other foreign packages.


Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!

Offline

#7 2023-08-10 13:23:09

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: Packages not in AUR

mpan wrote:

yay simply fails to distinguish between packages it manages and other foreign packages.

FTFY.

Failing to distinguish such categories is quite on-brand: yay also encourages users to fail to distinguish between packages in the AUR and in the repos.

That said, having a message about packages that it is unable to update would be useful - the wording should definitely change though.

Last edited by Trilby (2023-08-10 13:26:16)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#8 2023-08-10 13:31:12

Awebb
Member
Registered: 2010-05-06
Posts: 6,688

Re: Packages not in AUR

"Packages neither in a repository nor the AUR:"
"Foreign Packages not in the AUR:"

Offline

Board footer

Powered by FluxBB