From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: List of packages failing to build due to missing Cargo.lock
Date: Mon, 17 Apr 2023 20:17:27 +0200 [thread overview]
Message-ID: <20230417181727.XofkE2Qm1DQDVe0TLgaUX4PyD3WkeR9cspKEMHOKT6U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43482@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/issues/43482#issuecomment-1511865621
Comment:
I'd like to rename this issue: In some of these cases, the Cargo.lock file is present, but not up to date. In the case of cargo-auditable` for example, it's just a tiny issue around the version number of itself:
```
diff --git a/Cargo.lock2 b/Cargo.lock
index 00969c9e1c..5caabbda1c 100644
--- a/Cargo.lock2
+++ b/Cargo.lock
@@ -72,7 +72,7 @@ dependencies = [
[[package]]
name = "cargo-auditable"
-version = "0.6.0"
+version = "0.6.1"
dependencies = [
"auditable-info",
"auditable-serde",
```
next prev parent reply other threads:[~2023-04-17 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 17:43 [ISSUE] " paper42
2023-04-16 18:20 ` tranzystorek-io
2023-04-17 6:42 ` tranzystorek-io
2023-04-17 7:21 ` icp1994
2023-04-17 7:30 ` tranzystorek-io
2023-04-17 8:03 ` icp1994
2023-04-17 18:17 ` jcgruenhage [this message]
2023-04-17 18:58 ` jcgruenhage
2023-06-27 6:30 ` [ISSUE] [CLOSED] List of packages failing to build due to a missing or broken Cargo.lock classabbyamp
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=20230417181727.XofkE2Qm1DQDVe0TLgaUX4PyD3WkeR9cspKEMHOKT6U@z \
--to=jcgruenhage@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).