From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-text/epdfview
Date: Thu, 09 Aug 2012 11:23:02 +0300 [thread overview]
Message-ID: <50237366.8050708@gentoo.org> (raw)
In-Reply-To: <20120809025523.28862.qmail@stuge.se>
On 08/09/2012 05:55 AM, Peter Stuge wrote:
> Samuli Suominen wrote:
>> our mupdf package sucks wrt bugs 407805 and 407807
>
> It's pretty clear that the latter is an upstream problem.
We should patch it to build shared libs, with or without cooperation
from upstream.
> Will you fix it?
Absolutely, I didn't file the bug for nothing. It's there to remind me
until I do.
>
>
> //Peter
>
next prev parent reply other threads:[~2012-08-09 8:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 22:28 [gentoo-dev] Last rites: app-text/epdfview Andreas K. Huettel
2012-08-07 0:10 ` [gentoo-dev] Re: [gentoo-dev-announce] " Andreas K. Huettel
2012-08-07 9:06 ` grozin
2012-08-07 3:00 ` [gentoo-dev] " heroxbd
2012-08-07 7:35 ` Michał Górny
2012-08-07 8:06 ` Cyprien Nicolas
2012-08-07 9:40 ` Samuli Suominen
2012-08-09 2:55 ` Peter Stuge
2012-08-09 8:23 ` Samuli Suominen [this message]
2012-08-09 0:51 ` Walter Dnes
2012-08-09 1:22 ` Peter Stuge
2012-08-09 2:51 ` Walter Dnes
2012-08-09 8:52 ` Luca Barbato
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=50237366.8050708@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox