Bug#648034: python-scipy: Gaussian KDE on does not work on integer inputs
Package: python-scipy Version: 0.7.2+dfsg1-1 Severity: normal Applying scipy.stats.kde.gaussian_kde to a list of integers, e.g. [1,2,3,4,5], is not same as applying it to a list of floats [1.0, 2.0, 3.0, 4.0, 5.0]. This is quite surprising and should probably be fixed. The output for integers appears to be always 0, although I did not test with very wide range of inputs. This is probably a bug in the internals of gaussian_kde, since it probably converts the input into a NumPy array without specifying the type, and then does math on it expecting it to be an array of floats, whereas it will be an array of some integral type if input is all-integral. Converting input to floating point types manually allows one to work around this issue. Expected: python -c 'import scipy.stats;l=[1,2,3,3,3,3,4,5];k=[1,2,3,4,5];print scipy.stats.kde.gaussian_kde(l)(k) == scipy.stats.kde.gaussian_kde(map(float, l))(k)' to print [True True True True True] Actual: python -c 'import scipy.stats;l=[1,2,3,3,3,3,4,5];k=[1,2,3,4,5];print scipy.stats.kde.gaussian_kde(l)(k) == scipy.stats.kde.gaussian_kde(map(float, l))(k)' prints [False False False False False] -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-scipy depends on: ii libamd2.2.0 1:3.4.0-2approximate minimum degree orderin ii libblas3gf [libblas.so. 1.2-8Basic Linear Algebra Reference imp ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8GCC support library ii libgfortran34.4.5-8 Runtime library for GNU Fortran ap ii liblapack3gf [liblapack 3.2.1-8 library of linear algebra routines ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libumfpack5.4.0 1:3.4.0-2sparse LU factorization library ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-central 0.6.16+nmu1 register and build utility for Pyt ii python-numpy1:1.4.1-5Numerical Python adds a fast array Versions of packages python-scipy recommends: ii g++ [c++-compiler]4:4.4.5-1 The GNU C++ compiler ii g++-4.4 [c++-compiler]4.4.5-8The GNU C++ compiler Versions of packages python-scipy suggests: pn python-profiler none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642293: virtualbox-ose: Scheduling issues and eventually soft lockups occur when running VMs
Package: virtualbox-ose Version: 3.2.10-dfsg-1 Severity: important Hosting VirtualBox VMs on this machine often results in scheduling issues for user processes, and sometimes the machine becomes unresponsible for a long time, after which a message about soft lockup is found in system log. The system is running stock Debian kernel and VirtualBox. The system still reacts to external inputs. For example, when running the ping script below, and seeing that it has been stuck in sleep() for a few seconds, hitting a key on keyboard of the machine immediately ends the sleep. It appears as if the kernel fails to set a timer interrupt to wake itself up for some reason. The scheduling issues manifest easily as sleep() taking varying periods of time. Below is output of a Python script that attempts to ping some of the VMs and then sleep(1-ping_duration) seconds. Pings took 0.0038001537323 Trying to sleep 0.996199846268 Sleep took 1.77373981476 Pings took 0.00364708900452 Trying to sleep 0.996352910995 Sleep took 8.63721585274 Pings took 0.00382900238037 Trying to sleep 0.99617099762 Sleep took 5.65230202675 Pings took 0.00357413291931 Trying to sleep 0.996425867081 Sleep took 1.42871999741 Some example soft lockup messages with call traces and on without a call trace are attached below. For some reason not all messages include a call trace. Message 1 with call trace: Sep 21 07:15:38 testbase kernel: [504005.781003] BUG: soft lockup - CPU#2 stuck for 61s! [VBoxHeadless:14724] Sep 21 07:15:38 testbase kernel: [504005.781013] Modules linked in: vboxnetadp vboxnetflt vboxdrv bridge stp tun ext4 jbd2 crc16 loop snd_hda_codec_atihdmi snd_hda_intel snd_hda_codec radeon ttm snd_hwdep snd_pcm drm_kms_helper snd_timer drm snd psmouse i2c_algo_bit soundcore serio_raw snd_page_alloc i2c_piix4 pcspkr edac_core evdev k10temp edac_mce_amd i2c_core button shpchp pci_hotplug processor ext3 jbd mbcache sd_mod crc_t10dif ata_generic usbhid hid ohci_hcd thermal thermal_sys pata_atiixp ahci libata r8169 ehci_hcd mii scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] Sep 21 07:15:38 testbase kernel: [504005.781038] CPU 2: Sep 21 07:15:38 testbase kernel: [504005.781039] Modules linked in: vboxnetadp vboxnetflt vboxdrv bridge stp tun ext4 jbd2 crc16 loop snd_hda_codec_atihdmi snd_hda_intel snd_hda_codec radeon ttm snd_hwdep snd_pcm drm_kms_helper snd_timer drm snd psmouse i2c_algo_bit soundcore serio_raw snd_page_alloc i2c_piix4 pcspkr edac_core evdev k10temp edac_mce_amd i2c_core button shpchp pci_hotplug processor ext3 jbd mbcache sd_mod crc_t10dif ata_generic usbhid hid ohci_hcd thermal thermal_sys pata_atiixp ahci libata r8169 ehci_hcd mii scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] Sep 21 07:15:38 testbase kernel: [504005.781060] Pid: 14724, comm: VBoxHeadless Not tainted 2.6.32-5-amd64 #1 GA-MA78GM-UD2H Sep 21 07:15:38 testbase kernel: [504005.781061] RIP: 0010:[a03aa455] [a03aa455] g_abExecMemory+0x8d95/0x18 [vboxdrv] Sep 21 07:15:38 testbase kernel: [504005.781070] RSP: 0018:880223ff5d98 EFLAGS: 0212 Sep 21 07:15:38 testbase kernel: [504005.781072] RAX: RBX: 880223ff5dd8 RCX: 0001 Sep 21 07:15:38 testbase kernel: [504005.781074] RDX: a0410fb0 RSI: 0008 RDI: c900128d7000 Sep 21 07:15:38 testbase kernel: [504005.781075] RBP: 8101166e R08: c900128d7dd8 R09: c900128d7000 Sep 21 07:15:38 testbase kernel: [504005.781077] R10: 880223ff5de8 R11: a03aa370 R12: c900128bc000 Sep 21 07:15:38 testbase kernel: [504005.781078] R13: c90012a56050 R14: c900128d7000 R15: 80ef Sep 21 07:15:38 testbase kernel: [504005.781080] FS: 7f188b301700() GS:880008b0() knlGS: Sep 21 07:15:38 testbase kernel: [504005.781081] CS: 0010 DS: ES: CR0: 8005003b Sep 21 07:15:38 testbase kernel: [504005.781083] CR2: 7f0512e29380 CR3: 0001bb5cd000 CR4: 06e0 Sep 21 07:15:38 testbase kernel: [504005.781084] DR0: DR1: DR2: Sep 21 07:15:38 testbase kernel: [504005.781086] DR3: DR6: 0ff0 DR7: 0400 Sep 21 07:15:38 testbase kernel: [504005.781087] Call Trace: Sep 21 07:15:38 testbase kernel: [504005.781093] [a03aa497] ? g_abExecMemory+0x8dd7/0x18 [vboxdrv] Sep 21 07:15:38 testbase kernel: [504005.781097] [a03b54a9] ? g_abExecMemory+0x13de9/0x18 [vboxdrv] Sep 21 07:15:38 testbase kernel: [504005.781102] [8100f6c4] ? __switch_to+0x1ad/0x297 Sep 21 07:15:38 testbase kernel: [504005.781107] [a038e45f] ? supdrvIOCtlFast+0x3f/0x51 [vboxdrv] Sep 21 07:15:38 testbase kernel: [504005.78] [a038e23e] ? VBoxDrvLinuxIOCtl+0x3b/0x191 [vboxdrv] Sep 21 07:15:38 testbase kernel: [504005.781115] [81041ade] ? pick_next_task_fair+0xca/0xd6 Sep 21 07:15:38 testbase kernel:
Bug#569008: closed by Varun Hiremath va...@debian.org (Bug#569008: fixed in python-scipy 0.9.0+dfsg1-1)
On 2011-04-07 06:09, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the python-scipy package: #569008: python-scipy: scipy.stats.kde.gaussian_kde fails with non-obvious exception It has been closed by Varun Hiremath va...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Varun Hiremath va...@debian.org by replying to this email. Hello, It appears that with upstream version 0.9.0 the bug is not fixed: [9:01:09][tazle@orn][~/unsafe/pythons]% ./scipytest/bin/python -c 'from scipy.stats.kde import gaussian_kde; gaussian_kde([1])' Warning: invalid value encountered in divide Traceback (most recent call last): File string, line 1, in module File /home/tazle/unsafe/pythons/scipytest/lib/python2.5/site-packages/scipy/stats/kde.py, line 88, in __init__ self._compute_covariance() File /home/tazle/unsafe/pythons/scipytest/lib/python2.5/site-packages/scipy/stats/kde.py, line 341, in _compute_covariance self.inv_cov = linalg.inv(self.covariance) File /home/tazle/unsafe/pythons/scipytest/lib/python2.5/site-packages/scipy/linalg/basic.py, line 285, in inv a1 = asarray_chkfinite(a) File /home/tazle/unsafe/pythons/scipytest/lib/python2.5/site-packages/numpy/lib/function_base.py, line 547, in asarray_chkfinite array must not contain infs or NaNs) ValueError: array must not contain infs or NaNs I did not test with the actual Debian package, since I do not have unstable installation around. However, this should not be important, since the changelog indicates that upstream changes are what should close #569008. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569008: python-scipy: scipy.stats.kde.gaussian_kde fails with non-obvious exception
Package: python-scipy Version: 0.7.0-2+b1 Severity: normal When single-element input is given to scipy.stats.kde.gaussian_kde, it raises ValueError about infs or NaNs even if the input doesn't contain any. If computing KDE from single-element input does not make sense, the exception should report this. Expected result (with two-element input): % python -c 'from scipy.stats.kde import gaussian_kde; gaussian_kde([1,2])' /usr/lib/python2.5/site-packages/scipy/stats/stats.py:1486: DeprecationWarning: scipy.stats.cov is deprecated; please update your code to use numpy.cov. Please note that: - numpy.cov rowvar argument defaults to true, not false - numpy.cov bias argument defaults to false, not true , DeprecationWarning) /usr/lib/python2.5/site-packages/scipy/stats/stats.py:420: DeprecationWarning: scipy.stats.mean is deprecated; please update your code to use numpy.mean. Please note that: - numpy.mean axis argument defaults to None, not 0 - numpy.mean has a ddof argument to replace bias in a more general manner. scipy.stats.mean(a, bias=True) can be replaced by numpy.mean(x, axis=0, ddof=1). axis=0, ddof=1)., DeprecationWarning) Actual result: % python -c 'from scipy.stats.kde import gaussian_kde; gaussian_kde([1])' /usr/lib/python2.5/site-packages/scipy/stats/stats.py:1486: DeprecationWarning: scipy.stats.cov is deprecated; please update your code to use numpy.cov. Please note that: - numpy.cov rowvar argument defaults to true, not false - numpy.cov bias argument defaults to false, not true , DeprecationWarning) /usr/lib/python2.5/site-packages/scipy/stats/stats.py:420: DeprecationWarning: scipy.stats.mean is deprecated; please update your code to use numpy.mean. Please note that: - numpy.mean axis argument defaults to None, not 0 - numpy.mean has a ddof argument to replace bias in a more general manner. scipy.stats.mean(a, bias=True) can be replaced by numpy.mean(x, axis=0, ddof=1). axis=0, ddof=1)., DeprecationWarning) Traceback (most recent call last): File string, line 1, in module File /usr/lib/python2.5/site-packages/scipy/stats/kde.py, line 81, in __init__ self._compute_covariance() File /usr/lib/python2.5/site-packages/scipy/stats/kde.py, line 334, in _compute_covariance self.inv_cov = linalg.inv(self.covariance) File /usr/lib/python2.5/site-packages/scipy/linalg/basic.py, line 342, in inv a1 = asarray_chkfinite(a) File /usr/lib/python2.5/site-packages/numpy/lib/function_base.py, line 705, in asarray_chkfinite raise ValueError, array must not contain infs or NaNs ValueError: array must not contain infs or NaNs -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core) Locale: LANG=fi_FI, LC_CTYPE=fi_FI (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages python-scipy depends on: ii libamd2.2.0 1:3.4.0-1 approximate minimum degree orderin ii libblas3gf [libblas.so.3gf] 1.2-2 Basic Linear Algebra Subroutines 3 ii libc62.10.2-2GNU C Library: Shared libraries ii libgcc1 1:4.4.2-3 GCC support library ii libgfortran3 4.4.2-3 Runtime library for GNU Fortran ap ii liblapack3gf [liblapack.so.3 3.2.1-2 library of linear algebra routines ii libstdc++6 4.4.2-3 The GNU Standard C++ Library v3 ii libumfpack5.4.0 1:3.4.0-1 sparse LU factorization library ii python 2.5.4-5 An interactive high-level object-o ii python-central 0.6.14+nmu2 register and build utility for Pyt ii python-numpy 1:1.3.0-3 Numerical Python adds a fast array Versions of packages python-scipy recommends: ii g++ [c++-compiler]4:4.3.4-1 The GNU C++ compiler ii g++-4.3 [c++-compiler]4.3.4-6The GNU C++ compiler Versions of packages python-scipy suggests: ii python-profiler 2.5.2-1deterministic profiling of any Pyt -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559990: python-matplotlib: Segfault when importinb pylab fromt matplotlib
Package: python-matplotlib Version: 0.99.1.2-1 Severity: important After updating to latest python-matplotlib version, importing pylab from matplotlib causes a segfault. Presumably this issue is specific to my system/package configuration since it has not been reported yet (assuming 556943 is not a duplicate, which it doesn't seem to be, since the segfault there does not happen upon import). I'll try to track down the root cause next. Reproducing: [7:15:34][ta...@pryan][~]% python -c 'from matplotlib import pylab' zsh: segmentation fault python -c 'from matplotlib import pylab' -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32pryan (SMP w/2 CPU cores) Locale: LANG=en_US, lc_ctype=fi...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages python-matplotlib depends on: ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libc6 2.9-25GNU C Library: Shared libraries ii libcairo2 1.8.6-2 The Cairo 2D vector graphics libra ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib ii libgcc11:4.3.3-3 GCC support library ii libglib2.0-0 2.20.1-2 The GLib library of C routines ii libgtk2.0-02.16.1-2 The GTK+ graphical user interface ii libpango1.0-0 1.22.4-2 Layout and rendering of internatio ii libpng12-0 1.2.35-1 PNG library - runtime ii libstdc++6 4.3.3-3 The GNU Standard C++ Library v3 ii python 2.5.4-2 An interactive high-level object-o ii python-cairo 1.4.12-1.2Python bindings for the Cairo vect ii python-dateutil1.4.1-3 powerful extensions to the standar ii python-gobject 2.14.2-1 Python bindings for the GObject li ii python-matplotlib-data 0.99.1.2-1Python based plotting system (data ii python-numpy 1:1.2.1-1 Numerical Python adds a fast array ii python-pyparsing 1.5.1-2 Python parsing module ii python-support 1.0.3 automated rebuilding support for P ii python-tz 2009a-1 Python version of the Olson timezo ii tcl8.5 8.5.8-2 Tcl (the Tool Command Language) v8 ii tk8.5 8.5.8-1 Tk toolkit for Tcl and X11, v8.5 - ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages python-matplotlib recommends: ii python-glade2 2.12.1-6 GTK+ bindings: Glade support ii python-gtk2 2.12.1-6 Python bindings for the GTK+ widge ii python-tk 2.5.2-1Tkinter - Writing Tk applications Versions of packages python-matplotlib suggests: pn dvipngnone (no description available) pn ipython none (no description available) ii librsvg2-common 2.26.0-1 SAX-based renderer library for SVG ii python-configobj 4.5.2-2a simple but powerful config file ii python-excelerator0.6.3a-3.1 module for reading/writing Excel s ii python-matplotlib-doc 0.98.3-5 Python based plotting system (docu ii python-scipy 0.6.0-12 scientific tools for Python pn python-traits none (no description available) pn texlive-extra-utils none (no description available) pn texlive-latex-extra none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559990: Root cause
Root cause for this issue seems to be somewhere in init_path of src/_path.c in matplotlib, which calls init_array() of numpy. Upgrading numpy to 1:1.3.0-3 fixed the segfault. Perhaps the dependency version should be bumped. signature.asc Description: OpenPGP digital signature
Bug#550170: Traces
I ran into this kind of problem today as well. First notes about emacs -q and emacs --no-site-file. When the problem occurs, it occurs with them as well as with plain emacs. Then some tracing attempts: It was rather difficult to get the problem to show up under GDB, since for some reason I could not reproduce the problem when argv[0] was /usr/bin/emacs rather than emacs and I couldn't find a way to get gdb to execute Emacs in a fashion that most of the time reproduces the problem. Eventually I managed to background the emacs process before it hits the error, and attached GDB to the running process. I also had to compile Emacs with debug symbols to get anything useful out of it. With GDB, I got the elisp backtrace of the problem: (gdb) xbacktrace keymap-parent (0xbfa3f54c) x-setup-function-keys (0xbfa3f674) x-create-frame-with-faces (0xbfa3f7b4) make-frame (0xbfa3f8f4) frame-initialize (0xbfa3fa34) command-line (0xbfa3fb74) normal-top-level (0xbfa3fc40) The actual error is raised in get_keymap. The relevant C backtrace: #4 0x08125505 in get_keymap (object=140846637, error=1, autoload=1) at keymap.c:301 #5 0x08125db2 in keymap_parent (keymap=140846637, autoload=1) at keymap.c:315 #6 0x08125e29 in Fkeymap_parent (keymap=140846637) at keymap.c:335 On command line the end result is: Wrong type argument: keymapp, (DEAD . 17605828) This does not seem very useful, however. It only tells that someone passed keymap_parent a garbage-collected object. Most importantly it does not tell what the garbage-collected object is supposed to be or where it was allocated/deallocated. I also managed to reproduce the same keymapp error with different values by introducing breakpoint on get_keymap in GDB. 1) In GDB: Breakpoint 1, Fsignal (error_symbol=137967049, data=138245453) at eval.c:1641 1641 register struct handler *allhandlers = handlerlist; (gdb) bt #0 Fsignal (error_symbol=137967049, data=138245453) at eval.c:1641 #1 0x0817e878 in xsignal (error_symbol=137967049, data=138245453) at eval.c:1751 #2 0x0817ec37 in xsignal2 (error_symbol=137967049, arg1=137955913, arg2=139207485) at eval.c:1775 #3 0x0816cab1 in wrong_type_argument (predicate=137955913, value=139207485) at data.c:115 #4 0x08125505 in get_keymap (object=139207485, error=1, autoload=0) at keymap.c:301 #5 0x08125dd0 in keymap_parent (keymap=value optimized out, autoload=0) at keymap.c:322 #6 0x08125e64 in keymap_memberp (map=138245493, maps=137917301) at keymap.c:345 #7 0x081265e6 in Fset_keymap_parent (keymap=138245493, parent=137917301) at keymap.c:378 #8 0x081128ed in init_kboard (kb=0x8393d20) at keyboard.c:11568 #9 0x0811b722 in init_keyboard () at keyboard.c:11644 #10 0x081110fa in main (argc=1, argv=0xbf8028b4) at emacs.c:1760 (gdb) xbacktrace (gdb) c On command line: emacs: Wrong type argument: keymapp, ((kp-equal . [61]) (kp-divide . [47]) (kp-decimal . [46]) (kp-subtract . [45]) (kp-separator . [44]) (kp-add . [43]) (kp-multiply . [42]) (kp-enter . [13]) (kp-tab . [9]) (kp-space . [32]) (kp-9 . [57]) (kp-8 . [56]) (kp-7 . [55]) (kp-6 . [54]) (kp-5 . [53]) (kp-4 . [52]) (kp-3 . [51]) (kp-2 . [50]) (kp-1 . [49]) (kp-0 . [48]) (24 keymap (64 keymap (99 . event-apply-control-modifier) (83 . event-apply-shift-modifier) (97 . event-apply-alt-modifier) (109 . event-apply-meta-modifier) (115 . event-apply-super-modifier) (104 . event-apply-hyper-modifier))) (C-S-kp-9 . [C-S-prior]) (C-S-kp-8 . [C-S-up]) (C-S-kp-7 . [C-S-home]) (C-S-kp-6 . [C-S-right]) (C-S-kp-4 . [C-S-left]) (C-S-kp-3 . [C-S-next]) (C-S-kp-2 . [C-S-down]) (C-S-kp-1 . [C-S-end]) (C-S-kp-prior . [C-S-prior]) (C-S-kp-up . [C-S-up]) (C-S-kp-home . [C-S-home]) (C-S-kp-right . [C-S-right]) (C-S-kp-left . [C-S-left]) (C-S-kp-next . [C-S-next]) (C-S-kp-down . [C-S-down]) (C-S-kp-end . [C-S-end]) (S-kp-prior . [S-prior]) (S-kp-up . [S-up]) (S-kp-home . [S-home]) (S-kp-right . [S-right]) (S-kp-left . [S-left]) (S-kp-next . [S-next]) (S-kp-down . [S-down]) (S-kp-end . [S-end]) (kp-delete . [127]) (delete . [127]) (backspace . [127]) (kp-insert . [insert]) (kp-begin . [begin]) (kp-end . [end]) (M-kp-next . [M-next]) (kp-next . [next]) (kp-prior . [prior]) (kp-down . [down]) (kp-right . [right]) (kp-up . [up]) (kp-left . [left]) (kp-home . [home])) . [left]) (kp-home . [home])) 2) #0 Fsignal (error_symbol=137967049, data=138493661) at eval.c:1641 #1 0x0817e878 in xsignal (error_symbol=137967049, data=138493661) at eval.c:1751 #2 0x0817ec37 in xsignal2 (error_symbol=137967049, arg1=137955913, arg2=137923865) at eval.c:1775 #3 0x0816cab1 in wrong_type_argument (predicate=137955913, value=137923865) at data.c:115 #4 0x08125505 in get_keymap (object=137923865, error=1, autoload=1) at keymap.c:301 #5 0x08125dfe in keymap_parent (keymap=value optimized out, autoload=1) at keymap.c:326 #6 0x08125e29 in Fkeymap_parent (keymap=138245493) at keymap.c:335 #7 0x0817e4a4 in Ffuncall (nargs=2, args=0xbffcfc10) at eval.c:3045 #8 0x081b2ef0 in Fbyte_code (bytestr=139177427,
Bug#558268: xmlstarlet produces incorrect validation result
Package: xmlstarlet Version: 1.0.1-2 Severity: normal Xmlstarlet produces incorrect validation result on the following file: http://www.laurinolli.fi/~tazle/invalid.xml. The final validation result is 'valid' even though the document does not conform to its DTD and validation against embedded DTD is enabled. Reproduction: Run xmlstarlet val -E 'http://www.laurinolli.fi/~tazle/invalid.xml'. Expected result: http://www.laurinolli.fi/~tazle/invalid.xml:14: element test: validity error : Element test content does not follow the DTD, expecting (required), got (required invalid_extension ) /test ^ http://www.laurinolli.fi/~tazle/invalid.xml - invalid Actual result: http://www.laurinolli.fi/~tazle/invalid.xml:14: element test: validity error : Element test content does not follow the DTD, expecting (required), got (required invalid_extension ) /test ^ http://www.laurinolli.fi/~tazle/invalid.xml - valid -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=fi_FI, LC_CTYPE=fi_FI (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages xmlstarlet depends on: ii libc6 2.9-25GNU C Library: Shared libraries ii libxml22.7.6.dfsg-1 GNOME XML library ii libxslt1.1 1.1.26-1 XSLT processing library - runtime ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime xmlstarlet recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557579: octave-image: imtophat fails if parameter validity checks pass
Package: octave-image Version: 1.0.8-3+b1 Severity: normal Whenever imtophat is called with parameters that pass its parameter validation, and it attempts to perform the actual top-hat filtering operation, it attempts to access undefined variable and causes an error. Test code: test.m: I = [1 1 1; 1 1 1; 1 1 1;]; se = [1 1; 0 1;]; imtophat(I, se) Execution: % octave test.m Actual output: error: `SE' undefined near line 33 column 29 error: evaluating argument list element number 2 error: evaluating prefix operator `!' near line 33, column 17 error: evaluating binary operator `' near line 33, column 15 error: evaluating assignment expression near line 33, column 10 error: called from `imtophat' in file `/usr/share/octave/packages/3.0/image-1.0.8/imtophat.m' error: near line 3 of file `test.m' Expected output: ans = 0 0 1 0 0 1 1 1 1 Analysis: It appears that the imopen call in /usr/share/octave/packages/3.0/image-1.0.8/imtophat.m erroneously refers to 'SE' when it should refer to 'se'. How this could ever have worked, I don't know. Perhaps Octave was case-insensitive in the past? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.28.7pryan (SMP w/2 CPU cores) Locale: LANG=en_US, lc_ctype=fi...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages octave-image depends on: ii imagemagick7:6.3.7.9.dfsg2-1 image manipulation programs ii libatlas3gf-base [libl 3.6.0-24 Automatically Tuned Linear Algebra ii libatlas3gf-sse2 [libl 3.6.0-24 Automatically Tuned Linear Algebra ii libblas3gf [libblas.so 1.2-2 Basic Linear Algebra Subroutines 3 ii libc6 2.9-25GNU C Library: Shared libraries ii libfftw3-3 3.1.2-3.1 library for computing Fast Fourier ii libgcc11:4.3.3-3 GCC support library ii libgfortran3 4.3.3-3 Runtime library for GNU Fortran ap ii libhdf5-serial-1.8.3 [ 1.8.3-2.1 Hierarchical Data Format 5 (HDF5) ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii liblapack3gf [liblapac 3.1.1-6 library of linear algebra routines ii libncurses55.7+20090228-1shared libraries for terminal hand ii libpng12-0 1.2.35-1 PNG library - runtime ii libreadline5 5.2-4 GNU readline and history libraries ii libstdc++6 4.3.3-3 The GNU Standard C++ Library v3 ii octave3.0 1:3.0.5-7 GNU Octave language for numerical ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime octave-image recommends no packages. octave-image suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539088: [DebianGIS-dev] Bug#539088: libgeos-3.1.0: Assertion fails when buffering a specific multipolygon
On 2009-07-29, at 12:30, Francesco P. Lovergine wrote: On Wed, Jul 29, 2009 at 02:36:51AM +0300, Tuure Laurinolli wrote: The problem has been fixed in upstream GEOS release 3.1.1. Due to a license issue, you have to wait next geos release, or need to provide a minimal patch for the 3.1.0 version. What license issue would this be? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539088: libgeos-3.1.0: Assertion fails when buffering a specific multipolygon
Package: libgeos-3.1.0
Version: 3.1.0-1
Severity: normal
When doing 0-distance buffer on the geometry in script test2.py, GEOS prints
a message stderr and causes the process to exit with code 134.
Test script test2.py:
from shapely import wkt
mp = wkt.loads('MULTIPOLYGON (((3375988.599 6680548.657, 3375856.477
6680761.861, 3376067.385 6680748.959, 3375988.599 6680548.657), (3375921.642
6680736.744, 3375920.948 6680725.834, 3376044.612 6680717.931, 3375921.642
6680736.744)), ((3376292.713 6680820.212, 3376320.365 6680785.36, 3376043.927
6680525.464, 3376292.713 6680820.212)))')
mp.buffer(0)
Running the script requires package python-shapely. Run as follows:
% python test.py
Expected result:
MULTIPOLYGON (((3376292.712999888241 6680820.212002905726,
3376320.365002235174 6680785.360003352761, 3376043.927001415610
6680525.463996870756, 3376292.712999888241 6680820.212002905726)),
((3375988.598999292195 6680548.656996572733, 3375856.476999552965
6680761.860995678663, 3376067.384997764826 6680748.958997988343,
3375988.598999292195 6680548.656996572733), (3375921.64125494
6680736.743999478459, 3375920.947998584390 6680725.833997988343,
3376044.612001974404 6680717.930998658895, 3375921.64125494
6680736.743999478459)))
printed on stdout
Actual result:
bufferOriginalPrecision failed (TopologyException: unable to assign hole to a
shell), trying with reduced precision
recomputing with precision scale factor = 1e+09
Scaler: offsetX,Y: 0,0 scaleFactor: 1e+09
ReScaler: offsetX,Y: 0,0 scaleFactor: 1e+09
recomputing with precision scale factor = 1e+08
Scaler: offsetX,Y: 0,0 scaleFactor: 1e+08
ReScaler: offsetX,Y: 0,0 scaleFactor: 1e+08
recomputing with precision scale factor = 1e+07
Scaler: offsetX,Y: 0,0 scaleFactor: 1e+07
ReScaler: offsetX,Y: 0,0 scaleFactor: 1e+07
recomputing with precision scale factor = 1e+06
Scaler: offsetX,Y: 0,0 scaleFactor: 1e+06
ReScaler: offsetX,Y: 0,0 scaleFactor: 1e+06
recomputing with precision scale factor = 10
Scaler: offsetX,Y: 0,0 scaleFactor: 10
ReScaler: offsetX,Y: 0,0 scaleFactor: 10
recomputing with precision scale factor = 1
Scaler: offsetX,Y: 0,0 scaleFactor: 1
ReScaler: offsetX,Y: 0,0 scaleFactor: 1
recomputing with precision scale factor = 1000
Scaler: offsetX,Y: 0,0 scaleFactor: 1000
ReScaler: offsetX,Y: 0,0 scaleFactor: 1000
recomputing with precision scale factor = 100
Scaler: offsetX,Y: 0,0 scaleFactor: 100
ReScaler: offsetX,Y: 0,0 scaleFactor: 100
recomputing with precision scale factor = 10
Scaler: offsetX,Y: 0,0 scaleFactor: 10
ReScaler: offsetX,Y: 0,0 scaleFactor: 10
recomputing with precision scale factor = 1
recomputing with precision scale factor = 0.1
Scaler: offsetX,Y: 0,0 scaleFactor: 0.1
ReScaler: offsetX,Y: 0,0 scaleFactor: 0.1
recomputing with precision scale factor = 0.01
Scaler: offsetX,Y: 0,0 scaleFactor: 0.01
ReScaler: offsetX,Y: 0,0 scaleFactor: 0.01
recomputing with precision scale factor = 0.001
Scaler: offsetX,Y: 0,0 scaleFactor: 0.001
python: ../../source/headers/geos/noding/SegmentString.h:175: void
geos::noding::SegmentString::testInvariant() const: Assertion `pts-size() 1'
failed.
zsh: abort python test2.py
printed on stderr
The same problem can be reproduced using other software that uses GEOS
as well, e.g. postgresql-8.3-postgis and the operation:
SELECT ST_BUFFER(ST_GEOMFROMTEXT('MULTIPOLYGON (((3375988.599 6680548.657,
3375856.477 6680761.861, 3376067.385 6680748.959, 3375988.599 6680548.657),
(3375921.642 6680736.744, 3375920.948 6680725.834, 3376044.612 6680717.931,
3375921.642 6680736.744)), ((3376292.713 6680820.212, 3376320.365 6680785.36,
3376043.927 6680525.464, 3376292.713 6680820.212)))'), 0);
The problem has been fixed in upstream GEOS release 3.1.1.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.28.7pryan (SMP w/2 CPU cores)
Locale: LANG=en_US, lc_ctype=fi...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages libgeos-3.1.0 depends on:
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libgcc1 1:4.3.3-3 GCC support library
ii libstdc++64.3.3-3The GNU Standard C++ Library v3
libgeos-3.1.0 recommends no packages.
libgeos-3.1.0 suggests no packages.
-- debconf-show failed
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521206: python2.5: ctypes.string_at is not thread-safe
Hm, yes. Perhaps this shouldn't be fixed in stable. In any case, the same problem applies to python-ctypes package at least in testing. I will file another bug for that. signature.asc Description: OpenPGP digital signature
Bug#521337: python-ctypes: ctypes.string_at is not thread-safe
Package: python-ctypes Version: 1.0.2-6 Severity: normal ctypes.string_at and ctypes.wstring_at are not safe to use in software with multiple threads because they do not hold GIL. There is a report of this same issue in the version of ctypes packaged with Python in version 2.5 at at http://bugs.python.org/issue3554 . It seems that the same problem is present in this version of python-ctypes. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.28.7pryan (SMP w/2 CPU cores) Locale: LANG=en_US, lc_ctype=fi...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages python-ctypes depends on: ii binutils 2.19.1-1 The GNU assembler, linker and bina ii libc6 2.9-4 GNU C Library: Shared libraries ii libffi5 3.0.7-1Foreign Function Interface library ii python2.5.4-2An interactive high-level object-o ii python-central0.6.11 register and build utility for Pyt ii python2.4 2.4.6-2An interactive high-level object-o python-ctypes recommends no packages. python-ctypes suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521206: python2.5: ctypes.string_at is not thread-safe
Package: python2.5 Version: 2.5.2-15 Severity: normal ctypes.string_at and ctypes.wstring_at are not safe to use in software with multiple threads because they do not hold GIL. There is an upstream issue report about this at http://bugs.python.org/issue3554, and it has been fixed in new upstream versions (also apparently fixed in python2.5 of testing). -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python2.5 depends on: ii libbz2-1.01.0.5-1high-quality block-sorting file co ii libc6 2.7-18 GNU C Library: Shared libraries ii libdb4.5 4.5.20-13 Berkeley v4.5 Database Libraries [ ii libncursesw5 5.7+20081213-1 shared libraries for terminal hand ii libreadline5 5.2-3.1GNU readline and history libraries ii libsqlite3-0 3.5.9-6SQLite 3 shared library ii libssl0.9.8 0.9.8g-15 SSL shared libraries ii mime-support 3.44-1 MIME files 'mime.types' 'mailcap ii python2.5-minimal 2.5.2-15 A minimal subset of the Python lan python2.5 recommends no packages. Versions of packages python2.5 suggests: pn python-profiler none (no description available) pn python2.5-doc none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517251: d-feet causes segfault if started with $DISPLAY unset
Package: d-feet Version: 0.1.8-2 Severity: normal When started with empty $DISPLAY, d-feet causes a segmentation fault. I did not explore further as to what the exact cause is, but if $DISPLAY is set so that it can connect to an X server, the segfault does not happen. Steps to reproduce: 1. % export DISPLAY= 2. % d-feet Expected result: d-feet complains that it cannot open display, like xterm for example. Actual result: d-feet displays the following messages and segfaults: [19:34:17][ta...@pryan][~]% d-feet /var/lib/python-support/python2.5/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: Unknown property: GtkAction.enabled self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: Warning: invalid (NULL) pointer instance self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: Warning: g_object_get: assertion `G_IS_OBJECT (object)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: Warning: value TRUE of type `gboolean' is invalid or out of range for property `visible' of type `gboolean' self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: Screen for GtkWindow not set; you must always set a screen for a GtkWindow before using the window self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_context_set_font_description: assertion `context != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_context_set_base_dir: assertion `context != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_context_set_language: assertion `context != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_new: assertion `context != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_set_text: assertion `layout != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_set_attributes: assertion `layout != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_set_alignment: assertion `layout != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_set_ellipsize: assertion `PANGO_IS_LAYOUT (layout)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_set_single_paragraph_mode: assertion `PANGO_IS_LAYOUT (layout)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_set_width: assertion `layout != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_get_extents: assertion `layout != NULL' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: PangoWarning: pango_layout_get_pixel_extents: assertion `PANGO_IS_LAYOUT (layout)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: gtk_icon_theme_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: gtk_icon_size_lookup_for_settings: assertion `GTK_IS_SETTINGS (settings)' failed self.ui.add_from_file(ui_dir + '/' + file) /var/lib/python-support/python2.5/dfeet/_ui/uiloader.py:38: GtkWarning: Invalid
Bug#508128: python-iptcdata: Segfault on certain images
Package: python-iptcdata Version: 1.0.2+libtool01-2 Severity: important Accessing one of the data fields provided by the iptcdata python module for image http://fop3.kyla.fi/~tazle/PICT6104.JPG causes segfault. Steps to reproduce: 1. Download the image linked above. 2. Execute python /usr/share/doc/python-iptcdata/examples/show_iptc.py PICT6104.JPG Expected result: show_iptc.py should print all IPTC metadata of the image Actual result: show_iptc.py prints only the first IPTC record, and segfaults on the second one More information: GDB backtrace and relevant variable information from another program trying to access the title attribute of the ds object of the same image, showing get_title trying to dereference a null pointer: #0 0xb7a83e71 in get_title (self=0x827a320, closure=0x0) at /home/ianw/programs/libiptc/pkg-libiptcdata/build-area/libiptcdata-1.0.2+libtool01/./python/pyiptcdataset.c:67 #1 0x08088cbd in PyObject_GenericGetAttr () #2 0x080c69e9 in PyEval_EvalFrameEx () #3 0x080c89a5 in PyEval_EvalFrameEx () #4 0x080c89a5 in PyEval_EvalFrameEx () #5 0x080c89a5 in PyEval_EvalFrameEx () #6 0x080c89a5 in PyEval_EvalFrameEx () #7 0x080ca4b7 in PyEval_EvalCodeEx () #8 0x080ca607 in PyEval_EvalCode () #9 0x080e93a8 in PyRun_FileExFlags () #10 0x080e9649 in PyRun_SimpleFileExFlags () #11 0x08059233 in Py_Main () #12 0x080586f2 in main () (gdb) print self $1 = (DataSetObject *) 0x827a320 (gdb) print self-ds $2 = (IptcDataSet *) 0x82a9b08 (gdb) print self-ds-info $3 = (const IptcTagInfo *) 0x0 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24.7pryan (SMP w/2 CPU cores) Locale: LANG=en_US, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages python-iptcdata depends on: ii libc6 2.7-5 GNU C Library: Shared libraries ii libiptcdata0 1.0.2+libtool01-2 Library to parse IPTC metadata ii python 2.5.2-1 An interactive high-level object-o python-iptcdata recommends no packages. python-iptcdata suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411848: Fix in upstream?
This bug is probably fixed in upstream version 0.76. At least there is a report of adding fault tolerance to SVNPoller in the changelog. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345834: Workaround
Apparently level 0 matches are different from level 0 matches to file. Forcing it to level 1 allows if-then-else structures like the following I used for testing: 0 string \?xml 0 string \?xml 38 string \\!DOCTYPE\040svg image/svg+xml 38 string \\!DOCTYPE\040sve image/sve+xml 0 string \?xml text/xml The following patch against file-4.12-1 magic.mime fixes the problem: --- file-4.12/magic/magic.mime 2006-01-21 15:56:54.0 +0200 +++ magic.mime 2006-01-21 16:35:20.0 +0200 @@ -95,17 +95,12 @@ # end local stuff #-- -# xml based formats! - -# svg +# xml-based formats! 0 string \?xml -# text/xml -38string \\!DOCTYPE\040svg image/svg+xml - - -# xml -0 string \?xml text/xml +0 string \?xml +38 string \\!DOCTYPE\040svg image/svg+xml +0 string \?xml text/xml #-- @@ -400,7 +395,6 @@ 0 string \!-- text/html 0 string/c\h1text/html -0 string \?xml text/xml #-- # images: file(1) magic for image formats (see also c-lang for XPM bitmaps) signature.asc Description: OpenPGP digital signature
Bug#325473: mono-gmcs misses dependency mono-classlib-2.0
Package: mono-gmcs Version: 1.1.8.2-1 Severity: serious Justification: Policy 3.5 Apt-get installing mono-gmcs causes following error report when trying to use it for compiling C# files: [0:24:[EMAIL PROTECTED]/cs]% gmcs testprop.cs The assembly mscorlib.dll was not found or could not be loaded. It should have been installed in the `/usr/lib/mono/2.0/mscorlib.dll' directory. Installing mono-classlib-2.0 corrects this problem. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.9 Locale: LANG=en_GB, LC_CTYPE=fi_FI.iso88591 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages mono-gmcs depends on: ii mono-jit 1.1.8.2-1 fast CLI (.NET) JIT compiler for M Versions of packages mono-gmcs recommends: ii pkg-config0.19-1 manage compile and link flags for -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299243: libgstreamer0.8-dev: Fails to provide /usr/lib/pkgconfig/gstreamer-libs-0.8.pc
Package: libgstreamer0.8-dev Version: 0.8.8-1 Severity: normal When compiling a DVB module for gstreamer from their CVS, it depends on gstreamer-libs-0.8.pc providing correct CFLAGS etc. This file did not exist on my system. The module compiled fine when I created gstreamer-libs-0.8.pc that was a symlink to gstreamer-0.8.pc. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=en_GB, LC_CTYPE=fi_FI.iso88591 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages libgstreamer0.8-dev depends on: ii libc6-dev [libc-dev]2.3.2.ds1-20 GNU C Library: Development Librari ii libglib2.0-dev 2.6.3-1 Development files for the GLib lib ii libgstreamer0.8-0 0.8.8-1 Core GStreamer libraries, plugins, ii libpopt-dev 1.7-5lib for parsing cmdline parameters ii libxml2-dev 2.6.16-3 Development files for the GNOME XM ii pkg-config 0.15.0-4 Manage compile and link flags for -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
