[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Helmut, On Thu, Oct 20, 2016 at 09:09:03PM +0200, Helmut Grohne wrote: > Hi Dmitry, > > I'm still kinda split about this. I discussed this with Guillem Jover > and Ian Jackson at length to avoid that step and still don't like it. Same for me. > > Do you have any use cases where the

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Dmitry, On Wed, Oct 19, 2016 at 07:17:07PM +0300, Dmitry Shachnev wrote: > So are you also interested in me making Sphinx architecture:any? I'm still kinda split about this. I discussed this with Guillem Jover and Ian Jackson at length to avoid that step and still don't like it. > Do you

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Johannes, On Tue, Oct 18, 2016 at 09:26:36AM +0200, Johannes Schauer wrote: > I just built src:sphinx on all porter boxes of release architectures. Thanks for this effort, I appreciate it regardless of status of this bug. > The only FTBFS I observed was on mips and the problem on mips went

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Dmitry, On Sun, 13 Mar 2016 22:21:58 +0100 Dmitry Shachnev wrote: > (Also, if I just apply the change you suggested, sphinx will FTBFS on some > archs, because the tests use webkit which segfaults there — so it's a bit > more tricky). I just built src:sphinx on all porter

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Helmut, On Thu, May 12, 2016 at 08:40:00PM +0200, Helmut Grohne wrote: >> 161 is many packages, though in my opinion splitting the documentation into >> arch:all packages is something that should be done independently of this bug. >> Maybe we can have some kind of DD list whose packages are

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Dmitry, On Thu, May 12, 2016 at 01:34:04PM +0300, Dmitry Shachnev wrote: > As you can see, I don't always reply quickly. Sorry for the delay this time. Things go slowly in cross-land anyway. Thanks for your continued interest. :) > > Cross building only applied to arch-dep packages. So in

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Helmut, On Mon, Mar 14, 2016 at 07:05:11AM +0100, Helmut Grohne wrote: > Hi Dmitry, > > Thank you for your quick and insightful reply. As you can see, I don't always reply quickly. Sorry for the delay this time. > Cross building only applied to arch-dep packages. So in jansson's case, > it

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Control: tags -1 - patch Hi Dmitry, Thank you for your quick and insightful reply. Please Cc debian-cr...@lists.debian.org. On Sun, Mar 13, 2016 at 10:21:58PM +0100, Dmitry Shachnev wrote: > I wonder what's the point of cross-building the arch-indep packages at all? > In jansson case, it looks

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Hi Helmut, On Sun, Mar 13, 2016 at 09:32:28PM +0100, Helmut Grohne wrote: > [skip] > > So here is a patch: > > sed -i -e '/Package: python3\?-sphinx/,+1s/\(Architecture: a\)ll/\1ny/' > debian/control > > Please apply it, so we can start adding the :native annotation to > reverse dependencies

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

Package: python-sphinx Version: 1.3.6-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap Control: block #807848 by -1 Hi, I have a request that may sound strange: Please turn python-sphinx and python3-sphinx from Architecture: all into Architecture: any. On first hearing this, it may