[aur-general] aur-out-of-date: determine out-of-date AUR packages w.r.t. upstream

Eli Schwartz eschwartz at archlinux.org
Sun Feb 4 00:53:50 UTC 2018

On 02/02/2018 04:48 PM, Marcin Wieczorek wrote:
> Eli Schwartz via aur-general <aur-general at archlinux.org> writes:
>> 1) How does this handle PKGBUILDs that, say, have their homepage on
>> github, but do not tag releases there -- because :( :( :( -- and instead
>> push releases to PyPI or npmjs or something?
> Imho such cases should be always reported upstream as that is a very bad
> practice.

It certainly is, but there is a difference between reporting it upstream
and actually getting them to fix it...

See, for example, this upstream request for a Github tag (which has been
carefully ignored since October):

Which would fix these two outstanding bugs:

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20180203/dcbdc991/attachment.asc>

More information about the aur-general mailing list