Why does yay always ask me that?

Hello to all,

I don’t understand why, when I do yay, it always tells me that some packages (let’s take the zoom example) are not up to date.
Whereas when I do a yay -Sy zoom, it seems to tell me that it is already up to date.

Do you have an idea?
Thank you!

$ yay
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
 -> Missing AUR Packages:  gtkhash-nautilus  manjaro-documentation-en  manjaro-dynamic-wallpaper  manjaro-firmware  noto-fonts-compat  vino
 -> Flagged Out Of Date AUR Packages:  zoom
:: 4 Packages to upgrade.
4  aur/android-studio         2021.3.1.17-1         -> 2022.1.1.19-1
3  aur/virtualbox-ext-oracle  7.0.2-1               -> 7.0.6-1
2  aur/yay-git                11.3.1.r56.g0f45a99-1 -> 11.3.1.r92.gc40e949-1
1  aur/zoom                   5.12.6-1              -> 5.13.4-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
yay -Sy zoom
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  zoom-5.13.4-1

  1 zoom                                     (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> N
:: PKGBUILD up to date, Skipping (1/0): zoom
  1 zoom                                     (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> N
:: (1/1) Parsing SRCINFO: zoom
==> Making package: zoom 5.13.4-1 (Thu 19 Jan 2023 04:11:35 PM CET)
==> Retrieving sources...
  -> Found zoom-5.13.4.711_orig_x86_64.pkg.tar.xz
==> Validating source files with sha512sums...
    zoom-5.13.4.711_orig_x86_64.pkg.tar.xz ... Passed
==> Making package: zoom 5.13.4-1 (Thu 19 Jan 2023 04:11:36 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found zoom-5.13.4.711_orig_x86_64.pkg.tar.xz
==> Validating source files with sha512sums...
    zoom-5.13.4.711_orig_x86_64.pkg.tar.xz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting zoom-5.13.4.711_orig_x86_64.pkg.tar.xz with bsdtar
==> Starting prepare()...
==> Sources are ready.
==> Making package: zoom 5.13.4-1 (Thu 19 Jan 2023 04:11:45 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Sources are ready.
 -> zoom-5.13.4-1 already made -- skipping build
1 Like

zoom has been flagged as out-of-date on the AUR website but has not yet been updated by the maintainer.

See:
https://aur.archlinux.org/pkgbase/zoom/flag-comment

1 Like

You chose to use the AUR, so you should know what it means.

“Flagged out of date” means that someone flagged the package as out-of-date. The maintainer receives an email and is requested to update the package.

2 Likes

These has been deprecated and therefore removed from the repo.

When yay see’s files not in the official repo - it searches AUR - hence the message stating - these packages aren’t in AUR either.

Remove them as they are obsolete.

sudo pacman -Rns gtkhash-nautilus  manjaro-documentation-en  manjaro-dynamic-wallpaper  manjaro-firmware  noto-fonts-compat  vino
1 Like

It’s a good thing we don’t have to master a technology perfectly to use it, otherwise most of the people wouldn’t use much :slight_smile:

Thanks for the answer anyway!

Okay, for that I get it! Thanks

I agree with Zoom. But for Android Studio for example?

yay -Sy android-studio
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  android-studio-2022.1.1.19-1

  1 android-studio                           (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>  
:: PKGBUILD up to date, Skipping (1/0): android-studio
  1 android-studio                           (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: (1/1) Parsing SRCINFO: android-studio
==> Making package: android-studio 2022.1.1.19-1 (Thu 19 Jan 2023 04:52:55 PM CET)
==> Retrieving sources...
  -> Found android-studio-2022.1.1.19-linux.tar.gz
  -> Found android-studio.desktop
  -> Found license.html
==> Validating source files with sha256sums...
    android-studio-2022.1.1.19-linux.tar.gz ... Passed
    android-studio.desktop ... Passed
    license.html ... Passed
==> Making package: android-studio 2022.1.1.19-1 (Thu 19 Jan 2023 04:52:59 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found android-studio-2022.1.1.19-linux.tar.gz
  -> Found android-studio.desktop
  -> Found license.html
==> Validating source files with sha256sums...
    android-studio-2022.1.1.19-linux.tar.gz ... Passed
    android-studio.desktop ... Passed
    license.html ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting android-studio-2022.1.1.19-linux.tar.gz with bsdtar
==> Sources are ready.
==> Making package: android-studio 2022.1.1.19-1 (Thu 19 Jan 2023 04:53:11 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Sources are ready.
 -> android-studio-2022.1.1.19-1 already made -- skipping build

@TuxJaro, it is something wrong with your yay-git installation.

I recommend you replace it with yay from the community repository:

sudo pacman -S yay

And you are not the only one with this problem:

1 Like

It works!
Thank you !!!

14 posts were split to a new topic: Useless AUR helper debate: Yay vs. Paru