unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>,
	Timothy Sample <samplet@ngyro.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: missing patch for texlive-bin (e77412362f)
Date: Thu, 3 Feb 2022 00:20:10 +0100	[thread overview]
Message-ID: <CAJ3okZ1wKwLWfzi6mJFE5Y_YDAWCHx1gZSLgXmbUtX_si62+RA@mail.gmail.com> (raw)
In-Reply-To: <0711363a0e331db1e7bf94bc71daad69ba840f99.camel@telenet.be>

Hi Maxime,

Thanks for the pointer.


On Wed, 2 Feb 2022 at 23:57, Maxime Devos <maximedevos@telenet.be> wrote:
>
> zimoun schreef op wo 02-02-2022 om 19:42 [+0100]:
> >  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.
>
> Can we tell SWH to ingest svntogit-packages, in such a way that every
> individual file from every commit can be individually fetched from
> SWH?  If so, then all (historical?) patches in Archlinux would be
> saved.

The request for saving the repo is done; if it is not already in.  See [1].

But the question is if Disarchive dissambles and preserves external
patches.  Timothy?

For instance, the file sources.json ingested by SWH is not doing that
yet, if I remember correctly.


1: <https://archive.softwareheritage.org/save/#requests>


  reply	other threads:[~2022-02-02 23:21 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
2022-02-02 22:54 ` Maxime Devos
2022-02-02 22:57 ` Maxime Devos
2022-02-02 23:20   ` zimoun [this message]
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=CAJ3okZ1wKwLWfzi6mJFE5Y_YDAWCHx1gZSLgXmbUtX_si62+RA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=samplet@ngyro.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).