bodhi

bodhi@lists.fedorahosted.org

660 discussions

[devel] The Vagrant dev environment now uses Fedora stg auth
by Randy Barlow 03 Jan '19

03 Jan '19

Greetings! I just merged a PR[0] that makes Bodhi's Vagrant environment use Fedora's staging Ipsilon server for authentication, instead of production. This means you need to have an account in staging to authenticate to Bodhi by default, and I highly recommend setting that account password to be different than your production Fedora password. This way if there's ever a bug in the development environment that accidentally connects you to the production API (for example, when working on the CLI), your staging password won't be accepted and you won't accidentally put testing data in production. To get this change fully, you will need to update your development.ini file in similar ways to what I did to devel/development.ini.example in the pull request. An easy way to do that if you don't care about any changes you might have made to development.ini is: $ rm development.ini; vagrant destroy; vagrant up [0] https://github.com/fedora-infra/bodhi/pull/2820

1 0

Bodhi 4.0.0
by Randy Barlow 12 Dec '18

12 Dec '18

Greetings! I am about to start working on a set of backwards incompatible changes to Bodhi for its upcoming 4.0.0 release (Bodhi follows Semantic Versioning[0]): https://github.com/fedora-infra/bodhi/projects/6 If the thought of backwards incompatible changes to Bodhi raises one or both of your eyebrows, please peruse the list of proposed changes there and comment on any issues that may concern you. I can't be sure who is using Bodhi for what, so please let me know if you think any of these changes are a Bad Idea™. [0] https://semver.org/

1 0

Bodhi stakeholders' meeting next week
by Randy Barlow 11 Dec '18

11 Dec '18

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!

1 0

About bodhi client versions
by Chenxiong Qi 24 May '18

24 May '18

Hi, I'm one of the fedpkg maintainer. I have some questions about bodhi client versions. I'm currently adding override support to fedpkg, and it is good to use Python bindings in some logic instead of CLI. fedpkg now has code to detected bodhi CLI's major version, and fedpkg only works with version less than 4. Will this major version change in future impact the interfaces in Python bindings? Would that change mean the bodhi CLI interface could change only? Thanks. -- Regards, Chenxiong Qi

2 1

[dev] Vagrant upgrading to Fedora 27
by Randy Barlow 16 Feb '18

16 Feb '18

Just a heads up - I just submitted a pull request[0] to upgrade the Vagrant environment to Fedora 27. Once that is merged, you will need to edit your Vagrantfile to match the changes in that pull request. [0] https://github.com/fedora-infra/bodhi/pull/2158

1 0

Update a package
by Berend De Schouwer 22 Nov '17

22 Nov '17

Hi, I'm trying to update a package to resolve BZ 1494586. I need to update the gnome-shell-extension-pomodoro package from 0.13.3 to 0.13.4. I've seen various automated Bodhi build emails in various BZ, so I thought: "hey, let's try that." I tried creating an update, but "submit" does nothing (no error message.) I assume because one or both of: 1. I'm not the maintainer 2. The updated .src.rpm doesn't exist What do I do next? Koji? Copr? Berend PS. I'm personally running a locally updated RPM. I'm just trying to complete the BZ.

2 2

[devel] dev environment now requires Fedora >= 26
by Randy Barlow 08 Nov '17

08 Nov '17

Greetings! I've just merged a PR[0] that causes Bodhi to require Fedora >= 26. This means that you will probably need to upgrade your Vagrantfile. If you don't have local changes to worry about, you can just do this: $ vagrant destroy $ cp devel/Vagrantfile.example Vagrantfile $ vagrant up [0] https://github.com/fedora-infra/bodhi/pull/1958

1 0

[dev] Tests use less memory!
by Randy Barlow 05 Jul '17

05 Jul '17

Due to a recent and awesome pull request[0] by Jeremy Cline, it is now possible to run Bodhi's unit tests with about 1/10th the RAM they used to take (they went from about 4 GB to about 450 MB!) Because of this, you can now lower the amount of memory required in your Vagrantfile if you wish. There's a PR open to make the default 2 GB[1], but I think you could squeak by with even 1 GB. [0] https://github.com/fedora-infra/bodhi/issues/1668 [1] https://github.com/fedora-infra/bodhi/pull/1671

1 0

[dev] New development dependencies
by Randy Barlow 30 Jun '17

30 Jun '17

Hello! Due to merging https://github.com/fedora-infra/bodhi/pull/1664 you will need to vagrant destroy && vagrant up in order for btest to work correctly. Happy hacking!

1 0

[dev] Delete your development.ini file
by Randy Barlow 06 Jun '17

06 Jun '17

I just merged a PR[0] that majorly reworks how configuration in Bodhi works. The development.ini.example file had a problematic entry in it that will not work with this code. Fortunately, the default in production.ini did not have this issue, so it's not a backwards- incompatible change for our users. To fix your dev environment, either comment the compose_atomic_trees setting in your development.ini file, or simply rm it and do a vagrant destroy && vagrant up to get back up and running. [0] https://github.com/fedora-infra/bodhi/pull/1544

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

bodhi