[aur-general] Flagging out-of-date in AUR
Hello, some weeks ago Firmicus complained on this list that some of his packages are flagged out of date in AUR. Now I see one of gummibaerchens packages netbeans 6.01 flagged out of date. It is definitely not out of date, as he put it in AUR today. I suspect myself to be the one who is responsible for the issues Firmicus described. But if so, I did so accidentely, because I sometimes saw newly uploaded packages flagged out of date and unflagged them because they were not. Perhaps there is a caching problem? I use kazehakase 0.53 for browsing. Sorry for any inconvenience if I actually am the "evil". Stefan
On Sun, 16 Mar 2008 16:55:35 +0100 "stefan-husmann@t-online.de" <stefan-husmann@t-online.de> wrote:
some weeks ago Firmicus complained on this list that some of his packages are flagged out of date in AUR. Now I see one of gummibaerchens packages netbeans 6.01 flagged out of date. It is definitely not out of date, as he put it in AUR today.
Perhaps there is a caching problem?
There is a possibility that the database records in AUR are keeping some of the old values of old 'deleted' packages. From what I recall no records are ever completely deleted from the database. AUR even creates dummy records for package dependencies that have never been uploaded. Caching could be a problem in some situations.
participants (2)
-
Loui
-
stefan-husmann＠t-online.de