Bug 164344 - galeon package mozilla requires breaks rebuilding
galeon package mozilla requires breaks rebuilding
Product: Fedora
Classification: Fedora
Component: galeon (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dams
Fedora Extras Quality Assurance
Depends On:
Blocks: 163942
  Show dependency treegraph
Reported: 2005-07-27 00:27 EDT by Seth Vidal
Modified: 2007-11-30 17:11 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-09 14:38:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Seth Vidal 2005-07-27 00:27:50 EDT
Description of problem:
Galeon spec mozilla Requires breaks rebuilding in chroot.

Requires:   mozilla = %(rpm -q mozilla-devel --qf='%%{epoch}:%%{version}'

this queries the rpmdb inside the chroot and if there is no mozilla-devel
package present resolves out to:
mozilla = ''

The mozilla version should be hard-coded in the spec file b/c if the
mozilla-devel installed in the chroot isn't the one you're intending to build
for you will get a faulty build.

This is why the above command was removed from the epiphany spec file as well.
Comment 1 Dams 2005-07-27 15:55:12 EDT
I dont see the problem here, because
1. If there's no mozilla-devel installed, the build will fail anyway because the
package buildrequires mozilla-devel >= 37:1.7.2, so the package can _requires at
runtime_ whatever, it doesnt matter.

and because 2. any version mozilla >= 37:1.7.2 is good enough to rebuild galeon.
that's why a strict version is not hardcoded.
Comment 2 Warren Togami 2005-07-27 21:28:14 EDT
I think the problem has to do with the .src.rpm being put together outside of
the buildroot?

Does the build system implement this looping algorithm for populating
BuildRequires within the buildroot?

If the above algorithm is done, then this kind of syntax works in the spec:
# Require Binary Compatible glib
# returns bogus value if glib2-devel is not installed in order for parsing to
# bogus value wont make it into a real package
%define glib_ver %([ -a %{_libdir}/pkgconfig/glib-2.0.pc ] && pkg-config
--modversion glib-2.0 | cut -d. -f 1,2 || echo -n "999")
Requires:       glib2 >= %{glib_ver}

The || prevents a non-zero return value which causes the intial loop of spec
parsing to fail.  Subsequent loops correct the value with stuff actually that
*should* be in the buildroot.
Comment 3 Alex Lancaster 2005-07-29 16:27:43 EDT
Any chance that this can be fixed, or a workaround/fix made to the spec file so
that galeon can be rebuilt soon?  This bug blocks the mozilla upgrade which is a
security fix.
Comment 4 Seth Vidal 2005-08-01 00:12:36 EDT
the srpm is rebuilt once inside the chroot.

and the aforementioned syntax is god-awful-ugly. so why we would want to have
that sort of syntax in a specfile is beyond me, even if the buildsystem can deal
with it.
Comment 5 Warren Togami 2005-08-01 00:41:25 EDT
Ugly, but it works, and makes it easier to maintain in the long term because you
never need to touch it again.
Comment 6 Dams 2005-08-01 16:03:56 EDT
'ugly'... taste and colors. I consider it really readable. I can comment the
line in the spec file if you think that make it more `sane'. 

And as Warren said, this makes the spec file easier to maintain and this is
exactly why i'm doing this. If that's not okay anymore, I'll let someone else
maintain the package. Just dont hate me because I'm lazy.

So, Seth, is the package okay or do we still have a problem ?
Comment 7 Seth Vidal 2005-08-01 16:32:43 EDT
I'm not blocking anything from going through.

it wouldn't build last time it was tried. I filed the bug b/c when I asked about
it on #fedora-devel caillon said that epiphany used to have that same Requires
in it and it was removed b/c it was considered wrong.

Comment 8 Alex Lancaster 2005-08-07 02:58:22 EDT
Could somebody please just fix the spec file to make it build and worry about
the niceities later?  It's been over two weeks since the mozilla update and this
blocks a security update.
Comment 9 Dams 2005-08-09 14:38:43 EDT
No. And i'm dropping galeon support in FE.
Comment 10 Alex Lancaster 2005-08-09 15:26:13 EDT
Looks like build failed for the same reason as before on ppc because of the spec
file problem, compare:




Sorry to hear that you won't maintain galeon anymore, can anybody else pick this
up?  Why can't we just hardcode the mozilla version for the moment?  The spec
file will need to be updated for every mozilla release anyway.
Comment 11 Warren Togami 2005-08-09 17:59:54 EDT
Any existing cvsextras member or RH engineer may claim ownership of galeon if
they wish.
Comment 12 Alex Lancaster 2005-08-09 18:53:47 EDT
Seth modified spec file and rebuilt package.  Now in repository.
Comment 13 Seth Vidal 2005-08-09 23:15:58 EDT
I am not claiming the package.

I just wanted the problem to go away.

Note You need to log in before you can comment on or make changes to this bug.