[Bug 1185102] [NEW] dpkg/DebSrc3.0 should accept git-format-patch output (or error out)

[Björn Michaelsen]

Public bug reported:

dpkg/DebSrc3.0 patches should accept git format-patch output. In most
cases this is done, which causes even more confusion if it doesnt, e.g.
for this commit:

http://cgit.freedesktop.org/libreoffice/core/commit/?id=faf72664d11deaa570a0f8c7e702ff07bf5914c8

git writes the diff base filename for the newly-created file as
a/dev/null.


Observed behaviour:
The debian toolchain does neither abort hard on this, nor create the file as one would expect.

Expected behaviour:
A hard abort on such a patch in debian/patches/ or (better): handling such patches as git does.

** Affects: dpkg (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.
https://bugs.launchpad.net/bugs/1185102

Title:
  dpkg/DebSrc3.0 should accept git-format-patch output (or error out)

Status in “dpkg” package in Ubuntu:
  New

Bug description:
  dpkg/DebSrc3.0 patches should accept git format-patch output. In most
  cases this is done, which causes even more confusion if it doesnt,
  e.g. for this commit:

  http://cgit.freedesktop.org/libreoffice/core/commit/?id=faf72664d11deaa570a0f8c7e702ff07bf5914c8

  git writes the diff base filename for the newly-created file as
  a/dev/null.

  
  Observed behaviour:
  The debian toolchain does neither abort hard on this, nor create the file as one would expect.

  Expected behaviour:
  A hard abort on such a patch in debian/patches/ or (better): handling such patches as git does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1185102/+subscriptions