Github messages for voidlinux
 help / color / mirror / Atom feed
From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Rust 1.80
Date: Fri, 26 Jul 2024 06:03:31 +0200	[thread overview]
Message-ID: <20240726040332.076F421FC1@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51458@inbox.vuxu.org>

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

New comment by tranzystorekk on void-packages repository

https://github.com/void-linux/void-packages/pull/51458#issuecomment-2251408291

Comment:
Results of `build_style=cargo` rebuild for x86_64-gnu:

## New failures since 1.79

### https://github.com/time-rs/time/issues/693

(requires bumping `time` dependency to at least `0.3.35` - [fix commit](https://github.com/time-rs/time/commit/5b0c627366babea1636b35db641c0fec964ddbd1))

Likely no immediate fix is needed, just notify upstreams to ensure they have bumped `time` by next release, or else bump manually as needed:

```sh
post_install() {
    cargo update --package time@<current_version> --precise 0.3.35
}
```

- `aardvark-dns` cc @daniel-eys
- `amp` cc @wpbirney
- `bandwhich`
- `bottom` cc @cinerea0
- `cargo-c` cc @oreo639
- `cargo-crev`
- `cargo-geiger`
- `circadian` cc @abenson
- `czkawka` cc @sirkhancision
- `deepfilternet-ladspa` cc @Johnnynator
- `delta` cc @abenson
- `dua-cli` cc @cinerea0
- `eludris` cc @ooliver1
- `evtx` cc @abenson
- `eww` cc @shmishtopher
- `eza`
- `gcsf` cc @benalb
- `geckodriver` cc @mtvrsh
- `gleam` @leahneukirchen
- `ironbar` cc @caughtquick
- `kak-lsp`
- `leftwm` cc @uncomfyhalomacro
- `miniserve` cc @Gottox
- `ncspot` cc @ram02z
- `openpgp-ca`
- `openpgp-card-tools`
- `routinator` cc @CameronNemo
- `rust-cargo-audit`
- `rustypaste` cc @lukas-jo
- `shotman`
- `starship` cc @cinerea0
- `steamguard-cli` cc @filiprojek
- `taplo` cc @cinerea0
- `tectonic` cc @daniel-eys
- `typst` cc @classabbyamp
- `typst-lsp` cc @classabbyamp
- `wezterm` cc @jbenden
- `wiki-tui` cc @ethamck
- `yaydl` cc @atk

### Misc

- `ntdsextract2` https://0x0.st/Xfqr.txt cc @abenson

## Known failures

- `fool`
- `hurl`
- `ion`
- `lapce`
- `spotifyd`
- `spotify-tui`
- `wasmtime`

  parent reply	other threads:[~2024-07-26  4:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 19:58 [PR PATCH] " tranzystorekk
2024-07-25 21:14 ` tranzystorekk
2024-07-26  3:47 ` tranzystorekk
2024-07-26  4:03 ` tranzystorekk [this message]
2024-07-26  4:07 ` tranzystorekk
2024-07-26 14:07 ` leahneukirchen
2024-07-26 14:12 ` leahneukirchen
2024-07-26 22:16 ` abenson
2024-07-26 23:07 ` tranzystorekk
2024-07-26 23:13 ` tranzystorekk
2024-07-26 23:14 ` tranzystorekk
2024-07-26 23:19 ` tranzystorekk
2024-07-27 10:58 ` tranzystorekk
2024-07-27 13:16 ` [PR PATCH] [Updated] " tranzystorekk
2024-07-28 16:39 ` abenson
2024-07-28 16:44 ` abenson
2024-07-29  7:37 ` tranzystorekk
2024-07-29  7:39 ` tranzystorekk
2024-07-29 11:27 ` atk
2024-07-29 11:42 ` tranzystorekk
2024-07-29 11:49 ` tranzystorekk
2024-07-29 15:38 ` [PR PATCH] [Merged]: " tranzystorekk
2024-07-29 16:09 ` abenson

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=20240726040332.076F421FC1@inbox.vuxu.org \
    --to=tranzystorekk@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).