From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: missing patch for texlive-bin (e77412362f)
Date: Wed, 02 Feb 2022 23:45:33 +0100 [thread overview]
Message-ID: <8882b1ca1c76f50b9787629e2a0ef36b37a05bfb.camel@telenet.be> (raw)
In-Reply-To: <875ypx9kki.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
zimoun schreef op wo 02-02-2022 om 19:42 [+0100]:
> [...]
>
> This asks two questions:
>
> 1. How to get now this patch? Someone? Or is it lost forever?
> 2. How to preserve such patches? Other said, are they part of the
> Disarchive machinery? For now, some patches are probably missed by
> sources.json and thus not ingested by SWH. Or, do we systematically
> include them in 'gnu/packages/patches' (which appears to me the easiest
> and the robustest) and as proposed for instance by patch#49820 [1]?
>
My suggestion: in these cases, we can do
(origin
(patches
(list (file-append
(origin (uri (git-reference
(url "https://git.archlinux.org/...")
(commit "deadbeef...")))
(method git-fetch)
(sha256 "...")))
"/.../pdftex-poppler0.76.patch")))).
It's a bit long-winded, but SWH should be happy with this.
This doesn't retroactively unbreak old commits though ...
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-02 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 18:42 missing patch for texlive-bin (e77412362f) zimoun
2022-02-02 22:45 ` Maxime Devos [this message]
2022-02-02 22:54 ` Maxime Devos
2022-02-02 22:57 ` Maxime Devos
2022-02-02 23:20 ` zimoun
2022-02-03 15:46 ` Timothy Sample
2022-02-03 18:51 ` zimoun
2022-02-05 4:20 ` Timothy Sample
2022-02-05 13:43 ` zimoun
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=8882b1ca1c76f50b9787629e2a0ef36b37a05bfb.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).