[jira] [Updated] (ARROW-7794) [Rust] cargo publish fails for arrow-flight due to relative path to Flight.proto

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-7794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ARROW-7794:
----------------------------------
    Labels: pull-request-available  (was: )

> [Rust] cargo publish fails for arrow-flight due to relative path to Flight.proto
> --------------------------------------------------------------------------------
>
>                 Key: ARROW-7794
>                 URL: https://issues.apache.org/jira/browse/ARROW-7794
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Rust
>    Affects Versions: 0.16.0
>            Reporter: Andy Grove
>            Assignee: Andy Grove
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.17.0
>
>
> Running "cargo publish" for the arrow-flight crate resulted in this error:
> {code:java}
> error: failed to run custom build command for `arrow-flight v0.16.0 (/home/andy/apache-arrow-0.16.0/rust/target/package/arrow-flight-0.16.0)`Caused by:
>   process didn't exit successfully: `/home/andy/apache-arrow-0.16.0/rust/target/package/arrow-flight-0.16.0/target/debug/build/arrow-flight-1b2906a3933d2832/build-script-build` (exit code: 1)
> --- stderr
> Error: Custom { kind: Other, error: "protoc failed: ../../format: warning: directory does not exist.\nCould not make proto path relative: ../../format/Flight.proto: No such file or directory\n" }
>  {code}
> The workaround was to edit the build.rs and make the path absolute and then run "cargo publish --allow-dirty", but we should find a better solution before the next release.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)