From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: amd64-fbsd@gentoo.org
Subject: [gentoo-dev] Re: Last rites: sys-process/vixie-cron
Date: Thu, 20 Sep 2018 09:09:20 -0400 [thread overview]
Message-ID: <20b1ba65-819d-f32d-e5db-e940e7a40539@gentoo.org> (raw)
In-Reply-To: <21fb4372-2782-79da-9d6f-006bffb4cdb1@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 366 bytes --]
On 9/20/2018 5:17 AM, Mikle Kolyada wrote:
> # Mikle Kolyada <zlogene@gentoo.org> (20 Sep 2018)
> # Dead upstream and unmaintained for a long time,
> # has multiple bugs open, use sys-process/cronie
> # instead (the fork). Removal in 30 days.
> sys-process/vixie-cron
>
sys-process/cronie needs to be keyworded ~amd64-fbsd so that CI passes.
Thanks.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
next prev parent reply other threads:[~2018-09-20 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 9:17 [gentoo-dev] Last rites: sys-process/vixie-cron Mikle Kolyada
2018-09-20 13:09 ` Brian Evans [this message]
2018-09-20 21:07 ` Thomas Deutschmann
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=20b1ba65-819d-f32d-e5db-e940e7a40539@gentoo.org \
--to=grknight@gentoo.org \
--cc=amd64-fbsd@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