From: "Paul A. Patience" <paul@apatience.com>
To: Kaz Kylheku <kaz@kylheku.com>
Cc: Guillaume Le Vaillant <glv@posteo.net>, 49517@debbugs.gnu.org
Subject: [bug#49517] [PATCH] gnu: txr: Build documentation and update to 265.
Date: Sun, 18 Jul 2021 21:28:58 +0000 [thread overview]
Message-ID: <jQ1k4B4YWFlW-eDeV_xh7RMYvSc6-z8A8Bhb10wmDzXvNfnRPJ__gAZ25piSnz_wgzPB-pux6m4Aj5aRK7AxeH1P3QjPx8ZPka6QEUpAh50=@apatience.com> (raw)
In-Reply-To: <598802eda2050f063d01d802edfead99@mail.kylheku.com>
On Sunday, July 18th, 2021 at 16:27, Kaz Kylheku <kaz@kylheku.com> wrote:
> Either Ubuntu has a different upstream for these tools, or else they
> have some patches (which would be worth stealing instead of repeating
> the work).
>
> Moreover, if Ubuntu has patches for this, it might be getting them from
> Debian.
I know Debian is making great efforts to obtain reproducible builds [1],
and in fact if you look at the first message of the bug report I
previously linked [2], they mention that they have been using some
custom patches to get Ghostscript to produce reproducible output
(on Debian).
In fact, we can find some information about Debian's Ghostscript patch
here [3], though unfortunately the link to the patch is dead.
(There is also more information about reproducible builds here [4].)
Best regards,
Paul
[1]: https://isdebianreproducibleyet.com/
[2]: https://bugs.ghostscript.com/show_bug.cgi?id=696765
[3]: https://wiki.debian.org/ReproducibleBuilds/PdfGeneratedByGhostscript
[4]: https://wiki.debian.org/ReproducibleBuilds/Howto
next prev parent reply other threads:[~2021-07-18 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 0:37 [bug#49517] [PATCH] gnu: txr: Build documentation and update to 265 Paul A. Patience
2021-07-12 1:01 ` Paul A. Patience
2021-07-13 23:45 ` Paul A. Patience
2021-07-17 9:57 ` Guillaume Le Vaillant
2021-07-17 22:51 ` Kaz Kylheku
2021-07-18 3:43 ` Kaz Kylheku
2021-07-18 10:36 ` Guillaume Le Vaillant
2021-07-18 12:59 ` Paul A. Patience
2021-07-20 9:07 ` bug#49517: " Guillaume Le Vaillant
2021-07-18 20:27 ` [bug#49517] " Kaz Kylheku
2021-07-18 21:28 ` Paul A. Patience [this message]
2021-07-19 12:08 ` Guillaume Le Vaillant
2021-07-19 21:31 ` Kaz Kylheku
2021-07-20 9:18 ` Guillaume Le Vaillant
2021-07-19 3:23 ` Kaz Kylheku
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='jQ1k4B4YWFlW-eDeV_xh7RMYvSc6-z8A8Bhb10wmDzXvNfnRPJ__gAZ25piSnz_wgzPB-pux6m4Aj5aRK7AxeH1P3QjPx8ZPka6QEUpAh50=@apatience.com' \
--to=paul@apatience.com \
--cc=49517@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=kaz@kylheku.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 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.