* Marc Dequènes <[EMAIL PROTECTED]> [060328 11:04]:
> In the problem i encountered in #357803, adding a file built without -sa
> for a non -1 package resulted in reprepro complaining for missing source
> tarball, but with other files added into the pool. Either reprepro
> should copy files after all checks, or remove them when an error occur,
> leaving the pool in a sane state
This is quite difficult and the current emphasis is to try to never
delete anything that might cause high costs to retrieve (bandwidth) or
recreate (build). The problematic part is that makeing sure everything
will work before is only partially possible (md5summing all files,
checking all databases, everything having quite some overhead; and if
a file can be copied where it belongs to is only possible after it is
copied). Deleting afterwards has to make sure it does not hit files
already being in the pool (I do not want to delete them in this
situation, even if nothing else references them) or to rip a package
apart when it is told to move stuff to the pool and only some parts
can be moved back. So more atomic behaviour would be nice, but is quite
hard to get. The current behaviour should have no larger ill effects,
though.
> (even if the db is clean, the filesystem should be clean too).
Are those not in the database already? Unless that got missed,
a reprepro deleteunreferenced should remove all that stuff.
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
