Clarification needed on ART plans for PHP FPM

[dayo]

Hi Scott.

Noticed PHP 5.3.5 is up on the testing repo but without php-fpm as was the case with 5.3.4.

As I am stranded on 5.3.3 by this, can you kindly clarify whether you plan to add this later or whether you are ceasing building this?

This is just so that informed decisions can be made.

Thanks

[scott]

I thought it was built

[dayo]

Hi Scott

Thanks for the response.

I got this ...

Code: Select all

...
--> Finished Dependency Resolution
php-fpm-5.3.3-2.0.el5.art.i386 from installed has depsolving problems
  --> Missing Dependency: php-common = 5.3.3-2.0.el5.art is needed by package php-fpm-5.3.3-2.0.el5.art.i386 (installed)
...

... when I ran "yum --enablerepo=atomic-testing upgrade php"

I tried building myself using the spec file with no joy.

I thought it was the ...

Code: Select all

%if 0%{!?el4}
%global with_enchant 1
%global with_fpm 1
%else
%global with_enchant 0
%global with_fpm 0
%endif

... that was the issue. So I changed it to ...

Code: Select all

#%if 0%{!?el4}
%global with_enchant 1
%global with_fpm 1
#%else
#%global with_enchant 0
#%global with_fpm 0
#%endif

.. bit no joy still. (This was with 5.3.4 but I guess the spec file is essentially the same with 5.3.5)

Thanks again.

[scott]

The conditionals definitely need to be in there, what Id recommend you do is test builds under both el4 and el5 once you nail down what needs to be changed, otherwise we can't use the patch.

Check out mock if you havent already, thats what we use here for all the package builds. You'll find it considerably more efficient than trying to nail the dependencies down on an already built/running OS.

[dayo]

Starting to go beyond my ability level / comfort zone.

I'll look into downgrading to 5.2.x and patching FPM (which I know how) or just looking at other alternatives until you move the 5.3 branch into stable at which point I suppose you will take another look at this.

Thanks again.

[dayo]

BTW. When I removed the conditionals for el4 and all the other "with_fpm" ones so that it had to run the fpm related lines, it fell over on the "build-fpm" command.

[dayo]

What the heck.

Giving mock a shot. Don't know much about it so will appreciate tips and hints.

Managed to set it up and fire it off ... telling me "this may take a while" so will see what gives.

[dayo]

OK. Not going well

This is what I got ...

Code: Select all

[mockuser@server01 ~]$ wget http://www4.atomicorp.com/channels/source/php/php-5.3.5-1.art.src.rpm

...

[mockuser@server01 ~]$ mock rebuild php-5.3.5-1.art.src.rpm
init
clean
prep
This may take a while
setup
warning: /builddir/build/originals/php-5.3.5-1.art.src.rpm: Header V3 DSA signature: NOKEY, key ID 5ebd2744
php                         ##################################################
error: unpacking of archive failed on file /builddir/build/SOURCES/macros.php;4d2cb1fa: cpio: MD5 sum mismatch
Error installing srpm: php-5.3.5-1.art.src.rpm
ending
done

Something about MD5 sum mismatch.

Any clues?

Thanks

[dayo]

Using "mock -r default --rebuild php-5.3.5-1.art.src.rpm" as per https://fedoraproject.org/wiki/Using_Mo ... se_Mock.3F made no difference ... Same error message.

Help! tips!

Thanks

[dayo]

Something definitely wrong with the srpm.

A straight "rpm -ivv php-5.3.5-1.art.src.rpm" on a fresh download fails as well with the same "MD5 sum mismatch" message.

[scott]

quick mock primer:

mock -r <distro> <src.rpm>

example:
mock -r epel-5-i386 foo.src.rpm

Those MD5 mismatches are caused by the newer rpm system in fedora 14+ (which some of the build nodes here are) and running them with mock on an older system. What I normally do is rpm -Uvh --nomd5 whatever.src.rpm, and then rpmbuild -bs whatever.spec on the native OS. Theres a way to do this using mock too, but you still need to install it and its just faster to re-archive the src.rpm that way.

[dayo]

Thanks for the primer.

"default" in "mock -r default ..." is symlinked to the centos cfg file.

Anyway, with the supplied build not working as well as the MD5 check sum issue and stuff, I have hit a road block with the ART 5.3 branch.

At least I now have clarity on the status and can decide how to proceed.

Thanks.

[dayo]

OK resolved by using the RemiCollet Repo which has fpm built.

Loathe to mix and match repos but had on other choice.

I looked at the spec files from both here and there and noticed that while they were very similar (seems ART forked from that to start with) some of the patches have been iterated in the Remi spec file.

# Build fixes
Patch1: php-5.3.4-gnusrc.patch v Patch1: php-5.3.3-gnusrc.patch
Patch8: php-5.3.5-aconf26x.patch v Patch8: php-5.3.3-aconf26x.patch

# Functional changes
Patch44: php-5.3.4-mysql.patch added

# Fixes for test
Patch62: php-5.3.3-tests.patch added

Not sure how relevant these are. Could have tried to amend the ART srpm with these patches to see what gives but decided to take the path of least resistance and went ahead as it only installed php and didn't ask to put anything else on.

Hopefully, you will have the time at some point in the future to take a look at the 5.3 branch and resolve whatever it is that is making it not build all the included components ... maybe after 5.6 comes out.

Anyway, I went ahead because it only