From: "Brett Simpson" <simpsonb@hillsboroughcounty.org>
To: <robbat2@gentoo.org>
Cc: <gentoo-dev@gentoo.org>, <pauldv@gentoo.org>
Subject: Re: [gentoo-dev] **HEADS UP** Apache2 + MySQL4 moving to stable status
Date: Sun, 13 Jul 2003 09:32:55 -0400 [thread overview]
Message-ID: <sf112761.093@GroupWise> (raw)
>>> "Robin H.Johnson" <robbat2@gentoo.org> 07/13/03 01:28 AM >>>
> Apache1 with "emerge '=net-www/apache-1*'" and it will not > > conflict with Apache2.
I tried this with
emerge '=net-www/apache-1*' -up apache
and
emerge '=net-www/apache-1*' -p apache
The first one still wanted to upgrade my Apache to 2.0.x while the second wanted to rebuild Apache 1.3.x and then upgrade to 2.0.x.
Until I have a chance to test serveral of my production Gentoo servers on Apache 2.0.x I will need to maintain security updates on Apache 1.3.x for at least several more weeks. Is there another way to do this?
Brett
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-07-13 13:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 13:32 Brett Simpson [this message]
2003-07-13 19:29 ` [gentoo-dev] **HEADS UP** Apache2 + MySQL4 moving to stable status Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2003-07-13 22:01 Brett Simpson
2003-07-13 20:25 Brett Simpson
2003-07-13 20:47 ` Ian Truelsen
2003-07-15 1:30 ` Andrew Cowie
2003-07-15 10:32 ` Dhruba Bandopadhyay
2003-07-15 9:38 ` FRLinux
2003-07-15 10:01 ` Georgi Georgiev
2003-07-15 21:22 ` Robin H.Johnson
2003-07-16 12:10 ` Andrew Cowie
2003-07-16 12:37 ` Chris Gianelloni
2003-07-16 12:48 ` Andrew Cowie
2003-07-16 13:04 ` Chris Gianelloni
2003-07-17 10:37 ` Dhruba Bandopadhyay
2003-07-13 3:47 Brett Simpson
2003-07-13 5:28 ` Robin H.Johnson
2003-07-09 3:12 Donny Davies
2003-07-09 3:51 ` Alvaro Figueroa Cabezas
2003-07-09 19:16 ` Matthew Walker
2003-07-09 7:51 ` Alvaro Figueroa Cabezas
2003-07-09 20:37 ` Paul de Vrieze
2003-07-09 15:23 ` Owen Gunden
2003-07-09 16:13 ` Weeve
2003-07-09 17:15 ` Robin H.Johnson
2003-07-11 0:55 ` Weeve
2003-07-09 19:07 ` Stewart Honsberger
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=sf112761.093@GroupWise \
--to=simpsonb@hillsboroughcounty.org \
--cc=gentoo-dev@gentoo.org \
--cc=pauldv@gentoo.org \
--cc=robbat2@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