On Thu, 21 Oct 2010 17:22:58 +0200, Thomas Bächler <[email protected]> wrote: > Am 21.10.2010 15:56, schrieb Auguste Pop: >> I noticed this by compiling the package myself... When I sent this >> mail, the web page was not updated and I saw an old list of files that >> did not contain the .so file. I should have tried it first rather than >> relying on a presumably delayed response on the web site. Sorry for >> the false alarm. > > The update of the file list in the web interface might be delayed > compared to the update of the package data itself. > > Dan, what can we do here? Should a version mismatch between $repo.db and > $repo.files cause archweb to discard the file list, stating that "There > is currently no file list available for this package", or should archweb > print a warning "This is a file list from an older version of this > package and might differ from the current package". Is anything like > this already done in archweb? Should it? > > Right now, the delay between updating the package info and the file list > can be (in the worst case) little over 24 hours. Given that our packages > update and change frequently, I think we should avoid confusion like in > Auguste's case.
ATM the file lists are created twice a day (how do you compute > 24h?) But yes, maybe the web interface should show if there is no recent file list available. But if that is not super easy to implement it wont worth it as I am rethinking the file list creation anyway. (but cannot really tell when) -- Pierre Schmitz, https://users.archlinux.de/~pierre
