semi-automatic firefox rebuilds (was Re: Review queue/FESCo after the merge)

[Thorsten Leemhuis]

On 19.11.2007 17:49, Jesse Keating wrote:
> On Mon, 19 Nov 2007 17:23:05 +0100
> Thorsten Leemhuis <fedora at leemhuis.info> wrote:
> 
>> Firefox IMHO is the way better example -- I fail to understand why we
>> didn't create a script that rebuilds all packages that depend on it
>> once it's build and in the buildroot. Yes,
> 
> Again, it takes /somebody/ to write it.

We often say that in Fedora-land -- the result afaics often is: we scare
people away with it.

Sure, there is of course somebody needed, but sorry, especially FESCo
members instead of "Again, it takes /somebody/ to write it." should say
something like "yeah, this could be a solution; is somebody in our
friendly community willing to realize it?" or "yeah, nice idea, but
instead we should do .... to solve the problem is a even better way"

For more complicated tasks there is of course more needed. But just
requesting "do something" won't change anything most of the time --
especially for more comlicated tasks FESCo should say "yeah, we want
something like that; this is how it could look like ..." and guide
people. Then people can be sure than the solution they work out (which
could take many workhours of even days) is at least roughly what FESCo
wants.

>  FESCo can say all they want "I
> want this to happen", but until somebody sits down and cranks out a
> script, it's just not going to happen.

Come on, if our leaders are not able to do such a simple thing like this
own their own or find somebody do do it then there really is something
wrong in Fedora-land.

It's really not that hard, even I with my very limited programming
skills (aka "knurd the package monkey") I can do what's needed in just a
few minutes:

/me wanders of to create such a "script"

/me downloads
http://cvs.fedora.redhat.com/viewcvs/rebuild-scripts/bumpspecfile.py?root=fedora&view=markup

/me adjusts changelog comment

/me copy-and pastes list from
http://fedoraproject.org/wiki/WillWoods/Drafts/FirefoxUpdates
(one could create such a list with manually as well; "repoquery
--whatrequires --alldeps 'firefox = 2.0.0.9' 'gecko-libs = 1.8.1.9'" or
something like that would be a good start)

/me removes the newlines and created a quick loop in bash

Here is your "script":
---
for package in blam chmsee devhelp epiphany epiphany-extensions firefox
galeon gnome-python2-extras gnome-web-photo gtkmozembedmm kazehakase
liferea Miro openvrml ruby-gnome2 yelp; do
	pushd ${package}
	bumpspecfile.py *.spec
	make tag build
	popd
done
---

Find bumpspecfile.py attached. Run it in a full cvs checkout once the
new firefox is in the repo; if you don't have one add a "cvs co
${package}" at the right place and adjust the pushd call.

Before above works one needs to adjust some of the spec files so none
hard-code the gecko-* or firefox-* versions -- or instead use the same
format everywhere witch can be adjusted with a simple sed call. I can't
do that, something like that is unwanted in Fedora-land (see earlier in
this thread). If FESCo gives me the permission I'm of course
volunteering to do it.

Have fun.

CU
knurd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bumpspecfile.py
Type: text/x-python
Size: 3962 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20071119/bcbd8d93/attachment.py>