-
-
Notifications
You must be signed in to change notification settings - Fork 955
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
merge conflict that cannot be locally reproduced #8755
Comments
I can still reproduce this on the server. Do you have some git configuration ( For some reason, git doesn't recognize d7fca0ded34e60836b51c84479d2774ec73249bd (which is already in upstream repo) to be a cherry-pick of 11e2219ed7fcc519f3086640926bd7b1043c5529, and stops on that, even though there is actual conflict. I've just manually fixed that in the Weblate repo... |
I don't think my git config should affect it. Here's my ~/.gitconfig: [pull]
ff = only
[transfer]
fsckObjects = true
[advice]
skippedCherryPicks = false And the relevant bits in the repo's .git/config: [core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true |
I'm using git v2.39.1 from Debian/bookworm. |
We're on git 2.30.2, that might cause some differences... Will try to play with this more later. |
It turns out that the Weblate git configuration is guilty here – the merge driver for PO files didn't gracefully handle this. |
Thank you for your report; the issue you have reported has just been fixed.
|
I use the same tooling as @eighthave and have the same issue: Local gettext tooling:
Weblate:
po4a configuration has Weblate has Customize gettext output - No line wrapping: All other strings are ok, only PO Entry Header is affected. https://hosted.weblate.org/addons/organicmaps/website/ |
@rtsisyk That's not related to this issue. Moreover, I think Weblate behaves correctly – you ask it to not wrap lines, and it does not wrap them. |
Thanks for the quick response.You are right, Weblate behaves as requested. @eighthave how to you deal with this issue in F-Droid repo? |
I'm not sure what your issue is, but in F-Droid, we reformat msgid/msgstr
entries gettext files to be a single line, if that is useful to you.
|
This idea is not bad. I will check this option. Thanks! |
Describe the issue
In https://hosted.weblate.org/projects/f-droid/website/, it says there is a merge conflict. I cannot reproduce it locally. I do:
And it rebases fine every time. I also tried including the commits that Weblate say conflict, e.g.
11e2219ed
. But it still says there is a merge conflict.I already tried
Steps to reproduce the behavior
Expected behavior
If there is no merge conflict locally, I can't see why there is one in Weblate.
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: