From: Jeremy Olexa <darkside@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-lang/python: ChangeLog python-3.1.2_p20100801.ebuild python-2.7_p20100801.ebuild python-2.6.5_p20100801.ebuild
Date: Mon, 02 Aug 2010 21:37:34 -0500 [thread overview]
Message-ID: <b3498aab8ba1e3964ea1b89a56f1df3a@localhost> (raw)
In-Reply-To: <20100803014148.AE3932CE15@corvid.gentoo.org>
> Modified: ChangeLog
> Removed: python-3.1.2_p20100801.ebuild
> python-2.7_p20100801.ebuild
> python-2.6.5_p20100801.ebuild
> Log:
> remove the backported versions; they're autogenerated, obviously
> not tested for 2.6 (bug 330937, breaking portage for anyone runing
> unstable python at time of commit), and have been the source of a
> shitload of other rather odd bugs till identification of what was
> occuring (bug 330667). ignoring a PDEPEND.bad for 3.1.2-r3 for
> >=app-admin/python-updater-0.8 also to get these removed
> + -python-2.6.5_p20100801.ebuild, -python-2.7_p20100801.ebuild,
> + -python-3.1.2_p20100801.ebuild:
> + Remove untested versions, one of which flat out breaks emerge (bug
> 330937).
> + These should not be re-added without going through devrel/qa.
Hello fellow developers,
There is quite an issue with python here that I want a wider audience
to be aware of because it did affect our users. Especially ~arch users
that were trying to avoid python-3. The intent of this email is purely
FYI.
(You can find a fix on the mentioned bug, if you are wondering)
-Jeremy
parent reply other threads:[~2010-08-03 2:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100803014148.AE3932CE15@corvid.gentoo.org>]
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=b3498aab8ba1e3964ea1b89a56f1df3a@localhost \
--to=darkside@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