I want to announce that the Anitya 0.13.2 was deployed on
You can see changelog here
Here is the list of main changes:
- User ID is now visible for user on Settings page - this ID is needed
when user wants to be promoted to admin (just ask on #fedora-apps how to
become an admin of Anitya)
- Most of the github projects has now correct setup
- Documentation links are working again
- UI changes in Project page (versions are now displayed at side, so you
can see whole setting of the project without scrolling down)
- You can now choose how versions of the project will be sorted using
version scheme. Currently you can choose from sorting by Date or by RPM
versioning (NOTE: This could cause some issues in already existing
projects, because every version retrieved before this update is missing
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-10-17 at 14:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2018-10-17)
#chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
(Please use #info <the thing> - your name)
#topic announcements and information
#info tflink is on extended PTO
#info Final Freeze has started 2018-10-09
#info version 0.13.1 of release-monitoring.org deployed in production - mkonecny
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#info relrod is on call from 2018-10-18 -> 2018-10-25
#info smooge is on call from 2018-10-25 -> 2018-11-01
#info ??? is on call from 2018-11-01 -> 2018-11-08
#info Summary of last week: (from smooge )
#topic Tickets discussion
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
= Meeting end stuff =
#topic Open Floor
Stephen J Smoogen.
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 29
Final Release Readiness meeting. This meeting will be held on Thursday,
2018-10-18 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Final
release of Fedora 29. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
View the meeting on Fedocal:
Fedora Program Manager
Can Pete Travis do something about this?
This happens everytime I commit something in ansible.git
-------- Přeposlaná zpráva --------
Předmět: Undelivered Mail Returned to Sender
Datum: Wed, 17 Oct 2018 09:05:52 +0000 (UTC)
Od: Mail Delivery System <MAILER-DAEMON(a)fedoraproject.org>
This is the mail system at host bastion01.phx2.fedoraproject.org.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<me(a)petetravis.com> (expanded from <sysadmin-members(a)fedoraproject.org>): Host
or domain name not found. Name service error for name=petetravis.com
type=A: Host not found
I have been trying to make php7 works on my apache container.
This is my Dockerfile: https://github.com/wagnermarques/Fedora-Dockerfiles/blob/master/apache/Do...
When I access php_info page, I get the logs below:
[Mon Oct 15 18:28:53.444409 2018] [proxy:error] [pid 223:tid 140654374008576] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php-fpm/www.sock (*) failed
[Mon Oct 15 18:28:53.444500 2018] [proxy_fcgi:error] [pid 223:tid 140654374008576] [client 192.168.0.142:36490] AH01079: failed to make connection to backend: httpd-UDS
I suppose that the fastcgi php-fpm deamon is not running... If so, what should I do to start such process in docker container?
Or could someone shed some light about this issue, please?
Good Morning Everyone,
Kevin recently saw that pkgs02 is sending emails on commits again. I have been a
first-hand witness of this myself as well.
I'd like to apply the following PR manually and reload apache/restart
pagure-logcom. It should help figuring out why it's behaving this way.
The corresponding PR is at: https://pagure.io/pagure/pull-request/3907
I would like to do the following:
* Apply the attached ansible diff. This changes things to run the new
'reg' (which just has a 'server' subcommand, not a reg-server binary),
and also fixes varnish to not eat the requests to show more than 100
items from our registry. It also fixes some sync jobs where the flatpak
info would 'disappear' for 10min at a time due to a --delete that
shouldn't have been there.
* Upgrade 'reg' on sundries01.phx2 (prod). I've already tested this
version in staging and it works.
* Run playbooks: sundries, and proxies
The only thing that could affect things much here is the varnish change,
but it's one line and contained to the registry block.
This would make our registry nice and pretty before release.
From: Kevin Fenzi <kevin(a)scrye.com>
This simply installs the ipsilon plugin for fpdc scopes and
restarts it. If there's an issue we can easily remove it to
roll back to where we were.
Signed-off-by: Kevin Fenzi <kevin(a)scrye.com>
roles/ipsilon/tasks/main.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/roles/ipsilon/tasks/main.yml b/roles/ipsilon/tasks/main.yml
index 9bbccbf..ab2f0a7 100644
@@ -50,6 +50,7 @@
+ - fpdc
- reload apache
You are kindly invited to the meeting:
Infra Office Hours on 2018-10-16 from 18:00:00 to 19:00:00 UTC
The meeting will be about:
Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features.