From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30289@debbugs.gnu.org
Subject: [bug#30289] [PATCH] gnu: doxygen: Update to 1.8.14.
Date: Tue, 30 Jan 2018 16:39:26 -0500 [thread overview]
Message-ID: <20180130213926.GB14764@jasmine.lan> (raw)
In-Reply-To: <20180130100718.555f66d6@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On Tue, Jan 30, 2018 at 10:07:18AM +0100, Danny Milosavljevic wrote:
> Hi Leo,
>
> On Mon, 29 Jan 2018 23:14:56 -0500
> Leo Famulari <leo@famulari.name> wrote:
>
> > On Tue, Jan 30, 2018 at 01:14:07AM +0100, Danny Milosavljevic wrote:
> > > * gnu/packages/documentation.scm (doxygen): Update to 1.8.14.
> >
> > Thanks! A lot of packages depend on doxygen so we'll need to do this on
> > the next core-updates cycle, or potentially on a staging cycle before
> > the next core-updates cycle.
> >
> > Can you hold on to the patch and put it in the right place after the
> > current core-updates cycle?
>
> Sure.
>
> For later reference, 1.8.13 has a crash bug
>
> https://bugzilla.gnome.org/show_bug.cgi?id=776791
Hm... if we hit that bug, let's fix it. Until then, I think it's fine,
since doxygen is primarly run within the build chroot.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-30 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 0:14 [bug#30289] [PATCH] gnu: doxygen: Update to 1.8.14 Danny Milosavljevic
2018-01-30 4:14 ` Leo Famulari
2018-01-30 9:07 ` Danny Milosavljevic
2018-01-30 21:39 ` Leo Famulari [this message]
2018-06-22 19:53 ` [bug#30289] " Gábor Boskovits
2018-08-29 21:07 ` bug#30289: " Leo Famulari
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=20180130213926.GB14764@jasmine.lan \
--to=leo@famulari.name \
--cc=30289@debbugs.gnu.org \
--cc=dannym@scratchpost.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.