Re: gbp import-orig has defeated me

2018-10-01 Thread Steve Robbins
On Monday, October 1, 2018 10:35:01 PM CDT Shengjing Zhu wrote: > I think you have configured your git to auto convert the line ending > when commit. > > In the pristine-tar tarball, > $ file googletest-release-1.8.1/googlemock/msvc/2005/gmock.sln > googletest-release-1.8.1/googlemock/msvc/2005/g

Re: gbp import-orig has defeated me

2018-10-01 Thread Fritz Reichwald
Hi steve, > git init > gbp import-orig --pristine-tar ../googletest_1.8.1.orig.tar.gz > ... copy debian dir from the salsa repo & commit ... > gbp buildpackage have you added a new changelog entry after importing the new upstream tarball? e.g by executing 'dch -v 1.8.1-1' Regards Fritz sig

Re: gbp import-orig has defeated me

2018-10-01 Thread Shengjing Zhu
On Tue, Oct 2, 2018 at 10:51 AM Steve Robbins wrote: > > Hi, > > I would like to update the googletest salsa repo [1] with upstream 1.8.1. So > I downloaded the tarball and ran "gbp import-orig" on it. That appeared to > work, but "gbp buildpackage" fails with > > dpkg-source: error: aborting

gbp import-orig has defeated me

2018-10-01 Thread Steve Robbins
Hi, I would like to update the googletest salsa repo [1] with upstream 1.8.1. So I downloaded the tarball and ran "gbp import-orig" on it. That appeared to work, but "gbp buildpackage" fails with dpkg-source: error: aborting due to unexpected upstream changes ... from the diffs, my guess i

Re: Q: Best practice for maintainer address with "alioth"

2018-10-01 Thread Alex Muntada
Hi Ted, > Is there something official from the lists.d.o maintainers > about what their preferences should be? I found some pointers in «Alioth: the future of mailing lists»: https://lists.debian.org/debian-devel-announce/2017/09/msg4.html Hope this helps, Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex

Re: Q: Best practice for maintainer address with "alioth"

2018-10-01 Thread Theodore Y. Ts'o
On Mon, Oct 01, 2018 at 09:59:59AM +0200, Alex Muntada wrote: > Hi Paul, > > > As I understand it, alioth-lists.d.n is an interim location > > This is correct, when asked what to do we're encouraging people > to keep the former lists.alioth.d.o addresses. > > > and folks should migrate to either

Re: Q: Best practice for maintainer address with "alioth"

2018-10-01 Thread Alex Muntada
Hi Holger, > On Mon, Oct 01, 2018 at 09:59:59AM +0200, Alex Muntada wrote: > > > As I understand it, alioth-lists.d.n is an interim location > > This is correct, when asked what to do we're encouraging people > > to keep the former lists.alioth.d.o addresses. > > I find this quite confusing, bec

Re: Q: Best practice for maintainer address with "alioth"

2018-10-01 Thread Holger Levsen
On Mon, Oct 01, 2018 at 09:59:59AM +0200, Alex Muntada wrote: > > As I understand it, alioth-lists.d.n is an interim location > This is correct, when asked what to do we're encouraging people > to keep the former lists.alioth.d.o addresses. I find this quite confusing, because this way its not cl

Re: Q: Best practice for maintainer address with "alioth"

2018-10-01 Thread Alex Muntada
Hi Paul, > As I understand it, alioth-lists.d.n is an interim location This is correct, when asked what to do we're encouraging people to keep the former lists.alioth.d.o addresses. > and folks should migrate to either a lists.d.o list, a > tracker.d.o team or pkgn...@packages.debian.org. FWIW,