Mike Miller <mtmiller@ieee.org> writes: > On Fri, Jul 20, 2012 at 01:50:49PM +0200, Sébastien Villemot wrote: >> Andreas Beckmann <debian@abeckmann.de> writes: >> >> > octave depends on dpkg-dev in order to use dpkg-architecture at runtime. >> > This is a bad idea. The path that is being computed in this way needs to >> > be built into the binary. >> > >> > The current approach will fail in a multiarch installation of octave: >> > dpkg-architecture will report information about the primary >> > architecture, but octave may be installed from another architecture and >> > will be using a wrong path ... >> >> My understanding is that it is not possible to install a non-multi-arch >> aware package (like octave) from another architecture, so that the >> scenario that you describe cannot materialize. Am I wrong? > > This is not correct. You can install a foreign architecture package as > long as all dependencies are either multi-arch-aware or there are no > conflicts. Thanks for the clarification. > In any event, here's a patch against the experimental branch that has > the added bonus of using built-in octave functions instead of system(), > ok to commit? Thanks for the patch, it looks good. I would rather have it applied to the master branch. The present bug being of severity important, its fix can be accepted into Wheezy per freeze policy. -- .''`. Sébastien Villemot : :' : Debian Maintainer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594
Attachment:
pgpBY7RwaaOZm.pgp
Description: PGP signature