"Bernhard R. Link" <[EMAIL PROTECTED]> writes:
> package reprepro
> tags 476341 + wontfix
> thanks
>
> * Goswin Brederlow <[EMAIL PROTECTED]> [080416 07:19]:
>> I just updated reprepro to lenny and removed etch from my mirror and
>> reprepro complained about the removal and the db format.
>
> That is strange. when something is removed a clearvanishes (or the
> appropiate --ignore like to not care about package indicies no longer
> configured) should make everything work again.
>
>> So I started
>> to clone my old archive into a new one:
>>
>> This hardlinks all files so the space used for the cloned archive is
>> minimal. But the spacecheck doesn't consider hardlinks and claimed I
>> would need some 4GB for the update. I used '--spacecheck none' to run
>> the update but it would be better if spacecheck would calculate with
>> hardlinks in mind.
>
> I don't currently see a way to implement this. Reprepro has no inner
> knowledge about what a specific apt method will do. So it cannot know
> that a file:// URI will most likely just return some file to be
> copied/hardlinked. And even if it guessed so, it would have to
> second-guess what the original file would be, to know if it will be
> copied or hardlinked (as cross-partition hard-links are not possible).
>
> Another way for your use case, would have been to just hardlink
> all files manualy, tell reprepro to include them all into its file
> database (with the trick from the recovery file), and let it delete
> all unneeded afterwards.
>
> Hochachtungsvoll,
> Bernhard R. Link
Ok. Then I guess we can just close it. Second guessing what the apt
method will do sound bad indeed.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
