With the blessing of the previous sole maintainer, I am adopting python-iso8601 into DPMT. For all intents and purposes, there was no previous vcs of any kind, so I decided to use git-import-dscs to bootstrap the packaging history (there isn't a lot of it). There were a couple of things to note: * git-import-dscs seems pretty nice, especially in cases like this where there really is no other packaging history other than previous uploads. It's important to note though that g-i-d is only appropriate for the gbp-pq regime - it is not compatible with git-dpm. There is a `git-dpm import-dsc` command but it's less convenient than `git-import-dscs --debsnap`. Here's a nice opportunity for someone to contribute a `git-dpm import-dscs --debsnap`. * There are anomalies when pushing and pulling branches created with g-i-d. I get the following errors when I do the initial push: remote: fatal: Invalid revision range 0000000000000000000000000000000000000000..e14331dcbaf3f0972671111ca1a7a2ee6a7fd734 remote: fatal: Invalid revision range 0000000000000000000000000000000000000000..a9bb83a461be57ebcd09fa7b5a57597a866dfb52 remote: fatal: Invalid revision range 0000000000000000000000000000000000000000..48ba72c1bb849788fbe6ae0c20d9e28093039cd9 remote: fatal: Invalid revision range 0000000000000000000000000000000000000000..1a90ad5e79b2a5298d42a38308019e281bfc95c5 I have no idea what's causing these or what horrible deformity it's leaving the state of the repo in. It does *something* bad because subsequently cloning the repo afresh, I get this error: warning: remote HEAD refers to nonexistent ref, unable to checkout. This will leave you with an empty working copy, although everything seems to be cloned okay. A `git checkout master` (or any of the other gbp-pq branches) leaves you with a good looking working tree. If you have any ideas what's going on with the git errors, or how to fix them after the fact, please respond. Cheers, -Barry
Attachment:
signature.asc
Description: PGP signature