On Sun, Apr 29, 2007 at 06:09:13PM +0200, Roland Stigge wrote:
A textbox with $\GlucoseUptakeFunction$
turns into
\rput(9.10,-5.56){\scalebox{1
-1}{(\$\textbackslash{}GlucoseUptakeFunction\$)}}
when exported to pstricks macros.
Yes. What you see is what you get ;)
On Wed, Apr 25, 2007 at 07:21:36PM +0200, Andreas Metzler wrote:
Given the task of finding how -wholename pattern matching works, I
would start by reading the manpage description of the test:
Wondering what shell pattern exactly means, I would simply search
the manpage for shell pattern und
I tend to disagree with your report.
I am no native speaker of the English language, but to me it is rather
clear that metacharacters are simply the characters which have a
special meaning in the context and are not taken literally.
The context is specified: match shell pattern pattern.
On Fri, Jan 26, 2007 at 07:14:07AM +0100, Ola Lundqvist wrote:
Quite strange. I can not see any obvious reasons in the code. However
in some places with timeouts the code is in milliseconds but that should
not matter actually. We do not have an integer overflow either.
Do you know where the
Package: openoffice.org
Version: 2.0.4.dfsg.2-2
Severity: normal
When exporting to PDF, some of the letters are very close together
(touching in some cases). I haven't made any changes to the openoffice
settings, this is a fresh install. I have seen this with DejaVu Sans
and another font that
For anyone who finds this bug and is having this problem, a workaround I'm
currently using (assuming you have the CUPS printing system set up) is to use
the the cups-pdf printer and print to that instead of doing a PDF export. So
far it seems to work much better than the OpenOffice PDF export.
Package: vnc4server
Version: 4.1.1+X4.3.0-20
Severity: normal
When I use -IdleTimeout 4, everything works normally.
When I use -IdleTimeout 1000, the vnc viewer only updates the screen
when I move the mouse (I can type at a console for example, and the
typing only shows up once I move
Package: spampd
Version: 2.30-15
Severity: grave
$ aptitude install spampd
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following NEW packages will be automatically
It may be a out of memory problem. I have a Xen instance with low memory, and
I have discovered that many (well... make that most) applications don't
properly report out of memory errors. A nice exception is anything written in
Python; the reason I realized this was the culprit was when I ran
I tried downgrading libsane and sane-utils to the Sarge version and got the
exact same response. Then I tried downgrading libusb too (a pain) and got a
different, but similar response where it alternated between working and not
every other time I ran scanimage.
--
To UNSUBSCRIBE, email to
All these commands were run consecutively, although the timing between them
varied between 10 and 60 seconds. I tried this plugged directly into the USB
port of my computer (IBM Thinkpad 600E) and it didn't seem to make a
difference relative to plugging it into the USB hub.
$ scanadf
Package: dia
Version: 0.95.0-4.1+b1
Severity: normal
A textbox with $\GlucoseUptakeFunction$
turns into
\rput(9.10,-5.56){\scalebox{1
-1}{(\$\textbackslash{}GlucoseUptakeFunction\$)}}
when exported to pstricks macros.
-- System Information:
Debian Release: 4.0
APT prefers testing
Package: dia
Version: 0.95.0-4.1+b1
Severity: normal
Not sure the reason, but pstricks exports fail (during latex compile) with
ERROR: Illegal unit of measure (pt inserted).
unless \scalebox commands are changed to \psscalebox commands.
-- System Information:
Debian Release: 4.0
APT prefers
On Fri, Jan 05, 2007 at 08:38:06AM +0100, Adrian von Bidder wrote:
I'm not quite sure what the solution was, but I *think* it had something to
do with BerkeleyDB not always liking NFS or Xen or anything of the sort,
but I'm not sure anymore. Could that be an issue for you?
I don't have the
Package: postgrey
Version: 1.27-3
Severity: important
I don't know how to track this down, but postgrey has been hanging after
several days of use and can only be stopped with kill -9. My mail log
looks like this:
Jan 4 23:11:09 sly postfix/smtpd[10391]: connect from
Package: coreutils
Version: 5.97-5
Severity: minor
The man page for ls says:
-l use a long listing format
What long listing format means is never described. Since this format
is not obvious should be described briefly in the man page. An example
of where it is not obvious is for
Package: bash
Version: 3.1dfsg-8
Severity: normal
I'm not sure how to make a test case out of this because it only happens
for one case out of many in a program. The summary is: I have a
function 'global_getopt_scan' I use to parse arguments, and return the
array GLOBAL_ARGS to the caller.
1)
Package: bash
Version: 3.1dfsg-8
Severity: normal
I'm not sure how to make a test case for this one, but the script that will
cause the error is at
http://danielwebb.us/misc/bash_bug.tar.gz
Run:
$ ./unixy-backup.restore_metadata . .unixy-backup.meta_filelist
And I get:
malloc:
Package: grep
Version: 2.5.1.ds2-6
Severity: minor
Man page says:
The fundamental building blocks are the regular expressions that match a
single character. Most characters, including all letters and
digits, are regular expressions that match themselves. Any
metacharacter with special
Package: sysklogd
Version: 1.4.1-18
Severity: minor
From the man page:
Multiple selectors may be specified for a single action using the
semicolon (``;'') separator. Remember that each selector in the
selector field is capable to overwrite the preceding ones. Using this
behavior you
Package: findutils
Version: 4.2.28-1
Severity: minor
It mentions metacharacters, but does not define them and is not
precise about how they work, for example with --wholename. Also, it is
not clear if it is possible to escape metacharacters.
-- System Information:
Debian Release: 4.0
APT
Package: coreutils
Version: 5.97-5
Severity: minor
The stat man page refers to backslash escapes but never describes them.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to
I found this bug on accident, while using setfacl -R in the same way I was
using chmod -R. The behavior should be the same, and the man page describes
it as the same, but it isn't. I was fortunate in that I found out when a
symbolic link in a user directory pointed to the root partition which
On Wed, Apr 12, 2006 at 07:51:53PM +1000, Nathan Scott wrote:
Please do... actions speak alot louder than words.
[I'm CCing security because I already wrote them about this]
I've never used any of these libraries, so bear with me...
(looking at the Debian stable version)
setfacl.c line 341:
Package: python2.3-psycopg
Version: 1.1.18-1
Severity: normal
$ python
import psycopg
a=psycopg.BOOLEAN(True)
Segmentation fault
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.15.1
Package: scponly
Severity: normal
When I use scponly in chroot mode, I can see with debug on that the scp
in the chroot is saying:
unknown user 1030
(or whatever the user is)
The user exists in /etc/passwd, /chroot_dir/etc/passwd.
I copied my entire /lib, /usr/lib, and /etc trees to the
Package: rdiff-backup
Severity: normal
*** Please type your report below this line ***
I'm confused why the versions in sarge and unstable are both from Ben's
development branches of rdiff-backup? The current stable version of
rdiff-backup is 1.0.3. Ben also wondered why Debian is doing this
In sarge, we have 0.13.4-5. This version is not a development version,
it is just horribly outdated.
Oh, ok I was probably just confused about it, I thought Ben was using an odd
second number in the version to indicate the development branch. I would
image you know better than me on that.
On Mon, Dec 19, 2005 at 10:10:32PM -0500, Clint Adams wrote:
$ fakeroot
$ whoami
webb
I verified that SysV IPC is on in my kernel options.
On a 2.4.22 system I have also running Debian stable, I get the expected
root.
Does fakeroot-tcp exhibit the same behavior?
Yes. I can
Package: fakeroot
Version: 1.2.10
Severity: normal
$ fakeroot
$ whoami
webb
I verified that SysV IPC is on in my kernel options.
On a 2.4.22 system I have also running Debian stable, I get the expected
root.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500,
On Sat, Jun 11, 2005 at 12:14:17AM +0300, Lior Kaplan wrote:
Did you check that the recipient get your PID? or that's something that
only goes for the log?
I sent a fax and verified that the line at the top of the fax looks exactly
like the line in the log (and thus, includes my calling-card
session 196lpi 14.4kbps 8.5/215mm any 1D- - 0ms
efax: 36:36 sent TSI - caller ID
efax: 36:36 sent DCS - session format
efax: 36:40 sent TCF - channel check of 2700 bytes
efax: 36:44 received CFR - channel OK
efax: 36:45 header:[Sat 04-Jun-2005 17:35From Daniel Webb (
0
Package: libglib2.0-0
Version: 2.6.2-1
Severity: normal
# Autoconf snip:
AM_PATH_GLIB_2_0([1.2.0],,[AC_MSG_ERROR([glib 1.2 or newer is
required])])
$ autoreconf
$ ./configure
snip
checking for pkg-config... /usr/bin/pkg-config
checking for GLIB - version = 1.2.0...
*** 'pkg-config
Ugh! I spend nearly an hour trying to track down why this was
happening so as not to file a frivolous bug report, but here I've gone
and done it anyway. Turned out I have a /usr/local version of glib I
had forgotten about.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: xmms-liveice
Version: 1.0.0-6
Severity: normal
One of the bitrate options in xmms-liveice is 196000. I'm guessing
this should be 192000. xmms-liveice doesn't work with this setting
(nothing is streamed to liveice), but 16 and 256000 work fine.
-- System Information:
Debian
This should still be at least a wishlist to change the man page to
clarify that -g only works for -L port forwarding. In the SSH docs,
port forwarding is pretty much described the same for -L and -R
forwarding, so the -g description in the manual should make clear that
it is only for -L
Package: afio
Version: 2.5-2
Severity: minor
When using afio -i with the -Z option, files that have errors and don't
uncompress are still listed as being uncompressed in the -v output.
For example, I intentionally corrupted backup/D1.gz in the afio file,
and tried to install it. This is the
37 matches
Mail list logo
