bodhi

bodhi@lists.fedorahosted.org

660 discussions

Fedora-specific stuff in app.cfg
by Mathieu Bridon 10 Oct '12

10 Oct '12

Hi, I'm finally getting around to deploying Bodhi here at $dayjob. :) The first thing which strikes me is that app.cfg is not marked as % config in the Fedora package. That means I can't easily change all the "fedoraproject.org" URLs in this file for example. What would you recommend? Patching the source and rebuilding the package? Or would you make app.cfg be %config in the spec? Or...? Thanks, -- Mathieu

1 2

running a private bodhi instance
by Dennis van Dok 11 Sep '12

11 Sep '12

Hi, my software team builds and releases a set of some 30 packages of Grid Computing related software. We've come a long way from running rpmbuild by hand, to using mock and recently running and installing our own koji instance. We're very happy with how koji works, and we're looking at bodhi right now as an option to manage our releases. That is, running bodhi as a private instance, separate from the Fedora systems. We found that bodhi is packaged neatly in fc17, and with some fiddling we got it to work; but I find that there is very little documentation on how to set up a private instance (all examples lead to a development instance meant for the Fedora bodhi) and we're struggling with the tuning of the system. Does anybody have some tips or advice on how to continue? We believe the system has great potential for doing release management. We're certainly going to contribute some documentation on how to run a private instance if we succeed. Thanks, Dennis van Dok -- D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.biggrid.nl Phone +31 20 592 22 28 :: http://www.nikhef.nl/~dennisvd/

1 0

Can I push my commit?
by Christopher Meng 23 Aug '12

23 Aug '12

Hi, I found a bug in bodhi,and i think using git to commit is a good idea,now I don't know if doing this is acceptable,can anyone answer me? -- *Yours sincerely,* *Christopher Meng* Ambassador/Contributor of Fedora Project and many others. http://cicku.me

2 2

New bodhi release in production
by Luke Macken 09 Aug '12

09 Aug '12

A new release of Bodhi has just been deployed to production. https://admin.fedoraproject.org/updates Bugs and enhancement requests can be filed here: http://bodhi.fedorahosted.org Major changes in bodhi 0.9.2 ---------------------------- - fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean) - Re-organized the links on the front page, and link to the new Update Feedback Guidelines - The submitter of an update can no longer effect the karma (Till Maas) - Fix duplicate status change email notifications. (Till Maas) - Mention age of updates in testing digest mails (Till Maas) - Support e-mail threading in notification e-mails (Till Maas) - Add X-Bodhi mail headers (Till Maas) - Gracefully handle private bugs (Cole Robinson) - Set the default request for new updates to 'testing' in the web form - Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable. - Fixed the input box alignment in the login box (Kalpa Welivitigoda) Full list of changes since 0.8.7 -------------------------------- Kalpa Welivitigoda (1): fixed input box alignment issue in login box #579 Luke Macken (25): Convert our tags_url to a byte string before passing it to urlgrabber. Add a script to detect when older builds become the 'latest' in stable Update our test suite to reproduce ticket [ticket:683] Fix a bug in our critpath policy ([ticket:683]). Set the default request for new updates to 'testing' Clean up EOL buildroot overrides in our rmrelease tool (bz#818617) Fix a busted unit test (test_push_EPEL_critpath_before_tested) Add pkg_resources __requires__ hacks to bodhi tools to mitigate version conflicts Handle the case where a release doesn't have any overrides Change our X-Bodhi-Update-Release header to use the short name Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605) Update our unit tests to assume submitters cannot alter karma Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg Merge branch 'feature/bodhi1-fedmsg' into develop Fix a typo in the metrics tool Fix a typo in the new mail headers Re-organize our links, and add one to the new update feedback guidelines Clean up stray buildroot overrides Version bump for 0.9.2 Our build script uses bz2 Merge branch 'release/0.9.2' Mathieu Bridon (6): Have bodhi-init create all the tables masher: Fix the comparison masher: Reuse variable setup: Fix the Turbogears version requirement Don't version control auto-generated files setup: Add missing dependencies Ralph Bean (19): Sending messages with fedmsg. No longer using fedmsg schema/validation. fedmsg.ini -> fedmsg-config.py More detail in the update.complete message. More concise send_message calls. Ignore dev db. Merge branch 'master' into bodhi1-fedmsg Updates for the latest fedmsg. Getting tests passing. Merge branch 'master' into bodhi1-fedmsg Ignore mashing fedora file. Fixed what I think is a regression in login template. Merge branch 'master' into bodhi1-fedmsg Update to test fedmsg config. Work with both tests and under WSGI. Version bump for fedmsg in staging. Only send the comment with a comment is added, not the whole update. Using a "bodhi" user/group for mod_wsgi. fedmsg+ssl changes to bodhi.spec. Use modern fedmsg config format. Disable message signing for bodhi tests. Till Maas (8): Add X-Bodhi mail headers Support e-mail threading in notification e-mails Mention age of updates in testing digest mails Use format string instead of string concatenation Import exceptions from sqlite3 Remove files used by mercurial model.py: Change karma from Submitter to 0 Fix notification on automatic status change

1 0

Patches waiting to be deployed
by Till Maas 22 Jul '12

22 Jul '12

Hi, there are several patches that wait to be included and deployed for a while now: https://fedorahosted.org/bodhi/query?status=assigned&status=new&status=reop… Regards Till

1 0

Bodhi v2.0 meeting today at 19UTC
by Luke Macken 19 Jul '12

19 Jul '12

Hi, We're going to have a quick bodhi 2.0 status meeting today after the infrastructure meeting at 19 UTC in #fedora-meeting (or #fedora-apps) on Freenode. I'm hoping to just go over the current state of the port, and also I'd like to get input from QA, Releng, etc about the new features they want to see the most. Plus anything else people want to discuss! luke

1 1

More than two updates level
by Mathieu Bridon 27 May '12

27 May '12

Hi, At $dayjob, we build our own distro derived from EL6. We build the some additional packages we need (which I'm introducing in Fedora whenever possible), and so we have our own Koji setup. We'd like to use Bodhi to manage updates and coordinate their QA-ing, similarly to how it's done in Fedora. However, one major difference is that we don't have two release levels but three: "testing", "updates" and "release". The first two work just like they do in Fedora. But our customers asked us for a "patch Tuesday" process, so by default the "updates" repository is not enabled, they take packages only in "release". And every month, we move packages from "updates" to "release". (We do have an "out-of-cyle" process where updates can be pushed before the next "patch Tuesday" if required) Reading the code, it seems to me that Bodhi is making the assumption that there are two release levels only, as Release objects have a "testing_tag" and a "stable_tag" attributes. Am I understanding this correctly? If I am, is there a desire to have Bodhi able to implement our model? (I can work on the implementation) Or is there just no way to do that with Bodhi and I should start working on our own home-made solution? Thanks, -- Mathieu

1 0

Re: [bodhi] [Need guidance]
by Luke Macken 30 Apr '12

30 Apr '12

Hi Praveen, On Thu, Apr 26, 2012 at 04:03:10PM +0530, Praveen Kumar wrote: > Hi, > > Today I saw about easyfix on devel-mailing list, I am interested to know more > about https://fedorahosted.org/bodhi/ticket/639 , like from where can I start > and what scripting language it need ..etc. I am familiar with bodhi as a user > but have no idea about implementation. This ticket requires a little bit of Python knowledge. Sadly, it won't be easy to test these changes locally, but I will be able to review the patch and test it in our staging environment upon completion. So this change is going to require modifying Bodhi's Masher to add the number of days each update has spent in testing to the updates-testing digest[0]. Thankfully, bodhi's PackageUpdate objects already have a days_in_testing property[1], so all that needs to be done is to fetch the PackageUpdate object for each update during the digest creation, and add the value PackageUpdate.days_in_testing to it. Feel free to ask me any questions you have, from Python basics to bodhi specifics. Thanks, luke [0]: https://fedorahosted.org/bodhi/browser/bodhi/masher.py#L830 [1]: https://fedorahosted.org/bodhi/browser/bodhi/model.py#L1158

1 0

Bodhi critical path updates policy adjustment
by Luke Macken 01 Feb '12

01 Feb '12

FESCo recently made an adjustment to the updates policy to no longer require proventester karma for a critical path update to be deemed as stable. Critical path updates will now require just one regular +1 karma vote during the pre-beta phase and two regular +1 karma votes in other phases to be pushed to the stable updates repo. Anonymous karma is not taken into account. This policy change has been implemented and deployed to production with Bodhi v0.8.6. https://admin.fedoraproject.org/updates Please report any issues in bodhi's trac: http://bodhi.fedorahosted.org Thanks, luke

1 0

bodhi/config
by Luke Macken 20 Jan '12

20 Jan '12

bodhi/config/app.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit d0060f392b4797e58b4ce264750fb94de48ecd97 Author: Luke Macken <lmacken(a)redhat.com> Date: Fri Jan 20 13:28:38 2012 -0500 Remove the mandatory proventester karma requirements for critpath (#653) diff --git a/bodhi/config/app.cfg b/bodhi/config/app.cfg index d754828..b445046 100644 --- a/bodhi/config/app.cfg +++ b/bodhi/config/app.cfg @@ -199,7 +199,7 @@ critpath = "ConsoleKit ConsoleKit-libs ConsoleKit-x11 GConf2 GConf2-gtk ModemMan # The number of admin approvals it takes to be able to push a critical path # update to stable for a pending release. -critpath.num_admin_approvals = 1 +critpath.num_admin_approvals = 0 # The net karma required to submit a critial path update to a pending release) critpath.min_karma = 2 @@ -217,7 +217,7 @@ fedora_epel.mandatory_days_in_testing = 14 # https://fedoraproject.org/wiki/Updates_Policy #f15.status = 'pre_beta' #f15.pre_beta.mandatory_days_in_testing = 3 -#f15.pre_beta.critpath.num_admin_approvals = 1 +#f15.pre_beta.critpath.num_admin_approvals = 0 #f15.pre_beta.critpath.min_karma = 1 testing_approval_msg = "This update has reached %d days in testing and can be pushed to stable now if the maintainer wishes"

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

bodhi