Bug#900445: camlzip version 1.07 needed for zlib >= 1.2.9

Package: libzip-ocaml Version: 1.06-2+b1 I'd like to request that the Debian package of camlzip (libzip-ocaml) be updated at least to the latest numbered release, version 1.07. The reason this is significant is that older versions of camlzip up through 1.06 will no longer work reliably with recent

Bug#627132: New "-custom" binary generation breaks stack backtraces

SMcC> The "strip"ping problem that appeared to motivate the new SMcC> embedding process had never bothered us, so another suitable SMcC> workaround from our perspective would be if there was a way to SMcC> disable the new "-output-obj"-style behavior. SG> On 05/24/2011 11:41 AM, Stéphane Glondu wr

Bug#632670: check_current_directory fails with symlinks

The symlink problem bit me too. I would think it's actually a fairly common situation for /var/cache/approx to be a symlink, since it's easy to use much more space for .debs than any of the other contents for /var. (Especially if you save the old ones; my /var/cache/approx is currently 49GB, compar

Bug#627132: New "-custom" binary generation breaks stack backtraces

>>>>> "SG" == Stephane Glondu writes: SG> Le 17/05/2011 23:33, Stephen McCamant a ecrit : SMcC> [...] another suitable workaround from our perspective would be SMcC> if there was a way to disable the new "-output-obj"-style SMcC> behavior. SG>

Bug#627132: New "-custom" binary generation breaks stack backtraces

Package: ocaml Version: 3.12.0-5 Severity: normal It appears that the new "-output-obj" style strategy for generating -custom bytecode executables (cf. patches/0011-Embed-bytecode-in-C-object-when-using-custom.patch) has broken the normal usage of stack backtraces in such executables. We have a la

Bug#627125: Regenerate PDF to avoid "bfrange" warning

Package: asymptote-doc Version: 2.02-2 Severity: minor Recent versions of Debian have had a somewhat infamous bad interaction between 8.x versions of ghostscript and 0.12.x versions of poppler that causes mostly harmless but annoying error messages related to the tools' disagreement about the lega

Bug#357256: [xmem] switches view even if no swap is present

> "MK" == Michelle Konzack writes: MK> Hello Stephen, MK> can you test the package please? MK> It can be found here: MK> MK> "apt-get install" is currently not available because I have to MK> reinstall the mirror and the scr

Bug#357256: [xmem] switches view even if no swap is present

SMcC> Using ceil() to do the rounding would probably fix your version SMcC> of the problem. I think the best fix, though, might be to change SMcC> the calculation to "ceil(x - epsilon)", where epsilon is chosen SMcC> to be about the amount that would show up as a single pixel in SMcC> the display:

Bug#578586: Seconded: sysfs filename changes, priority vs. /proc/acpi

My experiences are the same as Ken's. My laptop is a whitebox model based on an Intel "Crestline" 82965GM chipset. My kernel version is 2.6.32-3, and my /sys/class/power_supply/ tree looks exactly like Ken's. I was able to get ibam to see my battery charge information only after switching to the

Bug#521729: mnemosyne: Fails to start when no locale is set in the environment

Package: mnemosyne Version: 1.2-r1-1 File: /usr/bin/mnemosyne Severity: normal I recently upgraded both mnemosyne and libc (to the new 2.9 version in unstable, 2.9-6). Now, for the first time, mnemosyne fails to start if no locale environment variables are set, which is the way my environment is g

Bug#515896: Disfavor "dieing" (already fixed upstream)

Package: scowl Version: 6-2.3 The normal -ing form of "to die" (to perish) is "dying". Related to the less common noun "die" meaning a metal forming tool there's a verb "to die" meaning to cut or shape with a die, and the -ing form of this is "dieing". This correct form of "dieing" is quite rare a

Bug#511854: Include dirs mis-ordered when /usr is a symlink, breaks

Package: g++-4.3 Version: 4.3.2-1.1 It looks like this is the same problem as bug #492817 and maybe also #102473, but those were closed rather than simply being tagged as moreinfo/unreproducible, so my understanding is that a new one is needed. When /usr is a symlink, g++'s approach for finding w

Bug#484738: Transcriber crashes under Tcl 8.5

RT> transcriber doesn't seem to work when tk8.5 is installed. I will RT> upload a new package with conflict to tk8.5 -Ralf. In my testing, it isn't that there's any strange conflict caused by having Tk 8.5 merely existing on the system. Rather, the problem is more straightforwardly that transcribe

Bug#487549: tcLex segfaults under tcl8.5 (in transcriber)

Package: tclex Version: 1.2a1-14 When I try to run transcriber, which uses tcLex, under a version 8.5 Tcl/Tk wish, it segfaults. If a file is specified on the command line, it crashes immediately; otherwise it opens a file chooser and then crashes after you choose a file. (I suspect that this is t

Bug#357256: [xmem] switches view even if no swap is present

SJR> the system I'm working on does not have swap space (for a SJR> reason), yet xmem still switches to include a horizontal line for SJR> the physical/swap boundary. Obviously, the upper half is empty; SJR> it even switches back sometimes. This appears to be a "slightly SJR> above 100%" condition

Bug#394380: int/long confusion causes xsetbg segfault on AMD64

Package: xloadimage Version: 4.1-14.3 A call to XGetWindowProperty() in root.c incorrectly casts between pointers to ints and longs, causing the values returned from the function to be incorrect on platforms such as AMD64 where longs are larger than ints. Under some circumstances, this seems to ca

Bug#348399: Incompatible instructions in povray binary

I'm having what sounds like the same problem as the previous reports. The packaged POV-Ray binary (I tried 3.6.1-3) crashes with SIGILL early in the processing of even a simple file. Like the previous posters, my machine is a K7 (an 2-processor Athlon MP 2600+, to be precise). However, if I recompi

Bug#316479: X11::Auth should warn on corrupt .Xauthority

Thanks for investigating this problem, and for saving the file to reproduce it. The corruption of the .Xauthority file seems to consist just of a bunch of extra null bytes at the front. A series of 10 null bytes represents an authority record for an Internet connected display whose address is the e

Bug#281632: Timezone in "cvs log" and "cvs ls" always shows UTC

I noticed this old bug on the list of ones I'd submitted that were still open, and was interested to see it was still broken. (Coincidentally, it just celebrated its one-year birthday.) For anyone who's interested, this problem was actually fixed in the upstream CVS even before I reported it, and

Bug#339032: ACL2 needs more inter-package dependencies to prevent upgrade breakage

Package: acl2-books-certs Version: 2.9.3-7 I have a group of computers here that are mainly trying to stay with sarge, with a few updates. They currently have ACL2 version 2.9.1-1 (rather than the 2.9-2 in sarge, for the :dir :system fix). ||/ Name VersionDescription +++-===

Bug#326832: libc6: valgrind reports use of uninitialized values

* Justin Pryzby: JP> valgrind reports 13 instances of "Conditional jump or move depends JP> on uninitialised value(s)" using the new libc6 in testing, for a JP> trivial program which just calls exit(0). This is JP> valgrind-2.4.0-3. FW> This means that the valgrind suppression files are out of d

Bug#331727: valgrind: suppression does not work

WD> I have the following entry in my ~/valgrind.supp file WD> { WD>L_2 WD>Memcheck:Cond WD>obj:/lib/ld-2.3.5.so WD>obj:/lib/ld-2.3.5.so WD>obj:/lib/ld-2.3.5.so WD>obj:/lib/ld-2.3.5.so WD>obj:/lib/ld-2.3.5.so WD>obj:/lib/ld-2.3.5.so WD> } WD> I still get WD> ==5270

Bug#302885: QSizePolicy type change in 3.14 breaks pyuic-generated UIs

Package: python2.3-qt3 Version: 3.14.1-1 Severity: important In the latest release of PyQt, it appears that the types allowed by the QSizePolicy constructor have changed in an incompatible way. They now must be enumerated values, such as QSizePolicy.MinimumExpanding, rather than the corresponding

Bug#302882: Need to regenerate UI for comparability with PyQt upgrade

Package: memaid-pyqt Severity: important Tags: patch Version: 0.2.3-2 The most recent (3.14) version of PyQt (python-qt3 3.14.1-1) makes an incompatible change to the arguments to the QSizePolicy constructor: only enumerated values are allowed, and not the corresponding integer values. Unfortunate