Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] pijul: FTBFS
Date: Sun, 27 Aug 2023 05:48:29 +0200	[thread overview]
Message-ID: <20230827034829.g6y_OVJ0WwEGzTyw4FLcOm8WM_6SewmDqyMY5JGxbTA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45689@inbox.vuxu.org>

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

Closed issue by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/45689

Description:
cc maintainer @Vaelatern 
seems it can't build with the current rust, and our only option would be to update to the latest version, which is considered a beta by upstream, or drop it. I need to be able to bump it for openssl3

```
   Compiling libpijul v0.12.2
error[E0507]: cannot move out of `self.basename` which is behind a shared reference
  --> /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/libpijul-0.12.2/src/backend/file_id.rs:10:5
   |
6  | #[derive(Debug, Hash, Eq, PartialEq, Clone)]
   |          ----- in this derive macro expansion
...
10 |     pub basename: SmallString,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ move occurs because `self.basename` has type `small_string::SmallString`, which does not implement the `Copy` trait
   |
   = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0507]: cannot move out of `self.basename` which is behind a shared reference
  --> /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/libpijul-0.12.2/src/backend/file_id.rs:10:5
   |
6  | #[derive(Debug, Hash, Eq, PartialEq, Clone)]
   |                 ---- in this derive macro expansion
...
10 |     pub basename: SmallString,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ move occurs because `self.basename` has type `small_string::SmallString`, which does not implement the `Copy` trait
   |
   = note: this error originates in the derive macro `Hash` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0507]: cannot move out of `self.basename` which is behind a shared reference
  --> /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/libpijul-0.12.2/src/backend/file_id.rs:10:5
   |
6  | #[derive(Debug, Hash, Eq, PartialEq, Clone)]
   |                           --------- in this derive macro expansion
...
10 |     pub basename: SmallString,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ move occurs because `self.basename` has type `small_string::SmallString`, which does not implement the `Copy` trait
   |
   = note: this error originates in the derive macro `PartialEq` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0507]: cannot move out of `other.basename` which is behind a shared reference
  --> /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/libpijul-0.12.2/src/backend/file_id.rs:10:5
   |
6  | #[derive(Debug, Hash, Eq, PartialEq, Clone)]
   |                           --------- in this derive macro expansion
...
10 |     pub basename: SmallString,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ move occurs because `other.basename` has type `small_string::SmallString`, which does not implement the `Copy` trait
   |
   = note: this error originates in the derive macro `PartialEq` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0507]: cannot move out of `self.basename` which is behind a shared reference
  --> /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/libpijul-0.12.2/src/backend/file_id.rs:10:5
   |
6  | #[derive(Debug, Hash, Eq, PartialEq, Clone)]
   |                                      ----- in this derive macro expansion
...
10 |     pub basename: SmallString,
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ move occurs because `self.basename` has type `small_string::SmallString`, which does not implement the `Copy` trait
   |
   = note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0507`.
error: could not compile `libpijul` (lib) due to 5 previous errors
warning: build failed, waiting for other jobs to finish...
warning: `sequoia-rfc2822` (lib) generated 94 warnings (run `cargo fix --lib -p sequoia-rfc2822` to apply 93 suggestions)
=> ERROR: pijul-0.12.2_6: do_build: '${make_cmd} build --release --locked --target ${RUST_TARGET} ${configure_args}' exited with 101
=> ERROR:   in do_build() at common/build-style/cargo.sh:8
```

      parent reply	other threads:[~2023-08-27  3:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 18:41 [ISSUE] " classabbyamp
2023-08-20 19:38 ` Vaelatern
2023-08-20 19:39 ` Vaelatern
2023-08-20 19:43 ` classabbyamp
2023-08-20 19:50 ` tranzystorek-io
2023-08-20 19:52 ` Vaelatern
2023-08-27  3:48 ` classabbyamp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230827034829.g6y_OVJ0WwEGzTyw4FLcOm8WM_6SewmDqyMY5JGxbTA@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).