It's no problem, Daviey has pushed your package based on the ppa contents.
Once you have a working .dsc, the easiest way to import that into a bzr tree is using
bzr import-dsc
Otherwise, any time after hand-applying a patch, you can do
bzr status
to see a list of both which files are modified, and which are unknown, i.e.:
# serge@sergelap:~/bzr/principia-tools$ bzr status
unknown:
cd
foo
Unknown source files can then be added by doing
bzr add cd foo
before committing.
Lastly, for the next full upstream release merge 'bzr merge-upstream' might be the easiest thing to do, but I've not used it myself. 'bzr help merge-upstream' shows its usage.
@Nate
It's no problem, Daviey has pushed your package based on the ppa contents.
Once you have a working .dsc, the easiest way to import that into a bzr tree is using
bzr import-dsc
Otherwise, any time after hand-applying a patch, you can do
bzr status
to see a list of both which files are modified, and which are unknown, i.e.:
# serge@sergelap: ~/bzr/principia -tools$ bzr status
unknown:
cd
foo
Unknown source files can then be added by doing
bzr add cd foo
before committing.
Lastly, for the next full upstream release merge 'bzr merge-upstream' might be the easiest thing to do, but I've not used it myself. 'bzr help merge-upstream' shows its usage.