Hello:
Assuming you did a gbp-pull and git-buildpackage is configured
correctly it should work. Also when I created the missing tag a while
ago I confirmed that upstream/1.7 contain the correct source when
compared to a tarball I downloaded from upstream and I also merged
upstream/1.7 to master
On Wed, Feb 02, 2011 at 08:09:44AM +, Miguel Colon wrote:
Hello:
Assuming you did a gbp-pull and git-buildpackage is configured
correctly it should work. Also when I created the missing tag a while
ago I confirmed that upstream/1.7 contain the correct source when
compared to a tarball I
Hello:
That should work. Try to pull the commit I just made to make sure.
It should complain at dh_installchangelogs now.
Cheers,
Miguel
On Wed, Feb 2, 2011 at 9:16 AM, Joel Roth jo...@pobox.com wrote:
On Wed, Feb 02, 2011 at 08:09:44AM +, Miguel Colon wrote:
Hello:
Assuming you did a
On Wed, Feb 02, 2011 at 09:45:50AM +, Miguel Colon wrote:
Hello:
That should work. Try to pull the commit I just made to make sure.
It should complain at dh_installchangelogs now.
Great. It goes much further. A few lintian warnings remain.
W: mma source: changelog-should-mention-nmu
Hello:
Sure, I fixed a few things since I only planned to make 1 commit but
made a mistake since I forgot about the dh_install limitations.
Anyway since you seem to be doing well on your own now I was gonna
leave it at this but I noticed that you added a new manpage on the
source. When using
Michael and others,
I wonder if I made a mistake in merging the upstream
version.
When I try building this package, I get a huge raft
of errors.
Could someone see if these are common or readily solved?
thanks,
Joel
--
Joel Roth
___
