* Julien Valroff <[EMAIL PROTECTED]> [060328 15:57]:
> >Are those not in the database already? Unless that got missed,
> >a reprepro deleteunreferenced should remove all that stuff.
>
> Maybe this can be run automatically after such an error occurs (or best,
> there could be an option in the the conf/distribution to deal with such
> special cases).
deleteunreferenced deletes *everything* in the file database not
referenced in any distribution. This could be gigabytes of data
if you try to include a package within some larger repository
reorganisation. (i.e. having removed some distributions and wanting
to include them after that in a different form, or some larger
upgrade failed to complete after everything was already downloaded
and is supposed to be continued later).
Not even upgrading the last instance of a package away from an old
version or removing the last instance of a package calls a unconditional
deleteunreferenced, but only limited to all those files that lost
a reference. (And I'm already there often wishing I gave a
--keepunreferencedfiles but realize that to late). Inclusion has the
additional problems, that some of those files may be lying around in the
pool without references by distributions on purpose, like a .orig.tar.gz
already placed there so a later .changes file include without it can
work. If it gets deleted in such cases the next try will fail....
I plan to add some more support for such cases, but that will need
some infrastructure work, so that it remember what it acutally copied.
Until now the high-level parts just say "I need those files, if you
do not have them, look there and copy/move them", which allows no
sensible way to revert it.
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
