Re: Freeze break: don't send fedmsgs for "private" lists

On Tue, 26 Apr 2016 01:07:41 +0200 Pierre-Yves Chibon wrote: > On Mon, Apr 25, 2016 at 01:37:58PM -0600, Kevin Fenzi wrote: > > Greetings. > > > > Right now we send fedmsgs for most lists. There's a small few lists > > that we don't want to send any messages for as they

Re: Freeze break: don't send fedmsgs for "private" lists

On Mon, Apr 25, 2016 at 01:37:58PM -0600, Kevin Fenzi wrote: > Greetings. > > Right now we send fedmsgs for most lists. There's a small few lists > that we don't want to send any messages for as they might have > sensitive items discussed on them. > > There's pretty much no way I can think of

Re: Freeze break: don't send fedmsgs for "private" lists

>> This is already on the bus anyway. > > Yes, but we don't want to _also_ create a new fedmsg for each mailing > list post. In addition to each pkgdb fedmsg, each scm commit fedmsg, > etc, etc. > > The patch doesn't change this, if you look up it's already been the > only thing in this mailing

Re: Freeze break: don't send fedmsgs for "private" lists

On Mon, 25 Apr 2016 19:46:23 + Patrick Uiterwijk wrote: > On Mon, Apr 25, 2016 at 7:37 PM, Kevin Fenzi wrote: > > Greetings. > > > > Right now we send fedmsgs for most lists. There's a small few lists > > that we don't want to send any messages for as

Re: Freeze break: don't send fedmsgs for "private" lists

On Mon, Apr 25, 2016 at 7:37 PM, Kevin Fenzi wrote: > Greetings. > > Right now we send fedmsgs for most lists. There's a small few lists > that we don't want to send any messages for as they might have > sensitive items discussed on them. > > There's pretty much no way I can

Freeze break: don't send fedmsgs for "private" lists

Greetings. Right now we send fedmsgs for most lists. There's a small few lists that we don't want to send any messages for as they might have sensitive items discussed on them. There's pretty much no way I can think of to tell this trait from mailman (we have 'advertised', but thats not at all

Re: Freeze break: codecs.fedoraproject.org

On Mon, Apr 25, 2016 at 7:03 PM, Kevin Fenzi wrote: > Greetings. > > Last week I setup codecs.stg.fedoraproject.org for testing and I think > everything there is looking good. > > I'd like to push it in production too. > > This will involve: > > - adding dns for

Freeze break: codecs.fedoraproject.org

Greetings. Last week I setup codecs.stg.fedoraproject.org for testing and I think everything there is looking good. I'd like to push it in production too. This will involve: - adding dns for codecs.fedoraproject.org (pointing to proxies). - populating /srv/web/codecs.fedoraproject.org/

Re: Freeze break: Run fedmsg-relay on pagure

+1 kevin pgpzgUAGa50Pp.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Freeze break: Run fedmsg-relay on pagure

Greetings, This morning while investigating a bug in pagure's fedmsg git hook, Patrick and I found out that fedmsg-relay isn't being run on pagure, while it should. This patch makes sure it will: From 60c4b52dba7c82c42626726bd47bbb463b4fd015 Mon Sep 17 00:00:00 2001 From: Pierre-Yves Chibon

Pagure 1.2 -> 2.x git URL breakage

Good Morning everyone, Something that was just realized this morning is that the url to pull/push to some of pagure's repositories have been broken by the upgrade to 2.0 This only concerns the repos: - docs - requests - tickets of *forks* This means, pushing/pulling from these three repos, of a