From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>, 30785@debbugs.gnu.org
Subject: bug#30785: Man pages truncated, repeated
Date: Wed, 16 Jan 2019 23:32:12 +0100 [thread overview]
Message-ID: <875zuotes3.fsf@gnu.org> (raw)
In-Reply-To: <20190116205728.616a0b7b@scratchpost.org> (Danny Milosavljevic's message of "Wed, 16 Jan 2019 20:57:28 +0100")
Hello!
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> Apparently, man-db has groff-minimal as a regular input, so I guess we are lucky.
> So we could adapt groff-minimal only if we wanted to.
>
> But that would mean that even after that, the "groff" package would still
> contain a memory corruption bug in preconv - which is arguably a security
> problem. Should we use grafts instead?
Though in practice we don’t do much with ‘groff’ itself, unless users
explicitly install it and use it, right? I’m leaning towards fixing it
in ‘core-updates’.
> From adc9e7940b54e467732ec923c6a3fcec810dce48 Mon Sep 17 00:00:00 2001
> From: Danny Milosavljevic <dannym@scratchpost.org>
> Date: Wed, 16 Jan 2019 15:00:04 +0100
> Subject: [PATCH] gnu: groff-minimal: Disable relocatability.
> Tags: patch
>
> * gnu/packages/groff.scm (groff-minimal)[arguments]<#:phases>
> [disable-relocatability]: New phase.
Please add the “Fixes” line in the log. Otherwise LGTM (I like the
description of the bug ;-)).
Thanks!
Ludo’.
next prev parent reply other threads:[~2019-01-16 22:33 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 21:24 bug#30785: Man pages truncated, repeated Tobias Geerinckx-Rice
2018-03-13 21:34 ` Ludovic Courtès
2018-03-13 22:01 ` Tobias Geerinckx-Rice
2018-03-14 13:22 ` Ludovic Courtès
2018-03-14 13:43 ` Andreas Enge
2018-03-15 0:40 ` Marius Bakke
2018-05-05 21:40 ` Marius Bakke
2018-05-06 13:53 ` Marius Bakke
2018-05-06 22:06 ` Marius Bakke
2018-05-05 1:31 ` Vagrant Cascadian
2018-08-20 10:32 ` Pierre Neidhardt
2019-01-13 16:09 ` Pierre Neidhardt
2019-01-13 16:15 ` Pierre Neidhardt
2019-01-13 17:00 ` Ludovic Courtès
2019-01-13 17:31 ` Pierre Neidhardt
2019-01-13 17:43 ` Pierre Neidhardt
2019-01-13 20:27 ` Ludovic Courtès
2019-01-13 20:37 ` Pierre Neidhardt
2019-01-14 8:36 ` Ludovic Courtès
2019-01-14 8:49 ` Pierre Neidhardt
2019-01-14 10:19 ` Pierre Neidhardt
2019-01-14 10:59 ` Gábor Boskovits
2019-01-14 15:06 ` Pierre Neidhardt
2019-01-14 16:10 ` Ludovic Courtès
2019-01-14 16:24 ` Pierre Neidhardt
2019-01-14 16:42 ` Danny Milosavljevic
2019-01-14 16:57 ` Pierre Neidhardt
2019-01-14 17:46 ` Danny Milosavljevic
2019-01-14 17:48 ` Danny Milosavljevic
2019-01-14 17:50 ` Danny Milosavljevic
2019-01-14 18:19 ` Pierre Neidhardt
2019-01-14 20:27 ` Ludovic Courtès
2019-01-14 21:42 ` Danny Milosavljevic
2019-01-14 21:59 ` Pierre Neidhardt
2019-01-14 22:14 ` Danny Milosavljevic
2019-01-14 22:39 ` Pierre Neidhardt
2019-01-15 12:29 ` Ludovic Courtès
2019-01-16 10:01 ` Pierre Neidhardt
2019-01-16 10:56 ` Danny Milosavljevic
2019-01-16 13:02 ` Pierre Neidhardt
2019-01-16 14:17 ` Danny Milosavljevic
2019-01-16 17:39 ` Pierre Neidhardt
2019-01-16 18:12 ` Efraim Flashner
2019-01-16 18:18 ` Pierre Neidhardt
2019-01-16 19:57 ` Danny Milosavljevic
2019-01-16 22:32 ` Ludovic Courtès [this message]
2019-01-16 22:45 ` Danny Milosavljevic
2019-01-17 7:31 ` Pierre Neidhardt
2019-01-17 8:43 ` Ludovic Courtès
2019-01-17 9:39 ` Pierre Neidhardt
2019-01-17 9:42 ` Pierre Neidhardt
2019-01-17 11:32 ` Pierre Neidhardt
2019-11-28 0:13 ` Marius Bakke
2019-01-17 9:10 ` Danny Milosavljevic
2019-01-17 8:33 ` Ludovic Courtès
2019-01-17 8:41 ` Pierre Neidhardt
2021-04-22 18:53 ` G. Branden Robinson
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=875zuotes3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30785@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=mail@ambrevar.xyz \
/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).