Re: git-dpm breakage src:faker

2017-01-29 Thread Brian May
Raphael Hertzog writes: > You don't need that. dpkg-buildpackage unapplies them automatically after > the build if it has applied them. If they were already applied before the > build, then it leaves them applied. Guess it depends how you build the package. I have been using: gbp buildpackage "

egg-info and Debian-specific submodule packages

2017-01-29 Thread Luke W Faraone
Hello, In bug #744741[1], we have a report where a lack of ``egg-info`` metadata breaks both ``pip``'s installation detection and packages that use ``pkg_resources`` to discover dependencies. Usually, the answer would be simple: ship the ``egg-info`` metadata as part of the package. But PySide is

Re: git-dpm breakage src:faker

2017-01-29 Thread Simon McVittie
On Sun, 29 Jan 2017 at 20:50:48 +0100, Raphael Hertzog wrote: > On Sun, 29 Jan 2017, Brian May wrote: > > 3. Update debian/source/options with "unapply-patches" (anything else?). > > You don't need that. dpkg-buildpackage unapplies them automatically after > the build if it has applied them. If

Re: git-dpm breakage src:faker

2017-01-29 Thread Scott Kitterman
On January 29, 2017 2:17:16 AM EST, Arto Jantunen wrote: >Scott Kitterman writes: > >> On Sunday, January 29, 2017 09:39:10 AM Brian May wrote: >>> Scott Kitterman writes: >>> > On Sunday, January 29, 2017 08:54:57 AM Brian May wrote: >>> >> Can we switch away from git-dpm yet? Sure this is mo

Re: git-dpm breakage src:faker

2017-01-29 Thread Raphael Hertzog
On Sun, 29 Jan 2017, Brian May wrote: > 3. Update debian/source/options with "unapply-patches" (anything else?). You don't need that. dpkg-buildpackage unapplies them automatically after the build if it has applied them. If they were already applied before the build, then it leaves them applied.