Opened 4 years ago

Last modified 4 years ago

#62538 new defect

coreutils: mv discards extended attributes when moving to a different volume

Reported by: DanielSmedegaardBuus (Daniel Smedegaard Buus) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: Cc:
Port: coreutils

Description (last modified by DanielSmedegaardBuus (Daniel Smedegaard Buus))

Hello :)

The mv version included with coreutils in MacPorts (also Homebrew, just for reference) discards extended attributes when moving a file from one volume to another (not intra-volume). This doesn't happen with the OS X bundled mv, or with coreutils on Ubuntu that I tested on, too.

daniel@titanic > xattr -w test fisso LICENSE
daniel@titanic > xattr -p test LICENSE
fisso
daniel@titanic > which mv
mv: aliased to /bin/mv
daniel@titanic > mv LICENSE /Volumes/Scratch
daniel@titanic > xattr -p test /Volumes/Scratch/LICENSE
fisso
daniel@titanic > /opt/local/libexec/gnubin//mv /Volumes/Scratch/LICENSE .
daniel@titanic > xattr -p test LICENSE
xattr: LICENSE: No such xattr: test

Change History (5)

comment:1 Changed 4 years ago by DanielSmedegaardBuus (Daniel Smedegaard Buus)

Description: modified (diff)

comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: mv removed
Summary: Coreutils mv discards extended attributes when moving to a different volumecoreutils: mv discards extended attributes when moving to a different volume

Sounds like not a MacPorts-specific problem that should be reported to the developers of coreutils. When they fix it and release a new version, we can of course update to that version in MacPorts.

comment:3 Changed 4 years ago by DanielSmedegaardBuus (Daniel Smedegaard Buus)

Roger that :) I've written to the bugs-coreutils mailing list. I'll report back.

comment:4 Changed 4 years ago by DanielSmedegaardBuus (Daniel Smedegaard Buus)

So far no news. Not sure they care :/ You sure this isn't a config/build issue?

comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

No, I am not sure, but I don't see much in the way of configuration in our coreutils Portfile; we pretty much just build the software its developers have created. If anything in the Portfile looks like it might be causing this, try changing it and see if that solves the problem. If so, you can send us a pull request, or a patch attached to this ticket.

Note: See TracTickets for help on using tickets.