Arch Linux

LinuxLover471

Member

From: Asia, India

Registered: 2025-02-23

Posts: 172

[SOLVED] What exactly counts as out-of-date in the AUR?

Hi! I hope that you are doing well.

I recently saw a few packages on the AUR with outdated dependencies, and one with a missing LICENSE file. I wanted to know when exactly is a package considered out-of-date?

One is obviously when a there's a new upstream release. But then what about the VCS (-git) packages? They don't commit pkgver bumps, if I remember correctly, a git package should be updated when upstream changes building method or something. But do outdated dependencies count as build changes? If so, can I flag the package?

Also if it's a base package, can I flag it out-of-date if the dependencies changed?

I am talking about dependencies because recently gcc-libs got split up, and many packages started depending on gcc-libs, even though they needed libstdc++ and/or libgcc only.

Also if there are any other circumstances under which a package can be considered out-of-date then please post them here.

Thanks!

Last edited by LinuxLover471 (2026-02-23 09:36:32)

---

--- asyync1024

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 544

Re: [SOLVED] What exactly counts as out-of-date in the AUR?

Think of the 'Flag Out-of-Date' button as a 'New Version Alert.' For anything else, like the gcc-libs split, missing licenses, or build errors, the comments section is your best friend. It allows for a conversation rather than just a status change, only flag VCS packages if the actual instructions to build them are now wrong...

Last edited by 5hridhyan (2026-02-22 16:16:55)

---

---

LinuxLover471

Member

From: Asia, India

Registered: 2025-02-23

Posts: 172

Re: [SOLVED] What exactly counts as out-of-date in the AUR?

Thanks for your response! Now my understanding is crystal clear.

Marking as [SOLVED].

---

--- asyync1024