I have updated system with yay and brave browser was flagged out of date

General system Newbie
1

When I updated system with yay -Syu I got a message:

-> Flagged Out Of Date AUR Packages: brave-bin

is this permenant or will be updated soon.

This post is because I use Brave extensivly for my class youtube forum etc…

an I had another post regarding timeshift errors on update with pacman, but didn’t see those errors or any timeshift autosnap message on updating via yay.

Update message:

(1/5) upgrading linux                                                                                [------------------------------------------------------------] 100%
(2/5) upgrading linux-headers                                                                        [------------------------------------------------------------] 100%
(3/5) upgrading linux-lts54                                                                          [------------------------------------------------------------] 100%
(4/5) upgrading linux-lts54-headers                                                                  [------------------------------------------------------------] 100%
(5/5) upgrading r8168                                                                                [------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Updating module dependencies...
(3/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.15.7-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.15.7-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts54.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts54 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts54.img
==> Starting build: 5.4.164-1-lts54
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts54.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts54.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts54 -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts54-fallback.img -S autodetect
==> Starting build: 5.4.164-1-lts54
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts54-fallback.img
==> Image generation successful
(4/6) Check if user should be informed about rebooting after certain system package upgrades.
(5/6) Cleaning Pacman Cache.... ;)
==> no candidate packages found for pruning
(6/6) Checking which packages need to be rebuilt
:: Searching databases for updates...
:: Searching AUR for updates...
 -> Flagged Out Of Date AUR Packages:  brave-bin
 there is nothing to do
2

It will be updated once the package maintainer updates the package.

2 Likes
3

You can monitor your package status (or any other package using search function) here (AUR) and here (normal repos) as well.

1 Like
4

As of 05:25 hrs (EST Canada) it is fine and I just updated it here (version 1.32.115). You must have gotten the message during a small window of time.

If you run yay -Qua it will tell you all AUR updates pending, as well as detail things like flags for outdated…

5

This often happens when a newer version of a particular package is released and is not updated in the AUR by its maintainer for a period of time.

6

but older version dangerous right, If it remains like that.

does this happens to all aur package

7

it sometimes takes time for a person to package it generally most packages are updated pretty quickly on Arch, especially popular apps like browsers.

8

You should invest some time and effort into understanding how the AUR works, ideally before using it (but that toothpaste is already out of the tube). There are some great posts on this forum about it. Look it up.

Using the AUR without understanding how it works is potentially more dangerous than using a slightly outdated browser.

2 Likes
9

It’s most dangerous when an orphaned package gets a new maintainer. That new maintainer could be malicious and it’s up to you too make that call.

You are the artisan of your own computer. If you don’t want to be, Arch/Endeavour may not be for you.

10

It happens all the time. Several days could go by before a new version is available. It is nothing to be worried about, being on EndeavourOS for 2 months now, I can say it will be replaced. Currently LibreWolf is flagged, before that Snapd and Bulky were for me. The packages still work. In closing Arch, Manjaro, EndeavourOS are more hands on then the Debian/Ubuntu distros. You should expect to investigate more before just doing something. Arch might not be for you.

11

FYI, -Syu is completely unnecessary with yay. Just type yay, it is an alias to yay -Syu

source:

2 Likes