| Summary: | Moved or new file contents not included in diff via arc(8) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Services | Reporter: | Jean-Sébastien Pédron <dumbbell> | ||||
| Component: | Code Review | Assignee: | Phabric Admin <phabric-admin> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Many People | CC: | brnrd, dim, koobs, kwm, smh | ||||
| Priority: | Normal | Keywords: | dogfood, needs-qa, regression | ||||
| Version: | unspecified | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| URL: | https://reviews.freebsd.org/D3234 | ||||||
| Attachments: |
|
||||||
|
Description
Jean-Sébastien Pédron
2015-09-12 10:08:47 UTC
Is this still an issue? How was the diff created (manually uploaded? 'arc diff') Hi Eitan! I don't know if this is still a problem as I didn't uploaded a new diff with a moved file recently. The diff was created with "arc diff". Just hit this issue as well. https://reviews.freebsd.org/D3953 The raw diff when applied using `patch` the files are emptied in mariadb- and the new mariadb53- directories are not created. After renaming the mariadb- folders to mariadb53 and applying the patch it works as expected. Next to that, the creation of files for the mariadb101- ports shows "Hunk succeeded" yet no file/directory is created. Can the patches only be applied to svn repos using `svn patch`? Thanks! Bernard. This happens for new files too, not only moves/renames. See: https://reviews.freebsd.org/D4058 *** Bug 204206 has been marked as a duplicate of this bug. *** Yer have filed a bug with phabricator here: https://secure.phabricator.com/T9970 Have tried with arc port: php5-arcanist-20150626_2 and from phabricators git version hash: dae2f0073f019221839924b4b1431c6cba5dcddaESC See my proposed fix here: https://secure.phabricator.com/D14755 Created attachment 164158 [details]
Fix the arcanist binary_safe_diff script to preserve diff's exit code
Fixed upstream by: https://secure.phabricator.com/rARC97056a3b85bbee72d6ede1b9478b03dee1db2d4e and: https://secure.phabricator.com/rARC7d25fcdbdb51f28a1e6465edd819aa5d99bc0f71 I can't reproduce this problem anymore, so an update to our Phabricator must have fixed this. Thank you! |