bug#57867: Tealdeer build fails

bug#57867: Tealdeer build fails

[Cairn via Bug reports for GNU Guix]

[-- Attachment #1.1: Type: text/plain, Size: 253 bytes --]

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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 855 bytes --]

bug#57867: Tealdeer build fails

[Daniel Sockwell via Bug reports for GNU Guix]

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

bug#57867: Tealdeer build fails

[Maxime Devos]

[-- Attachment #1.1.1: Type: text/plain, Size: 537 bytes --]



On 17-09-2022 13:55, Daniel Sockwell via Bug reports for GNU Guix wrote:
>         --> /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 #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

bug#57867: Tealdeer build fails

[Corvo Liu]

[-- Attachment #1: Type: text/plain, Size: 113 bytes --]

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 #2: Type: text/html, Size: 172 bytes --]

bug#57867: Tealdeer build fails

[Josselin Poiret via Bug reports for GNU Guix]

Hi Corvo,

Corvo Liu <lyhokia@gmail.com> writes:

> 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

bug#57867: Tealdeer build fails

[Simon Tournier]

Hi,

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

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

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

>        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:

--8<---------------cut here---------------start------------->8---
$  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
--8<---------------cut here---------------end--------------->8---

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,

--8<---------------cut here---------------start------------->8---
$ 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];
--8<---------------cut here---------------end--------------->8---

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

1: <http://ci.guix.gnu.org/build/156858/details>
2: <http://ci.guix.gnu.org/build/156858/log/raw>
3: <http://ci.guix.gnu.org/eval/5349>


Cheers,
simon