From: Vagrant Cascadian <vagrant@debian.org>
To: "Ricardo Wurmus" <rekado@elephly.net>,
"Mădălin Ionel Patrașcu" <madalinionel.patrascu@mdc-berlin.de>
Cc: 59911@debbugs.gnu.or, control@debbugs.gnu.org
Subject: [bug#59911] Add r-shinywidgets, r-wpm
Date: Fri, 01 Sep 2023 21:41:27 -0700 [thread overview]
Message-ID: <8734zxp4p4.fsf@wireframe> (raw)
In-Reply-To: <87a63s1opr.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
retitle 59911 Add r-shinywidgets, r-wpm
thanks
On 2022-12-12, Ricardo Wurmus wrote:
> I applied five of these seven patches. As I wrote earlier
> r-shinywidgets contains minified JavaScript that would need to be
> compiled from source instead. Consequently, r-wpm cannot be accepted
> because it depends on r-shinywidgets.
Updating bug title appropriately.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-09-02 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 21:10 [bug#59911] [PATCH] gnu: Add r-logging, r-shinycustomloader, r-anytime, r-shinywidgets, r-attempt, r-golem and r-wpm MadalinIonel.Patrascu
2022-12-08 21:13 ` [bug#59911] [PATCH 1/7] gnu: Add r-logging Mădălin Ionel Patrașcu
2022-12-08 21:13 ` [bug#59911] [PATCH 2/7] gnu: Add r-shinycustomloader Mădălin Ionel Patrașcu
2022-12-08 21:13 ` [bug#59911] [PATCH 3/7] gnu: Add r-anytime Mădălin Ionel Patrașcu
2022-12-08 21:13 ` [bug#59911] [PATCH 4/7] gnu: Add r-shinywidgets Mădălin Ionel Patrașcu
2022-12-12 17:49 ` Ricardo Wurmus
2022-12-08 21:13 ` [bug#59911] [PATCH 5/7] gnu: Add r-attempt Mădălin Ionel Patrașcu
2022-12-08 21:13 ` [bug#59911] [PATCH 6/7] gnu: Add r-golem Mădălin Ionel Patrașcu
2022-12-08 21:13 ` [bug#59911] [PATCH 7/7] gnu: Add r-wpm Mădălin Ionel Patrașcu
2022-12-12 18:03 ` [bug#59911] [PATCH 1/7] gnu: Add r-logging Ricardo Wurmus
2023-09-02 4:41 ` Vagrant Cascadian [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
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=8734zxp4p4.fsf@wireframe \
--to=vagrant@debian.org \
--cc=59911@debbugs.gnu.or \
--cc=control@debbugs.gnu.org \
--cc=madalinionel.patrascu@mdc-berlin.de \
--cc=rekado@elephly.net \
/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).