How to use debuild hooks (--signing-hook-foo etc)
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
The man page isn't clear on that.
How would I use a signing hook? Especially using the parameter without the config file.
What is the meaning of foo
in the documentation? For example in --signing-hook-foo
? Do I replace foo
with my bash script? The would seem very odd and against all conventions that I know.
For example, would this be the way you are supposed to use it?
echo "#!/usr/bin/env bash" > /signing-hook-script.sh
echo "(pwd; ls -la; tree /) > /output.txt" >> /signing-hook-script.sh
chmod +x /signing-hook-script.sh
debuild -i -S --signing-hook-/signing-hook-script.sh
debian dpkg hook
add a comment |
up vote
3
down vote
favorite
The man page isn't clear on that.
How would I use a signing hook? Especially using the parameter without the config file.
What is the meaning of foo
in the documentation? For example in --signing-hook-foo
? Do I replace foo
with my bash script? The would seem very odd and against all conventions that I know.
For example, would this be the way you are supposed to use it?
echo "#!/usr/bin/env bash" > /signing-hook-script.sh
echo "(pwd; ls -la; tree /) > /output.txt" >> /signing-hook-script.sh
chmod +x /signing-hook-script.sh
debuild -i -S --signing-hook-/signing-hook-script.sh
debian dpkg hook
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
The man page isn't clear on that.
How would I use a signing hook? Especially using the parameter without the config file.
What is the meaning of foo
in the documentation? For example in --signing-hook-foo
? Do I replace foo
with my bash script? The would seem very odd and against all conventions that I know.
For example, would this be the way you are supposed to use it?
echo "#!/usr/bin/env bash" > /signing-hook-script.sh
echo "(pwd; ls -la; tree /) > /output.txt" >> /signing-hook-script.sh
chmod +x /signing-hook-script.sh
debuild -i -S --signing-hook-/signing-hook-script.sh
debian dpkg hook
The man page isn't clear on that.
How would I use a signing hook? Especially using the parameter without the config file.
What is the meaning of foo
in the documentation? For example in --signing-hook-foo
? Do I replace foo
with my bash script? The would seem very odd and against all conventions that I know.
For example, would this be the way you are supposed to use it?
echo "#!/usr/bin/env bash" > /signing-hook-script.sh
echo "(pwd; ls -la; tree /) > /output.txt" >> /signing-hook-script.sh
chmod +x /signing-hook-script.sh
debuild -i -S --signing-hook-/signing-hook-script.sh
debian dpkg hook
debian dpkg hook
edited Nov 21 at 13:02
Stephen Kitt
158k23346423
158k23346423
asked Nov 21 at 12:57
Forivin
195113
195113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Well spotted, the manpage is incorrect. debuild --help
shows the appropriate syntax:
--dpkg-buildpackage-hook=HOOK
--clean-hook=HOOK
--dpkg-source-hook=HOOK
--build-hook=HOOK
--binary-hook=HOOK
--dpkg-genchanges-hook=HOOK
--final-clean-hook=HOOK
--lintian-hook=HOOK
--signing-hook=HOOK
--post-dpkg-buildpackage-hook=HOOK
These hooks run at the various stages of the
dpkg-buildpackage run. For details, see the
debuild manpage. They default to nothing, and
can be reset to nothing with --foo-hook=''
So your example would be
debuild --signing-hook=/signing-hook-script.sh -i -S
(debuild
options must be specified before dpkg-buildpackage
options).
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
Clone the repository (debcheckout devscripts
), editscripts/debuild.1
, and submit the resulting patch usingreportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)
– Stephen Kitt
Nov 21 at 13:35
Hm, I getdpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when runningdebuild -i -S --signing-hook=/signing-hook-script.sh
.
– Forivin
Nov 21 at 13:39
1
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Thank you, that worked!
– Forivin
Nov 21 at 14:52
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Well spotted, the manpage is incorrect. debuild --help
shows the appropriate syntax:
--dpkg-buildpackage-hook=HOOK
--clean-hook=HOOK
--dpkg-source-hook=HOOK
--build-hook=HOOK
--binary-hook=HOOK
--dpkg-genchanges-hook=HOOK
--final-clean-hook=HOOK
--lintian-hook=HOOK
--signing-hook=HOOK
--post-dpkg-buildpackage-hook=HOOK
These hooks run at the various stages of the
dpkg-buildpackage run. For details, see the
debuild manpage. They default to nothing, and
can be reset to nothing with --foo-hook=''
So your example would be
debuild --signing-hook=/signing-hook-script.sh -i -S
(debuild
options must be specified before dpkg-buildpackage
options).
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
Clone the repository (debcheckout devscripts
), editscripts/debuild.1
, and submit the resulting patch usingreportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)
– Stephen Kitt
Nov 21 at 13:35
Hm, I getdpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when runningdebuild -i -S --signing-hook=/signing-hook-script.sh
.
– Forivin
Nov 21 at 13:39
1
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Thank you, that worked!
– Forivin
Nov 21 at 14:52
add a comment |
up vote
2
down vote
accepted
Well spotted, the manpage is incorrect. debuild --help
shows the appropriate syntax:
--dpkg-buildpackage-hook=HOOK
--clean-hook=HOOK
--dpkg-source-hook=HOOK
--build-hook=HOOK
--binary-hook=HOOK
--dpkg-genchanges-hook=HOOK
--final-clean-hook=HOOK
--lintian-hook=HOOK
--signing-hook=HOOK
--post-dpkg-buildpackage-hook=HOOK
These hooks run at the various stages of the
dpkg-buildpackage run. For details, see the
debuild manpage. They default to nothing, and
can be reset to nothing with --foo-hook=''
So your example would be
debuild --signing-hook=/signing-hook-script.sh -i -S
(debuild
options must be specified before dpkg-buildpackage
options).
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
Clone the repository (debcheckout devscripts
), editscripts/debuild.1
, and submit the resulting patch usingreportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)
– Stephen Kitt
Nov 21 at 13:35
Hm, I getdpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when runningdebuild -i -S --signing-hook=/signing-hook-script.sh
.
– Forivin
Nov 21 at 13:39
1
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Thank you, that worked!
– Forivin
Nov 21 at 14:52
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Well spotted, the manpage is incorrect. debuild --help
shows the appropriate syntax:
--dpkg-buildpackage-hook=HOOK
--clean-hook=HOOK
--dpkg-source-hook=HOOK
--build-hook=HOOK
--binary-hook=HOOK
--dpkg-genchanges-hook=HOOK
--final-clean-hook=HOOK
--lintian-hook=HOOK
--signing-hook=HOOK
--post-dpkg-buildpackage-hook=HOOK
These hooks run at the various stages of the
dpkg-buildpackage run. For details, see the
debuild manpage. They default to nothing, and
can be reset to nothing with --foo-hook=''
So your example would be
debuild --signing-hook=/signing-hook-script.sh -i -S
(debuild
options must be specified before dpkg-buildpackage
options).
Well spotted, the manpage is incorrect. debuild --help
shows the appropriate syntax:
--dpkg-buildpackage-hook=HOOK
--clean-hook=HOOK
--dpkg-source-hook=HOOK
--build-hook=HOOK
--binary-hook=HOOK
--dpkg-genchanges-hook=HOOK
--final-clean-hook=HOOK
--lintian-hook=HOOK
--signing-hook=HOOK
--post-dpkg-buildpackage-hook=HOOK
These hooks run at the various stages of the
dpkg-buildpackage run. For details, see the
debuild manpage. They default to nothing, and
can be reset to nothing with --foo-hook=''
So your example would be
debuild --signing-hook=/signing-hook-script.sh -i -S
(debuild
options must be specified before dpkg-buildpackage
options).
edited Nov 21 at 13:45
answered Nov 21 at 13:01
Stephen Kitt
158k23346423
158k23346423
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
Clone the repository (debcheckout devscripts
), editscripts/debuild.1
, and submit the resulting patch usingreportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)
– Stephen Kitt
Nov 21 at 13:35
Hm, I getdpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when runningdebuild -i -S --signing-hook=/signing-hook-script.sh
.
– Forivin
Nov 21 at 13:39
1
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Thank you, that worked!
– Forivin
Nov 21 at 14:52
add a comment |
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
Clone the repository (debcheckout devscripts
), editscripts/debuild.1
, and submit the resulting patch usingreportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)
– Stephen Kitt
Nov 21 at 13:35
Hm, I getdpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when runningdebuild -i -S --signing-hook=/signing-hook-script.sh
.
– Forivin
Nov 21 at 13:39
1
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Thank you, that worked!
– Forivin
Nov 21 at 14:52
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
How would one go about correcting the issue with the manpage?
– kemotep
Nov 21 at 13:21
Clone the repository (
debcheckout devscripts
), edit scripts/debuild.1
, and submit the resulting patch using reportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)– Stephen Kitt
Nov 21 at 13:35
Clone the repository (
debcheckout devscripts
), edit scripts/debuild.1
, and submit the resulting patch using reportbug
. (If any of that isn’t clear, ask and I’ll expand my answer.)– Stephen Kitt
Nov 21 at 13:35
Hm, I get
dpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when running debuild -i -S --signing-hook=/signing-hook-script.sh
.– Forivin
Nov 21 at 13:39
Hm, I get
dpkg-buildpackage: error: unknown option or argument --signing-hook=/signing-hook-script.sh
when running debuild -i -S --signing-hook=/signing-hook-script.sh
.– Forivin
Nov 21 at 13:39
1
1
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Ah yes, see my update.
– Stephen Kitt
Nov 21 at 13:45
Thank you, that worked!
– Forivin
Nov 21 at 14:52
Thank you, that worked!
– Forivin
Nov 21 at 14:52
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f483197%2fhow-to-use-debuild-hooks-signing-hook-foo-etc%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown