[csw-maintainers] Repository Woos

[Jonathan Craig]

No problem.  Can you point me to anything that will get me started
understanding the existing process and will I need any additional
privileges (access to the master repository, etc.).  I worked up a
quick and dirty perl script to fix my repository that I should be able
to rework for the master. If the repository is held on a zfs
filesystem on another box it would be nice to have access to that box
to setup and run the process (use of zfs snaphots makes me a lot less
nervous about linking/unlinking a large number of files).

Jon

2011/9/10 Maciej Bliziński <maciej at opencsw.org>:
> 2011/9/10 Jonathan Craig <jcraig at opencsw.org>:
>> Just curious if anyone else is rsync'ing a local copy of the
>> repository.  At some point my rsync messed up and broke my hard links
>> which caused a dramatic increase in storage requirements.  Did anyone
>> else experience this?  Also, I wondered about re-swizzling the links
>> so actual files are always stored in "allpackages" and everything else
>> would use symlinks.  The problem is once rsync breaks your hard links
>> you have to manually go through and recreate them.
>
> I personally didn't investigate this issue yet.  All the new packages
> are uploaded to allpkgs and then hardlinked, so the "one physical copy
> of each file" rule should hold for anything new.  But I didn't write
> any checks to verify this is actually the case.  Would you be willing
> to develop / provide some sort of diagnostic and/or fixing tool for
> the catalog?
>
> Maciej
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers
> .:: This mailing list's archive is public. ::.