@@ -146,16 +146,16 @@ fn incompat_in_dependency() {
146
146
. with_stderr_data ( str![ [ r#"
147
147
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
148
148
[WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
149
- [NOTE] To solve this problem, you can try the following approaches:
149
+ [NOTE] to solve this problem, you can try the following approaches:
150
150
151
- - Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
152
- or even helping with a fix (e.g. by creating a pull request):
151
+ - ensure the maintainers know of this problem (e.g. creating a bug report if needed)
152
+ or even helping with a fix (e.g. by creating a pull request)
153
153
154
154
155
- - Repository : https://example.com/
156
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
155
+ - repository : https://example.com/
156
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
157
157
158
- - Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
158
+ - use your own version of the dependency with the `[patch]` section in `Cargo.toml`
159
159
For more information, see:
160
160
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
161
161
@@ -176,16 +176,16 @@ to be in wide use.
176
176
Each warning should contain a link for more information on what the warning
177
177
means and how to resolve it.
178
178
179
- To solve this problem, you can try the following approaches:
179
+ to solve this problem, you can try the following approaches:
180
180
181
- - Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
182
- or even helping with a fix (e.g. by creating a pull request):
181
+ - ensure the maintainers know of this problem (e.g. creating a bug report if needed)
182
+ or even helping with a fix (e.g. by creating a pull request)
183
183
184
184
185
- - Repository : https://example.com/
186
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
185
+ - repository : https://example.com/
186
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
187
187
188
- - Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
188
+ - use your own version of the dependency with the `[patch]` section in `Cargo.toml`
189
189
For more information, see:
190
190
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
191
191
@@ -595,29 +595,29 @@ fn suggestions_for_updates() {
595
595
[CHECKING] foo v0.1.0 ([ROOT]/foo)
596
596
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
597
597
[WARNING] the following packages contain code that will be rejected by a future version of Rust: big_update v1.0.0, with_updates v1.0.0, without_updates v1.0.0
598
- [NOTE] To solve this problem, you can try the following approaches:
598
+ [NOTE] to solve this problem, you can try the following approaches:
599
599
600
- - Update to a newer version to see if the issue has been fixed:
600
+ - update to a newer version to see if the issue has been fixed
601
601
602
602
- big_update v1.0.0 has the following newer versions available: 2.0.0
603
603
- with_updates v1.0.0 has the following newer versions available: 1.0.1, 1.0.2, 3.0.1
604
604
605
- - Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
606
- or even helping with a fix (e.g. by creating a pull request):
605
+ - ensure the maintainers know of this problem (e.g. creating a bug report if needed)
606
+ or even helping with a fix (e.g. by creating a pull request)
607
607
608
608
609
- - Repository : <not found>
610
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
609
+ - repository : <not found>
610
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
611
611
612
612
613
- - Repository : <not found>
614
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
613
+ - repository : <not found>
614
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
615
615
616
616
617
- - Repository : <not found>
618
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
617
+ - repository : <not found>
618
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
619
619
620
- - Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
620
+ - use your own version of the dependency with the `[patch]` section in `Cargo.toml`
621
621
For more information, see:
622
622
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
623
623
@@ -638,29 +638,29 @@ to be in wide use.
638
638
Each warning should contain a link for more information on what the warning
639
639
means and how to resolve it.
640
640
641
- To solve this problem, you can try the following approaches:
641
+ to solve this problem, you can try the following approaches:
642
642
643
- - Update to a newer version to see if the issue has been fixed:
643
+ - update to a newer version to see if the issue has been fixed
644
644
645
645
- big_update v1.0.0 has the following newer versions available: 2.0.0
646
646
- with_updates v1.0.0 has the following newer versions available: 1.0.1, 1.0.2, 3.0.1
647
647
648
- - Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
649
- or even helping with a fix (e.g. by creating a pull request):
648
+ - ensure the maintainers know of this problem (e.g. creating a bug report if needed)
649
+ or even helping with a fix (e.g. by creating a pull request)
650
650
651
651
652
- - Repository : <not found>
653
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
652
+ - repository : <not found>
653
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
654
654
655
655
656
- - Repository : <not found>
657
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
656
+ - repository : <not found>
657
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
658
658
659
659
660
- - Repository : <not found>
661
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
660
+ - repository : <not found>
661
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
662
662
663
- - Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
663
+ - use your own version of the dependency with the `[patch]` section in `Cargo.toml`
664
664
For more information, see:
665
665
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
666
666
@@ -700,16 +700,16 @@ fn correct_report_id_when_cached() {
700
700
[CHECKING] foo v1.0.0 ([ROOT]/foo)
701
701
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
702
702
[WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
703
- [NOTE] To solve this problem, you can try the following approaches:
703
+ [NOTE] to solve this problem, you can try the following approaches:
704
704
705
- - Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
706
- or even helping with a fix (e.g. by creating a pull request):
705
+ - ensure the maintainers know of this problem (e.g. creating a bug report if needed)
706
+ or even helping with a fix (e.g. by creating a pull request)
707
707
708
708
709
- - Repository : https://example.com/
710
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
709
+ - repository : https://example.com/
710
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
711
711
712
- - Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
712
+ - use your own version of the dependency with the `[patch]` section in `Cargo.toml`
713
713
For more information, see:
714
714
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
715
715
@@ -723,16 +723,16 @@ https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch
723
723
. with_stderr_data ( str![ [ r#"
724
724
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
725
725
[WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
726
- [NOTE] To solve this problem, you can try the following approaches:
726
+ [NOTE] to solve this problem, you can try the following approaches:
727
727
728
- - Ensure the maintainers know of this problem (e.g. creating a bug report if needed)
729
- or even helping with a fix (e.g. by creating a pull request):
728
+ - ensure the maintainers know of this problem (e.g. creating a bug report if needed)
729
+ or even helping with a fix (e.g. by creating a pull request)
730
730
731
731
732
- - Repository : https://example.com/
733
- - Detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
732
+ - repository : https://example.com/
733
+ - detailed warning command: `cargo report future-incompatibilities --id 1 --package [email protected] `
734
734
735
- - Use your own version of the dependency with the `[patch]` section in `Cargo.toml`.
735
+ - use your own version of the dependency with the `[patch]` section in `Cargo.toml`
736
736
For more information, see:
737
737
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
738
738
0 commit comments