Patrick McCarty 0af0308dd2 Revert "have tar follow symlinks" ...

After closer inspection, I've determined that prior to this commit,
clr_debug_prepare was behaving properly with respect to the handling of
symlinks in debuginfo packages. Reverting this commit fixes the issue.

Details:

 - Symlinks under /usr/lib/debug/.build-id that are not broken should be
 unsymlinked so that the actual debuginfo is added to the automatic
 debuginfo tarballs. In the debuginfo packages, these files have a
 .debug extension and point to files under /usr/lib/debug/usr.

 - Symlinks under /usr/lib/debug/.build-id that *are* broken cannot be
 unsymlinked, and therefore, tar should not follow these symlinks,
 because fatal errors (and empty tarballs) are the result. These
 symlinks lack the .debug extension and point to the corresponding
 libraries or binaries under /usr when exposed via clr_debug_fuse. So it
 is correct for the symlinks to be broken when packaged by
 clr_debug_prepare, since they point to non-debuginfo files, and the
 debuginfo.raw directory tree only contains debuginfo content.

This reverts commit 7dcddfd0ca8f5539ef34028a1c680f6e82dcf246.

2018-12-10 17:04:05 -08:00

..

nica

nica/files: Ensure we really do break on a read error

2017-03-09 15:44:09 +00:00

client.c

Make -daemon socket activated.

2018-04-23 15:15:33 -07:00

fuse.c

Fix print statements when a dir cannot be created

2016-05-17 17:20:31 +01:00

prepare.c

Revert "have tar follow symlinks"

2018-12-10 17:04:05 -08:00

server.c

add cdn-alt

2018-05-17 13:54:16 +00:00