public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Elfyn McBratney <beu@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Moving the updated apache and associated ebuilds back into package.mask
Date: Sat, 16 Apr 2005 06:56:34 +0100	[thread overview]
Message-ID: <200504160656.43452@zippy.emcb.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

Hi Folks,

As I'm sure many of you will know, the updated apache and associated ebuilds 
(so-called apache refresh) have caused a number of problems since coming out 
of package.mask and going into testing.  As a result, we have a number of 
packages that simply do not function with the updated apache ebuilds, 
rendering testing (on the apache side of things) broken.

Currently, we have at least two (possibly three) weeks worth of work to do 
before we can mark things stable, so these breakages will likely exist until 
then.

A number of people have suggested putting these updated ebuilds back into 
package.mask, or lessening the impact of the upgrade from current stable 
apache to the new ~arch apache.  So, I would like to solicit advice from the 
developer community as to how we can rectify this.

The way I see it, we have three options:
 - package.mask (downgrades for those early adopters)
 - keep the same layout (/etc/apache2/conf, etc.) and wait until 2.2 is out to
   change it
 - have the newer apache ebuilds migrate from old-style to new-style config
   (very hard to do, but possible)

Personally, I'm for package.masking, heh.  Let the flames commence.

Best,
Elfyn

-- 
Elfyn McBratney                                     http://beu.merseine.nu/
beu/irc.freenode.net                            http://dev.gentoo.org/~beu/
+------------O.o--------------------- http://dev.gentoo.org/~beu/pubkey.asc

PGP Key ID: 0x69DF17AD
PGP Key Fingerprint:
  DBD3 B756 ED58 B1B4 47B9  B3BD 8D41 E597 69DF 17AD

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-04-16  5:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16  5:56 Elfyn McBratney [this message]
2005-04-16  6:10 ` [gentoo-dev] Moving the updated apache and associated ebuilds back into package.mask Lance Albertson
2005-04-16 12:38 ` Paul Varner
2005-04-19 19:31   ` Paul de Vrieze
2005-04-19 19:45     ` Elfyn McBratney
2005-04-19 20:51       ` Paul de Vrieze
2005-04-20  7:36         ` Christian Parpart
2005-04-20  8:59           ` Paul de Vrieze
2005-04-20 15:25             ` Christian Parpart
2005-04-21 13:13               ` Paul de Vrieze
2005-04-20 12:14           ` Lance Albertson
2005-04-20 15:22             ` Christian Parpart
2005-04-20 15:35               ` Lance Albertson
2005-04-20 22:38             ` Donnie Berkholz
2005-04-16 13:18 ` [gentoo-dev] " Duncan
2005-04-20 16:39 ` [gentoo-dev] " Francesco Riosa

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=200504160656.43452@zippy.emcb.local \
    --to=beu@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