Ouch ...

Sorry, I already wrote to you a nice answer on feb. the 13th but since
we are using [EMAIL PROTECTED] as our outgoing mail i got crushed by debian
spam policy (I still don't like not to be able to use admin as a valid
adress )
This is what I've written in the old mail ...

Simon Paillard wrote:
> One more time ping !
>
>   
Thanks to keep trying by the way ...
> On Tue, Feb 12, 2008 at 08:30:06PM +0100, Simon Paillard wrote:
>   
>> Hello,
>>
>> That is a still opened bug, because I've received no reply from you
>> about the points below.
>>
>> Could you please have a look at them ?
>>
>> Regards,
>>
>> On Thu, Jan 10, 2008 at 04:15:10PM +0100, Simon Paillard wrote:
>>     
>>> On Thu, Jan 10, 2008 at 01:51:25PM +0000, GRN wrote:
>>>       
>>>> Site: debian.grn.cat
>>>> Aliases: debian.grn.es
>>>>         
>>> That cannot be updated as is, you should fix your anonftpsync config so
>>> that your local trace file is named debian.grn.cat instead of
>>> ftp://debian.grn.cat/debian/project/trace/ftp.grn.es
>>>
>>>       
>>>> Archive-architecture: amd64 i386 ia64 powerpc 
>>>>         
>>> It seems you use an old anonftpsync, that doesn't exclude some
>>> architecture specific files.
>>>
>>>       
We are using the last version of anonftpsync (v 1.33 ) in three
versions, one with each mirror type (volatile, security and std)

mirror_debian:ARCH_EXCLUDE="alpha arm hppa hurd-i386 m68k mipsel mips
s390 sparc"
mirror_debian_security:ARCH_EXCLUDE="alpha arm hppa hurd-i386 m68k
mipsel mips s390 sparc"
mirror_debian_volatile:ARCH_EXCLUDE="alpha arm hppa hurd-i386 ia64 m68k
mipsel mips s390 sparc"


May it be the problem that some new architectures have been added and
aren't on the script?
>>> It implies a waste in both bandwidht and disk capacity, and moreoever it
>>> prevents the mirror from being usable during updates
>>>
>>> That's why we strongly recommend you to upgrade your anonftpsync
>>> version, that fix the problems above :
>>> http://www.debian.org/mirrors/anonftpsync
>>>       
Cheers



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to