patches-applied historical imports (usd import)

[Nish Aravamudan]

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 have found one source
> > package (util-linux 2.13~rc3-5), where dpkg-source emits:
> 
> I would just introspect for the debian/source/format file.  If it has a
> line "3.0 (.*)" then it's 3.0, otherwise it's 1.0 (for all packages that
> were ACCEPTed to ftp-master).

Ok, is this documented in the manual or anything (for my own
edification). I spent some time searching, but didn't find anything
definitive except for the hint provided by `dpkg-source --print-format`.
And, presumably, if a historical publish exists without any
debian/source/format file, it should be treated as 1.0? Ah, yep, I see
that documented in `man dpkg-source` under DIAGNOSTICS.

> > ii) some patches may fail to apply with a trivial `quilt push`. This
> > occurs with, at least, a historical publish of samba.
> 
> Have you considered obtaining the patches-applied tree using
> `dpkg-source -x`?  That applies the patches without using quilt(1), so
> might workaround this sort of bug (if it didn't, the package would
> FTBFS).

Well, I would do that, but afaict, there is no way to tell dpkg-source
to only apply one patch at a time? This is to go from a
patches-unapplied state to the fully patches-applied state, commiting
each patch application into the repository. Perhaps I missed a flag in
the manpage, though?

Thanks,
Nish


-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd