On 03.11.2016 [19:37:41 +], Ian Jackson wrote:
> Nish Aravamudan writes ("DEP14 policy for two dots"):
> > [ Raphael, apologies for sending twice, had a error in the headers in
> > the prior one ]
> >
> > Not sure exactly where to ask this better than deb
On 09.11.2016 [21:27:14 +], Ian Jackson wrote:
> Raphael Hertzog writes ("Re: DEP14 policy for two dots"):
> > Ok, can you prepare a patch for DEP-14 then? I'll apply it as it looks like
> > a reasonable extension.
>
> Attached. FYI I intend to implement this in dgit.
Thank you! We will foll
On 09.11.2016 [23:38:30 +], Ian Jackson wrote:
> Nish Aravamudan writes ("Re: DEP14 policy for two dots"):
> > Thank you! We will follow the same in the Ubuntu tooling used by the Server
> > Team.
>
> Great, thanks.
>
> Can I ask you a rather unrelate
Hi Ian,
I've got a few questions/comments about git-based publishing imports and
history for patches-applied imports that I was hoping to bounce off you
and other VCS folks. I apologize for the very long e-mail to follow!
For context for everyone: I (along with Robie Basak and others) have
been d
Hi Sean,
On 08.01.2017 [21:34:50 -0700], Sean Whitton wrote:
> Hello Nish,
>
> On Fri, Jan 06, 2017 at 02:26:29PM -0800, Nish Aravamudan wrote:
> > 2) How do we determine if a source package is 1.0 vs. 3.0? I am
> > currently using `dpkg-source --print-format`, but
On 09.01.2017 [13:40:16 +], Ian Jackson wrote:
> Nish Aravamudan writes ("patches-applied historical imports (usd import)"):
> > 1) Some source packages (bouncycastle, php7.0 are the ones I can think
> > of off the top of my head) upstream tarballs contain .gitattribu
On 09.01.2017 [15:36:08 -0700], Sean Whitton wrote:
> Hello Nish,
>
> On Mon, Jan 09, 2017 at 02:15:53PM -0800, Nish Aravamudan wrote:
> > > Have you considered obtaining the patches-applied tree using
> > > `dpkg-source -x`? That applies the patches without usi
On 09.01.2017 [14:33:29 -0800], Nish Aravamudan wrote:
> On 09.01.2017 [13:40:16 +], Ian Jackson wrote:
> > Nish Aravamudan writes ("patches-applied historical imports (usd import)"):
> > > ii) some patches may fail to apply with a trivial `quilt push`. This
&g
Ian,
I noticed today that our Ubuntu git importer failed to import
src:nplan (which is only in Ubuntu). This is because the upload
(incorrectly) includes a .git directory. I see that dgit's behavior
for the same DSC file with `dgit import-dsc` is to delete the .git
directory from the source packag
On 24.05.2017 [22:56:52 +0100], Ian Jackson wrote:
> Nish Aravamudan writes ("What to do with .git directories in source package
> uploads?"):
> > I noticed today that our Ubuntu git importer failed to import
> > src:nplan (which is only in Ubuntu). This is because
10 matches
Mail list logo
