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

Re: pandoc-*.deb cleaning in OCA repositories

Avatar

Re: pandoc-*.deb cleaning in OCA repositories

by
Acsone SA/NV, Denis Roussel
- 29/07/2024 20:48:34
As said, I understand the technical reasons.

I'm more concerned about commit history after the file merge. Nothing more.

Le lun. 29 juil. 2024, 20:42, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :
If we remove the file in a commit, it will not be removed from history, so, it will take a lot of Mb when we download the repository. The only way is to remove the file from history.

El lun, 29 jul 2024 a las 20:38, Roussel, Denis (<notifications@odoo-community.org>) escribió:
Even if I understand the issue here, I'm more doubtful about the force push mandatory operation (even if I understand the technical reason behind not to have the file appearance at all).

I'm more concerned by the sha hashes problems we can have towards authorship.
That said, I'm more to a commit removing the conflicting file.

Apart of that, @Pedro Manuel Baeza , an ecological reason cannot be put on the table here if we continue to recreate main branches from scratch as that leads to more repository space than the problem here araised.

Le lun. 29 juil. 2024, 18:12, Pedro M. Baeza <notifications@odoo-community.org> a écrit :
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

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



--
Enric Tobella Alomar
CEO & Founder

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

Reference