Op 13-04-2008 om 20:37 schreef Adam D. Barratt:
>
> debrsign copies the file to the remote host, runs debsign there, and
> then copies the result back. The signing and updating of the changes
> file is performed by debsign. If you're seeing a problem with the file
> not being updated correctly, my suspicion would be that the remote host
> isn't running an up-to-date debsign.
Okay, now I getting it...
It is even in the manual page:
NAME
debrsign - remotely sign a Debian changes and dsc file pair using
SSH
SYNOPSIS
debrsign [options] [EMAIL PROTECTED] [changes-file|dsc-file]
DESCRIPTION
debrsign takes either an unsigned .dsc file or an unsigned .changes
file and the associated unsigned .dsc file (found by replacing the
architecture name and .changes by .dsc) if it appears in the .changes
file and signs them by copying them to the remote machine using ssh(1)
and remotely running debsign(1) on that machine. All options not
listed below are passed to the debsign program on the remote machine.
> I've just checked using two up-to-date hosts and the .changes file was
> updated correctly.
I have to wait until devscripts 2.10.25 moves into testing.
> I'm therefore closing this bug with this message.
Fine for me.
I hope that this bugreport will prevent further bugging from people
with no up-to-date debsign on the remote host.
> Regards,
>
> Adam
Thank you very much!
Geert Stappers
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
