- Mailing Lists
- Contributors
- Re: pandoc-*.deb cleaning in OCA repositories
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: pandoc-*.deb cleaning in OCA repositories
The problem is that this files and changes will be imported on future migration PRs on future branches (some files are inside the module folder). This is a decision that will impact the future of all OCA users. So this is something that will not disappear with time. Letting it go because we think it will disappear is a mistake.
Change nothing is the easiest choice but we all know that this will not disappear and is a bad choice. We also are discussing this, but I think that there is not so many repositories affected.
On Mon, 5 Aug 2024, 12:17 Jairo Llopis, <notifications@odoo-community.org> wrote:
El vie, 2 de ago de 2024 a las 12:52:18 P. M., Enric Tobella Alomar <notifications@odoo-community.org> escribió:I think the benefits are bigger than the consI think the opposite.Benefits:
- Save disk space in case you're either not cloning with --depth 1, or you're going to do a git gc after all the manual work that will mean updating all your local clones.
- Save bandwith space under similar conditions.
Potential problems:
- Break your lock files.
- Need to rebase almost every open PR against those branches.
- Inclusion of unwanted commits (that include those wonderful 30MB files) in more PRs.
- Disturbing many developers.
- Making oca-port unable to detect relationship between commits and PRs.
- Manual work involving the repo admins and almost all OCA developers.
- Things I don't imagine right now.
Definitely not worth it. One day we'll stop using those branches (hopefully in about 3-5 years) and we won't care about those few extra MBs._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Enric Tobella Alomar - 02:31 - 5 Aug 2024
Reference
-
pandoc-*.deb cleaning in OCA repositories
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:git fetch origin 17.0 git reset --hard origin/17.0(beingoriginthe 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.
by Pedro M. Baeza - 06:11 - 29 Jul 2024