Re: [release] pkgdb2 1.21

2014-12-11 Thread Pierre-Yves Chibon
On Fri, Nov 21, 2014 at 05:33:16PM +0100, Pierre-Yves Chibon wrote:
 Hi all,
 
 I have just released and pushed to staging a new version of pkgdb2, here is 
 the
 changelog:
 
 * Fri Nov 21 2014 Pierre-Yves Chibon pin...@pingoured.fr - 1.21-1
 - Update to 1.21
 - DB optimization: do not use LIKE in queries where there is no '%'
 - Update the layout of the user list page
 - Add flag to set/update the monitoring flag on packages. This flag tells
   the-new-hotness whether the maintainers are interested in getting bugzilla
   tickets about updates available on their package (updates being monitored
   via anitya: release-monitoring.org)
 - Clean(er) logic to mark the fields mandatory in the forms
 - Fix indentation in the mail_logging module
 - Branch orphaned packages as well as we branch for new releases (Subho-bcrec)
 - Auto select packagers search in packager details page. (Ratnadeep Debnath)
 - Obsolete all ACLs on a package that is retired
 - Nicer docstring and API documentation by using textwrap.dedent()
 - Add a `former_poc` argument to the orphan API endpoint allowing to restrict
   the orphan to only the package of a certain packager
 - Add the former_poc keyword argument to api_acl_reassign, same principle as
   when orphaning a package
 - DB optimization: optimize the API endpoint returning the packager's ACLs
 - Include the monitoring state in the GET API. (Ralph Bean)
 - Include the api_groups and api_monitored in the API documentation
 - Update the update_package_info script to include other releases than rawhide
 
 The biggest change being likely the introduction of the monitoring flag to
 integrate pkgdb, anitya and the-new-hotness.

Prod has been updated to run this new version :)

Pierre
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

Re: [release] pkgdb2 1.21

2014-12-11 Thread Vít Ondruch
Dne 11.12.2014 v 13:44 Pierre-Yves Chibon napsal(a):
 On Fri, Nov 21, 2014 at 05:33:16PM +0100, Pierre-Yves Chibon wrote:
 - Add flag to set/update the monitoring flag on packages. This flag tells
   the-new-hotness whether the maintainers are interested in getting bugzilla
   tickets about updates available on their package (updates being monitored
   via anitya: release-monitoring.org)

Hmmm, this is probably not self explanatory enough. Looking at Ruby [1],
is it enabled or not? I am afraid to click on the kye or the off button
:) And how is the relation to the wiki page [2]. Since all rubygem-
packages were monitored automatically up to now, what is their state.


Vít



[1] https://admin.fedoraproject.org/pkgdb/package/ruby/
[2] https://fedoraproject.org/wiki/Upstream_release_monitoring

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

Re: [release] pkgdb2 1.21

2014-12-11 Thread Pierre-Yves Chibon
On Thu, Dec 11, 2014 at 04:24:39PM +0100, Vít Ondruch wrote:
 Dne 11.12.2014 v 13:44 Pierre-Yves Chibon napsal(a):
  On Fri, Nov 21, 2014 at 05:33:16PM +0100, Pierre-Yves Chibon wrote:
  - Add flag to set/update the monitoring flag on packages. This flag tells
the-new-hotness whether the maintainers are interested in getting 
  bugzilla
tickets about updates available on their package (updates being monitored
via anitya: release-monitoring.org)
 
 Hmmm, this is probably not self explanatory enough. Looking at Ruby [1],
 is it enabled or not? I am afraid to click on the kye or the off button
 :) And how is the relation to the wiki page [2]. Since all rubygem-
 packages were monitored automatically up to now, what is their state.

This is clearly not documented enough and I have probably been too quickly to
push this update to prod (I wanted it out to get the improved API out).

So looking at Ruby, it is currently off (I have to run the script to sync the
packages from the wiki to pkgdb2).

The idea is:
- Having the upstream project on anitya
- Having the upstream project mapped onto a Fedora package in anitya
- Having the monitoring flag `on` on pkgdb
- the-new-hotness will monitor for new releases announced by anitya
  - it will create a bugzilla ticket announcing the new release (so far we
reproduce the behavior of cnucnu, the current upstream monitoring solution)
  - it will download the sources and the spec file
  - it will adjust the spec file to bump version and fix release
  - it will do a scratch build using the new sources and adjusted spec
  - it will report on the bugzilla ticket if the scratch build was successful or
not.

As the-new-hotness isn't running yet, changing the flag will not have any effect
yet.
When we push the-new-hotness in production, we will retire cnucnu and adjust the
wiki page to provide more information on how these three systems work together.

I hope this answers your question and sorry for the confusion.

Cheers,
Pierre
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

mailing list mail stuck for over a week?

2014-12-11 Thread Matthew Miller
any idea what's going on here?

- Forwarded message from Rex Dieter rdie...@fedoraproject.org -

 Return-Path: famsco-boun...@lists.fedoraproject.org
 Delivered-To: mattdm@[...]
 Received: from bastion.fedoraproject.org (bastion01.fedoraproject.org
   [209.132.181.2])
   by disco.[...] (Postfix) with ESMTP id 9805A801C6
   for mattdm@[...]; Thu, 11 Dec 2014 10:20:28 -0500 (EST)
 Received: by bastion01.phx2.fedoraproject.org (Postfix)
   id 31B7D6087E03; Thu, 11 Dec 2014 15:20:28 + (UTC)
 Delivered-To: mat...@fedoraproject.org
 Received: from lists.fedoraproject.org (collab03.vpn.fedoraproject.org
   [192.168.1.70])
   by bastion01.phx2.fedoraproject.org (Postfix) with ESMTP id
   149B860879F7;
   Thu, 11 Dec 2014 15:20:28 + (UTC)
 Received: by lists.fedoraproject.org (Postfix, from userid 503)
   id D22B780E55; Thu, 11 Dec 2014 15:20:27 + (UTC)
 Received: from collab03.fedoraproject.org (localhost [127.0.0.1])
   by lists.fedoraproject.org (Postfix) with ESMTP id B5CBA806DA;
   Thu, 11 Dec 2014 15:20:25 + (UTC)
 X-Original-To: fam...@lists.fedoraproject.org
 Delivered-To: fam...@lists.fedoraproject.org
 Received: by lists.fedoraproject.org (Postfix, from userid 503)
   id B554380A5B; Tue,  2 Dec 2014 16:54:59 + (UTC)
 Received: from smtp-mm-ib01.fedoraproject.org (vm4.fedora.ibiblio.org
   [152.19.134.143])
   by lists.fedoraproject.org (Postfix) with ESMTP id 1881180A62
   for fam...@lists.fedoraproject.org;
   Tue,  2 Dec 2014 16:54:58 + (UTC)
 Received: from mailforward3.unl.edu (mailforward3.unl.edu [129.93.2.93])
   by smtp-mm-ib01.fedoraproject.org (Postfix) with ESMTP id 780C86CA
   for fam...@lists.fedoraproject.org;
   Tue,  2 Dec 2014 16:54:57 + (UTC)
 Received: from localhost.localdomain (ip174-74-10-163.om.om.cox.net
   [174.74.10.163]) (authenticated bits=0)
   by mailforward3.unl.edu (8.14.4/8.14.4) with ESMTP id sB2GstPf013792
   (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
   for fam...@lists.fedoraproject.org; Tue, 2 Dec 2014 10:54:56 -0600
 Message-ID: 547deedf.7090...@fedoraproject.org
 Date: Tue, 02 Dec 2014 10:54:55 -0600
 From: Rex Dieter rdie...@fedoraproject.org
 User-Agent: Mozilla/5.0 (X11; Linux x86_64;
   rv:31.0) Gecko/20100101 Thunderbird/31.2.0
 MIME-Version: 1.0
 To: fam...@lists.fedoraproject.org
 X-Mailman-Approved-At: Thu, 11 Dec 2014 15:20:25 +
 Subject: [FAmSCo] kde-sig request for f21 kde live media
 X-BeenThere: fam...@lists.fedoraproject.org
 X-Mailman-Version: 2.1.12
 Precedence: list
 Reply-To: Fedora Ambassadors Steering Committee
   fam...@lists.fedoraproject.org
 List-Id: Fedora Ambassadors Steering Committee
   famsco.lists.fedoraproject.org
 List-Unsubscribe: https://admin.fedoraproject.org/mailman/options/famsco,
   mailto:famsco-requ...@lists.fedoraproject.org?subject=unsubscribe
 List-Archive: http://lists.fedoraproject.org/pipermail/famsco/
 List-Post: mailto:fam...@lists.fedoraproject.org
 List-Help: mailto:famsco-requ...@lists.fedoraproject.org?subject=help
 List-Subscribe: https://admin.fedoraproject.org/mailman/listinfo/famsco,
   mailto:famsco-requ...@lists.fedoraproject.org?subject=subscribe
 Content-Transfer-Encoding: base64
 Content-Type: text/plain; charset=utf-8; Format=flowed
 Sender: famsco-boun...@lists.fedoraproject.org
 Errors-To: famsco-boun...@lists.fedoraproject.org

-- 
Matthew Miller
mat...@fedoraproject.org
Fedora Project Leader
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

Re: mailing list mail stuck for over a week?

2014-12-11 Thread Kevin Fenzi
On Thu, 11 Dec 2014 11:46:00 -0500
Matthew Miller mat...@fedoraproject.org wrote:

 any idea what's going on here?
 
 - Forwarded message from Rex Dieter rdie...@fedoraproject.org
 -
...snip...
  X-Mailman-Approved-At: Thu, 11 Dec 2014 15:20:25 +

It was in the moderation queue until today. 

So, perhaps the user was not subscribed, or otherwise moderated. 

kevin



pgp7NZNgedgsz.pgp
Description: OpenPGP digital signature
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

Re: [release] pkgdb2 1.21

2014-12-11 Thread Pierre-Yves Chibon
On Thu, Dec 11, 2014 at 04:24:39PM +0100, Vít Ondruch wrote:
 Dne 11.12.2014 v 13:44 Pierre-Yves Chibon napsal(a):
  On Fri, Nov 21, 2014 at 05:33:16PM +0100, Pierre-Yves Chibon wrote:
  - Add flag to set/update the monitoring flag on packages. This flag tells
the-new-hotness whether the maintainers are interested in getting 
  bugzilla
tickets about updates available on their package (updates being monitored
via anitya: release-monitoring.org)
 
 Hmmm, this is probably not self explanatory enough. Looking at Ruby [1],
 is it enabled or not? I am afraid to click on the kye or the off button
 :) And how is the relation to the wiki page [2]. Since all rubygem-
 packages were monitored automatically up to now, what is their state.

The script that syncs the data from the wiki to pkgdb finished to run, so now
Ruby is marked as being monitored :)

Pierre
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

Summary/Minutes from today's Fedora Infrastructure meeting (2014-12-11)

2014-12-11 Thread Kevin Fenzi

#fedora-meeting: Infrastructure (2014-12-11)



Meeting started by nirik at 18:00:36 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-12-11/infrastructure.2014-12-11-18.00.log.html
.



Meeting summary
---
* aloha  (nirik, 18:00:37)

* New folks introductions and Apprentice tasks  (nirik, 18:02:05)

* FAD recap  (nirik, 18:06:48)
  * got lots of details about mirrormanager 1 from Matt Domsch  (nirik,
18:07:31)
  * got Mirrormanager 2 pretty much all implemented  (nirik, 18:08:38)
  * got some test coverage added to Mirrormanager 2  (nirik, 18:08:50)
  * got Mirrormanager2 mostly added to ansible and deployed in staging
(nirik, 18:09:09)
  * LINK: https://admin.stg.fedoraproject.org/mirrormanager2/   (pingou,
18:09:19)
  * targeting mid january for production deployment. Might do some kind
of phased approach with mirrorlist vs the rest.  (nirik, 18:12:01)
  * ansible migrations took up the rest of the FAD time.  (nirik,
18:13:01)
  * puiterwijk got nameservers in ansible and all redeployed with it.
(nirik, 18:13:34)
  * various other playbooks written, just need to finish things up.
(nirik, 18:14:13)
  * down to 57 machines in puppet.  (nirik, 18:14:21)

* Applications status / discussion  (nirik, 18:15:38)
  * puiterwijk got single login in badges, and spec for single logout
(more to come)  (nirik, 18:17:00)
  * proxy playbooks are about 75% done. TODO list is in
playbooks/groups/proxies-reverseproxy.yml  (nirik, 18:20:05)
  * hopefully roll out a bodhi2 instance in stg asap and see what all we
need for production  (nirik, 18:27:35)

* Sysadmin status / discussion  (nirik, 18:28:28)
  * monday outage - updates/reboots  (nirik, 18:29:59)
  * tuesday outage - database server migrations  (nirik, 18:30:08)
  * wed outage - more ansible/rhel7 migrations  (nirik, 18:30:19)

* nagios recap  (nirik, 18:35:31)

* Upcoming Tasks/Items  (nirik, 18:37:28)
  * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/
(nirik, 18:37:28)
  * we will meet next week as normal, but not the following 2 weeks
(nirik, 18:38:34)
  * ACTION: nirik to send list of ansible work we still need done to
list.  (nirik, 18:40:33)

* Open Floor  (nirik, 18:40:39)
  * talk to puiterwijk if you want single login on your fedora app
(nirik, 18:41:43)

Meeting ended at 18:43:04 UTC.




Action Items

* nirik to send list of ansible work we still need done to list.




Action Items, by person
---
* nirik
  * nirik to send list of ansible work we still need done to list.
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* nirik (102)
* pingou (20)
* puiterwijk (16)
* lmacken (13)
* wallison (11)
* tflink (9)
* threebean (8)
* zodbot (5)
* adimania (3)
* mirek-hm (3)
* Khaytsus (1)
* bwood09 (1)
* danielbruno (1)
* relrod (1)
* abadger1999 (0)
* smooge (0)
* mdomsch (0)
* dgilmore (0

--
18:00:36 nirik #startmeeting Infrastructure (2014-12-11)
18:00:37 zodbot Meeting started Thu Dec 11 18:00:36 2014 UTC.  The chair is 
nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:37 zodbot Useful Commands: #action #agreed #halp #info #idea #link 
#topic.
18:00:37 nirik #meetingname infrastructure
18:00:37 zodbot The meeting name has been set to 'infrastructure'
18:00:37 nirik #topic aloha
18:00:37 nirik #chair smooge relrod nirik abadger1999 lmacken dgilmore 
mdomsch threebean pingou puiterwijk
18:00:37 zodbot Current chairs: abadger1999 dgilmore lmacken mdomsch nirik 
pingou puiterwijk relrod smooge threebean
18:00:42 * lmacken 
18:00:42 * threebean waves
18:00:45 * puiterwijk is here
18:00:48 * danielbruno is here
18:00:52 * mirek-hm is here
18:01:00 * adimania is here
18:01:03 * pingou 
18:01:09 * bwood09 here
18:02:05 nirik #topic New folks introductions and Apprentice tasks
18:02:20 nirik any new folks like to provide a short introduction of 
themselves?
18:02:28 nirik or apprentices with questions or comments ?
18:02:48 wallison Guess I'll go...
18:03:23 wallison My name is Will, I'm still working through the Primary 
Steps of Getting Started
18:03:33 nirik cool. welcome wallison
18:03:44 wallison I'm not an IT pro, but have been using Linux at home for at 
least 15 years
18:03:53 nirik are you primarilly interested in sysadmin type things, or 
application development, or both?
18:04:00 wallison and want to contribute (finally) to the FOSS community
18:04:10 wallison Fedora seems to make that easy!
18:04:15 threebean :)
18:04:18 nirik we try. ;)
18:04:24 wallison nirik sysadmin stuff
18:04:40 wallison i'd like to do that as a second career after college
18:04:46 nirik cool. See me after the meeting over in #fedora-admin and I can 
get you added to our apprentice group...
18:04:49 wallison threebean: nice vids by the way
18:04:58 nirik and you can look