public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: P Levine <plevine457@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] removal of bopm before hopm is in tree
Date: Sun, 28 Aug 2016 12:45:19 -0400	[thread overview]
Message-ID: <CADX8ZBKyt17A6ZUK-b+jQrRWBJ5enHvbcTDwQ=d68fJkNumgKA@mail.gmail.com> (raw)
In-Reply-To: <9cae4789-033f-0dbb-6b73-8bb6d811c9a8@gentoo.org>

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

From the dev mailing list:

# Pacho Ramos <pacho@gentoo.org> (21 Aug 2016)
# Dead for a long time in favour of hopm, bug #473754.
# Removal in a month.
net-misc/bopm

On Sun, Aug 28, 2016 at 2:40 AM, Daniel Campbell <zlg@gentoo.org> wrote:

> On 08/25/2016 07:29 PM, Raymond Jennings wrote:
> > I still use bopm, and it built fine last time I emerged it.
> >
> > If hopm isn't in the tree yet, why was bopm still pmasked for removal?
> >
> > Reason for asking is I'm curious about removal procedures.  I was under
> > the impression that replacement packages get added to the tree before
> > their obsolete predecessors get pmasked for booting out.
> >
> > And if that's not the case, should it be?
> That's a good question, best answered by the developer who chose to have
> the package removed.
>
> --
> Daniel Campbell - Gentoo Developer
> OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
> fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
>
>

[-- Attachment #2: Type: text/html, Size: 2014 bytes --]

      reply	other threads:[~2016-08-28 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  2:29 [gentoo-user] removal of bopm before hopm is in tree Raymond Jennings
2016-08-26 13:43 ` Michael Mol
2016-08-30 22:18   ` Raymond Jennings
2016-08-30 22:26     ` Raymond Jennings
2016-08-28  6:40 ` Daniel Campbell
2016-08-28 16:45   ` P Levine [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='CADX8ZBKyt17A6ZUK-b+jQrRWBJ5enHvbcTDwQ=d68fJkNumgKA@mail.gmail.com' \
    --to=plevine457@gmail.com \
    --cc=gentoo-user@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