Your message dated Fri, 20 Jan 2017 10:09:25 +0100
with message-id <[email protected]>
and subject line Re: Bug#734379: doesn't set the hooks when creating
collab-maint repositories
has caused the Debian Bug report #734379,
regarding doesn't set the hooks when creating collab-maint repositories
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
734379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734379
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.6.8
Severity: important
File: /usr/bin/gbp-create-remote-repo
Hi,
following the (new) advice on
https://wiki.debian.org/Alioth/Git?action=recall&rev=95#Collab_Maint_project
I used gbp create-remote-repo to create a new collab-maint git
repository. Unfortunately, this tool doesn't set the hooks set by
/git/collab-maint/setup-repository, aka (currently):
# Enable the hook scripts
[ -f hooks/post-update ] || cp hooks/post-update.sample
hooks/post-update
cat >hooks/post-receive <<END
#!/bin/sh
exec /usr/local/bin/git-commit-notice
END
chmod a+x hooks/post-update hooks/post-receive
Without doing the first of both, the https:// url listed on the gitweb
won't work and the repository needs manual fixing afterwards.
I wonder if it'd be possible to delegate the building of the bare
repository to the alioth script and only care about pushing once its
done.
Cheers, OdyX
-- System Information:
Debian Release: jessie/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'),
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages git-buildpackage depends on:
ii devscripts 2.13.9
ii git 1:1.8.5.2-1
ii man-db 2.6.5-3
ii python 2.7.5-5
ii python-dateutil 1.5+dfsg-0.1
ii python-pkg-resources 2.0.2-1
Versions of packages git-buildpackage recommends:
pn cowbuilder <none>
ii pristine-tar 1.30
Versions of packages git-buildpackage suggests:
ii python-notify 0.1.1-3
ii unzip 6.0-10
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Didier,
On Mon, Jan 06, 2014 at 05:46:26PM +0100, Guido Günther wrote:
> On Mon, Jan 06, 2014 at 04:38:35PM +0100, Didier Raboud wrote:
> > Package: git-buildpackage
> > Version: 0.6.8
> > Severity: important
> > File: /usr/bin/gbp-create-remote-repo
> >
> > Hi,
> >
> > following the (new) advice on
> > https://wiki.debian.org/Alioth/Git?action=recall&rev=95#Collab_Maint_project
> > I used gbp create-remote-repo to create a new collab-maint git
> > repository. Unfortunately, this tool doesn't set the hooks set by
> > /git/collab-maint/setup-repository, aka (currently):
> >
> > # Enable the hook scripts
> > [ -f hooks/post-update ] || cp hooks/post-update.sample
> > hooks/post-update
> >
> > cat >hooks/post-receive <<END
> > #!/bin/sh
> > exec /usr/local/bin/git-commit-notice
> > END
> >
> > chmod a+x hooks/post-update hooks/post-receive
>
> The right thing to do in this case would be to invoke
>
> gbp reate-remote-repo --template-dir=/sane/templates/for/collab-maint ...
>
> while /sane/templates/for/collab-maint (on git.debian.org) would contain
> the post-update and post-receive hooks you want. This way we could to
> away with the script and gbp create-remote-repo and git init could just
> use the same templates without manual fiddling.
>
> I'd be happy to help to setup /git/collab-maint/templates/hooks. We
> should then change setup-repository to use this templates as well.
Since setting up the hooks is possible and there was no further feedback
I'm closing this report. In case I can help to make this simpler let me
know. E.g. you can avoid passing --template-dir by using --remote-config
option that will pick up a template from you gbp.conf, similar to:
[remote-config cowbuilder]
template-dir = /home/agx/pkgs/templates
remote-url-pattern = ssh://cowbuilder/~/pkgs/%(pkg)s
Cheers,
-- Guido
--- End Message ---
