From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unmasking db 4.6
Date: Fri, 25 Apr 2008 17:56:06 +0200 [thread overview]
Message-ID: <1209138966.5378.1.camel@ip6-localhost> (raw)
In-Reply-To: <43389.192.168.2.159.1209125934.squirrel@www.aei-tech.com>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Fri, 2008-04-25 at 08:18 -0400, Caleb Tennis wrote:
> Does anyone have any objections to unmasking db 4.6.21? It's been in portage now
> for a long time, but was quickly masked when some packages had some issues with it.
> The only remaining package that has an issue that I'm aware of is openldap, and I've
> submitted a patch that makes openldap just use a lower installed db version.
>
> Any other packages that need looked at, or does anyone else have thoughts or
> objections?
Most likely it will cause problems for XEmacs, which will probably be
easy to solve with some configure script tweaking. I've put testing it
on my todo list.
Kind regards,
Hans
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-04-25 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 12:18 [gentoo-dev] Unmasking db 4.6 Caleb Tennis
2008-04-25 15:56 ` Hans de Graaff [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=1209138966.5378.1.camel@ip6-localhost \
--to=graaff@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