public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: stable-bot is down. Temporary? Forever? Can we have a contacts page for it?
Date: Mon, 7 Oct 2019 22:27:23 +1100	[thread overview]
Message-ID: <22ab5980-ba41-bbd6-819c-7ffd211a61b7@gentoo.org> (raw)
In-Reply-To: <CAEdQ38GZDRs=m_WE8wxXmdXmtuRNPZD14p42h3w72_=R=yeHQQ@mail.gmail.com>

Sorry for the late reply here.

On 10/3/19 1:43 AM, Matt Turner wrote:
> On Thu, Sep 26, 2019 at 12:29 AM Sergei Trofimovich <slyfox@gentoo.org> wrote:
>>
>> I noticed that stable-bot stopped marking bugs as verified for stbilization.
>> Example:
>>      https://bugs.gentoo.org/695252
>>
>> 1. Is it gone forever and arch teams should stop relying on it's presence?

There was some temporary, unintentional breakage which regrettably I did 
not notice. Thanks to whissi for pinging me.

>> 2. If not can the owner tweak it?

stable-bot has since returned to normal service.

>> 3. Can we have a wiki page that describes the setup and who to send reports to?
>>     Doc would be useful to run it locally, send bugs/enhancements, post current
>>     status if it's known to be broken.

I agree, this is long overdue.

> It looks like it is working now, but I think we really should know a few things:
> 
>     (1) Who maintains it

That is me.

>     (2) Where the code is
Due to slacking on my part, the code currently just lives on my server. 
The intention has always been to clean it up and publish it with the 
client at https://github.com/kensington/bugbot.

>     (3) and perhaps what happened to bring it down
vixie-cron got last-rited and I neglected to configure its placement 
correctly.


  parent reply	other threads:[~2019-10-07 11:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26  7:28 [gentoo-dev] stable-bot is down. Temporary? Forever? Can we have a contacts page for it? Sergei Trofimovich
2019-10-02 15:43 ` Matt Turner
2019-10-03 19:32   ` Robin H. Johnson
2019-10-04  3:09     ` bman
2019-10-04 11:30       ` Mike Gilbert
2019-10-07 11:29     ` [gentoo-dev] " Michael Palimaka
2019-10-07 19:11       ` Robin H. Johnson
2019-10-07 20:21         ` Andreas K. Huettel
2019-10-08 11:57           ` Michael Palimaka
2019-10-08 12:22             ` Rich Freeman
2019-10-08 15:46             ` Alec Warner
2019-10-07 11:27   ` Michael Palimaka [this message]
2019-12-24 12:19     ` Sergei Trofimovich
2019-12-06 16:15 ` [gentoo-dev] " Matt Turner

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=22ab5980-ba41-bbd6-819c-7ffd211a61b7@gentoo.org \
    --to=kensington@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