From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"joaog.bastos" <joaog.bastos@protonmail.ch>
Cc: 54978@debbugs.gnu.org, control@debbugs.gnu.org
Subject: [bug#54978] [PATCH] gnu: Add utsushi.
Date: Fri, 01 Sep 2023 16:48:46 -0700 [thread overview]
Message-ID: <87cyz1qwtd.fsf@wireframe> (raw)
In-Reply-To: <87mtfe1svx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
retitle 54978 add support for utsushi to sane-backends
thanks
On 2022-05-18, Ludovic Courtès wrote:
> "joaog.bastos" <joaog.bastos@protonmail.ch> skribis:
>
>> From 9743540edfd9e87b7f8fc0057f9fb5acc6bd7917 Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?Jo=C3=A3o=20Gabriel?= <joaog.bastos@protonmail.ch>
>> Date: Sat, 16 Apr 2022 18:05:44 -0300
>> Subject: [PATCH] gnu: Add utsushi.
>>
>> * gnu/packages/scanner.scm (utsushi): New variable.
>> (sane-backends)[inputs, arguments]: Add utsushi backend.
>
> I pushed the first part (adding utushi), with minor changes: the license
> is ‘gpl3+’ (because source file headers say “or any later version”), ran
> ‘guix style’.
>
> Unfortunately the second part with have to wait a little longer due to
> the large number of packages that depend on sane-backends:
>
> --8<---------------cut here---------------start------------->8---
> $ guix refresh -l sane-backends
> Building the following 1337 packages would ensure 2416 dependent packages are rebuilt: […]
> --8<---------------cut here---------------end--------------->8---
When reviewing weather this bug was completed, it would appear that this
second part for sane-backends was never finished...
Retitling appropriately.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-09-01 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 0:31 [bug#54978] [PATCH] gnu: Add utsushi joaog.bastos via Guix-patches via
2022-05-18 20:35 ` Ludovic Courtès
2023-09-01 23:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyz1qwtd.fsf@wireframe \
--to=vagrant@debian.org \
--cc=54978@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=joaog.bastos@protonmail.ch \
--cc=ludo@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.