From: Gabriel Arazas <foo.dogsquared@gmail.com>
To: 43414@debbugs.gnu.org
Subject: [bug#43414] (no subject)
Date: Wed, 16 Sep 2020 19:36:53 +0800 [thread overview]
Message-ID: <0710a5a6-9fba-86f3-6157-95b2d777527b@gmail.com> (raw)
In-Reply-To: <20200915005226.1978-1-foo.dogsquared@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Of all the packages I forgot to test, it's the one with the obvious
error. :/
Sorry for the rookie mistake, I triple-checked it and got the same error
as you reported. I only tested two dependent packages (out of four
according to the page,
https://crates.io/crates/lab/reverse_dependencies, anyways) so far and
it compiled successfully. I think it is safe to assume it's from the
test suite.
> These two packages don't actually use the same dependencies as > rust-lab-0.8. I normally check https://crates.io/crates/package-name
> to make sure I have the correct dependencies.
I also forgot to check and correct the dependencies for the lower
versions of rust-lab. Apologies for another mistake. I'll keep that in
mind next time.
Anyways, thanks for checking things out. :) I'll have to clean up my
workflow for next time, write up a note or something for reminders. Just
getting used to packaging with different tools and stuff.
Best regards,
Gabriel Arazas
[-- Attachment #2: Type: text/html, Size: 3742 bytes --]
prev parent reply other threads:[~2020-09-16 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 0:52 [bug#43414] [PATCH 1/3] gnu: Add rust-lab Gabriel Arazas
2020-09-15 8:36 ` [bug#43414] [PATCH 2/3] gnu: Add rust-delta-e Gabriel Arazas
2020-09-15 8:36 ` [bug#43414] [PATCH 3/3] gnu: Add rust-ansi-colours Gabriel Arazas
2020-09-15 8:43 ` [bug#43414] [PATCH 1/3] gnu: Add rust-lab Gabriel Arazas
2020-09-16 6:49 ` bug#43414: " Efraim Flashner
2020-09-16 6:48 ` [bug#43414] " Efraim Flashner
2020-09-16 11:36 ` Gabriel Arazas [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=0710a5a6-9fba-86f3-6157-95b2d777527b@gmail.com \
--to=foo.dogsquared@gmail.com \
--cc=43414@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.