From: Michael Cummings <mcummings@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Heads up to the arch's - perl module testing bugs on their way (internal QA)
Date: Mon, 14 Mar 2005 05:50:54 -0500 [thread overview]
Message-ID: <1110797454.8422.4.camel@sys947.dtic.mil> (raw)
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
I can't guarantee how fast this will happen, maybe only a few at a time,
but I wanted to give the arch's a heads up that I will be filing "bugs"
for having perl-modules tested and unmasked in response to bug 84744. To
sum it up real quick like for the lazy/browser-shy - we have ebuilds in
dev-perl for perl modules that are also distributed as a part of the
core perl install. The issue is that some of these ebuilds were last
marked as stable for versions that are older than what is provided by
the stable perl ebuild. To avoid this QA nightmare before it becomes
one, I'm going through the tree, making sure all of the ebuilds we
provide that replace core perl modules are up to date, then in my local
repository marking which ones will need to be re-DEP'd to <perl-version.
That's where you come in my exotic architecture friends (exotic being
defined as anything I can't afford to own or house :) ) and the slow,
steady stream of bugs I'm going to be filing. On the up side, if you
have perl installed, in most cases you already have the version of the
module installed too :)
Thanks for your patience and understanding,
Mike
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-03-14 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1110797454.8422.4.camel@sys947.dtic.mil \
--to=mcummings@gentoo.org \
--cc=gentoo-dev@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