We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are using DebianPackaging, and getting error on generated chown command.
In generated postinst there is:
# Chown definitions created by SBT Native Packager a_lot_of_files_and_then_this_one chown website:website /usr/share/project-name/share/doc/api/website/engine/utils/Binders$$WknsBinder$.html
But when running it it gives error:
Binders33321WknsBinder$.html': No such file or directory
because $$ is replaced with PID. Generated command should surround filepath with single quotes, e.g.:
chown website:website '/usr/share/project-name/share/doc/api/website/engine/utils/Binders$$WknsBinder$.html'
Incorrect chown command.
1.3.4.
Error seems to be here: https://github.com/sbt/sbt-native-packager/blob/v1.3.6/src/main/scala/com/typesafe/sbt/packager/debian/DebianPlugin.scala#L422, no quote around $path.
The text was updated successfully, but these errors were encountered:
Fix generated chown command (sbt#1151)
dad0044
834f449
c39bde7
c82729c
Fix generated chown command (#1151) (#1152)
64b8ed7
Fixed in 1.3.7.
Sorry, something went wrong.
No branches or pull requests
Expected behaviour
We are using DebianPackaging, and getting error on generated chown command.
In generated postinst there is:
But when running it it gives error:
because $$ is replaced with PID. Generated command should surround filepath with single quotes, e.g.:
Actual behaviour
Incorrect chown command.
Information
1.3.4.
Error seems to be here: https://github.com/sbt/sbt-native-packager/blob/v1.3.6/src/main/scala/com/typesafe/sbt/packager/debian/DebianPlugin.scala#L422, no quote around $path.
The text was updated successfully, but these errors were encountered: