Changes

Ibiblio appears to be unreliable, making it difficult to track changes. This is because Ibiblio is experiencing intermittent full hard drive issues. All downstream mirrors from them thus also have issues. Historically ibiblio was the place to see if packages had propagated out of the buildsys. We've recently moved our primary mirror to the CA mirror (mirror.canada.pialasse.com). That is the one that you should check for what should actually be on the mirrors.   

Ibiblio appears to be unreliable, making it difficult to track changes. This is because Ibiblio is experiencing intermittent full hard drive issues. All downstream mirrors from them thus also have issues. Historically ibiblio was the place to see if packages had propagated out of the buildsys. We've recently moved our primary mirror to the CA mirror (mirror.canada.pialasse.com). That is the one that you should check for what should actually be on the mirrors.   

Observation: I just refreshed (rsync) my tree against  

:Observation: I just refreshed (rsync) my tree against  

distro.ibiblio.org::smeserver  

:distro.ibiblio.org::smeserver  

1354247245 - www.smeserver.org - Fri, 30 Nov 2012 03:47:25 +0000  

:1354247245 - www.smeserver.org - Fri, 30 Nov 2012 03:47:25 +0000  

Traces are:  

:Traces are:  

Fri Nov 30 03:48:16 UTC 2012  

:Fri Nov 30 03:48:16 UTC 2012  

Used ftpsync version: 80387  

:Used ftpsync version: 80387  

Running on host: canada.canada.pialasse.com  

:Running on host: canada.canada.pialasse.com  

Fri Nov 30 03:48:27 UTC 2012  

:Fri Nov 30 03:48:27 UTC 2012  

Used ftpsync version: 80387  

:Used ftpsync version: 80387  

Running on host: login1.ibiblio.org  

:Running on host: login1.ibiblio.org  

Question: When doing rsync from Ibilbio, are we pulling packages from  

Question: When doing rsync from Ibilbio, are we pulling packages from  

the new primary mirrors at pialasse.com only, or a mix of Ibiblio and CA?

the new primary mirrors at pialasse.com only, or a mix of Ibiblio and CA?