From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: net-misc/zsync destiny?
Date: Mon, 25 Feb 2008 22:30:25 -0600 [thread overview]
Message-ID: <fq04m6$20h$1@ger.gmane.org> (raw)
In-Reply-To: <m23arhxflq.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
Diego 'Flameeyes' Pettenò wrote:
> I was just looking around in package.mask to see if I forgot to get rid
> of something, and I've noticed that zsync is currently masked because it
> contains an internal _vulnerable_ copy of zlib.
>
> It is currently maintainer-needed, so I don't see anybody actually
> fixing it to use system zlib anytime soon.
>
> Any reason why it isn't simply lastrited unless someone wants to
> maintain it? Treecleaners?
https://bugs.gentoo.org/show_bug.cgi?id=208660
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwindows @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-02-26 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 14:42 [gentoo-dev] net-misc/zsync destiny? Diego 'Flameeyes' Pettenò
2008-02-26 4:30 ` Ryan Hill [this message]
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='fq04m6$20h$1@ger.gmane.org' \
--to=dirtyepic@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