[arch-dev-public] website no longer updating
Hi, The website still shows the heimdal rebuilds in testing although they were moved to core/extra. Is there something preventing the website update because of the number of packages moved? Can someone look into this? Thanks Eric -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Sat, Dec 13, 2008 at 4:00 PM, Eric Bélanger <belanger@astro.umontreal.ca> wrote:
Hi,
The website still shows the heimdal rebuilds in testing although they were moved to core/extra. Is there something preventing the website update because of the number of packages moved? Can someone look into this?
This is exactly it. I'll force it to run in a minute here. FYI- you can diagnose these problems by looking at /tmp/archweb_update.log on gerolde. -Dan
On Sat, Dec 13, 2008 at 4:27 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Sat, Dec 13, 2008 at 4:00 PM, Eric Bélanger <belanger@astro.umontreal.ca> wrote:
Hi,
The website still shows the heimdal rebuilds in testing although they were moved to core/extra. Is there something preventing the website update because of the number of packages moved? Can someone look into this?
This is exactly it. I'll force it to run in a minute here.
FYI- you can diagnose these problems by looking at /tmp/archweb_update.log on gerolde.
Yeah, there's that check that says "if more than 50 packages are removed from a repo, lets just assume something went wrong". I think Dusty suggested removing this restriction for the testing repo, though, which might be a good idea.
On Sat, 13 Dec 2008, Aaron Griffin wrote:
On Sat, Dec 13, 2008 at 4:27 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Sat, Dec 13, 2008 at 4:00 PM, Eric Bélanger <belanger@astro.umontreal.ca> wrote:
Hi,
The website still shows the heimdal rebuilds in testing although they were moved to core/extra. Is there something preventing the website update because of the number of packages moved? Can someone look into this?
This is exactly it. I'll force it to run in a minute here.
FYI- you can diagnose these problems by looking at /tmp/archweb_update.log on gerolde.
Thanks for the fix and info.
Yeah, there's that check that says "if more than 50 packages are removed from a repo, lets just assume something went wrong". I think Dusty suggested removing this restriction for the testing repo, though, which might be a good idea.
We could do that. OTOH, these big rebuilds are scarce so we could do the website update manually as long as we remember to do it. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Sat, Dec 13, 2008 at 4:55 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Sat, Dec 13, 2008 at 4:27 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Sat, Dec 13, 2008 at 4:00 PM, Eric Bélanger <belanger@astro.umontreal.ca> wrote:
Hi,
The website still shows the heimdal rebuilds in testing although they were moved to core/extra. Is there something preventing the website update because of the number of packages moved? Can someone look into this?
This is exactly it. I'll force it to run in a minute here.
FYI- you can diagnose these problems by looking at /tmp/archweb_update.log on gerolde.
Yeah, there's that check that says "if more than 50 packages are removed from a repo, lets just assume something went wrong". I think Dusty suggested removing this restriction for the testing repo, though, which might be a good idea.
It's a 50% check (if newsize < .5 * oldsize, panic). I can make this fix sometime. -Dan
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Eric Bélanger