config issue with PET for pkg-ruby-extras?

[Cédric Boutillier]

Dear Damyan,

Thank you very much for your answer.

On Fri, Oct 07, 2011 at 07:34:25AM +0300, Damyan Ivanov wrote:
> -=| Cédric Boutillier, 06.10.2011 22:58:32 +0200 |=-
> > #!/bin/sh
> > exec /usr/local/bin/git-commit-notice
> > /home/groups/pet/PET2/pkg-ruby-extras/pet-git-helper update <ruby-package>.git

> The "exec" above should be removed.

> From exec(1):
>   The  exec() family of functions replaces the current process image 
>   with a new process image.

> This means, that the shell running the above script is replaced with 
> another process, running git-commit-notice and the next line (the PET 
> hook) is never run.

What you wrote makes indeed a lot of sense. I thus removed the exec
prefixes.

> There was a script somewhere to force update of a group of 
> repositories, butch would be helpful for bringing them up to date wrt 
> PET. I hope real PET experts would tell its name :)

I found that pet-git-helper could be run with the parmater "update-all".
The .json file is now up-to-date, but still did not change. At least,
most of the problems I mentionned before are still indicated, whereas
solved in the repository.

All the commits presented on
http://pet.debian.net/pkg-ruby-extras/pet.cgi are from before August,
28. This date coincides almost with the date of last modification of
pkg-rubyextras/pet-git-helper. I guess it corresponds to the change from
pet.41-3.org to pet.debian.net. I was wondering if something could have
affected the notification process responsible to the update of the page?

Best wishes,

  Cédric
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pet-devel/attachments/20111007/1e4598d4/attachment.pgp>