fedora/linux/development/25
by Adrian Reber
For some time now mirrormanager points to fedora/linux/releases/25 for all
the categories 'Fedora Linux' and 'Fedora Secondary Arches'.
The files at fedora/linux/development/25 could now be deleted. At least
from MirrorManager's point of view.
Adrian
7 years, 3 months
Weekly Koji Infra Tag Report
by Nobody
This is a list of packages in the various infrastructure koji tags
Please check and make sure there are not any that can be removed/dropped
epel6-infra
(no matching packages)
epel7-infra
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
freeipa-ktutils epel7-infra puiterwijk
glusterfs epel7-infra kevin
fedmsg-beaker-repoupdate epel7-infra tflink
fedocal epel7-infra pingou
python-robosignatory epel7-infra puiterwijk
pdc-updater epel7-infra ralph
blockerbugs epel7-infra tflink
mirrormanager2 epel7-infra puiterwijk
f23-infra
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
libphutil, f23-infra tflink
arcanist, f23-infra tflink
phabricator f23-infra tflink
phabricator-extension-ipsilonauth f23-infra tflink
libphutil f23-infra tflink
arcanist f23-infra tflink
f24-infra
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
mediawiki-openid f24-infra kevin
phabricator-extension-oauth f24-infra tflink
python-twill f24-infra codeblock
stickynotes2modernpaste f24-infra codeblock
python-flask-testing f24-infra codeblock
modern-paste f24-infra codeblock
mediawiki-skin-fedora f24-infra puiterwijk
mediawiki-FedoraBadges f24-infra kevin
basset f24-infra puiterwijk
phabricator f24-infra tflink
mediawiki-Lockdown f24-infra kevin
libphutil f24-infra tflink
arcanist f24-infra tflink
mediawiki-RSS f24-infra kevin
mirrormanager2 f24-infra puiterwijk
f25-infra
Package Tag Extra Arches Owner
----------------------- ----------------------- ---------------- ---------------
fas f25-infra kevin
mediawiki-openid f25-infra kevin
arcanist f25-infra tflink
python-twill f25-infra codeblock
phabricator f25-infra tflink
stickynotes2modernpaste f25-infra codeblock
python-flask-testing f25-infra codeblock
arcanist, f25-infra tflink
modern-paste f25-infra codeblock
python-coveralls f25-infra codeblock
mediawiki-skin-fedora f25-infra kevin
phabricator-extension-ipsilonauth f25-infra tflink
mediawiki-FedoraBadges f25-infra kevin
libphutil, f25-infra tflink
basset f25-infra puiterwijk
mdapi f25-infra pingou
mediawiki-Lockdown f25-infra kevin
mediawiki-RSS f25-infra kevin
plus-plus-service f25-infra pingou
libphutil f25-infra tflink
7 years, 3 months
Spacewalk: so long and thanks for all the fish!
by Grant Gainey
Hey folks,
The Spacewalk project started its open-source life on fedorahosted.org in 2008. We moved the code-base to Github at the community's request in 2013, and as of today, we've moved our (large) Trac wiki to Github as well.
Just wanted to take a moment to thank everyone on the infrastructure team(s). It can be a tedious, painful job, and nobody notices 99% of what you do unless something breaks - but it's so, so important. Thanks much for all the work y'all have done, and continue to do, keeping our communities online!
Stop by at
https://github.com/spacewalkproject/spacewalk/wiki
and visit sometime :)
G
(PS - for anyone else who needs to migrate from Trac to Github-Markdown - feel free to make use of the tool I wrote to ease the pain somewhat:
https://github.com/ggainey/tracwiki2githubwiki
Open issues there if/when/as you find problems...)
--
Grant Gainey
Principal Software Engineer, Red Hat Satellite
7 years, 3 months
Dreams and Plans and Ideas for 2017
by Kevin Fenzi
Greetings and happy new year to everyone.
I'd like to divide this email up into 2 parts:
Firstly, what all do we want to get done in the next 2 months?
The end of Feb is the end of the Red Hat Fiscal year and many of us
have goals tied to that timeframe. :)
For myself:
* Finish migrating things off fedorahosted so we can retire it at the
end of Feb. I need to make a survey of how many things are left, etc.
* Get mirrorlist containers all deployed and running (With a bunch of
help from Patrick). We have it working in staging, just need to get
things setup to build using OSBS and deploy in production. This
should allow us to avoid outages even more from mirrorlists service.
* Get database replication setup finished in stg and hopefully setup in
production. We still need to sort out how to get db schema upgrades
fully working for people, but otherwise hopefully this should allow
us much less scheduled outages. I am waiting on BDR 2.0 to be
released (with postgresql 9.6 support, so this might slip out some).
* Get s390 merged into the main/primary koji. This is waiting on
firewall/networking changes.
What things are others trying to get done? I know there was a plan for
fas3, I know Ricky is working on modernpaste replacing sticky-notes,
what else is on the short term timeline?
Secondly, there's the rest of the year. It's not too early to dream
about what we want to try and get done in the coming year. :)
For myself:
* I'd like to try and move askbot to current upstream code. This likely
will require us to try and move it to python3 and django1.8. I am
pretty sure this will require some python savvy coding action. :)
* I'd love to try and do a FAD sometime this coming year if we can
identify something that we could tackle and solve/complete over a few
days.
* I'd like to do some more apprentice work days to get apprentices more
involved. We should try and brainstorm some things we could do on
such work days.
* I'm sure to think of more things as time goes on. ;)
What does everyone else have on their radar?
kevin
7 years, 3 months
Plan for tomorrow's Fedora Infrastructure meeting - 2017-01-12
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2017-01-12 at 18:00 UTC in #fedora-meeting 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.
kevin
--
This shared document is for the next fedora infrastructure meeting.
= 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 (2017-01-12)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions
= Status / information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info FESCo/Council/FOSCo voting is running - go vote! - everyone
#info pgbdr01 had a full disk, fixed up and back in sync - kevin
#info arm builders updated and rebooted - kevin
#info arm03-packager/qa instances reinstalled to f25 - kevin
#info
= 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)
#topic
= Apprentice office hours =
#topic Apprentice Open office hours
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 improvement,
etc. Whoever would like to do this, just add the info 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 3 months
[release] fedocal: 0.15.1
by Pierre-Yves Chibon
Good Morning Everyone,
New release means new bug-fix release, so I just cut and released: 0.15.1
Here is the changelog:
* Wed Jan 11 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.15.1-1
- Update to 0.15.1
- Fix double time-zone conversion
It was affecting the meeting details making things a little odd.
It was hotfixed yesterday and this release makes things square :)
Happy planning,
Pierre
7 years, 3 months
[release] pagure-importer : 2.0.1
by Clement Verna
Hi all,
A new release of pagure-importer is available from COPR (https://copr.fedorainfracloud.org/coprs/cverna/pagure-importer/)
Note that pagure-importer has moved to python 3.
$ sudo dnf copr enable cverna/pagure-importer $ sudo dnf install python3-pgimport
And it contains the following PR :
2.0.1
=======
- Fix urlparse and encoding for python3
- Fix attachment name encoding error (Athos Ribeiro)
- Fix broken links in group projects attachment (Athos Ribeiro)
- Add support for pagure custom close status
- Fix typo, modify code to let length of repo_issues (Vivek Anand)
- Move pagure-importer to python3
- Add support for github issue assignee (Vivek Anand)
Many Thanks,
Clement
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com
7 years, 3 months
January status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
https://fedoraproject.org/wiki/Infrastructure_Apprentice
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
to more?
3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. What is your favorite gui application?
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Note that we recently revamped the getting started and other pages.
Please do take a minute to re-read them and let me know if they are
more clear or need further adjustments.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!
kevin
7 years, 3 months
