The infrastructure team will be having its weekly meeting tomorrow,
2020-02-20 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
Please try and review and edit that document before the meeting and we
will use it to have our agenda of
The infrastructure team will be having its weekly meeting tomorrow,
2020-01-23 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
Please try and review and edit that document before the meeting and we
will use it to have our agenda of
On Fri, 2019-10-25 at 15:50 -0400, Neal Gompa wrote:
> a lot of Fedora-specific information isn't
> present.
Though true for the entire packages app, I think this site does do the
one use case I described at a quick glance.
signature.asc
Description: This is a digitally signed message part
On Fri, 2019-10-25 at 14:53 -0400, Neal Gompa wrote:
> It's not a bad feature to have in fedpkg, but it fundamentally does
> not help *other people* discover what we have in the distribution.
Yeah I've discussed this a bit with some people, and I agree. Fedora
*users* might use the packages app
On Fri, 2019-10-25 at 21:00 +0200, Mikolaj Izdebski wrote:
> I am planning to deploy Package Version Matrix in communishift [1].
> Example how it can look like: [2]
>
> [1] https://pagure.io/fedora-infrastructure/issue/8314
> [2] https://koji.kjnet.xyz/kojifiles/versions/
Oh that could be a good
On Fri, 2019-10-25 at 21:47 +0200, Clement Verna wrote:
> https://pkgs.org/ might be a good replacement for that. Does anybody
> have used or is using this website ? Any feedback on it ?
I haven't seen this before, but if it does a good job staying up to
date then it seems like a good replacement
On Thu, 2019-10-24 at 20:12 +0200, Clement Verna wrote:
> The packages app (https://apps.fedoraproject.org/packages/) was
> originally running on RHEL6, I tried to move it to RHEL 7 but they
> were some dependencies missing there so we decided to move it to
> Fedora. I don't remember which
On Fri, 2019-10-25 at 19:04 +0200, Clement Verna wrote:
> I think the main reason why we don't already have it on Pagure is
> that we don't want to be dependent of our own infrastructure to host
> this repo. It currently lives on the batcave01 host which is the box
> we use to deploy our
Greetings!
The packages app is running on Fedora 30, and its dependencies are not
available in Fedora 31+ as I understand it.
This means it has about 7 months before we need to do something about
it, or shut it off.
Do we know if it can run on RHEL 7?
signature.asc
Description: This is a
On Mon, 2019-10-21 at 11:48 -0700, Kevin Fenzi wrote:
> Personally, I am willing to try 1 (will need more +1's for freeze
> break), I don't really like 2 and 3 seems a bit scary, but I guess it
> could be ok until after freeze.
>
> Thoughts?
I think #1 is fine, and we could even bump it to a
On Fri, 2019-10-18 at 09:13 +0200, Adrian Reber wrote:
> Thanks for that recommendation. Can you point me to a place in
> ansible
> where you are using this? For this FBR I would rather not change it
> and
> go with the current solution. The goal is to completely remove the
> conditionals because
I'm a +1 to doing this. The change to production is not too huge, so I
think it's low risk. As I've said elsewhere, I've used this technique
to do backups and analytics before to avoid putting load on production
and it worked well.
I personally think going without backups is a higher risk than
On Wed, 2019-10-16 at 10:50 +0200, Adrian Reber wrote:
> {% if env == "staging" or inventory_hostname ==
> "proxy14.fedoraproject.org" %}
Rather than inlining host names like this, why not use host vars to
define a boolean variable like "enable_cool_new_rust_mirrorlist". Then
you can make that
On Wed, 2019-10-16 at 14:58 -0400, Stephen John Smoogen wrote:
> This was requested by me as we usually get a spike of traffic in the
> 8
> days after a release compared to the rest of the time. This would
> mean
> we would not be able to test the code's viability against load until
> May when we
Greetings!
On Mon, 2019-10-14 at 21:05 +0300, Benson Muite wrote:
> The tool seems useful. I wish there was a high level description of
> the design. Seems like many issues are common with distributed nosql
> databases. Are there any common techniques one can use to have good
> performance?
We
Greetings ya'll,
I spent the last few weeks studying repoSpanner with the goal of
developing a plan to improve its performance. I started by testing its
performance with a few common git operations with a couple repos (our
Infrastructure Ansible repository since it is on the large side, and
Bodhi
On Tue, 2019-09-24 at 16:55 -0400, Randy Barlow wrote:
> On Tue, 2019-09-24 at 15:20 +0200, Petr Bokoc wrote:
> > Sure! You guys are the experts and you know all about what people
> > need to do and how to do it, so it's best if you do most of the
> > actual content writing;
On Tue, 2019-09-24 at 15:20 +0200, Petr Bokoc wrote:
> Sure! You guys are the experts and you know all about what people
> need to do and how to do it, so it's best if you do most of the
> actual content writing; I'm happy to help you with markup, structure
> and that sort of stuff. Some basic
Hey Kevin and Petr (and anyone else on the list who is interested),
I've been talking with Ben Cotton about moving the elections
application into Communishift[0]. We had a few back and forth e-mails,
and it became clear that it would be helpful if we had quality
documentation describing how
Here are the meeting minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-19/infrastructure.2019-09-19-15.00.html
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list --
On Tue, 2019-09-17 at 19:01 -0400, Neal Gompa wrote:
> Out of curiosity, do we know where the bottlenecks are in
> repoSpanner?
> In theory, the architecture of repoSpanner isn't supposed to be too
> different from gitaly, so I'm curious where we're falling down.
I believe it needs a more
to make a throw away
account just to test this.
On Mon, 2019-09-16 at 18:51 -0400, Randy Barlow wrote:
> I pushed the Ansible repository into it. This took a very long time:
> 298m2.157s!
This took 6m44.705s to get to GitLab. However, since I only have 6 Mbps
outbound and the repository is
nirik suggested trying out board.net for the weekly meeting agenda, so
I created a meeting agenda there:
https://board.net/p/fedora-infra
Feel free to add your own material to the agenda. Here is what it looks
like at the time of this writing:
---
title: Infrastructure Meeting template
tags:
+1
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Greetings!
Kevin asked me last week whether we are ready to move our
infrastructure Ansible repository into repospanner. The benefit of
moving it into repospanner is that it is one way to enable us to allow
pull requests into the repository, which I think would be nice.
repospanner seems to work
+1
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
+1
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
+1
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
+1
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
+1
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Tue, 2019-06-18 at 14:06 +, Jeremy Cline wrote:
> the problems we hit were things like not knowing you had to add some
> extra Ansible steps to create your queue in the first place (and then
> asking the obvious question of why you have to repeat yourself in the
> config in Ansible and then
On Mon, 2019-06-17 at 14:02 -0700, Kevin Fenzi wrote:
> Can you clarify what repo you mean here?
> https://pagure.io/fedora-infrastructure/issues ?
> Or ?
Yep, that's the one! The Pagure bug has made it hard to follow that
repo even during normal working schedule, as there are a lot of issues
Notice: I am no longer watching the infrastructure repo, because it
results in a huge volume of mail most of which is not relevant to me,
and I am about to take an extended leave of absence and don't want to
return to thousands of e-mails. However, due to a long-standing Pagure
bug[0], this means
There will be a Bodhi stakeholder's meeting on June 26 at 15:00 UTC in
#fedora-meeting on Freenode.
https://apps.fedoraproject.org/calendar/infrastructure/2019/6/24/#m9545
signature.asc
Description: This is a digitally signed message part
___
On Wed, 2019-05-29 at 11:58 -0400, Josh Boyer wrote:
> Could you make a container image based on F30 that can be run on
> F29/EPEL 7/8? That offers users a way to use the new tool on the OS
> of their choice and avoids you having to write new code or bring back
> a bunch of dependencies to the
On Tue, 2019-05-28 at 20:22 -0600, Orion Poplawski wrote:
> Perhaps this is the source of:
>
> # /etc/cron.hourly/0yum-hourly.cron
> Updateinfo file is not valid XML: '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d1
> 53d7a3e27ff41946f476af5b4-updateinfo.xml.zck',
> mode
On Tue, 2019-05-28 at 17:41 -0400, Dan Čermák wrote:
> I just tried to submit an update via `fedpkg update` but got a
> failure
> via the cli:
> $ fedpkg update
> Could not execute update: Could not generate update request:
> 'anonymous'
> A copy of the filled in template is saved as
On Tue, 2019-05-28 at 20:22 -0600, Orion Poplawski wrote:
> Perhaps this is the source of:
>
> # /etc/cron.hourly/0yum-hourly.cron
> Updateinfo file is not valid XML: '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d1
> 53d7a3e27ff41946f476af5b4-updateinfo.xml.zck',
> mode
Greetings!
I have just deployed Bodhi 4.0.0 to production:
https://bodhi.fedoraproject.org/docs/user/release_notes.html
One known issue has been found[0] so far: after creating an update,
your browser will be redirected to a URL that does not exist. The
update was created, however, and you
On Thu, 2019-05-23 at 22:07 +0100, Jonathan Dieter wrote:
> Unless I'm mistaken, that patch is specific to updateinfo.xml. The
> other metadata in updates and updates-testing is currently zchunked,
> just without a zdict at the moment.
Ah yes, that's correct!
signature.asc
Description: This is
On Thu, 2019-05-23 at 10:33 -0700, Kevin Fenzi wrote:
> Applied. Thanks.
One note: The patch to do zchunking is part of Bodhi 4.0.0, which is
not yet in production; we plan to deploy it on Tuesday.
signature.asc
Description: This is a digitally signed message part
Greetings!
Back in December, I sent out a threat^Wannouncement that I would be
making a lot of backwards incompatible changes to Bodhi in an upcoming
4.0.0 release[0].
I didn't expect it to take this long at the time, but five months later
we finally have a beta built[1] and deployed to
On Mon, 2019-04-29 at 14:49 -0700, Adam Williamson wrote:
> I also find it significant that libdnf still has, so far as I can
> tell,
> absolutely no interface documentation -
> https://github.com/rpm-software-management/libdnf links to "the
> hawkey
> documentation page", which is obviously
On Mon, 2019-04-29 at 21:46 +0200, Daniel Mach wrote:
> I'll discuss the issue with my team and we will reach back to
> you with a solution soon.
Thanks Daniel!
signature.asc
Description: This is a digitally signed message part
___
infrastructure
Also, I cannot find documentation on the new version of hawkey as
distributed with libdnf. Since the change is in Rawhide, I will need to
adjust Bodhi's code[0] so that it works with the new version of hawkey.
Can you advise me about what I should use in place of the cited code
with the new
Hi Pavla,
I noticed today that a backwards incompatible update was pushed to
Fedora 29 stable for libdnf[0]. This breaks Bodhi[1], which uses
hawkey.Repo which was removed in that version. The update notes did not
mention a backwards incompatible API, and in general backwards
incompatible updates
On Tue, 2019-04-16 at 15:35 +0200, Sebastian Wojciechowski wrote:
> The initial plan was to just add some argument to cli "bodhi releases
> create/edit", something like:
>
> >> bodhi releases edit --name F29 --frozen true)
Releases have states - it might be nice to just reuse that machinery
This change is in place now.
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
FEDORA-CONTAINER-2019-3e42a55b54[0] references a container that has
been deleted from the candidate registry. As a result, the compose has
failed. Since the update is locked, it cannot be edited to replace it
with a build that exists. To fix this, I propose to unlock the update
like this:
$ sudo
On Fri, 2019-03-15 at 15:17 +0100, Clement Verna wrote:
> Hi all,
>
> So after setting higher timeout to the openshift route, it seems that
> now we are hitting gunicorn worker default timeout (30s).
>
> The following patch increase this value.
>
> +1s ?
-1 to this too. Now Bodhi's cron job is
On Fri, 2019-03-15 at 12:11 +0100, Clement Verna wrote:
> I would like to increase this timeout to 330 seconds, greenwave will
> timeout after 300 seconds.
I don't think we should do this. Two problems immediately come to mind.
Bodhi still gets timeout errors from Greenwave, because Bodhi will
Thanks for the +1's. This change has been deployed and I've confirmed
that I can push F30 updates between the 3 and 7 day mark.
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list --
Greetings!
The Bodhi frontend container was not rebuilt when the Fedora 30
configurations were added to production.ini. This means that the
frontend is not aware of the policy of 3 days to stable, while the
backend is aware. This means that the backend is adding comments to
updates to tell
On Wed, 2019-03-06 at 14:17 -0800, Kevin Fenzi wrote:
> * add ansible play to copy files from our repo to the filesystem
> * commit all the files you are going to touch.
> * commit in a second commit the changes for the hotfix.
> * push both with a comment about it.
> * run playbook.
* Make sure
On Tue, 2019-02-26 at 20:38 +0100, Clement Verna wrote:
> Should we approach the Council to see if we can get founding to have
> this service hosted by Elastic ?
If we use the service hosted by Elastic that's a nice way to support
development of an open source project with some cold hard cash.
On Wed, 2019-02-27 at 10:48 +0100, Pierre-Yves Chibon wrote:
> We look at Elasticsearch at one point (I believe Aurélien was even
> looking at
> setting up an instance in our cloud) but it came down to two aspects:
> - setting it up is another application to maintain
> - an application we have no
Greetings!
I've scheduled another quarterly Bodhi stakeholder's meeting for March
22 at 15:00 UTC in #fedora-meeting-2. There will be an agenda in Gobby
by March 20. We will talk about what's been going on in Bodhi, and what
is planned future.
Bodhi 3.13.3 is deployed to production, and test gating is enabled
again:
https://bodhi.fedoraproject.org/docs/user/release_notes.html#v3-13-3
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list --
On Fri, 2019-02-15 at 14:46 -0500, Randy Barlow wrote:
> Bodhi 3.13.0 is released and deployed to staging:
>
> https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html
>
> I plan to deploy it to production on Monday.
It was deployed today (hooray), but it had a regression
Bodhi 3.13.0 is released and deployed to staging:
https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html
I plan to deploy it to production on Monday.
signature.asc
Description: This is a digitally signed message part
___
infrastructure
On Sun, 2018-12-16 at 15:43 -0800, Kevin Fenzi wrote:
> I think this might be a good rule of thumb to apply to our commits,
> at
> least in ansible repo. I'm as guilty as the next person on useless
> commits, but I'm gonna try and do better. ;)
I will say that I find the whimsical nature of some
On Fri, 2018-12-14 at 19:02 +, Jonathan Dieter wrote:
> Hey Randy, at the moment the --zck option *only* applies to
> primary.xml, filelists.xml and other.xml. It should be pretty
> straightforward to add it to the others, but I wanted to get those
> three working first.
Cool, sounds good to
On Thu, 2018-12-13 at 22:56 +, Jonathan Dieter wrote:
> The call to createrepo_c or mergerepo_c
> (whichever is run last to generate the final metadata) would need to
> be
> run with the new zchunk arguments:
>
> --zck --zck-dict-dir=/usr/share/fedora-repo-zdicts/f30
Hey Jonathan!
Bodhi
Greetings!
I have planned an IRC meeting for Bodhi stakeholders for Tuesday 2018-
12-18 at 17:00 UTC in #fedora-meeting on Freenode:
https://apps.fedoraproject.org/calendar/infrastructure/2018/12/17/#m9429
Feel free to drop by and say hi!
signature.asc
Description: This is a digitally signed
Bodhi 3.11.1 was released and deployed to production today:
https://bodhi.fedoraproject.org/docs/user/release_notes.html
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list --
Bodhi 3.11.0 is now released:
https://github.com/fedora-infra/bodhi/releases/tag/3.11.0
I plan to deploy it to production on Monday.
signature.asc
Description: This is a digitally signed message part
___
infrastructure mailing list --
Greetings!
bodhi-3.11.0 beta has been deployed to staging:
https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html#v3-11-0
This deployment uses Python 3 only!
signature.asc
Description: This is a digitally signed message part
___
On Wed, 2018-10-31 at 09:22 -0700, Kevin Fenzi wrote:
> With the release of Fedora 29 yesterday, we are out of final freeze.
/me takes off his jacket and puts sunglasses on.
signature.asc
Description: This is a digitally signed message part
___
On Fri, 2018-10-12 at 13:43 +0530, Sinny Kumari wrote:
> Next Fedora Atomic Host TwoWeek release will be based on F29
> stream and same will be followed in future releases.
> So, building F28 AH artifacts during bodhi run is
> not needed.
Shouldn't we wait until Fedora 29 is released to stop
On Wed, 2018-10-10 at 00:17 +, ke...@scrye.com wrote:
> +/usr/bin/pg_dump --exclude-table-data users --exclude-table-data
> tokens --exclude-table-data 'social*' --exclude-table-data sessions
> -C $DB | /usr/bin/pxz -T4 > /backups/$DB-public-$(date +%F).dump.xz
It might be good to add a
Greetings!
I just wrote up a blog post about the recent work I've been doing to
get Bodhi's CI setup to be much nicer, in case that interests any of
you:
https://blog.electronsweatshop.com/goodbye-jjb-hello-jenkies-pipeline.html
signature.asc
Description: This is a digitally signed message
On Thu, 2018-10-04 at 17:09 -0700, Kevin Fenzi wrote:
> And secondly:
>
> https://github.com/fedora-infra/bodhi/issues/2579
>
> we probibly need at least that bug fixed, although we could put a
> lock
> wrapper around it so it only runs one at a time ever.
Mohan's code did ensure that the len()
This FBR is applied on production.
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code
Also the formatting on this e-mail was terrible. Sorry for that. Next
time I'll just attach a file so Thunderbird doesn't try to get too smart.
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list --
On 9/18/18 12:22 PM, Stephen John Smoogen wrote:
> I see this removing it from 85853d46b5 but how does it connect to the
> other update?
Hi Smooge!
I'm trying to do the minimum amount needed in the FBR, so I plan to use
Bodhi's normal features after doing this to add the build to the other
Context: https://pagure.io/releng/issue/7825
In order to fix that issue, I propose running the following commands on
bodhi-backend01:
$ sudo -u apache pshell /etc/bodhi/production.ini
2018-09-18 16:09:51,892 INFO [bodhi][MainThread] Using the
FakeBugTracker
2018-09-18 16:09:51,892 DEBUG
On 09/12/2018 04:01 AM, Clement Verna wrote:
> [0] https://github.com/dhatim/python-license-check
This looks useful, thanks for sharing!
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list --
On 09/03/2018 07:15 AM, Miro Hrončok wrote:
> Hi. As per the consensus reached in nonresponsive maintainer: lmacken [0], I
> offer this list of packages to be taken over by infra. Any takers?
I took a few of them:
https://pagure.io/releng/issue/7764
signature.asc
Description: OpenPGP digital
This change has been made.
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of
On 08/29/2018 03:44 PM, Stephen John Smoogen wrote:
> The original is fine. Thank you for the training. I just wanted to make
> sure there weren't more objects in the DB, that the query wouldn't give
> you a random return from a hashtable etc.
>
> +1
Excellent. I will make it so.
--
Number
On 08/29/2018 03:26 PM, Stephen John Smoogen wrote:
> Can you give me more information on what this will due, what could go
> wrong and how to recover? If not I don't think I can give an answer.
I have two +1's now, but I wanted to make sure you are satisfied too
before I take action. Shall I
On 08/29/2018 03:26 PM, Stephen John Smoogen wrote:
> Can you give me more information on what this will due, what could go
> wrong and how to recover? If not I don't think I can give an answer.
Bodhi has a database model called a Compose, which is used to keep track
of each of its daily compose
There is a Fedora 29 Compose in Bodhi's DB that has gotten into a weird
state due to being run when the process didn't know about Fedora 29. To
fix it, I wish to use pshell on bodhi-backend01 to delete it:
$ sudo -u apache pshell /etc/bodhi/production.ini
>>> c = m.Compose.query.first()
>>>
On 08/29/2018 02:07 PM, Kevin Fenzi wrote:
> Also we need to restart fedmsg-hub on bodhi-backend01 for this and other
> things to take effect.
>
> +1s?
My vote doesn't count, but I support this ☺
signature.asc
Description: OpenPGP digital signature
On 08/29/2018 11:43 AM, Randy Barlow wrote:
> -clean_old_mashes.remove_old_composes()
OK, this is now in place on backend01 - Mohan if you resume the failed
mash I think it'll succeed now.
I am preparing a better fix upstream today:
https://github.com/fedora-infra/bodhi/issues/2
This replaces the other FBR I filed today. I would like to manually
apply (i.e., hotfix) this patch to bodhi-backend01 as a temporary
workaround for #7194[0]:
diff --git a/bodhi/server/consumers/masher.py
b/bodhi/server/consumers/masher.py
index ecf88fd3..43c2ac5f 100644
---
On 08/29/2018 09:57 AM, Randy Barlow wrote:
> The number is not specified, so it will also change for when Bodhi calls it.
Ugh, which actually means it won't work.
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing l
On 08/29/2018 09:56 AM, Dusty Mabe wrote:
> So basically the solution is to run clean_old_mashes.py as root and change
> it so that it deletes "more than" what the bodhi run will delete when it runs
> as non-root, thus rendering the bodhi run clean_old_mashes.py as a no-op ?
Yes.
> Is the number
On 08/29/2018 09:19 AM, Randy Barlow wrote:
> Basically, the current script deletes the most recent 10.
Correction: the script deletes *all but* the most recent 10.
signature.asc
Description: OpenPGP digital signature
___
infrastructure mailing l
Fedora 28 will always fail to compose with Bodhi 3.9.0 because of a
recent change that is causing some ostree files to be root owned in
/mnt/koji/compose/updates/[0]. I filed a ticket to ask for help in
deciding a solution to the problem, but we need an immediate solution
because the current
Bodhi 3.9.0 is released upstream, and i plan to deploy it to production
on Monday.
https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html
Happy updating!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe
On 07/23/2018 05:05 PM, Kevin Fenzi wrote:
> bodhi-backend - ?
> bodhi-web - ?
Both of these are close to ready. Theoretically they should work with
Python 3 right now, but there are a few tests that fail (they are
skipped so the test suite passes) in Python 3 (most likely due to the
test code
On 06/13/2018 08:04 PM, Kevin Fenzi wrote:
> I can take it to them, I just wanted to see if there was a general sense
> that it was useful and we should keep it, or it was pointless and we
> should drop it. Perhaps I'll post to devel about it to see what the
> general feeling is.
I only have a
On 06/13/2018 03:03 PM, Kevin Fenzi wrote:
> ok. Note that this data changes over time, and releng needs a script to
> update it (or better a automatic updating of it).
Yeah there is a Bodhi ticket about this and I noted that we will need to
make sure we still work with releng's script if we make
On 06/07/2018 12:20 PM, Pierre-Yves Chibon wrote:
> I propose that we meet up next week on Monday at 14:00 UTC.
Works for me.
> What do you prefer, IRC or video (bluejeans)?
I have a slight preference for IRC.
signature.asc
Description: OpenPGP digital signature
On 05/17/2018 05:02 PM, Randy Barlow wrote:
> I don't
> think it's reasonable to state that it's the only valid means.
After re-reading your message, I realized that I may have misinterpreted
your words a bit more strongly than perhaps they were intended to be.
Please accept my apology
On 05/17/2018 01:10 PM, Pierre-Yves Chibon wrote:
> We went over the event that lead to disabling gating in bodhi last week
> (see fesco ticket: https://pagure.io/fesco/issue/1872)
> If this situation happens again we encourage a stronger reach out for help
> from
> the folks involved (in this
Greetings!
At the hackathon we did recently, we talked about the need for one of us
to attend the Modularity WG meetings so we could be more aware of what
work is coming our way before it's a surprise, and I volunteered to be
that person.
For $reasons, today was the first of the WG meetings I
Greetings!
I would like feedback from you about the usefulness and/or
format/schedule of the Bodhi stakeholders' meeting.
I've been holding this meeting about once every 4 weeks. It started off
pretty well with lots of seemingly interested participation, but over
time it seems that fewer people
On 05/09/2018 12:07 PM, Randy Barlow wrote:
> Aaand it also doesn't work in production. I tested the Greenwave API
> just yesterday and it did return the data that Bodhi looks for. Today
> the exact same query omits the specific data that Bodhi looks for, which
> means tha
1 - 100 of 212 matches
Mail list logo
