Hi Roberto, Indeed, I had not thought of pushing the upstream and pristine-tar branches to the remote repository. Those two branches have now been pushed to the remote, and I expect it now to work fine. I did a quick check whether the file "bibledit_5.0.140.orig.tar.gz.delta" exists in the local repo, and it does exists there, so now after pushing them, I expect it to be okay now.
Thanks for spotting the issue, and for recommending the fix, and for trying to build from Alioth. Regards, Teus. On Sun, 2 Apr 2017 at 22:54 Roberto C. Sánchez <[email protected]> wrote: > Hi Teus, > > Thanks for addressing each of the items > > I pulled from Alioth and tried to build, but got this message: > > fatal: Path 'bibledit_5.0.140.orig.tar.gz.delta' does not exist in > 'refs/heads/pristine-tar' > pristine-tar: git show > refs/heads/pristine-tar:bibledit_5.0.140.orig.tar.gz.delta failed > gbp:error: Couldn't checkout "bibledit_5.0.140.orig.tar.gz": it exited > with 128 > > You probably need to run 'git push --all --tags' to get the upstream and > pristine-tar branches updated on the remote. Looking at the head > commits of both of those branches, they are still on a 4.9 verison. > > Also, I agree that uploading to mentors would not be especially > valuable. > > Feel free to update the branches at your convenience and then I will > build and review the package. > > Regards, > > -Roberto > > On Fri, Mar 31, 2017 at 03:44:16PM +0000, Teus Benschop wrote: > > Hi Roberto, > > All issues were now attended to, as follows: > > 1. The debian/README* was removed because it does not provide useful > > information. > > 2. All lintian messages for the source and for the binary including > > bibledit-data were either fixed or else overridden. > > 3. All the architecture-independent data was split off into package > > bibledit-data. > > 4. I no longer uploaded the package to [1]mentors.debian.net, as I > could > > not see the extra advantage of that. > > 5. A pristine-tar branch for git-buildpackage was added. > > Most of the steps have been scripted now, for easier updating with a > new > > upstream tarball for in the future, so it's going to be easy to keep > > up-to-date with upstream. > > Teus. > > On Wed, 29 Mar 2017 at 21:28 Roberto C. Sánchez <[2] > [email protected]> > > wrote: > > > > On Wed, Mar 29, 2017 at 09:58:58AM +0000, Teus Benschop wrote: > > > Hi Roberto, > > > I am sorry that I did not address the comments you made > previously. > > Trying > > > to trace down what happened, it seems the comments were buried > in > > my mail > > > box and I had overlooked them. > > > I will attend to all four comments, and try to address them > all. If > > I > > > don't manage to tackle everything, I'll ask for assistance - > thank > > you in > > > advance for offering that. > > > > Hi Teus, > > > > No need to apologize. It happens to me too :-) > > > > Regards, > > > > -Roberto > > > > -- > > Roberto C. Sánchez > > _______________________________________________ > > Pkg-crosswire-devel mailing list > > [3][email protected] > > [4] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel > > > > References > > > > Visible links > > 1. http://mentors.debian.net/ > > 2. mailto:[email protected] > > 3. mailto:[email protected] > > 4. > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel > > > _______________________________________________ > > Pkg-crosswire-devel mailing list > > [email protected] > > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel > > > -- > Roberto C. Sánchez > _______________________________________________ > Pkg-crosswire-devel mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
_______________________________________________ Pkg-crosswire-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
