-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[stable20] Update 3rdparty after Archive_Tar #25199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Joas Schilling <[email protected]>
3906664 to
31b7040
Compare
|
🤖 beep boop beep 🤖 Here are the logs for the failed build: Status of 1473: failureacceptance-users
Show full log |
|
Hi This change breaks installing some applications due to the changes in Archive_Tar, |
|
Mind elaborating what kind of applications you are talking about? Nextcloud apps? Why would they have symlinks? Do you have any tickets? |
|
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 |
Please let the authors of that apps know that they are not supposed to put symlinks into their tarballs. |
|
It's already known as per mtierltd/timetracker#86 and mtierltd/timetracker#90 |
|
Can you elaborate on why symlinks are not to be used? What is the technical reason behind it? |
|
See the 3rdparty bump nextcloud/3rdparty#603 for details |
|
Okay so no technical reason. Thanks. |
Signed-off-by: Joas Schilling [email protected]