1. Mailing Lists
  2. Contributors
  3. Re: pandoc-*.deb cleaning in OCA repositories

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: pandoc-*.deb cleaning in OCA repositories

Avatar

Re: pandoc-*.deb cleaning in OCA repositories

by "Graeme Gellatly" <graeme@moahub.nz> - 29/07/2024 20:18:48
Nothing we all haven't done ourselves on our own repos. I would consider to copy relevant parts of this email as a pinned issue for a little while on affected repos.

On Tue, 30 Jul 2024, 4:12 am Pedro M. Baeza, <notifications@odoo-community.org> wrote:
Due to a mistake on the tool to generate the READMES (fixed in [1]), some very big files ~30 MB each~ (with extension .deb or .dmg for Mac users) have been added both by the merge bot or by users doing a module migration.

This makes that on branch/repository clonation, or any free pull operation on any local git repository copy (of any branch) wastes a lot of bandwidth and resources, and is not ecological friendly.

Due to this, and although not ideal, we plan to force push the affected repositories (note that this has been only in 17.0 branches), following [3] technique recommended by Nils.

The drawback of doing this is that your next `git pull` operations on that branches will fail, saying about unrelated commit histories or creating a merge commit with possible conflicts.

The solution for avoiding it is to do the commands:

g
 it fetch origin 17.0
git reset --hard origin/17.0

(being origin the OCA remote). In fact, this is the recommended way to do it in automated pulling systems.

If you don't have any strong counter-arguments, I will perform it at the end of the week. I will announce here the affected repositories after the operation.

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference