This has been fixed in dpatch 2.0.32, Ubuntu has 2.0.33 as far as I see.
** Changed in: dpatch (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121259
** Changed in: dpatch (Debian)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121259
Title:
dpatch must depend on dpkg-dev
To manage notifications about
** Changed in: dpatch (Debian)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121259
Title:
dpatch must depend on dpkg-dev
To manage notifications about this bug
** Changed in: dpatch (Debian)
Status: Unknown = New
--
dpatch must depend on dpkg-dev
https://bugs.launchpad.net/bugs/121259
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: Debian Bug tracker #473680
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473680
** Also affects: dpatch (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473680
Importance: Unknown
Status: Unknown
--
dpatch must depend on dpkg-dev
The changelog of dpatch 1.7 says:
* debian/control (Recommends): Recommend dpkg-dev, fakeroot and
patchutils, since we are using them in some of the scripts.
But currently the only action not using dpkg-architecture seems to be
patch-template.
I'll forward it to Debian and then we can sync
Confirmed, I met this problem too. It's rather obvious. Please add the
dpkg-dev dependency to dpatch.
** Changed in: dpatch (Ubuntu)
Status: New = Confirmed
--
dpatch must depend on dpkg-dev
https://bugs.launchpad.net/bugs/121259
You received this bug notification because you are a
