Skip to content
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

error when compiling #1190

Closed
Jorpy76 opened this issue Mar 16, 2023 · 1 comment · Fixed by #1182
Closed

error when compiling #1190

Jorpy76 opened this issue Mar 16, 2023 · 1 comment · Fixed by #1182

Comments

@Jorpy76
Copy link

Jorpy76 commented Mar 16, 2023

Hi there : I have an error when compiling in Debian 11:

cargo 1.68.0 (115f34552 2023-02-26)
spotifyd 0.3.4

warning: unused imports: error, warn
--> src/setup.rs:20:11
|
20 | use log::{error, info, warn};
| ^^^^^ ^^^^
|
= note: #[warn(unused_imports)] on by default

warning: spotifyd (bin "spotifyd") generated 1 warning
Finished release [optimized] target(s) in 0.33s
warning: the following packages contain code that will be rejected by a future version of Rust: daemonize v0.4.1
note: to see what the problems were, use the option --future-incompat-report, or run cargo report future-incompatibilities --id 2

@Jorpy76 Jorpy76 added the bug A functionality or parts of a program that do not work as intended label Mar 16, 2023
@eladyn
Copy link
Member

eladyn commented Mar 16, 2023

Thank you for the report! The messages you're getting aren't actually errors, but warnings which shouldn't prevent you from successfully compiling spotifyd. Nonetheless, both are valid points! The first warning (unused imports) should be fixed by #1182 and the second by #1183 (assuming daemonize 0.5 gets rid of that incompatible code).

@eladyn eladyn removed the bug A functionality or parts of a program that do not work as intended label Mar 16, 2023
@slondr slondr linked a pull request Mar 22, 2023 that will close this issue
@slondr slondr removed a link to a pull request Mar 22, 2023
@slondr slondr linked a pull request Mar 22, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants