"Bernhard R. Link" <[EMAIL PROTECTED]> writes:
> * Goswin von Brederlow <[EMAIL PROTECTED]> [070824 13:27]:
>> I'm mirroring etch (normal etch) and etch-security (security updates
>> for etch) into one archive. Now I have a problem with conflicting
>> md5sums between etch and etch-security:
>>[...]
>> As you can see the problem is that a different source build was
>> uploaded to etch-proposed-updates instead of copying the security
>> upload and now the files do differ.
>
> I consider this a bug in the Debian archive (which I hoped was already
> fixed).
Diggin into it I found out that they made a security upload of etch2
while s-p-u already had an etch2 upload. Someone droped the ball
there. Andreas said they are working on it but didn't give any details
or timeframe. :(
>> But how do I get reprepro to work despite that?
>
> See the FAQ, 1.2, first subpoint: You cannot store two different files
> with the same name in the same repository. If you take one of the
> packages and put it manually in the other distribution, all will be
> fine.
I was hoping for some ignore option but I will do that then. Now what
way to push?
>> Can I set some option
>> so that etch-security will store its files in pool/updates/... like
>> the official repository?
>
> I think this would severly contradict the notion of a pool. (And I also
> don't know how to implement it in a way that would not cause very
> strange side effects or anomalies).
>
> Hochachtungsvoll,
> Bernhard R. Link
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
