The infrastructure team will be having it's weekly meeting tomorrow,
2013-12-12 at 19:00 UTC in #fedora-meeting on the freenode network.
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic Upcoming Tasks/Items
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
-----BEGIN PGP SIGNED MESSAGE-----
as an emergency fix I bumped the cpus on the koji boxes to 16 each from
6 and increased the memory to 16G from 10G. this was due to the systems
being highly stressed after changes last week to the ssl certs used. we
moved from 2048 bit certs and md5 hashing to 4096 bit certs and sha256
hashing. which resulted in an increase in cpu from about 60% to 100% so
while the change has been done id like a couple of acks please.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----
We are currently seeing mirrorlist crashing on ibiblio03 every couple of
hours. This seems to be due to something with the boxes network card and
its virtual guests. Due to the fact we have a release coming up we would
like this to be more stable when final comes.
Steps to be done:
1) Edit ansible/inventory/host_vars/mirrorlist-ibiblio.fedoraproject.org
2) Nuke ibiblio03 copy of mirrorlist
3) Reboot ibiblio03 so other guests feel good about themselves again
4) Build new mirrorlist on either ibiblio02 or ibiblio01
Stephen J Smoogen.
Hi, I just joined the group. I a developer (Python, HTML5 & CSS)
like to give a little contribution to the Fedora project.
My IRC handle is "jaimico88"
I'm have a little experience with development,
and know some Python. I really want to learn more
about python, Fedora Infrastructure and maybe something new, most of
all: I want to meet developers who are best than me and learn with them.
I can spend 3~6 hours weak and honestly I do not know where I can start
to work. Please, if some one have a advice, please.
bugzilla.redhat.com has rolled out support for subcomponents in their
for more info
I suspect we will have some packages that will want to take advantage
of these. I know the kernel maintainers have expressed interest in it.
In their case, they want to be able to put bugs (or have them just
filed in) subcomponents with different owner/cc lists.
So, I'd like to collect questions and gather information from
maintainers on what they would use this for and get FESCo to look at
the policy issues before we implement anything.
Off the top of my head:
- Who can use subcomponents? Any package? Packages that are acked by
FESCo or some other body?
- Who manages the subcomponents point of contact and cc? maintainers of
the primary component, or should the subcomponents have different
- pkgdb2 is close to a early release, do we want to try and add support
for subcomponents before we release it? Or just push it later in a
update/point release? In any case we might think about how to make
implementing things easier now even if we don't implement anything
- If we don't implement now, is there some hacky way we can still do
things for a limited number of components? Like say the kernel?
- We will need to modify our sync to bugzilla scripts to handle
subcomponents. Not sure how much work this will be. ;(
Other thoughts or ideas?
Working on Copr, I want to replace/add one line in file. I spent more
then hour trying various things, but I'm out of ideas.
What I'm trying to do is:
self.conn.module_name = "lineinfile"
self.conn.module_args = "dest=/etc/mock/%s.cfg
line=\"config_opts['chroot_setup_cmd'] = 'install @build %s'\"
regexp=\"^.*chroot_setup_cmd.*$\"" % (self.chroot, self.buildroot_pkgs)
Which in yaml language should be (with placeholders expanded):
- name: putting scl-utils-build into minimal buildroot of fedora-19-i386
line="config_opts['chroot_setup_cmd'] = 'install @build
I tried several things - among all:
- change regexp
- do not use regexp at all as that should put $line at the end of
file, which would work as well
- use command module with sed, but there is too much of escaping and
it is unreadable
Can somebody advise me what should be correct form to replace or add
that line to mock config please?
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
So, at todays fesco meeting there was some discussion about coprs.
In particular some folks want to be able to ship copr repo files in the
main Fedora repository. This would allow users to easily install
software from there without having to discover how to enable it.
However, copr packages are not signed or mirrored currently.
So, this brings up thoughts around if we can somehow sign them, and how
we could mirror them, or even if we want to go down this road at all.
(as it seems like not a use case copr's was designed for anyhow).
1. Do we even want to persue this?
2. If so, do we have any ideas how signing copr packages could work?
3. Mirroring doesn't seem like it would be that hard, just rsync off
the repos and push them out in our regular mirroring system. Could be a
fair bit of churn tho, and there's no set schedule, so we would have to
decide on frequency, etc.
4. If coprs moves to being inside koji, could we at that point have a
better time with these needs?
5. Perhaps we could propose some kind if pergatory type setup between
coprs (experemental, just builds, may set your house on fire, may
update incompatibly every day) and fedora repository packages (with all
the updates guidelines, reviews, etc).
Possibly related to this: I wonder if copr could grow a 'meta repo'
that has all the repodata of all existing coprs. Then you could just
enable one thing and be able to install any coprs?