Question about out-of-date AUR packages

bananabrain · 2021-03-12 00:31:07

A possibly naive question:

Is the idea to flag an AUR package out of date when it will no longer build on an up to date system, or simply when newer upstream source becomes available?

It seems to me the former would be quite worthwhile and the latter an example of whinging at a maintainer who's likely to get around to the job at some point anyway.

Not trying to ruffle any feathers. Just wondering if the "out of date" logitechmediaserver will compile and run on my machine ok.

Trilby · 2021-03-12 00:36:48

The out-of-date flag is for packages that are ... wait for it ... out of date. Nothing else.

Of course, they are completely worthless now because users end up spamming away at them anytime they're unhappy because there is a problem in the PKGBUILD, or there is a problem on their own system, or they run out of their favorite flavor of soda at the groccery store.

So you should only use it when there is a new upstream source available. And you should comment or contact the maintainer if there is some other issue. And other people should follow this advice as well. But they will not.

Slithery · 2021-03-12 00:38:31

bananabrain wrote:

...or simply when newer upstream source becomes available?

^ This.

Unless of course if it's a VCS package ending in -{git,cvs,svn,hg,darcs,bz} etc. in which case the PKGBUILD only needs updating when the build process changes...
https://wiki.archlinux.org/index.php/VC … guidelines

eschwartz · 2021-03-12 00:45:10

Trilby wrote:

Of course, they are completely worthless now because users end up spamming away at them anytime they're unhappy because there is a problem in the PKGBUILD, or there is a problem on their own system, or they run out of their favorite flavor of soda at the groccery store.
So you should only use it when there is a new upstream source available. And you should comment or contact the maintainer if there is some other issue. And other people should follow this advice as well. But they will not.

In practice, they tend to skip right over flagging it out of date and going right to the... wait for it...

Deletion requests.

Yup, you heard that correctly. Not the orphan requests, the *deletion* requests.

jasonwryan · 2021-03-12 00:56:17

bananabrain wrote:

Just wondering if the "out of date" logitechmediaserver will compile and run on my machine ok.

It's running fine on mine. And the OOD flag is wrong: the last *stable* release was 8.1.1 https://github.com/Logitech/slimserver/tags

# edit: and to second Trilby's point: way too many people seem incapable of reading the pinned notes, wiki pages, or any of the other documentation that is supposed to govern how things work on the AUR. Much like the rest of Arch, really...

Last edited by jasonwryan (2021-03-12 00:58:38)

bananabrain · 2021-03-12 01:50:58

Well that was an entertaining read... ;-)

Thanks for the replies guys, I think I'm with it now.

actionless · 2024-11-12 23:23:10

The out-of-date flag is for packages that are ... wait for it ... out of date. Nothing else.
Of course, they are completely worthless now because users end up spamming away at them anytime they're unhappy

this problem is still actual to date:

what about making in out-of-date form "New Version URL" required field which must contain an URL?

Last edited by actionless (2024-11-12 23:26:21)

actionless · 2024-11-13 08:07:19

now, this escalated quickly:

https://imgur.com/An8qnEB

Scimmia · 2024-11-13 12:51:25

actionless wrote:

The out-of-date flag is for packages that are ... wait for it ... out of date. Nothing else.
Of course, they are completely worthless now because users end up spamming away at them anytime they're unhappy

this problem is still actual to date:
what about making in out-of-date form "New Version URL" required field which must contain an URL?

You're in the wrong on this one. See post #3 in this thread.

And this kind of shit is completely unacceptable.
https://aur.archlinux.org/cgit/aur.git/ … c8970a54da

Last edited by Scimmia (2024-11-13 12:53:06)

V1del · 2024-11-13 13:14:25

Closing this necroed and old thread.

While I'd think that the out of date flag was incorrectly used here is up to debate, acting like this to a relevant change suggestion is pretty petty.

But you should handle this better if you care about your package being used.

Arch Linux

#1 2021-03-12 00:31:07

Question about out-of-date AUR packages

#2 2021-03-12 00:36:48

Re: Question about out-of-date AUR packages

#3 2021-03-12 00:38:31

Re: Question about out-of-date AUR packages

#4 2021-03-12 00:45:10

Re: Question about out-of-date AUR packages

#5 2021-03-12 00:56:17

Re: Question about out-of-date AUR packages

#6 2021-03-12 01:50:58

Re: Question about out-of-date AUR packages

#7 2024-11-12 23:23:10

Re: Question about out-of-date AUR packages

#8 2024-11-13 08:07:19

Re: Question about out-of-date AUR packages

#9 2024-11-13 12:51:25

Re: Question about out-of-date AUR packages

#10 2024-11-13 13:14:25

Re: Question about out-of-date AUR packages

Board footer