Can't login to fedora.zanata.org
by Martin Kolman
Hi,
it looks like loging to the Fedora Zanata translation service instance no longer works
When I go to Fedora Zanata (https://fedora.zanata.org) and click to "login",
nothing happens - no FAS loging page shows up as it used to before.
Tried in both Firefox, Chrome and private mode, always the same. Also have seen some
others having the same issue.
In case this is not the proper channel to reaching the people taking care of
the Fedora Zanata instance, then please let me know which is the correct one as
it seems to be rather unclear at the moment.
Best Wishes
Martin Kolman
5 years
[PATCH] bodhi-backend: Add zchunk support to updates and updates-testing repositories
by Jonathan Dieter
This re-adds zchunk support for the updates and updates-testing repositories
for both rpms and modularity.
Zchunk metadata was turned off due to a broken version of librepo that made it
out to stable, but a fixed version has been pushed and FESCo has decided[1] to
go ahead and turn this back on.
1: https://pagure.io/fesco/issue/2116
Signed-off-by: Jonathan Dieter <jdieter(a)gmail.com>
---
roles/bodhi2/backend/templates/pungi.module.conf.j2 | 3 +++
roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 3 +++
2 files changed, 6 insertions(+)
diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2
index 43c6a7e5f..b5bb0c1fb 100644
--- a/roles/bodhi2/backend/templates/pungi.module.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.module.conf.j2
@@ -61,6 +61,9 @@ greedy_method = 'build'
createrepo_c = True
createrepo_checksum = 'sha256'
createrepo_deltas = False
+[% if release.version_int >= 30 %]
+createrepo_extra_args = ['--zck', '--zck-dict-dir=/usr/share/fedora-repo-zdicts/f[[ release.version_int ]]']
+[% endif %]
#jigdo
create_jigdo = False
diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
index 8d9e9a3f2..020736aee 100644
--- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
+++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2
@@ -66,6 +66,9 @@ createrepo_deltas = [
('^Everything$', {'*': True})
]
createrepo_database = True
+[% if release.version_int >= 30 %]
+createrepo_extra_args = ['--zck', '--zck-dict-dir=/usr/share/fedora-repo-zdicts/f[[ release.version_int ]]']
+[% endif %]
# CHECKSUMS
media_checksums = ['sha256']
--
2.21.0
5 years
[PATCH] tag2distrepo: also regen f*-coreos-continuous repos
by Jonathan Lebon
We want to be able to get automatically regenerated yum repos whenever
we build into the continuous tags. This will be used by the Fedora
CoreOS team for building and testing.
See https://pagure.io/releng/issue/8165 for more details.
---
roles/bodhi2/backend/templates/tag2distrepo.py.j2 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/roles/bodhi2/backend/templates/tag2distrepo.py.j2
b/roles/bodhi2/backend/templates/tag2distrepo.py.j2
index 943e543b9..1a845d089 100644
--- a/roles/bodhi2/backend/templates/tag2distrepo.py.j2
+++ b/roles/bodhi2/backend/templates/tag2distrepo.py.j2
@@ -24,6 +24,8 @@ config = {
'epel6-infra-stg': ['47dd8ef9'],
'epel7-infra': ['47dd8ef9'],
'epel7-infra-stg': ['47dd8ef9'],
+ 'f29-coreos-continuous': [],
+ 'f30-coreos-continuous': [],
}
}
}
--
2.20.1
5 years
Greenwave released
by Giulia Naponiello
Hello,
I've released the new version of Greenwave in prod.
The new version is 1.1.0.
Here are the release notes:
* Retrieve only latest results when verbose=True: that's a decision API
performance improvement and refactor.
* PackageSpecificBuild is obsolete, not deprecated: fixing the error
message, to be sure to not create confusion.
* Add the option to use git archive to retrieve a gating.yaml file from
dist-git: this is to address when the dist-git deployment doesn't have a UI
that updates in real-time, such as cgit.
* Consider scenario when selecting latest results for the decision making
process.
* Add tests for subject type bodhi_update.
* Return warning if there is no parent policy for a remote rule policy:
users may mistakenly configure a parent policy with a decision_context and
a gating.yaml file with another decision_context. This can cause
unnecessary delays for the user. In order to avoid this, add a check in the
validate_gating_yaml endpoint.
* Bug fix: Greenwave was publishing a message even when the decision didn't
change.
* Greenwave now allows messaging also with fedora-messaging.
* Remove duplicated waivers and results from response: when asked for a
decision, Greenwave returns multiple results or waivers when verbose==True
in case the same subject gets repeated.
* Add several other tests and improved dev environment.
Let me know if you have questions or doubts!
Cheers
Giulia
5 years
Meeting for 2019-04-11 Agenda
by Stephen John Smoogen
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2019-04-11 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
which can be edited for the agenda (see:
https://fedoraproject.org/wiki/Gobby )
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 (2019-04-11)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk
mkonecny abompard bowlofeggs
= 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:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
= 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 Beta Freeze Is Finished.
#info Final Freeze Starts on 2019-04-16
#info Taskotron major upgrade planned for 2019-04-09
#info Another blogpost about release-monitoring.org was published
https://communityblog.fedoraproject.org/stories-from-the-amazing-world-of...
- mkonecny
#info update reboots happened this week
#info uploads of packages to look-aside cache were broken for some people.
#info git.centos.org/src.fedoraproject.org progressing
= 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 Oncall
#info https://fedoraproject.org/wiki/Infrastructure/Oncall
#info smooge is on call from 2019-04-04 -> 2019-04-11
#info nirik is on call from 2019-04-11 -> 2019-04-18
#info ????? is on call from 2019-04-18 -> 2019-04-25
#info ????? is on call from 2019-04-25 -> 2019-05-02
#info Summary of last week: (from relrod )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
https://pagure.io/fedora-infrastructure/issue/7704
Go thru each ticket one by one
#topic Priorities for next week?
#info please put tickets or projects needing to be focused on here
=====
Put all topics for discussion under here
=====
= 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
improvement,
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.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
5 years