Re: Csetprune Existing Repositories

Hi Brad,

The csetprune alters the structure which makes push and pull
work.  

Csetprune is good when switching everybody to a new base,
or when chopping up a repository into a number of smaller ones.

Another way is to delete all the undesired files and have that
propagate out to everywhere desired, then remove the unwanted
BitKeeper/deleted/SCCS/s.<files> and follow the instructions
in the 'bk help gone' page:

	bk -r check -ag | bk -R gone -
	bk commit -y'mark deleted files as gone'

When that propagates out, people can then see what files would
be removed by running:
	bk rmgone -n

and if the list has nothing surprising:
	bk rmgone

-- Rick
BitMover

On Wed, Aug 31, 2005 at 09:01:45AM -0500, Bradford Beckmann wrote:
> 
> BK,
> 
> I used the command 'bk csetprune' to permanently remove several 100 MBs of
> files that was accidentally checked into a bk repository.  Most of the
> files were initially deleted by the 'bk rm' command, but all that did was
> move the files to the BitKeeper/deleted/SCCS directory.  The csetprune was
> successful in significantly reducing the size of the parent repository,
> however, it appears that now all child repositories can no longer pull
> from the parent.
> 
> Are all child repositories permanently disjointed from the parent
> repository?  Is there any way to resync the child repositories with the
> parent?
> 
> Thanks,
> 
> Brad
> _______________________________________________
> Bitkeeper-users mailing list
> [email protected]
> http://mail.bitmover.com/mailman/listinfo/bitkeeper-users
bk gone(1)                  BitKeeper User's Manual                 bk gone(1)

NAME
       bk gone - mark a file (key) as gone

SYNOPSIS
       bk gone [-q] [<key key ...> | -]

DESCRIPTION
       The  gone  command  is  used  when  a  file has been lost or physically
       deleted and the administrator of the repository has  decided  that  the
       file should be marked as gone.

       The key of the file can be generated from an existing file like this:

           $ bk prs -hr+ -d:ROOTKEY: file

       The  key that is returned from the above command  needs to be marked as
       gone if the file is to be removed from the repository.

       Sometimes a file is lost (i.e. the gotten file and the s.file have been
       removed  by accident). Whenever repository-level commands are run, con-
       sistency checks are performed. When these checks run, they will  notice
       that  a file is lost and will complain.  After looking over the consis-
       tency check output carefully, you can  run  the  following  command  to
       automatically mark all the missing files as gone:

           bk -r check -ag | bk -R gone -

OPTIONS
       -q     be quiet.

NOTE
       Just  adding the key to the gone file does not make the file "go away".
       All it does is make BitKeeper be happy if the file  is  actually  gone.
       If  you want to really remove the file, save the key, physically remove
       the file, and run  bk -r check -a.  If that  complains,  run  the  gone
       command on the listed keys.

SEE ALSO
       bk help check

CATEGORY
       Admin

BitMover, Inc                     2004/11/22                        bk gone(1)