Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-22 Thread Maximiliano Curia
¡Hola Daniel! El 2019-08-14 a las 15:16 +0200, Daniel Leidert escribió: Am Mittwoch, den 14.08.2019, 09:48 -0300 schrieb Maximiliano Curia: El 2019-08-13 a las 01:17 +0200, Daniel Leidert escribió: `gbp pq` doesn't work with this layout. Actually, it does, you just have to add the option --

Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-14 Thread Daniel Leidert
Am Mittwoch, den 14.08.2019, 09:48 -0300 schrieb Maximiliano Curia: > El 2019-08-13 a las 01:17 +0200, Daniel Leidert escribió: > > `gbp pq` doesn't work with this layout. > > Actually, it does, you just have to add the option --pq-from=TAG. How so? There is no upstream branch. So independent of

Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-14 Thread Maximiliano Curia
¡Hola Daniel! El 2019-08-13 a las 01:17 +0200, Daniel Leidert escribió: `gbp pq` doesn't work with this layout. Actually, it does, you just have to add the option --pq-from=TAG. Happy hacking, -- "The most important thing in the programming language is the name. A language will not succeed w

Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-14 Thread Daniel Leidert
Am Dienstag, den 13.08.2019, 22:10 +0200 schrieb Alexis Murzeau: [..] > I'm curious about keeping only debian/ in git. > How to build such git repository ? > > I've tried one of yours but failed like this: > ``` > $ gbp clone https://salsa.debian.org/ruby-team/ruby-html-proofer > gbp:info: Clonin

Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-13 Thread Andreas Metzler
Alexis Murzeau wrote: > Le 13/08/2019 à 01:17, Daniel Leidert a écrit : >> Am Montag, den 12.08.2019, 19:53 +0200 schrieb Marc Haber: [...] >>> I haven't heard that a debian/ only repository layout is possible with >>> git-buildpackage before today. >> Works nicely. I keep a file debian/gbp.conf

Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-13 Thread Alexis Murzeau
Le 13/08/2019 à 01:17, Daniel Leidert a écrit : > Am Montag, den 12.08.2019, 19:53 +0200 schrieb Marc Haber: >> On Sun, 11 Aug 2019 15:03:51 +0200, Daniel Leidert >> wrote: >>> Am Sonntag, den 11.08.2019, 01:55 +0800 schrieb Drew Parsons: Upstreams are starting to use git lfs in their git rep

Re: Why keep upstream sources in Git at salsa.d.o?

2019-08-12 Thread Daniel Leidert
Am Montag, den 12.08.2019, 19:53 +0200 schrieb Marc Haber: > On Sun, 11 Aug 2019 15:03:51 +0200, Daniel Leidert > wrote: > > Am Sonntag, den 11.08.2019, 01:55 +0800 schrieb Drew Parsons: > > > Upstreams are starting to use git lfs in their git repos. In some cases > > > the git-lfs references fi

Re: Why keep upstream sources in Git at salsa.d.o? (was: how to handle upstream orig tarball with git-lfs reference files?)

2019-08-12 Thread Marc Haber
On Sun, 11 Aug 2019 15:03:51 +0200, Daniel Leidert wrote: >Am Sonntag, den 11.08.2019, 01:55 +0800 schrieb Drew Parsons: >> Upstreams are starting to use git lfs in their git repos. In some cases >> the git-lfs references files are retained in the source tarball, not >> replacing the reference

Re: Why keep upstream sources in Git at salsa.d.o? (was: how to handle upstream orig tarball with git-lfs reference files?)

2019-08-11 Thread Simon McVittie
On Sun, 11 Aug 2019 at 15:03:51 +0200, Daniel Leidert wrote: > What I really don't understand is, why we duplicate upstream files (now even > really large files) on salsa.d.o. I can't tell you every maintainer's reasons to do this, but here's why *I* prefer having upstream source code in our packa

Why keep upstream sources in Git at salsa.d.o? (was: how to handle upstream orig tarball with git-lfs reference files?)

2019-08-11 Thread Daniel Leidert
Am Sonntag, den 11.08.2019, 01:55 +0800 schrieb Drew Parsons: > Upstreams are starting to use git lfs in their git repos. In some cases > the git-lfs references files are retained in the source tarball, not > replacing the reference with the actual files. This happens for > instance with githu