AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

- Please report bugs related to Arch Linux official packages here: http://bugs.archlinux.org/index.php?project=1
- Please report bugs for [community] packages here: http://bugs.archlinux.org/index.php?project=5
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:
https://projects.archlinux.org/aurweb.git/
Tasklist

FS#67268 - Dependencies/Source/Licenses vanished from package page after new version pushed

Attached to Project: AUR web interface
Opened by Michael Lelli (ToadKing) - Monday, 13 July 2020, 22:35 GMT
Task Type Bug Report
Category Backend
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.7.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I pushed an update for a package and the licenses, dependencies, and source listing for it disappeared from the package page. My changes included some small modifications to .SRCINFO but it doesn't look like it's invalid at all, and it parses with python-srcinfo just fine.

Package: https://aur.archlinux.org/packages/deadbeef-git/
SRCINFO is attached.
   .SRCINFO (2.3 KiB)
This task depends upon

2020-07-15: A task closure has been requested.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 14 July 2020, 22:35 GMT
Interesting, I do not see any immediate issues. Did you see any error message when pushing the change?
Comment by Lukas Fleischer (lfleischer) - Tuesday, 14 July 2020, 22:37 GMT
Also, looking at the package page, it seems like the dependencies are all back now. I wonder whether this is related to caching (cache not being invalidated properly on push and now fixed by cache expiry).
Comment by Michael Lelli (ToadKing) - Tuesday, 14 July 2020, 22:48 GMT
I don't remember seeing any error when pushing changes, although I admit I was not paying too much attention to the terminal after pushing them.

I'll try pushing another change when the package repo gets updated (want to avoid spamming users) and see if I can reproduce it and if there's any messages after pushing.
Comment by Michael Lelli (ToadKing) - Wednesday, 15 July 2020, 23:12 GMT
I just tried to reproduce it with no success. Unless this pops up again I think it's safe to close this bug for now.

Loading...