Upstream bug + patch at:
https://bugs.freedesktop.org/show_bug.cgi?id=104789
Reproduced here:
Package: octave-symbolic
Priority: optional
Section: math
Installed-Size: 988
Maintainer: Debian Octave Group pkg-octave-de...@lists.alioth.debian.org
Architecture: amd64
Source: octave-symbolic (1.0.9-1)
Version: 1.0.9-1+b1
vi...@noise:~$ octave
GNU Octave, version 3.2.4
@@ -37,7 +37,7 @@
dh_testroot
dh_clean -k
dh_installdirs
- - echo -e \n\n\n\n\n | perl ./installer.pl /usr/bin/perl /usr
/usr/share/perl5 `pwd`/debian/dbishell
+ echo \n\n\n\n\n | perl ./installer.pl /usr/bin/perl /usr
/usr/share/perl5 `pwd`/debian/dbishell
I will have to release a new version of lpc mode, the current version won't
work in emacs22 because the underlying cc-mode infrastructure has changed
quite a lot (and there was a bug in the new cc-mode, until semi-recently,
which prevented external modes like lpc mode from compiling).
Now that
lpc-mode in its current form doesn't work in emacs22, or didn't
last time I checked, so the dependency (as it stands) is correct.
If you've tried lpc-mode in emacs22 and it _does_ work, let me know -
I have some notes here somewhere about what needs to be done to update
it but I haven't one
Thanks, looks like the NMU was incomplete. I will try and get a
fixed package out tonight or tomorrow.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, 30 Oct 2006, Christian Perrier wrote:
Please let me know whether I should continue with the NMU or if you
will do a regular upload (which needs to be done pretty quickly as the
freeze might happen any time).
I have not completed the DD process and am not sure why the debconf
note is a
Package: kernel-source-2.6.11
Version: 2.6.11-3
Severity: important
When running an em64t kernel with either the megaraid driver or the newer
megaraid_mbox driver, and the machine in question has 4GiB of memory,
reads/writes past the 130GiB mark (approximately) of a partition on the
logical
Scratch the whole 2.6.11 good thing. Apparently, 4GiB of memory instead
of 2GiB means massive corruption of data written to/read from the scsi
devices presented to the OS by the SATA raid card.
Basically, with 2GiB of memory, everything is peachy. With 4GiB, anything
written past a certain point
I should further note that TIOCSPTLCK: Invalid Argument is not the
cause of dbishell failing to build: this is a warning to let me/the
user know that that ioctl numbers shipped with debian's perl are
still broken (see #190887).
This is worked around in the makefile.
--
To UNSUBSCRIBE, email to
believe they are required to do.
The command fakeroot dpkg-buildpackage build.log works for me.
(build.log attached)dpkg-buildpackage: source package is dbishell
dpkg-buildpackage: source version is 0.8.9-7
dpkg-buildpackage: source maintainer is Vivek Dasmohapatra [EMAIL PROTECTED]
dpkg
A few things that came up during an install recently:
The p4-em64t-smp kernels can panic on contact with a megaraid controller.
One machine here worked fine, the other panicked every time.
You can get around this by choosing go back at some point and setting
the debconf question priority to low,
Ok, I finally stumbled on the answer when somebody reported a problem
on another system.
Term::ReadLine::Perl ignores the filehandle passed to it when calling
Term::ReadKey, so all the pty magic in the makefile is ignored, as
trl-perl just attempts to call ioctls on STDIN instead of the
dbishell --driver Oracle --dsn host=foobar\;sid=argh--user=scott
dbishell --driver
mysql --dsn host=narf\;database=argh --user vivek dbishell --driver
Sybase --dsn
hostname=narf\;database=argh --user=sa dbishell --driver ODBC --dsn FOO:
14 matches
Mail list logo
