I've been talking to Paul and various other folks about investigating
the use of some of the new tools that are out there these days (atomic,
docker, containers in general, even cloud really) in Fedora
I'd like to schedule a brainstorming session next week sometime for
interested parties to get together and talk about this area and how we
might be able to use some of the new tools in our infrastructure.
In this session we will discuss what absolute requirements we have for
production and non production and nice to haves and such. Also,
hopefully we can decide on something to use as a pilot so we can make
something and see what the actual problems are.
I've created a whenisgood for this:
If you are interested, please fill out your name, timezone and when you
can meet. This meeting will take place on IRC, channel to be announced
when we have a time. :)
Hello everybody my name is Adrian Alves, my fas account is alvesadrian
you can check my background on fedora at my wiki page:
and my sponsor at infra is threebean in irc, thanks to him for all the help
I am Esteban, Fedora Ambassador for Paraguay, and contributing to the
translation team L10n (trans_es) and team leader of trans_GN. I would like
to bring to the team, in professional work and 12 years as a Sysadmin linux.
*Esteban A. Ruiz Diaz*
ownCloud Insider / VOIPSA THREAT TAXONOMY / Fedora L10N Project
GPG KeyID = 6EAA05D0
fingerprint = 824B C711 B9F9 D5FA 025A 86F4 00A8 ADE1 6EAA 05D0
I just cut and pushed a new anitya release: 0.5.0
Here is its changelog:
* Tue May 05 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.5.0-1
- Update to 0.5.0
- Adjust the default regex to ignore .asc in filename
- Adjust php backends and fix unit-tests
- Fix link to the regex documentation
- Use vcr to mock out all http stuff in the tests (Ralph Bean)
- Fix mapping of a project on an existing package
- Invert the project name and SF name in the SourceForge backend.
The last point means that tomorrow I will have to go through the projects that
failed to update , filter their log for sourceforge and adjust as needed.
Feel free to join if you feel like :)
Good morning everyone,
Yesterday I have been working with Luke to set-up the elections for the talks
for Flock 2015. This morning when I tried to see if everything was fine, I ran
into a bug due to our use (for the first time) of the simplified range voting.
This has been fixed, and put into a new release: 2.5.3
Here is its changelog:
* Tue May 05 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.5.3-1
- Update to 2.5.3
- Fix the simplified range voting
I have been playing with it in stg and it seems to behave as expected, so I
updated prod as well and tested the flock election (not voting per say but the
step just before), and it seems to be fine as well.
So we can turn-on the election flock-2015 whenever we want.
There was recently a discussion on the Fedora Rel-Eng list as the
result of a Project Planning workflow. As this was discussed
further in irc it was decided that this is likely a conversation that
should be had across more Fedora groups to see if there's a solution
that we would all like to utilize. If we can all agree on a workflow
and utility we'll hopefully remove the potential for duplicating
efforts or requesting multiple solutions to the same problem be hosted
by the Infrastructure team. In an attempt to not cross-post I am
duplicating this post on the rel-eng, qa, infrastructure, docs,
buildsys, and env-and-stacks mailing lists. I would like to request
that if there are any discussions around this, please rely to the
rel-eng list so we can consolidate the discussion.
All interested parties please fill out the following WhenIsGood so
that we can find a meeting time to discuss this.
 - https://lists.fedoraproject.org/pipermail/rel-eng/2015-April/019806.html
I just cut a new release of MirrorManager2: 0.0.9
Here is its changelog:
* Mon May 04 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.0.9-1
- Update to 0.0.9
- Include and install alembic files
- Try explicit garbage collection in the crawler (Adrian Reber)
- Use defined timeout also for HTTP/FTP connections (Adrian Reber)
- Add documentation about the crawler (Adrian Reber)
- Also add a /var/run directory for the backend (Adrian Reber)
- Add fedmenu integration
- Add new utility script to be used to create the fedora-install-X repositories
- Added last-sync script as mm2_last-sync (Adrian Reber)
It's happily running in stg and prod.
More testers welcome as always :)
My name is Sattar Feizollahi, I'm a System and Database administrator,
specifically, on Linux and IBM DB2 platform.
I have just joined to this group for improving my knowledge of both Linux
Is there a way to opt a package out of the automatic scratch build? I don't see any
toggle in Anitya or pkgdb.
There are cases where this will always fail so putting builds through is a waste of
Example: Wine will never work. On a new release it relies on a version-matching
patchset that is only generated about 24-48 hours after a wine release.