<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Michael Schwendt wrote: <blockquote cite="mid:20070904005353.16333c36.bugs.michael@gmx.net" type="cite"> <pre wrap="">On Mon, 03 Sep 2007 23:46:44 +0200, Ralf Corsepius wrote: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">[hans@... FC-6] make build <or oops forgotten> <some time later, hey a bugzilla ticket why I never build foo for FC-6> </pre> </blockquote> <pre wrap="">Ohh? I am permanently nagged with mails reminding me about EVR problesm with packages between FC-6 and FC-7, because I can't push them for FC-7 because, I could not find them in bodhi. </pre> </blockquote> <pre wrap=""> That is because of a premature roll-out of the new updates system [1] where you are expected to enter the full src.rpm %name of each of your builds before the auto-completion would list them with full NEVR. Honestly, I have no idea how the major package contributors like Hans handle that for their many a dozen packages. ESR would have run wild. [1] Which otherwise comes with several good features, such as a web ui and announcement mails. -- Fedora-maintainers mailing list <a class="moz-txt-link-abbreviated" href="mailto:Fedora-maintainers@redhat.com">Fedora-maintainers@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/fedora-maintainers">https://www.redhat.com/mailman/listinfo/fedora-maintainers</a> </pre> </blockquote> I'm a spare-time contributor too and i happy about bodhi, I think there is a need for a tool like that and i think i have some good features. * link to bugzilla reports, that get updated when a package is push to testing & stable. * update notes. * testers can comment the update. * easy push to testing & stable & unpush I only maintain a couple of packages so i don't have any problems, but i can see that for people there maintain a lot of packages, there need to be taken some steps to make there life easier. * Command line tool to submit updates to bodhi, there can be integrated with the CVS Makefile Allready in works. <a class="moz-txt-link-freetext" href="https://hosted.fedoraproject.org/projects/bodhi/browser/tools/bodhi.py">https://hosted.fedoraproject.org/projects/bodhi/browser/tools/bodhi.py</a> * Better package lookup when adding new updates. I have created a local bodhi instance ( <a class="moz-txt-link-freetext" href="https://hosted.fedoraproject.org/projects/bodhi/wiki/Development">https://hosted.fedoraproject.org/projects/bodhi/wiki/Development</a>) and tested the latest upstream code, the typeahead lookup is much better. But the easiest way would be a button on the package build in koji to launch a populated new update in bodhi. This has to be done in koji. <a class="moz-txt-link-freetext" href="https://hosted.fedoraproject.org/projects/bodhi/ticket/36">https://hosted.fedoraproject.org/projects/bodhi/ticket/36</a> I have asked Luke, where i can help and i have started to checkout the code and is started to hack on some of the open tickets. <a class="moz-txt-link-freetext" href="https://hosted.fedoraproject.org/projects/bodhi/report/1">https://hosted.fedoraproject.org/projects/bodhi/report/1</a> Tim </body> </html>