Bug#623649: matlab-support: is the libxp dependency necessary?
On Thu, 29 Mar 2012, Michael Hanke wrote: On Fri, Mar 30, 2012 at 12:36:02AM +1100, Drew Parsons wrote: Thanks for digging this out! No I wonder whether we should drop this dependency for wheezy or afterwards. Any thoughts on this? It comes down to an evaluation of how many matlab versions lower than 7.13 are still in current use on users' machines running Debian unstable/testing. Are there likely to be many 6.0/7.0 matlab users? I have no clue. In our machines we still have a 2010 release, but Matlab is not used very much at all. Curious question to resolve. MathWorks still lists as a Support Feature, that they continue to support versions preceding R2008a (never mind R2011a). https://www.mathworks.com.au/accesslogin/benefits.jsp But of course, few of those installations are likely to be on a post-wheezy Debian system. The other main packages holding up libxp removal are ecore and xtel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623649: matlab-support: is the libxp dependency necessary?
On Wed, 28 Mar 2012 21:00:30 +0200, Michael Hanke wrote: Hi, On Wed, Mar 28, 2012 at 06:25:33PM +0200, Sébastien Villemot wrote: Looks like MATLAB no longer depends on libxp, starting from version 7.13 (R2011b). Thanks for digging this out! No I wonder whether we should drop this dependency for wheezy or afterwards. Any thoughts on this? It comes down to an evaluation of how many matlab versions lower than 7.13 are still in current use on users' machines running Debian unstable/testing. Are there likely to be many 6.0/7.0 matlab users? As far as libxp is concerned, there are still a few other packages depending on it, and the indirect dependence via lesstif/motif could be tricky to unravel. So I'm not aiming to remove libxp for wheezy, and therefore there's no need to rush into removing it from matlab-support. We could consider cleaning this up to be a release goal for wheezy+1. Drew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623649: matlab-support: is the libxp dependency necessary?
On Fri, Mar 30, 2012 at 12:36:02AM +1100, Drew Parsons wrote: Thanks for digging this out! No I wonder whether we should drop this dependency for wheezy or afterwards. Any thoughts on this? It comes down to an evaluation of how many matlab versions lower than 7.13 are still in current use on users' machines running Debian unstable/testing. Are there likely to be many 6.0/7.0 matlab users? I have no clue. In our machines we still have a 2010 release, but Matlab is not used very much at all. As far as libxp is concerned, there are still a few other packages depending on it, and the indirect dependence via lesstif/motif could be tricky to unravel. So I'm not aiming to remove libxp for wheezy, and therefore there's no need to rush into removing it from matlab-support. We could consider cleaning this up to be a release goal for wheezy+1. Sounds good to me! Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623649: matlab-support: is the libxp dependency necessary?
Drew Parsons dpars...@debian.org writes: On Fri, 2011-04-22 at 09:13 -0400, Michael Hanke wrote: Would Mathworks pay attention if you draw their attention to the deprecation of Xprint? (Would be very interesting to learn if they have customers who actually use the libXp support!) Looks like MATLAB no longer depends on libxp, starting from version 7.13 (R2011b). On my system: sebastien@karaba:~$ ldd /usr/local/MATLAB/R2011a/bin/glnxa64/MATLAB |grep libXp libXpm.so.4 = /usr/lib/x86_64-linux-gnu/libXpm.so.4 (0x7f4da2c5b000) libXp.so.6 = /usr/lib/x86_64-linux-gnu/libXp.so.6 (0x7f4da1765000) sebastien@karaba:~$ ldd /usr/local/MATLAB/R2011b/bin/glnxa64/MATLAB |grep libXp sebastien@karaba:~$ ldd /usr/local/MATLAB/R2012a/bin/glnxa64/MATLAB |grep libXp sebastien@karaba:~$ -- Sébastien Villemot Researcher in Economics Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594 pgpMqcRuxm4aO.pgp Description: PGP signature
Bug#623649: matlab-support: is the libxp dependency necessary?
Hi, On Wed, Mar 28, 2012 at 06:25:33PM +0200, Sébastien Villemot wrote: Drew Parsons dpars...@debian.org writes: On Fri, 2011-04-22 at 09:13 -0400, Michael Hanke wrote: Would Mathworks pay attention if you draw their attention to the deprecation of Xprint? (Would be very interesting to learn if they have customers who actually use the libXp support!) Looks like MATLAB no longer depends on libxp, starting from version 7.13 (R2011b). Thanks for digging this out! No I wonder whether we should drop this dependency for wheezy or afterwards. Any thoughts on this? Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623649: matlab-support: is the libxp dependency necessary?
On Fri, Apr 22, 2011 at 11:54:36AM +1000, Drew Parsons wrote: Your package depends on libxp. This situation sometimes arises historically from the time before xprint was considered obsolete, with Build-depends: libxp-dev being set in the past and then forgotten and untouched. This bug has been filed to prompt you to check if you really want Xprint (libxp) support in your package. The matlab-support package represents a local Matlab installation in a Debian system. The package itself doesn't need libxp. However, the reason for this is: mih@hydra /apps/matlab % ldd Matlab_R2010a/bin/glnxa64/MATLAB |grep libXp libXpm.so.4 = /usr/lib/libXpm.so.4 (0x7f80e2f6) libXp.so.6 = /usr/lib/libXp.so.6 (0x7f80e1e34000) Matlab doesn't ship with libXp, hence removing it would make Matlab incompatible with Debian, until Mathworks adjusts to this situation. I understand the issues related to proprietary software, but Matlab is a fairly popular piece of software. Is there a plan how to deal with this (or at all)? Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623649: matlab-support: is the libxp dependency necessary?
On Fri, 2011-04-22 at 09:13 -0400, Michael Hanke wrote: The matlab-support package represents a local Matlab installation in a Debian system. The package itself doesn't need libxp. However, the reason for this is: mih@hydra /apps/matlab % ldd Matlab_R2010a/bin/glnxa64/MATLAB |grep libXp libXpm.so.4 = /usr/lib/libXpm.so.4 (0x7f80e2f6) libXp.so.6 = /usr/lib/libXp.so.6 (0x7f80e1e34000) Matlab doesn't ship with libXp, hence removing it would make Matlab incompatible with Debian, until Mathworks adjusts to this situation. I understand the issues related to proprietary software, but Matlab is a fairly popular piece of software. Thanks for the analysis. I'm a great fan of octave but I agree its worthwhile supporting the installation and utility of matlab on Debian systems. Social contract #4 etc. Is there a plan how to deal with this (or at all)? The plan is a simple one: don't remove libxp :) We'll leave it in until nothing uses it anymore. Would Mathworks pay attention if you draw their attention to the deprecation of Xprint? (Would be very interesting to learn if they have customers who actually use the libXp support!) Thanks for the response, Drew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623649: matlab-support: is the libxp dependency necessary?
Package: matlab-support Version: 0.0.14 Severity: wishlist The xprint package is obsolete and scheduled for removal. A related library is libxp, which provides an API that enables client programs to access and use an Xprint server. Since we're getting rid of xprint, one could argue it makes sense to get rid of libxp as well. Your package depends on libxp. This situation sometimes arises historically from the time before xprint was considered obsolete, with Build-depends: libxp-dev being set in the past and then forgotten and untouched. This bug has been filed to prompt you to check if you really want Xprint (libxp) support in your package. We'll leave libxp in the archives for the time being until you and the other packages using it have determined whether you want to keep the dependency. But we'll be removing xprint itself and other related packages now. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
