Thanks for tracking this down, I've hit it during port builds but had assumed it was dpb changes.
OK sthen@ to revert. On 2015/05/07 14:29, David Coppa wrote: > > Hi, > > As found while running the git test-suite (for an upcoming update > to git-2.4.0): > > <dcoppa@t420:/usr/pobj/git-2.4.0/git-2.4.0/t/trash directory.t7001-mv>$ cd sub > <dcoppa@t420:/usr/pobj/git-2.4.0/git-2.4.0/t/trash directory.t7001-mv/sub>$ > rm -rf .git > <dcoppa@t420:/usr/pobj/git-2.4.0/git-2.4.0/t/trash directory.t7001-mv/sub>$ > cp -R -P -p ../.git/modules/sub .git > cp: chflags: .git/refs/heads: Invalid argument > cp: chflags: .git/refs/tags: Invalid argument > cp: chflags: .git/refs/remotes/origin: Invalid argument > cp: chflags: .git/refs/remotes: Invalid argument > cp: chflags: .git/refs: Invalid argument > cp: chflags: .git/branches: Invalid argument > cp: chflags: .git/hooks: Invalid argument > cp: chflags: .git/info: Invalid argument > cp: chflags: .git/objects/pack: Invalid argument > cp: chflags: .git/objects/info: Invalid argument > cp: chflags: .git/objects/87: Invalid argument > cp: chflags: .git/objects/d0: Invalid argument > cp: chflags: .git/objects/91: Invalid argument > cp: chflags: .git/objects/b2: Invalid argument > cp: chflags: .git/objects: Invalid argument > cp: chflags: .git/logs/refs/remotes/origin: Invalid argument > cp: chflags: .git/logs/refs/remotes: Invalid argument > cp: chflags: .git/logs/refs/heads: Invalid argument > cp: chflags: .git/logs/refs: Invalid argument > cp: chflags: .git/logs: Invalid argument > cp: chflags: .git/: Invalid argument > > Reverting to 1.36 makes cp work again as expected. > > Ciao! > David >
