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.  

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.   

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.  You can always check to see what mirrors systems should be using for updates by looking at the mirrorlist files that are generated and housed on the CA master mirror.

Observation:  

As an example:

 

 

{| style="color:red;background-color:#ffffcc;"

{| style="color:red;background-color:#ffffcc;"

|

|

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

We will need to come up with a tree of which mirrors sync from where so we can see what mirrors are affected by issues or outages.

 

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

|}

|}