Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incremental Synchronization Issue with Bandersnatch #1663

Open
lxyeternal opened this issue Feb 5, 2024 · 2 comments
Open

Incremental Synchronization Issue with Bandersnatch #1663

lxyeternal opened this issue Feb 5, 2024 · 2 comments

Comments

@lxyeternal
Copy link

I am currently using bandersnatch for mirroring PyPI and have encountered an issue regarding incremental synchronization. I want to set up my bandersnatch mirror to only sync new packages added to pypi.org. For packages that have been removed from pypi.org, do not delete these packages from the local mirror during synchronization. In short, only perform incremental backups without deleting any packages.

how to configure bandersnatch.conf to achieve this?

@cooperlees
Copy link
Contributor

cooperlees commented Feb 5, 2024

You're in luck. bandersnatch does not delete unless you run a bandersnatch verify. So you get that by default.

We do not have a feature to only take new packages created/added on PyPI to day. But I am not sure you mean this. I would take a PR to do so, but I don't know the cleanest way. I guess pull down the fill mirror list via the XMLRPC call we do and save all the package names and use that as your start point. Then from there compare to the original list and make that an allow list maybe?

This would need to be some sort of filter plugin to be accepted.

@lxyeternal
Copy link
Author

Thank you very much. I only want to mirror all packages from the pypi.org. My target is to build a comprehensive dataset of python registry for research.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants