all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: 66839@debbugs.gnu.org
Cc: Steve George <steve@futurile.net>, efraim@flashner.co.il
Subject: [bug#66839] [PATCH 10/19] gnu: Add rust-tracing-error-0.2.
Date: Mon, 30 Oct 2023 21:06:16 +0000	[thread overview]
Message-ID: <6d490dc1e227784abf235e43206b3cf7560bafb9.1698699809.git.steve@futurile.net> (raw)
In-Reply-To: <cover.1698696699.git.steve@futurile.net>

* gnu/packages/crates-io.scm (rust-tracing-error-0.2): New variable.
---
 gnu/packages/crates-io.scm | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/gnu/packages/crates-io.scm b/gnu/packages/crates-io.scm
index 0cdd69fbd7..8f267a8dd8 100644
--- a/gnu/packages/crates-io.scm
+++ b/gnu/packages/crates-io.scm
@@ -77145,6 +77145,30 @@ (define-public rust-tracing-core-0.1
     (license (list license:asl2.0
                    license:expat))))
 
+(define-public rust-tracing-error-0.2
+  (package
+    (name "rust-tracing-error")
+    (version "0.2.0")
+    (source
+     (origin
+       (method url-fetch)
+       (uri (crate-uri "tracing-error" version))
+       (file-name (string-append name "-" version ".tar.gz"))
+       (sha256
+        (base32 "0vi0rns7r8iny2milg0kikz1mhgcl9wz5clpy1vi4jrq1wffr1nn"))))
+    (build-system cargo-build-system)
+    (arguments
+     `(#:tests? #f
+       #:cargo-inputs (("rust-tracing" ,rust-tracing-0.1)
+                       ("rust-tracing-subscriber" ,rust-tracing-subscriber-0.3))))
+    (home-page "https://github.com/tokio-rs/tracing")
+    (synopsis "Enriched error handling for Rust's @code{Tracing} framework")
+    (description
+     "An enriched error type with diagnostic information for
+Rust's @code{Tracing} framework.  Provides additional formatting for errors
+and automatically generates tracing events when errors occur.")
+    (license license:expat)))
+
 (define-public rust-tracing-futures-0.2
   (package
     (name "rust-tracing-futures")
-- 
2.41.0





  parent reply	other threads:[~2023-10-30 21:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 20:16 [bug#66839] [PATCH 00/19] Series to add spotifyd Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 01/19] gnu: Add rust-librespot-connect-0.4 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 02/19] gnu: Add rust-daemonize-0.5 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 03/19] gnu: rust-gethostname-0.4 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 04/19] gnu: rust-libdbus-sys-0.2: Update to 0.2.5 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 05/19] gnu: rust-dbus-0.9: Update to 0.9.7 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 06/19] gnu: Add rust-dbus-crossroads-0.5 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 07/19] gnu: Add rust-dbus-tokio-0.7 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 08/19] gnu: rust-heapless-0.5: Update to 0.5.6 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 09/19] gnu: Add rust-ansi-parser-0.8 Steve George
2023-10-30 21:06 ` Steve George [this message]
2023-10-30 21:06 ` [bug#66839] [PATCH 11/19] gnu: Add rust-color-spantrace-0.2 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 12/19] gnu: Add rust-color-eyre-0.6 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 13/19] gnu: Add rust-syslog-6 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 14/19] gnu: Add rust-simple-logging-2 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 15/19] gnu: Add rust-reopen-1 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 16/19] gnu: Update rust-reopen-0.3 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 17/19] gnu: rust-fern-0.6: Update to 0.6.2, add rust-syslog-6 dependency Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 18/19] gnu: rust-sha-1-0.10: Downgrade to 0.10.1 Steve George
2023-10-30 21:06 ` [bug#66839] [PATCH 19/19] gnu: Add rust-spotifyd-0.3 Steve George
2023-11-05 10:31 ` bug#66839: [PATCH 00/19] Series to add spotifyd Efraim Flashner

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=6d490dc1e227784abf235e43206b3cf7560bafb9.1698699809.git.steve@futurile.net \
    --to=steve@futurile.net \
    --cc=66839@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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.