summaryrefslogtreecommitdiffstats
path: root/lib/libalpm/conflict.c
diff options
context:
space:
mode:
authorDan McGee <dan@archlinux.org>2011-10-26 23:43:36 +0200
committerDan McGee <dan@archlinux.org>2011-10-27 00:31:43 +0200
commit5c1885b55eae870a10c91793d05a74d74a075e83 (patch)
tree3160bb76a3b24c28640f79340b650c101bbe15e7 /lib/libalpm/conflict.c
parent7a6b01d46c1da385dd34466e757beafa33e02afa (diff)
downloadpacman-5c1885b55eae870a10c91793d05a74d74a075e83.tar.gz
pacman-5c1885b55eae870a10c91793d05a74d74a075e83.tar.xz
Add some unowned symlink replacement tests
These should all prevent installation, and yet two of the three tests currently fail. Not good. The best way to see what is going on here is to diff the three new tests side by side- there is only a small difference between the three tests, and that is in the destination of the symlink in question that should never be overwritten. symlink010.py: myprogsuffix -> myprog symlink011.py: myprogsuffix -> broken symlink012.py: myprogsuffix -> otherprog Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to 'lib/libalpm/conflict.c')
0 files changed, 0 insertions, 0 deletions