From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-web-user@lists.gentoo.org
Subject: [gentoo-dev] Release: webapp-config v1.11 - call for testers
Date: Mon, 30 May 2005 22:11:43 +0100 [thread overview]
Message-ID: <1117487503.8160.25.camel@mogheiden.gnqs.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hi,
I've just released webapp-config v1.11 into the Portage tree. It
contains fixes for all the problems reported since September (well, the
ones I've managed to reproduce), as well as recent security problems
discovered by the Gentoo Security Audit Team.
It's currently marked ~arch, as it needs wider testing before I'm happy
to mark it stable. All (constructive) feedback gratefully received.
I've also removed webapp-config v1.10-r14 from the tree, as it causes
bug #92388. If you're running off the stable tree, you might see
Portage downgrade your webapp-config to v1.10-r12.
Best regards,
Stu
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-05-30 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 21:11 Stuart Herbert [this message]
2005-11-06 11:21 ` [gentoo-dev] Release: webapp-config v1.11 - call for testers Kevin
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=1117487503.8160.25.camel@mogheiden.gnqs.org \
--to=stuart@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-web-user@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