subject:"Questions about port revision numbers, portsnap, csup"

Re: Questions about port revision numbers, portsnap, csup

2010-04-20 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joe Auty wrote:
> Greg,
> 
> After applying the update (which I noticed was available immediately
> after my last response to you, sorry about that!), everything is just
> peachy now, or at least not causing the segfaults, thanks!
> 
> Not to sound unappreciative and purely in the spirit of being
> constructive, I'd suggest a little more specificity as far as what a
> "break" is on the commit history. This goofy title was created because
> it didn't occur to me that the break fix committed on April 12 was only
> for compilation. I would suggest specifying whether the break and the
> fix is for compiling, or for the software to work properly
> post-compilation. This would have saved me a little confusion and time.
> 
> 
> Again, you kick ass, in no way do I want this to sound harshly critical,
> I hope this can be taken as purely constructive :)
> 
> Thanks again for your help with this fix!
> 

Hi Joe,

Great, I'm glad to hear that's working for you now.  I do appreciate
your input, re: commit logs.  "Unbreak" is too nebulous, and I'll plan
to add further info like "fixed compiler error" in the future.

I admit we were in a bit of a rush to get various PHP modules building
again after the PHP 5.3.2 update, and I somehow missed the fact that
this one supported 5.3.2 with a new release of itself. I think I'll be
better prepared for this kind of thing in the future!

Regards,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzf7v0sRouByUApARAockAKC61isslQlss2C03zRPbovtBG6H9QCgkOFE
g2xUYqmTQvdFXZibSEgi5A0=
=qfdq
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-20 Thread Joe Auty

Greg,

After applying the update (which I noticed was available immediately
after my last response to you, sorry about that!), everything is just
peachy now, or at least not causing the segfaults, thanks!

Not to sound unappreciative and purely in the spirit of being
constructive, I'd suggest a little more specificity as far as what a
"break" is on the commit history. This goofy title was created because
it didn't occur to me that the break fix committed on April 12 was only
for compilation. I would suggest specifying whether the break and the
fix is for compiling, or for the software to work properly
post-compilation. This would have saved me a little confusion and time.


Again, you kick ass, in no way do I want this to sound harshly critical,
I hope this can be taken as purely constructive :)

Thanks again for your help with this fix!

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-20 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joe Auty wrote:
> Greg Larkin wrote:
>> Joe Auty wrote:
>>> Greg Larkin wrote:
 John Levine wrote:
> I have the same problem, recently upgraded to PHP 5.3.2 and Apache
> was crashing whenever I tried to use a mediawiki page until I
>> commented
> out the apc library.  (Apache is 2.0, Freebsd is still 7.0, if that
> matters.)
>> cd /usr/ports
>> fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
>> patch < pecl-APC-3.1.3p1.diff
> Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
> edited the patch to be www/ rather than devel/ at which point the
> patch applied but make failed due to one of the other patches:
 Hi John,

 Sorry about that bit - I'll check my local development environment.

> ===>  Patching for pecl-APC-3.1.3.p1
> ===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
> 1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
> => Patch patch-apc_sem.c failed to apply cleanly.
> *** Error code 1
 Please run the other commands in my email to move those now-obsolete
 patch files out of the way:

 mkdir /usr/ports/devel/pecl-APC/files/save-patches
 mv /usr/ports/devel/pecl-APC/files/patch-*  \
 /usr/ports/devel/pecl-APC/files/save-patches

 Regards,
 Greg
>>> I just did a search/replace of devel->www in Greg's patch...
>>> It downloaded the beta, but I have compile errors now. Isn't pcre
>>> supposed to be built into PHP 5.3 now?
 In file included from
>> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
 /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No
 such file or directory
 In file included from
>> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
 /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=',
 ',', ';', 'asm' or '__attribute__' before '*' token
>> Hi Joe,
>>
>> PCRE problems are very common after upgrading to 5.3.2.  ale@ added an
>> entry in /usr/ports/UPDATING that recommends uninstalling all
>> PHP-related ports and recompiling, IIRC.  That's the best way to clean
>> out all remnants of the php5-pcre port.
>>
> 
> Yeah, I saw that notice and I've actually done this already... Perhaps I
> missed something, although why would the older version compile before
> applying this patch?

Hi Joe,

My apologies, I went down the wrong path while troubleshooting that
error message.  I later reproduced the same compiler error here and then
committed a fix for it.  If you refresh your ports tree again to get the
latest version of www/pecl-APC, you should be all set.  Let me know if
you run into any problems after that.

Thank you,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzflJ0sRouByUApARAqtGAJ0UPNqW0g83i/W9GEXjdu5RPEu+/gCdGR8a
MBPUq23QNFsF2saB03HpKho=
=a/iE
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-20 Thread Joe Auty

Greg Larkin wrote:
> Joe Auty wrote:
> > Greg Larkin wrote:
> >> John Levine wrote:
> >>> I have the same problem, recently upgraded to PHP 5.3.2 and Apache
> >>> was crashing whenever I tried to use a mediawiki page until I
> commented
> >>> out the apc library.  (Apache is 2.0, Freebsd is still 7.0, if that
> >>> matters.)
>  cd /usr/ports
>  fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
>  patch < pecl-APC-3.1.3p1.diff
> >>> Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
> >>> edited the patch to be www/ rather than devel/ at which point the
> >>> patch applied but make failed due to one of the other patches:
> >> Hi John,
> >>
> >> Sorry about that bit - I'll check my local development environment.
> >>
> >>> ===>  Patching for pecl-APC-3.1.3.p1
> >>> ===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
> >>> 1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
> >>> => Patch patch-apc_sem.c failed to apply cleanly.
> >>> *** Error code 1
> >> Please run the other commands in my email to move those now-obsolete
> >> patch files out of the way:
> >>
> >> mkdir /usr/ports/devel/pecl-APC/files/save-patches
> >> mv /usr/ports/devel/pecl-APC/files/patch-*  \
> >> /usr/ports/devel/pecl-APC/files/save-patches
> >>
> >> Regards,
> >> Greg
> > I just did a search/replace of devel->www in Greg's patch...
>
> > It downloaded the beta, but I have compile errors now. Isn't pcre
> > supposed to be built into PHP 5.3 now?
>
> >> In file included from
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
> >> /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No
> >> such file or directory
> >> In file included from
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
> >> /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=',
> >> ',', ';', 'asm' or '__attribute__' before '*' token
>
> Hi Joe,
>
> PCRE problems are very common after upgrading to 5.3.2.  ale@ added an
> entry in /usr/ports/UPDATING that recommends uninstalling all
> PHP-related ports and recompiling, IIRC.  That's the best way to clean
> out all remnants of the php5-pcre port.
>

Yeah, I saw that notice and I've actually done this already... Perhaps I
missed something, although why would the older version compile before
applying this patch?


> Regards,
> Greg

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


-- 
Joe Auty, NetMusician
NetMusician helps musicians, bands and artists create beautiful,
professional, custom designed, career-essential websites that are easy
to maintain and to integrate with popular social networks.
www.netmusician.org 
j...@netmusician.org 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

John R. Levine wrote:
> fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
> patch < pecl-APC-3.1.3p1.diff
 Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
 edited the patch to be www/ rather than devel/ at which point the
 patch applied but make failed due to one of the other patches:
>>>
>>> Hi John,
>>>
>>> Sorry about that bit - I'll check my local development environment.
>>>
 ===>  Patching for pecl-APC-3.1.3.p1
 ===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
 1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
 => Patch patch-apc_sem.c failed to apply cleanly.
 *** Error code 1
>>>
>>> Please run the other commands in my email to move those now-obsolete
>>> patch files out of the way:
>>>
>>> mkdir /usr/ports/devel/pecl-APC/files/save-patches
>>> mv /usr/ports/devel/pecl-APC/files/patch-*  \
>>> /usr/ports/devel/pecl-APC/files/save-patches
> 
> Again, I had to change /devel to /www, but having done that, it compiled
> and installed.  Based on 30 seconds of testing, the mediawiki stuff that
> used to crash now seems to work, phpinfo confirms that apc 3.1.3p1 is
> active.
> 
> Adjust the paths and ship it, it's vastly better than the status quo.
> 
> R's,
> John
> 
> PS: Thanks!

Hi John,

I just committed the 3.1.3p1 version of APC to the ports tree, and that
one should work with PHP 5.3.2, as you noted.

Thank you,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzQ5g0sRouByUApARAhptAKCPCZVhZ3brpxkcdhlHMAvgMUPZAgCfaqc3
3MnVbhQIyeIhb1cMV8DTMrw=
=MnWU
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread RW

On Mon, 19 Apr 2010 19:04:05 +0100
Matthew Seaman  wrote:

> You could change to using csup rather than portsnap, but be aware that
> this pretty much means scrubbing all of your portsnap state.  Indeed,
> for best results with csup, starting with an empty /usr/ports might be
> an idea -- I don't think that will be necessary, but I can't be
> certain. If you switch to csup, switching back to portsnap will
> definitely require you to re-download the ports tree and replace
> everything you had installed via csup.

As I understand it portsnap's state is split between /var and the ports
directory itself. The former contains the snapshot and its metadata, and
the latter contains the metadata for that specific copy of the tree.
Using csup shouldn't affect the stuff under /var, but it invalidates
the metadata in the ports directory.

If you return to portsnap after using csup you should only need to do a
new "extract" which overwrite the individual files and each
"origin-directory", and generates the local portsnap metadata. If you
are paranoid (or want to clean-up extra cruft) delete the ports
directory first.

Going the other way the tree should really be deleted and redownloaded
to ensure that csup keeps track of all the patch files. That's more of
a long-term issue though.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joe Auty wrote:
> Greg Larkin wrote:
>> John Levine wrote:
>>> I have the same problem, recently upgraded to PHP 5.3.2 and Apache
>>> was crashing whenever I tried to use a mediawiki page until I commented
>>> out the apc library.  (Apache is 2.0, Freebsd is still 7.0, if that
>>> matters.)
 cd /usr/ports
 fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
 patch < pecl-APC-3.1.3p1.diff
>>> Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
>>> edited the patch to be www/ rather than devel/ at which point the
>>> patch applied but make failed due to one of the other patches:
>> Hi John,
>>
>> Sorry about that bit - I'll check my local development environment.
>>
>>> ===>  Patching for pecl-APC-3.1.3.p1
>>> ===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
>>> 1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
>>> => Patch patch-apc_sem.c failed to apply cleanly.
>>> *** Error code 1
>> Please run the other commands in my email to move those now-obsolete
>> patch files out of the way:
>>
>> mkdir /usr/ports/devel/pecl-APC/files/save-patches
>> mv /usr/ports/devel/pecl-APC/files/patch-*  \
>> /usr/ports/devel/pecl-APC/files/save-patches
>>
>> Regards,
>> Greg
> 
> I just did a search/replace of devel->www in Greg's patch...
> 
> It downloaded the beta, but I have compile errors now. Isn't pcre
> supposed to be built into PHP 5.3 now?
> 
>> In file included from /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
>> /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No
>> such file or directory
>> In file included from /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
>> /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=',
>> ',', ';', 'asm' or '__attribute__' before '*' token

Hi Joe,

PCRE problems are very common after upgrading to 5.3.2.  ale@ added an
entry in /usr/ports/UPDATING that recommends uninstalling all
PHP-related ports and recompiling, IIRC.  That's the best way to clean
out all remnants of the php5-pcre port.

Regards,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzLnt0sRouByUApARAj71AJ9YUquDrbHDSwg3owfZ8eF6hQfzUgCgqjxW
wI00gh64HXkDFRYXGe7AwqI=
=Y9/g
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread John R. Levine


fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
patch < pecl-APC-3.1.3p1.diff

Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
edited the patch to be www/ rather than devel/ at which point the
patch applied but make failed due to one of the other patches:


Hi John,

Sorry about that bit - I'll check my local development environment.


===>  Patching for pecl-APC-3.1.3.p1
===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
=> Patch patch-apc_sem.c failed to apply cleanly.
*** Error code 1


Please run the other commands in my email to move those now-obsolete
patch files out of the way:

mkdir /usr/ports/devel/pecl-APC/files/save-patches
mv /usr/ports/devel/pecl-APC/files/patch-*  \
/usr/ports/devel/pecl-APC/files/save-patches


Again, I had to change /devel to /www, but having done that, it compiled 
and installed.  Based on 30 seconds of testing, the mediawiki stuff that 
used to crash now seems to work, phpinfo confirms that apc 3.1.3p1 is 
active.


Adjust the paths and ship it, it's vastly better than the status quo.

R's,
John

PS: Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Joe Auty

Greg Larkin wrote:
> John Levine wrote:
> > I have the same problem, recently upgraded to PHP 5.3.2 and Apache
> > was crashing whenever I tried to use a mediawiki page until I commented
> > out the apc library.  (Apache is 2.0, Freebsd is still 7.0, if that
> > matters.)
>
> >> cd /usr/ports
> >> fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
> >> patch < pecl-APC-3.1.3p1.diff
> > Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
> > edited the patch to be www/ rather than devel/ at which point the
> > patch applied but make failed due to one of the other patches:
>
> Hi John,
>
> Sorry about that bit - I'll check my local development environment.
>
> > ===>  Patching for pecl-APC-3.1.3.p1
> > ===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
> > 1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
> > => Patch patch-apc_sem.c failed to apply cleanly.
> > *** Error code 1
>
> Please run the other commands in my email to move those now-obsolete
> patch files out of the way:
>
> mkdir /usr/ports/devel/pecl-APC/files/save-patches
> mv /usr/ports/devel/pecl-APC/files/patch-*  \
> /usr/ports/devel/pecl-APC/files/save-patches
>
> Regards,
> Greg

I just did a search/replace of devel->www in Greg's patch...

It downloaded the beta, but I have compile errors now. Isn't pcre
supposed to be built into PHP 5.3 now?

> In file included from /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
> /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No
> such file or directory
> In file included from /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:43:
> /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=',
> ',', ';', 'asm' or '__attribute__' before '*' token
> /usr/local/include/php/ext/pcre/php_pcre.h:38: error: expected '=',
> ',', ';', 'asm' or '__attribute__' before '*' token
> /usr/local/include/php/ext/pcre/php_pcre.h:44: error: expected
> specifier-qualifier-list before 'pcre'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:368: error: expected
> specifier-qualifier-list before 'pcre'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c: In function
> 'apc_regex_compile_array':
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:429: error: 'apc_regex'
> has no member named 'preg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:429: error: 'apc_regex'
> has no member named 'preg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:430: error: 'apc_regex'
> has no member named 'nreg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:430: error: 'apc_regex'
> has no member named 'nreg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c: In function
> 'apc_regex_match_array':
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:462: error: 'apc_regex'
> has no member named 'preg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:462: error: 'apc_regex'
> has no member named 'preg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:463: error: 'apc_regex'
> has no member named 'nreg'
> /usr/ports/www/pecl-APC/work/APC-3.1.3p1/apc.c:463: error: 'apc_regex'
> has no member named 'nreg'
> *** Error code 1
>
> Stop in /usr/ports/www/pecl-APC/work/APC-3.1.3p1.
> *** Error code 1
>
> Stop in /usr/ports/www/pecl-APC.
> *** Error code 1
>
> Stop in /usr/ports/www/pecl-APC.

Feel free to change the subject of this message if that would be
appropriate...

I did notice the full PHP 5.3 support in APC 3.1.3, but I figured that
the "initial support" in 3.0.19 was sufficient. I was obviously wrong!

http://pecl.php.net/package-changelog.php?package=APC



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

John Levine wrote:
> I have the same problem, recently upgraded to PHP 5.3.2 and Apache
> was crashing whenever I tried to use a mediawiki page until I commented
> out the apc library.  (Apache is 2.0, Freebsd is still 7.0, if that
> matters.)
> 
>> cd /usr/ports
>> fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
>> patch < pecl-APC-3.1.3p1.diff
> 
> Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
> edited the patch to be www/ rather than devel/ at which point the
> patch applied but make failed due to one of the other patches:

Hi John,

Sorry about that bit - I'll check my local development environment.

> 
> ===>  Patching for pecl-APC-3.1.3.p1
> ===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
> 1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
> => Patch patch-apc_sem.c failed to apply cleanly.
> *** Error code 1

Please run the other commands in my email to move those now-obsolete
patch files out of the way:

mkdir /usr/ports/devel/pecl-APC/files/save-patches
mv /usr/ports/devel/pecl-APC/files/patch-*  \
/usr/ports/devel/pecl-APC/files/save-patches

Regards,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzKoz0sRouByUApARApGpAKCCtODOcSfyhAQoU8YlrcRU37caKQCgiNpT
psKkzZi2vyAvJFzpJTSpZCM=
=sHLu
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread John Levine

I have the same problem, recently upgraded to PHP 5.3.2 and Apache
was crashing whenever I tried to use a mediawiki page until I commented
out the apc library.  (Apache is 2.0, Freebsd is still 7.0, if that
matters.)

>cd /usr/ports
>fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
>patch < pecl-APC-3.1.3p1.diff

Didn't work, because pecl-APC is www/pecl-APC, not devel/pecl-APC.  I
edited the patch to be www/ rather than devel/ at which point the
patch applied but make failed due to one of the other patches:

===>  Patching for pecl-APC-3.1.3.p1
===>  Applying FreeBSD patches for pecl-APC-3.1.3.p1
1 out of 2 hunks failed--saving rejects to apc_sem.c.rej
=> Patch patch-apc_sem.c failed to apply cleanly.
*** Error code 1


Here's what's in apc_sem.c.rej


***
*** 82,93 
  }
  }
  
- if ((semid = semget(key, 1, IPC_CREAT | IPC_EXCL | perms)) >= 0) {
  /* sempahore created for the first time, initialize now */
  arg.val = initval;
  if (semctl(semid, 0, SETVAL, arg) < 0) {
  apc_eprint("apc_sem_create: semctl(%d,...) failed:", semid);
  }
  }
  else if (errno == EEXIST) {
  /* sempahore already exists, don't initialize */
--- 82,97 
  }
  }
  
+ if ((semid = semget(key, 2, IPC_CREAT | IPC_EXCL | perms)) >= 0) {
  /* sempahore created for the first time, initialize now */
  arg.val = initval;
  if (semctl(semid, 0, SETVAL, arg) < 0) {
  apc_eprint("apc_sem_create: semctl(%d,...) failed:", semid);
  }
+ arg.val = getpid();
+ if (semctl(semid, 1, SETVAL, arg) < 0) {
+ apc_eprint("apc_sem_create: semctl(%d,...) failed:", semid);
+ }
  }
  else if (errno == EEXIST) {
  /* sempahore already exists, don't initialize */




R's,
John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joe Auty wrote:
> Greg Larkin wrote:
>> Does pecl-APC not compile, or is it functionally broken after compiling
>> succesfully?
> It compiles, but once loaded it causes either Apache child processes to
> segfault or abort traps depending on where the extension is listed in my
> extensions.ini file. Apache itself is running fine, I don't have these
> problems on non-PHP pages. Commenting out the apc.so in extensions.ini
> makes Apache work again. I haven't done an extensive job of looking for
> PHP extension conflicts just yet, but I've slowly been testing my PHP
> extensions one by one on a test machine. I got as far as this:
> 
>> extension=session.so
>> extension=mysql.so
>> extension=json.so
>> extension=curl.so
>> extension=openssl.so
>> ;extension=apc.so
> 
> apc.so is commented out because this was the point where I realized that
> it was the culprit after this upgrade. So, I'd imagine that APC has some
> sort of problem with PHP 5.3, or possibly one of these extensions?
> 
>>> 2) Is there a way to look at the commit history of the ports I have
>>> installed in /usr/ports so that I can verify whether or not I have the
>>> revision with this particular fix? Thus far I've been relying on
>>> freshports.org and trusting that doing a portsnap will always fetch the
>>> latest stuff visible on freshports.org, but now I'm not so sure...
>> Is /usr/ports/www/pecl-APC/files/patch-php_apc.c present on your
>> machine?  If so, then you have the latest commit.
>>
> Yeah, I have that file... I didn't know that the patch fixed compiling
> problems, that was never my problem.
> 
> Perhaps PHP 5.3 needs different APC related php.ini options or
> something? I'm generally pretty lazy about doing a diff between the
> stock config files and my own...
> 
> I've been trying to no avail to get a good backtrace of my problem,
> would that be useful to anybody? Should I keep at this?
> 
> 
> Thanks for your help Greg!

Hi Joe,

I believe this is a compatibility problem with the 3.0.x version of the
APC extension and PHP 5.3.2.  I committed the compiler fix to CVS on
4/12 to get APC building again.  I did this at the request of portmgr
after the PHP 5.3.2 upgrade, but I didn't go far enough testing the changes.

There is a beta version of APC available (3.1.3p1) that is PHP
5.3.2-compatible, and I have prepared a diff for you to try.  Can you
apply this file to your ports tree and rebuild like so:

cd /usr/ports
fetch http://people.freebsd.org/~glarkin/diffs/pecl-APC-3.1.3p1.diff
patch < pecl-APC-3.1.3p1.diff
mkdir /usr/ports/devel/pecl-APC/files/save-patches
mv /usr/ports/devel/pecl-APC/files/patch-*  \
/usr/ports/devel/pecl-APC/files/save-patches
cd devel/pecl-APC
make deinstall
make clean
make install

Let me know how that goes,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzJ5k0sRouByUApARAihmAKCvwVT6DVUR7kNpI/HDc/rfJm197wCfYnYT
FRNXpElWFPeLdsDrc9CAA5M=
=/0Yu
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Matthew Seaman

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 19/04/2010 18:10:36, Joe Auty wrote:
> Hello,
> 
> I've identified my pecl-APC install as being broken after upgrading to
> PHP 5.3.2. According to the commit history listed here:
> http://www.freshports.org/www/pecl-APC/ there is a fix out. However,
> doing a portsnap fetch update does not seem to fetch this latest
> revision to this port, after doing my portsnap it shows no updates are
> available for the port although I'm pretty certain that I last
> portsnapped before April 12. I'm assuming that portsnap only grabs a new
> version of the portrevision number has been bumped?
> 
> My questions:
> 
> 1) If I were to csup my ports tree to force a fetch of this update,
> would this break portsnap?
> 
> 2) Is there a way to look at the commit history of the ports I have
> installed in /usr/ports so that I can verify whether or not I have the
> revision with this particular fix? Thus far I've been relying on
> freshports.org and trusting that doing a portsnap will always fetch the
> latest stuff visible on freshports.org, but now I'm not so sure...
> 
> 3) Shouldn't the portrevision number be bumped whenever there is an
> update? I always assumed that the _x suffixes indicated a portrevision
> bump. Why was it not bumped for this pecl-APC fix? Human error? Is there
> any other way I can force the download of this port, or is csup my best bet?

The only change in the last update (12th April) to pecl-APC was the
addition of files/patch-php_apc.c

That's good in the sense that you can simply download that file from CVS
and put it into the files sub directory if it isn't there already and
then force a rebuild of the port to get the benefit.  Note that running
portsnap after doing that could blow away the patch file if portsnap
really is missing it.  However, I suspect that it is known to portsnap
and that something else is wrong with your build.

You could change to using csup rather than portsnap, but be aware that
this pretty much means scrubbing all of your portsnap state.  Indeed,
for best results with csup, starting with an empty /usr/ports might be
an idea -- I don't think that will be necessary, but I can't be certain.
 If you switch to csup, switching back to portsnap will definitely
require you to re-download the ports tree and replace everything you had
installed via csup.  In any case, I don't think the problem you're
experiencing is sufficient justification for making such a sweeping
change -- both portsnap and csup are effective at what they do, and
losing a whole file would be a pretty disastrous failure.

Since the port revision number wasn't bumped on 12th April, you'll have
to check the oldest date on files inside /var/db/pkg/pecl-APC-3.0.19 --
don't check the date on the directory itself: the normal operation of
portupgrade(1) will modify it.

The rule about PORTREVISION numbers is that they should be applied when
the update causes a material difference in the state of the installed
port.  Fixing a problem that stops the port compiling at all doesn't
usually count: some maintainers/committers might bump portrevision,
others wouldn't.

Cheers,

Matthew

- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvMmxUACgkQ8Mjk52CukIyHJACfVrNIjL8p/CgY59e6S/xo+jX4
sNoAn2+7bEKxr42Ta5Jn7zbWEnKz5HUZ
=Fevg
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Joe Auty

Greg Larkin wrote:
>
> Does pecl-APC not compile, or is it functionally broken after compiling
> succesfully?
It compiles, but once loaded it causes either Apache child processes to
segfault or abort traps depending on where the extension is listed in my
extensions.ini file. Apache itself is running fine, I don't have these
problems on non-PHP pages. Commenting out the apc.so in extensions.ini
makes Apache work again. I haven't done an extensive job of looking for
PHP extension conflicts just yet, but I've slowly been testing my PHP
extensions one by one on a test machine. I got as far as this:

> extension=session.so
> extension=mysql.so
> extension=json.so
> extension=curl.so
> extension=openssl.so
> ;extension=apc.so

apc.so is commented out because this was the point where I realized that
it was the culprit after this upgrade. So, I'd imagine that APC has some
sort of problem with PHP 5.3, or possibly one of these extensions?

>
> > 2) Is there a way to look at the commit history of the ports I have
> > installed in /usr/ports so that I can verify whether or not I have the
> > revision with this particular fix? Thus far I've been relying on
> > freshports.org and trusting that doing a portsnap will always fetch the
> > latest stuff visible on freshports.org, but now I'm not so sure...
>
> Is /usr/ports/www/pecl-APC/files/patch-php_apc.c present on your
> machine?  If so, then you have the latest commit.
>
Yeah, I have that file... I didn't know that the patch fixed compiling
problems, that was never my problem.

Perhaps PHP 5.3 needs different APC related php.ini options or
something? I'm generally pretty lazy about doing a diff between the
stock config files and my own...

I've been trying to no avail to get a good backtrace of my problem,
would that be useful to anybody? Should I keep at this?

Thanks for your help Greg!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Greg Larkin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Joe Auty wrote:
> Hello,

Hi Joe,

> 
> I've identified my pecl-APC install as being broken after upgrading to
> PHP 5.3.2. 

Does pecl-APC not compile, or is it functionally broken after compiling
succesfully?

According to the commit history listed here:
> http://www.freshports.org/www/pecl-APC/ there is a fix out. However,
> doing a portsnap fetch update does not seem to fetch this latest
> revision to this port, after doing my portsnap it shows no updates are
> available for the port although I'm pretty certain that I last
> portsnapped before April 12. I'm assuming that portsnap only grabs a new
> version of the portrevision number has been bumped?

No, portsnap builds new updates based on the latest bits committed to
the ports tree CVS repository, no matter if PORTREVISION has been bumped
or not.

> 
> My questions:
> 
> 1) If I were to csup my ports tree to force a fetch of this update,
> would this break portsnap?

Yes, you would have to do "portsnap fetch extract" again at a later time.

> 
> 2) Is there a way to look at the commit history of the ports I have
> installed in /usr/ports so that I can verify whether or not I have the
> revision with this particular fix? Thus far I've been relying on
> freshports.org and trusting that doing a portsnap will always fetch the
> latest stuff visible on freshports.org, but now I'm not so sure...

Is /usr/ports/www/pecl-APC/files/patch-php_apc.c present on your
machine?  If so, then you have the latest commit.

> 
> 3) Shouldn't the portrevision number be bumped whenever there is an
> update? I always assumed that the _x suffixes indicated a portrevision
> bump. Why was it not bumped for this pecl-APC fix? Human error? Is there
> any other way I can force the download of this port, or is csup my best bet?

No, PORTREVISION is only bumped in certain circumstances.  In this case,
PHP 5.3.2 caused compiler errors for pecl-APC.  Committing a change to
the port to get it to compile does not necessitate a PORTREVISION bump.
 You can find more information here:
http://www.freebsd.org/doc/en/books/porters-handbook/book.html#MAKEFILE-NAMING-REVEPOCH

> 
> 
> 
> 
> 

Regards,
Greg
- --
Greg Larkin

http://www.FreeBSD.org/   - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/sourcehosting/ - Follow me, follow you
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFLzJNj0sRouByUApARAoM+AKC/vBEWijwa0DNF2riicpmzsGnNfACeLjaS
kxmePUMG3CnGuwPwrrZZvCI=
=9JNL
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Questions about port revision numbers, portsnap, csup

2010-04-19 Thread Joe Auty

Hello,

I've identified my pecl-APC install as being broken after upgrading to
PHP 5.3.2. According to the commit history listed here:
http://www.freshports.org/www/pecl-APC/ there is a fix out. However,
doing a portsnap fetch update does not seem to fetch this latest
revision to this port, after doing my portsnap it shows no updates are
available for the port although I'm pretty certain that I last
portsnapped before April 12. I'm assuming that portsnap only grabs a new
version of the portrevision number has been bumped?

My questions:

1) If I were to csup my ports tree to force a fetch of this update,
would this break portsnap?

2) Is there a way to look at the commit history of the ports I have
installed in /usr/ports so that I can verify whether or not I have the
revision with this particular fix? Thus far I've been relying on
freshports.org and trusting that doing a portsnap will always fetch the
latest stuff visible on freshports.org, but now I'm not so sure...

3) Shouldn't the portrevision number be bumped whenever there is an
update? I always assumed that the _x suffixes indicated a portrevision
bump. Why was it not bumped for this pecl-APC fix? Human error? Is there
any other way I can force the download of this port, or is csup my best bet?





-- 
Joe Auty, NetMusician
NetMusician helps musicians, bands and artists create beautiful,
professional, custom designed, career-essential websites that are easy
to maintain and to integrate with popular social networks.
www.netmusician.org 
j...@netmusician.org 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Re: Questions about port revision numbers, portsnap, csup

Questions about port revision numbers, portsnap, csup

16 matches

Site Navigation

Mail list logo

Footer information