[Bug 543812] New: beagle: git won't work properly when beagle is running
http://bugzilla.novell.com/show_bug.cgi?id=543812 Summary: beagle: git won't work properly when beagle is running Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: jbottomley@novell.com QAContact: qa@suse.de Found By: --- Git uses file timestamps to track its index file. Meaning that if the timestamp of the file matches that in the git index git believes it hasn't altered. When beagle is running, git eventually finds a mismatch and thinks the local tree has been altered. This causes it to abort a lot of operations until the local alteration is fixed. The tree can be fixed temporarily by running git update-index --refresh, but after a while git finds spurious local alterations again. The only way to make git run correctly on my laptop (and not find spurious local alterations) is to kill beagled while using git. This is on a laptop running ext3 as root (where the git trees are stored) mounted with rw,noatime,acl,user_xattr -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543812
User jbottomley@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543812#c1
--- Comment #1 from James Bottomley
http://bugzilla.novell.com/show_bug.cgi?id=543812
User jbottomley@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543812#c2
--- Comment #2 from James Bottomley
http://bugzilla.novell.com/show_bug.cgi?id=543812
User mxwu@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543812#c3
Mingxi Wu
http://bugzilla.novell.com/show_bug.cgi?id=543812
User jbottomley@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543812#c4
--- Comment #4 from James Bottomley
So close it as it is already a upstream bug?
No ... because that's not our process. This stays open until either a fix is applied or it gets closed as wontfix. The reason is that even if upstream fixes it, the fix may be applied to a version ahead of what we carry, so we'd still have to backport (using this bug). Additionally, if upstream ignores the bug (as lamentably often happens), we get to evaluate whether we fix it here and then submit upstream (again, using this bug). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=543812
https://bugzilla.novell.com/show_bug.cgi?id=543812#c5
Vincent Untz
participants (1)
-
bugzilla_noreply＠novell.com