creating the arpwatch repo

[Lukas Schwaighofer]

On Fri, 7 Apr 2017 15:54:07 +0200
Lukas Schwaighofer <lukas at schwaighofer.name> wrote:

> * I started working on the package on top of the existing arpwatch
>   packaging repository on collab-maint; as pushing interact with the
> BTS (tagging any fixed bugs as pending), does pushing the complete
> repo (containing "old commits" with fixes to old bugs) into the
> repository create any problems?

I worked around that by temporarily disabling the commit hook to get
the repository in the "old" state (i.e. similar to what it is on
collab-maint currently), and then re-enabled it before pushing my own
changes. They were still more than 20 commits, so no commit mails were
sent out, but bugs that are fixed by my upload have been tagged as
pending in the BTS as they should.

If somebody knows (for future reference), I would still like to know if
it would have been "safe" to push with the hook enabled.

Thanks
Lukas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-security-team/attachments/20170409/9e1b75fe/attachment.sig>