Uh oh!
There was an error while loading. Please reload this page.
[stable20] Update 3rdparty after Archive_Tar - #25199
Conversation
Signed-off-by: Joas Schilling <coding@schilljs.com>
3906664 to
31b7040Compare🤖 beep boop beep 🤖 Here are the logs for the failed build: Status of 1473: failureacceptance-users
Show full log |
mtierltd
commented
Jan 28, 2021
Hi This change breaks installing some applications due to the changes in Archive_Tar, |
ChristophWurst
commented
Jan 28, 2021
Mind elaborating what kind of applications you are talking about? Nextcloud apps? Why would they have symlinks? Do you have any tickets? |
mtierltd
commented
Jan 28, 2021
A nextcloud application yes that has a symlink in the vendor directory, which was not a problem before. We have been having issues after updating to 20.0.6 and I've done a test with Archive_Tar 1.4.12 which |
ChristophWurst
commented
Jan 28, 2021
Please let the authors of that apps know that they are not supposed to put symlinks into their tarballs. |
ChristophWurst
commented
Jan 28, 2021
It's already known as per mtierltd/timetracker#86 and mtierltd/timetracker#90 |
mtierltd
commented
Jan 28, 2021
Can you elaborate on why symlinks are not to be used? What is the technical reason behind it? |
ChristophWurst
commented
Jan 28, 2021
See the 3rdparty bump nextcloud/3rdparty#603 for details |
mtierltd
commented
Jan 28, 2021
Okay so no technical reason. Thanks. |
Signed-off-by: Joas Schilling coding@schilljs.com