https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230114
--- Comment #5 from Nathan <ndowens.f...@yandex.com> --- (In reply to Kai from comment #4) > (In reply to Nathan from comment #1) > (In reply to Nathan from comment #3) > > It depends in which context you do apply the patch. If you do e.g. > > > $ cd /path/to/your/ports/tree > > $ svn patch --dry-run ~/scancode-toolkit.patch textproc/ > > from the root of your svn tree, you should get a similar output like below: > > > A textproc/scancode-toolkit > > A textproc/scancode-toolkit/Makefile > > A textproc/scancode-toolkit/distinfo > > A textproc/scancode-toolkit/files > > A textproc/scancode-toolkit/files/patch-setup.py > > A textproc/scancode-toolkit/files/patch-src_commoncode_system.py > > A textproc/scancode-toolkit/pkg-descr > > The same result you would get with: > > > $ cd /path/to/your/ports/tree > > $ cd textproc > > $ svn patch --dry-run ~/scancode-toolkit.patch > > The output would be: > > > A scancode-toolkit > > A scancode-toolkit/Makefile > > A scancode-toolkit/distinfo > > A scancode-toolkit/files > > A scancode-toolkit/files/patch-setup.py > > A scancode-toolkit/files/patch-src_commoncode_system.py > > A scancode-toolkit/pkg-descr > > When applying your patch with the "corrected" paths the output will show > some differences which yields into a non functional port that cannot be > built: > > > $ cd /path/to/your/ports/tree > > $ svn patch --dry-run ~/corrected_paths.patch textproc/ > > A textproc/textproc > > A textproc/textproc/scancode-toolkit > > A textproc/textproc/scancode-toolkit/Makefile > > A textproc/scancode-toolkit > > A textproc/scancode-toolkit/distinfo > > A textproc/scancode-toolkit/files > > A textproc/scancode-toolkit/files/patch-setup.py > > A textproc/scancode-toolkit/files/patch-src_commoncode_system.py > > A textproc/scancode-toolkit/pkg-descr > > As for the info about the non-existent origins - have you updated your ports > tree? Your ports tree needs to be at least at r475546 to have all the ports > that are required to build textproc/scancode-toolkit successfully. https://www.freebsd.org/doc/en/books/porters-handbook/book.html#porting-submitting Example 3.1. Creating a .diff for a New Port Add all the files with svn add. cd to the base of the ports tree so full paths to the changed files are included in the diff, then generate the diff with svn diff. For example: % svn add . % cd ../.. % svn diff games/oneko > oneko.diff Important: To make it easier for committers to apply the patch on their working copy of the ports tree, please generate the .diff from the base of your ports tree. Updated ports tree and finally seems it found deps needed -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
