public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PSA: 13.0 profiles will be removed in a week
Date: Wed, 19 Jun 2019 15:29:33 -0400	[thread overview]
Message-ID: <0bb3d563-6f2f-dc3f-a749-c554f29dc0d5@gentoo.org> (raw)
In-Reply-To: <20190619081941.246392c0@sf>

On 6/19/19 3:19 AM, Sergei Trofimovich wrote:
> 
> This is now tracked as https://bugs.gentoo.org/688342. I hope to get
> at least some followup there.
> 

When I try to look at that bug, it says I'm not authorized.  I'm
concerned about two remaining mips profiles (uclibc and musl) which I'm
working to migrate to 17.0.  I don't think that the removal of the 13.0
profiles will affect them, but I'd like to know.

The reason this is taking so long is 1) mips is a ~arch profile so
there's a lot of blockers and 2) my mips equipment is slow.

--Tony

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA


  reply	other threads:[~2019-06-19 19:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 20:51 [gentoo-dev] PSA: 13.0 profiles will be removed in a week Sergei Trofimovich
2019-06-10  8:18 ` Sergei Trofimovich
2019-06-10 13:28   ` Brian Evans
2019-06-10 17:53     ` Sergei Trofimovich
2019-06-16  9:13       ` Sergei Trofimovich
2019-06-19  7:19         ` Sergei Trofimovich
2019-06-19 19:29           ` Anthony G. Basile [this message]
2019-06-21  6:54             ` Sergei Trofimovich
2019-06-21  8:25               ` Anthony G. Basile
2019-06-21 13:17               ` Michał Górny
2019-06-29  8:49                 ` Sergei Trofimovich

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=0bb3d563-6f2f-dc3f-a749-c554f29dc0d5@gentoo.org \
    --to=blueness@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