public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Joshua Kinard <kumba@gentoo.org>
Subject: Re: [gentoo-dev] keywording ~sys-libs/glibc-2.26
Date: Sun, 12 Nov 2017 21:32:43 +0100	[thread overview]
Message-ID: <2142395.cnhFrAXS4J@pinacolada> (raw)
In-Reply-To: <d2a2f288-0b87-99ac-1e51-cb419e91eca5@gentoo.org>

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

Am Sonntag, 12. November 2017, 20:53:15 CET schrieb Joshua Kinard:
> 
> I take it Python was fixed to handle this? 
>

Yes, newest ~arch in all python slots is fixed.

(That was the main blocker for keywording.)

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

      reply	other threads:[~2017-11-12 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 16:49 [gentoo-dev] keywording ~sys-libs/glibc-2.26 Andreas K. Huettel
2017-11-12 14:21 ` Andreas K. Huettel
2017-11-12 19:53 ` Joshua Kinard
2017-11-12 20:32   ` Andreas K. Huettel [this message]

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=2142395.cnhFrAXS4J@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=kumba@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