Tealdeer build fails

  • Open
  • quality assurance status badge
Details
6 participants
  • Cairn
  • Daniel Sockwell
  • Josselin Poiret
  • Corvo Liu
  • Maxime Devos
  • Simon Tournier
Owner
unassigned
Submitted by
Cairn
Severity
normal
C
C
Cairn wrote on 16 Sep 2022 21:36
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
21_uKPbmYw9lk1dKRtNbk4d_vN2Qt9DmuQdJjlpa6oyEKD2Xn5Wp0OUQakLz5lLId2rDvMX0A__pFdEsZ-1nixsUoZ1Pyb5hO4eH1mHI5-c=@pm.me
The builds have been unsuccessful since about the start of this month on both my machine and ci.guix.gnu.org. I tried to fix the issue, but I'm unfamiliar with Rust, so I just ended up fumbling around. Thanks to anyone who can get this working again! :D
Attachment: signature.asc
D
D
Daniel Sockwell wrote on 17 Sep 2022 13:55
(address . 57867@debbugs.gnu.org)
0b37b04494c2f19e679bc6765072884d@codesections.com
I have also run into this build failure.

The relevant error message from the build log appears to be:

Compiling openssl-macros v0.1.0
error[E0659]: `parse_quote_spanned` is ambiguous (`macro_rules` vs non-`macro_rules` from other module)
--> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/pin_project/derive.rs:859:67
|
859 | proj_generics.make_where_clause().predicates.push(parse_quote_spanned! { span =>
| ^^^^^^^^^^^^^^^^^^^ ambiguous name
|
note: `parse_quote_spanned` could refer to the macro defined here
--> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/utils.rs:22:1
|
22 | / macro_rules! parse_quote_spanned {
23 | | ($span:expr => $($tt:tt)*) => {
24 | | syn::parse2(quote::quote_spanned!($span => $($tt)*)).unwrap_or_else(|e| panic!("{}", e))
25 | | };
26 | | }
| |_^
note: `parse_quote_spanned` could also refer to the macro imported here
--> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/pin_project/derive.rs:7:5
|
7 | *,
| ^
= help: use `self::parse_quote_spanned` to refer to this macro unambiguously
M
M
Maxime Devos wrote on 17 Sep 2022 14:46
642e46ac-214e-61da-1963-5e9144ceccc2@telenet.be
On 17-09-2022 13:55, Daniel Sockwell via Bug reports for GNU Guix wrote:
Toggle quote (1 lines)
> --> /tmp/guix-build-tealdeer-1.4.1.drv-0/tealdeer-1.4.1/guix-vendor/rust-pin-project-internal-0.4.22.tar.gz/src/pin_project/derive.rs:859:67
In antioxidant, I noticed that rust-pin-project-internal@0.4 doesn't
build so I replaced it with rust-pin-project-internal@1 (and likewise
for rust-pin-project).
Maybe the same issue was present in the original cargo-build-system
using code, and a similar fix would work?
Greetings,
Maxime.
Attachment: OpenPGP_0x49E3EE22191725EE.asc
Attachment: OpenPGP_signature
C
C
Corvo Liu wrote on 28 Dec 2022 04:53
Tealdeer build fails
(address . 57867@debbugs.gnu.org)
CAAtoMVNBAEazmNLMb0PN8EdD1XAmwQAoKJZ_iNb+tGSRkRF8-Q@mail.gmail.com
I don't get it. How can a package "used to work" and "fail" now? If that is
the case, how is guix "declarative"?
Attachment: file
J
J
Josselin Poiret wrote on 29 Dec 2022 12:19
87cz82o3t0.fsf@jpoiret.xyz
Hi Corvo,

Corvo Liu <lyhokia@gmail.com> writes:

Toggle quote (3 lines)
> I don't get it. How can a package "used to work" and "fail" now? If that is
> the case, how is guix "declarative"?

Some dependencies might have been updated in the meantime resulting in
build failures. If you use a Guix commit from back when that package
was building fine, it will still build fine. Guix being reproducible
doesn't mean that Guix doesn't update any of its packages.

Best,
--
Josselin Poiret
S
S
Simon Tournier wrote on 5 Jan 2023 19:00
(name . Daniel Sockwell)(address . daniel@codesections.com)(address . 57867@debbugs.gnu.org)
87r0w8kgiz.fsf@gmail.com
Hi,

On Sat, 17 Sep 2022 at 11:55, "Daniel Sockwell" <daniel@codesections.com> wrote:

Toggle quote (2 lines)
> The relevant error message from the build log appears to be:

Indeed, this evaluation of the CI [1] reports [2] this error:

Toggle quote (3 lines)
> Compiling openssl-macros v0.1.0
> error[E0659]: `parse_quote_spanned` is ambiguous (`macro_rules` vs non-`macro_rules` from other module)

Well, it is part of the Evaluation 5349 [3] which points commit
e6dd58cfb511c23beb4d2732f898bb5479bd52d5, and it reads:

Toggle snippet (26 lines)
$ git log --format="%h %cd %s" | grep -C 11 e6dd58cfb
e5cfb7674a Mon Nov 28 14:02:37 2022 +0400 gnu: rust-clap-3: Update to 3.1.18.
05528a7b10 Mon Nov 28 14:02:20 2022 +0400 gnu: rust-clap-derive-3: Update to 3.1.18.
d32ed485e1 Mon Nov 28 14:02:12 2022 +0400 gnu: Add rust-clap-lex-0.2.
8bbc4dc2fb Mon Nov 28 14:01:56 2022 +0400 gnu: Add rust-rt-format-0.3.
dc685baad0 Mon Nov 28 14:01:44 2022 +0400 gnu: Add rust-swayipc-3.
622c3be7b6 Mon Nov 28 13:36:41 2022 +0400 Revert "gnu: Add rust-swayipc-3."
7922f610d2 Mon Nov 28 13:36:40 2022 +0400 Revert "gnu: Add rust-rt-format-0.3."
ddb3450684 Mon Nov 28 13:36:38 2022 +0400 Revert "gnu: Add rust-clap-lex-0.2."
1cc89f0be3 Mon Nov 28 13:36:36 2022 +0400 Revert "gnu: rust-clap-derive-3: Update to 3.1.18."
fd0bd21e66 Mon Nov 28 13:36:34 2022 +0400 Revert "gnu: rust-clap-3: Update to 3.1.18."
87e36d7478 Mon Nov 28 13:36:27 2022 +0400 Revert "gnu: Add swayr."
e6dd58cfb5 Mon Nov 28 12:50:22 2022 +0400 gnu: waybar: Update to 0.9.16.
b8a000b33b Mon Nov 28 12:50:21 2022 +0400 gnu: Add swayr.
93edae81b6 Mon Nov 28 12:50:20 2022 +0400 gnu: rust-clap-3: Update to 3.1.18.
7760e3fb09 Mon Nov 28 12:50:19 2022 +0400 gnu: rust-clap-derive-3: Update to 3.1.18.
4cb299e22e Mon Nov 28 12:50:18 2022 +0400 gnu: Add rust-clap-lex-0.2.
bf7c69b043 Mon Nov 28 12:50:17 2022 +0400 gnu: Add rust-rt-format-0.3.
655956131c Mon Nov 28 12:50:16 2022 +0400 gnu: Add rust-swayipc-3.
2db12d3c31 Mon Nov 28 12:50:15 2022 +0400 gnu: Add rust-swayipc-types-1.
df038ad39b Mon Nov 28 12:50:14 2022 +0400 gnu: Add rust-textwrap-0.15.
f7c95ecb67 Mon Nov 28 12:50:13 2022 +0400 gnu: rust-thiserror-1: Update to 1.0.37.
51cf11739d Mon Nov 28 12:50:12 2022 +0400 gnu: rust-thiserror-impl-1: Update to 1.0.37.
7f9a2930bf Sun Nov 27 00:24:56 2022 +0100 gnu: ardour: Update to 7.1

It means the culprit is probably one of these updates:

e6dd58cfb5 gnu: waybar: Update to 0.9.16.
93edae81b6 gnu: rust-clap-3: Update to 3.1.18.
7760e3fb09 gnu: rust-clap-derive-3: Update to 3.1.18.
f7c95ecb67 gnu: rust-thiserror-1: Update to 1.0.37.
51cf11739d gnu: rust-thiserror-impl-1: Update to 1.0.37.

Well, because it is not “inputs” but “hidden” in ’arguments’ via
#:cargo-inputs or #:cargo-development-inputs, “guix graph --path” is
useless here. However,

Toggle snippet (5 lines)
$ guix graph -t derivation tealdeer | grep label | grep rust-thiserror
"/gnu/store/2yqdbbrprafpi8a8zbf9vg9fl29m4bgb-rust-thiserror-impl-1.0.37.tar.gz.drv" [label = "rust-thiserror-impl-1.0.37.tar.gz.drv", shape = box, fontname = sans];
"/gnu/store/a0zc524q6im368xvwm3sp8bn9368p83b-rust-thiserror-1.0.37.tar.gz.drv" [label = "rust-thiserror-1.0.37.tar.gz.drv", shape = box, fontname = sans];

therefore, one (or both) is the culprit. It seems worth to try with
1.0.26 instead of 1.0.37. Any taker?



Cheers,
simon
?