From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 60539@debbugs.gnu.org
Subject: [bug#60539] teams: Add Reproducible Builds.
Date: Tue, 03 Jan 2023 21:47:49 -0800 [thread overview]
Message-ID: <878riiam0q.fsf@yucca> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 192 bytes --]
I would like to propose a Reproducible Builds team covering tooling
related to reproducible builds as well as a catch-all for reproducible
builds issues. Patch attached.
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-teams-Add-Reproducible-Builds-team.patch --]
[-- Type: text/x-diff, Size: 1006 bytes --]
From d5fca087fdc3cfad99ab5684d493806b98354bec Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Tue, 3 Jan 2023 21:36:58 -0800
Subject: [PATCH 1/4] teams: Add Reproducible Builds team.
* etc/teams.scm.in (reproduciblebuilds): New team.
---
etc/teams.scm.in | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/etc/teams.scm.in b/etc/teams.scm.in
index 96a04aca3d..7a7b2800d3 100644
--- a/etc/teams.scm.in
+++ b/etc/teams.scm.in
@@ -416,6 +416,13 @@ importer."
#:scope (list "gnu/packages/chez.scm"
"gnu/packages/racket.scm")))
+(define-team reproduciblebuilds
+ (team 'reproduciblebuilds
+ #:name "Reproducible Builds team"
+ #:description
+ "Reproducible Builds tooling and issues that affect any guix packages."
+ #:scope (list "gnu/packages/diffoscope.scm")))
+
\f
(define-member (person "Thiago Jung Bauermann"
"bauermann@kolabnow.com")
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2023-01-04 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 5:47 Vagrant Cascadian [this message]
2023-01-04 6:16 ` [bug#60539] teams: Add Reproducible Builds Vagrant Cascadian
2023-01-04 6:18 ` Vagrant Cascadian
2023-01-08 13:43 ` Mathieu Othacehe
2023-01-11 0:20 ` bug#60539: " Vagrant Cascadian
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878riiam0q.fsf@yucca \
--to=vagrant@reproducible-builds.org \
--cc=60539@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).