[php-maint] An automatic script to build PEAR packages
thomas at goirand.fr
Wed Dec 30 04:56:07 UTC 2009
Thanks for your answer.
Raphael Geissert wrote:
>> Let's say if the workflow is that I create or update php package, then I
>> send a mail with the link of my .dsc file on this list, then one of the
>> member of the pkg-php team review it and upload, instead of just asking
>> -mentors, would you think it's the way to go?
> The procedure I'd prefer would be:
> * You prepare the package, if you don't have a sponsor you send a RFS
> to here and -mentors
> And then if I say I'll sponsor it, I review it and give you feedback
> for you to improve the package over and over again until it is ready.
> Finally, I upload it and when there are updates (bug fixes, new
> version, etc) you contact me.
What's the point send a request to BOTH -mentors and here? Shouldn't I
just ask here, and if you don't want to, I ask someone else? I believe
it's better to ask people I know in Debian, than just ask in -mentors
for nothing. In my experience, posting to -mentors is often useless as
nobody would pickup the package 80% of the time, if you don't know
anyone. I'd rather ask a specific person that I know has a chance to
accept each time, I know it works better.
Also, I have an AM that has been assigned to me, so I hope all this
sponsoring needs will soon be over. I'll do my best not to be soft
rejected because of my stupidity this time! :)
>> Now, few years ago, I applied on Alioth to be a member of the php team,
>> but I guess because I didn't introduce myself properly, I got rejected
>> after MONTHS. Now I understand better that communication in Debian is
>> very important. Would you guys accept me this time? I do believe that I
>> made quite some progress with my packaging skills too ... :)
> As long as your intentions are explained there's no reason to reject anyone.
> Please request to be added via the alioth project page.
Ok, I will.
>>> Send me an email with links to the .dsc of the PEAR packages and I'll
>>> check them.
>> Sure! Here's the ones to check for update:
> Ok, will check them. When do you plan to update php-net-ping?
That's done. As of today, ALL of my php-* packages that needed update
(because of a new version of the upstream version) are in our Debian
repositories and mirror. Obviously, php-net-ping is in:
It seems that the way it has been patched in the upstream version is
different from the one by the security team. The upstream uses
escapeshellcmd(), while the security team patch uses escapeshellarg().
Does anyone has comments to do on this?
>> And here's some NEW packages (no ITP yet, if you tell me they are in
>> good shape, I'll ask for an ITP and let you know (yes I know, I should
>> the the opposite way... :) )):
> Let me know when you've updated them to include the ITP bug closer.
Done as well. All packages are lintian clean.
>> The goal of the one just above is to have php-text-captcha (and all its
>> dependencies) working as I need a good captcha system. I didn't try it
>> yet, so I'm not sure yet if this captcha is efficient. Has any of you
>> tried, and know if it's worth the effort to have it packaged in Debian?
>> I may give up if someone says I should, or if there is a better alternative.
> It's been a while since I've last used it. Nowadays I would use
> reCAPTCHA instead.
Is that a hosted service? Meaning that you need to register on the
website, and rely on them? If so, then I don't like it at all. I don't
see why I should rely on something external, even if it looks better.
> We have svn and git repositories setup and in use.
> Check the way the current packages are organised in the repositories.
I didn't find the repository. Can you give me the URL of the git and
gitweb of it?
More information about the pkg-php-maint