sappnd flag getting set?

[René J.V. Bertin]

Hi,

I have run into a weird issue just now. I've been using the patch to portimage.tcl that has it call bsdtar instead of the regular tar, adding the --hfsCompression option. That gives an appreciable space gain, but apparently it's not without potential side-effects.

After waiting a couple of hours building the Calligra port I'm working on, I got an error during the activation step. In short, the mpextract* directory couldn't be emptied because lots if not all files had the `sappnd` attribute set.

That flag was *not* set in the destroot folder, but apparently got into the archive tarball somehow. I didn't change anything to that step, and indeed it's the 1st time I ran into this issue.
I tried regenerating the archive tarball and even the destroot folder, didn't change anything. In the end I had to unpack the tarball by hand (sudo, otherwise the sappnd flag gets discarded) and then recreate it with a regular `sudo tar -cJf` to filter out the flag from the tarball.

What went wrong here?

NB: I installed a different variant of the same port earlier today without running into this issue... The only thing I did different this time is that I ran afsctool on the destroot folder before running port install, but 1) AFAICT that doesn't set a sappnd flag and 2) I rewound the state file and removed & recreated the destroot and archive tarball without effect.

Thanks,
R.