From: Wout Mertens <wmertens@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Apache security hole and ebuild
Date: Thu, 20 Jun 2002 13:46:59 +0200 (CEST) [thread overview]
Message-ID: <Pine.GSO.4.44.0206201343330.19554-100000@oaktree.cisco.com> (raw)
In-Reply-To: <20020619221317.GB2151@wasd.dk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1108 bytes --]
Hey Bjarke,
On Thu, 20 Jun 2002, Bjarke [iso-8859-1] Sørensen wrote:
> On Wed, Jun 19, 2002 at 09:44:38AM -0400, Grant Goodyear wrote:
> > Actually, all of the changes are documented. Take a look
> > at /usr/portage/net-www/apache/ChangeLog.
>
> Ohh, yeah.
>
> Just not when you already worked arround this and have this
> "complicated/large site". Sorry I missed the announce that something
> vital was done to apache. Good thing I havn't blindly upgraded.
Which is very good, as a "complicated/large site"-admin, you need to test
things before you make them happen. If you tweak stuff in a package, you
can expect it to break updates...
> Too many people have problems with it. But maybe we all expected
> something more than a note in a changelog for such a change.
But that is exactly what Changelog is for, notifying the user about what
changed. Although I admit it doesn't have a lot of visibility, we might
want to do something about that, like an option on emerge that shows the
changelogs since your version...
If you have other ideas, please tell us.
Wout.
next prev parent reply other threads:[~2002-06-20 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 11:05 [gentoo-dev] Apache security hole and ebuild Kim Nielsen
2002-06-19 12:39 ` Sloan Poe
2002-06-19 13:44 ` Grant Goodyear
2002-06-19 18:37 ` Doug Goldstein
2002-06-19 19:30 ` Kim Nielsen
2002-06-19 22:13 ` Bjarke Sørensen
2002-06-20 11:46 ` Wout Mertens [this message]
2002-06-20 13:48 ` Bjarke Sørensen
2002-06-20 14:58 ` Jean-Michel Smith
2002-06-21 4:00 ` [gentoo-dev] gperf and gprof Luke Graham
2002-06-21 7:24 ` Luke Graham
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=Pine.GSO.4.44.0206201343330.19554-100000@oaktree.cisco.com \
--to=wmertens@gentoo.org \
--cc=gentoo-dev@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