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

On 19.11.2007 17:49, Jesse Keating wrote:
> On Mon, 19 Nov 2007 17:23:05 +0100
> Thorsten Leemhuis <fedora@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
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

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

On Mon, 19 Nov 2007 18:52:12 +0100
Thorsten Leemhuis <fedora@leemhuis.info> wrote:

> /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

So this is great and all, but it's FF specific, where we're moving to
xulrunner anyway. Time is better spent getting these things to support
xul.

Not that this script isn't handy at all. In fact, I think we (as
Fedora) need to appoint somebody or some "body" (like a SIG) to oversee
the entire gecko stack both now and in the future to ensure that
updates are coordinated. Just building is only one part of the puzzle,
they all have to get pushed out at the same time and into the same
repos.

I don't have the time or energy to own this problem space. I can tell
you from my perspective where the problems are, and take a look at
proposed solutions. Your script may indeed prove very handy to those
that are going to own this problem space, especially if it were tied
into the makefile changes Luke made for auto-filing bodhi push requests.

--
Jesse Keating
Fedora -- All my bits are free, are yours?
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

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

On 19.11.2007 19:02, Jesse Keating wrote:
> On Mon, 19 Nov 2007 18:52:12 +0100
> Thorsten Leemhuis <fedora@leemhuis.info> wrote:
>
>> /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
> So this is great and all, but it's FF specific, where we're moving to
> xulrunner anyway. Time is better spent getting these things to support
> xul.

F8 will still be around for about 12 months, which IMHO is more then
enough a reason to warrant one or two of work. Especially as it safes
the maintainers of the packages some work, so in the end less work for
everybody.

BTW, does xulrunner properly and for real solve the problem? The current
rawhide package just as firefox has a path with a version number in it
(/usr/lib64/xulrunner-1.9a9pre/) so I fear that there sill will be
packages taht depend on a particular xulrunner version. Or is there some
abstraction somewhere to make sure packages don't depend on a particular
version of xulrunner?

> Not that this script isn't handy at all. In fact, I think we (as
> Fedora) need to appoint somebody or some "body" (like a SIG) to oversee
> the entire gecko stack both now and in the future to ensure that
> updates are coordinated.

Maybe, yes, but I tend a bit to the "who broke something should at least
do minimal efforts to get it fixed". IOW: the one that rebuilds firefox
should ask rel-eng to put it into the buildroot and call the script once
it really exists.

> Just building is only one part of the puzzle,
> they all have to get pushed out at the same time and into the same
> repos.

With the new bodhi command line interface this shouldn't be to hard afaics.

> I don't have the time or energy to own this problem space.

I'd be willing to create the script properly and modify the packages if
I can do it directly in CVS (after a public review of course) if FESCO
backs the effort.

> [...]

CU
knurd

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

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

Thorsten Leemhuis wrote:


On 19.11.2007 19:02, Jesse Keating wrote:

On Mon, 19 Nov 2007 18:52:12 +0100
Thorsten Leemhuis <fedora@leemhuis.info> wrote:


/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

So this is great and all, but it's FF specific, where we're moving to
xulrunner anyway. Time is better spent getting these things to support
xul.


F8 will still be around for about 12 months, which IMHO is more then
enough a reason to warrant one or two of work. Especially as it safes
the maintainers of the packages some work, so in the end less work for
everybody.

BTW, does xulrunner properly and for real solve the problem? The current
rawhide package just as firefox has a path with a version number in it
(/usr/lib64/xulrunner-1.9a9pre/) so I fear that there sill will be
packages taht depend on a particular xulrunner version. Or is there some
abstraction somewhere to make sure packages don't depend on a particular
version of xulrunner?


I also don't understand. I thought the whole point of having xulrunner
was precisely so we can package it properly using a more classic dynamic
libraries versioning scheme...


-d

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list