Hi, toogley wrote: > Additionally I've set up the github repo > https://github.com/toogley/pkg-wicd - but i didn't make any changes > yet.
You should also push at least the "upstream" and preferably also the "pristine-tar" branch to your repo. At least these are the three branches which the git-buildpackage toolchain (see below) uses a lot. > Question: Jessie has currently this package > https://packages.debian.org/jessie/git-remote-bzr which would allow > us (since upstream uses bazaar) to fetch new upstream changes more > easily. But i don't know if its appropriate for debian packaging, > since it's an additional dependency for the process of maintaining > itself. There's no real widely adopted workflow for incorporating upstream git (or other repos) into the packaging repositories. On the other hand, there's a very established workflow for importing upstream tar balls ("gbp import-orig" from the git-buildpackage package). This is also the one which has been used for the wicd repository you cloned. So unless you want to track upstream VCS snapshots, "gbp import-orig" should suffice for nearly all cases. Regards, Axel -- ,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
