Bug#653202: git-doc: description of paths argument to git-bisect is ambiguous

2011-12-24 Thread Britton Leo Kerin
Package: git-doc Severity: normal The description of the paths options to git-bisect looks like this: Cutting down bisection by giving more parameters to bisect start You can further cut down the number of trials if you know what part of the tree is involved in the problem you are

Bug#620209: make: inconsistant description of ifdef directive behavior

2011-03-31 Thread Britton Leo Kerin
Package: make Version: 3.81-5 Severity: normal The manual says: ifdef variable-name The ifdef form takes the name of a variable as its argument, not a reference to a variable. The value of that variable has a non-empty value, the text-if-true is effective; otherwise, the

Bug#620211: make: it would be nice to get -R behavior using a directive inside a Makefile

2011-03-31 Thread Britton Leo Kerin
Package: make Version: 3.81-5 Severity: wishlist Please note I'm actually running my own compiled version of 3.82. I just find the debian bug reporting interface a little too easy, and this is an upstream wishlist item :) The subject pretty much says it. What I do now is:

Bug#601251: perl: /x modifier doesn't seem to make regex completely whitespace-insensitive

2010-10-24 Thread Britton Leo Kerin
Package: perl Version: 5.10.0-19lenny2 Severity: normal Given: $tdl = 'dir call netrw#Explore(count,0,0+bang0,q-args) ' This doesn't die: $tdl =~ s/^( augroup | buffer | command | dir | environment | event | expression | file | shellcmd | function |

Bug#599432: zenity munges underscores into activators without mentioning in man page

2010-10-07 Thread Britton Leo Kerin
Package: zenity Version: 2.22.1-2 Severity: normal I found some documentation on the web which explicitly mentiontions this behavior. The man page doesn't. Neither source seems to mention that you appear to be able to get around the problem by using a double underscore to mean underscore.

Bug#587704: vim-gnome: built-in perl emulator Buffer-Get method doesn't work as documented

2010-06-30 Thread Britton Leo Kerin
Package: vim-gnome Version: 1:7.1.314-3+lenny2 Severity: normal This fragment: our $curbuf; my $buf_header = $curbuf-Get( 1 .. 3 ); Doesn't work as described in the documentation, I end up with $buf_header empty (with a buffer that does contain these lines). -- System Information: Debian

Bug#432149: fetchmailconf: username with '@' required by email service provider causes problems

2007-07-07 Thread Britton Leo Kerin
Package: fetchmailconf Version: 6.3.6-1 Severity: normal I have a service provider which requires my username to be: [EMAIL PROTECTED] fetchmailconf warns me that this can cause trouble, but I don't have a choice since this is what fastmail explicitly requires. The produced config file

Bug#432149: fetchmailconf: actually it works (but confused me)

2007-07-07 Thread Britton Leo Kerin
Package: fetchmailconf Version: 6.3.6-1 Followup-For: Bug #432149 Ok, actually you do get to change the offered local name to bkerin in the GUI dialog for the individual user if you want. So all I can say is that it confused me (daunting to have to remove the very user ID you are trying to

Bug#389491: manpages-dev: mq_open man page lists nonexistent errno code 'EACCESS'

2006-09-25 Thread Britton Leo Kerin
Package: manpages-dev Version: 2.39-1 Severity: normal I think it should be 'EACCES'. -- 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.16-2-k7 Locale:

Bug#387551: manpages-dev: mq_receive man page shows wrong return type 'mqd_t' (correct is ssize_t)

2006-09-14 Thread Britton Leo Kerin
Package: manpages-dev Version: 2.39-1 Severity: normal As the subject says. Looking in /usr/include/mqueue.h the actual return type is ssize_t, as expected. Britton -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386

Bug#384104: gnome: making caps lock an additional ctrl give slightly different cntr-x cntr-c behavior in emacs

2006-08-21 Thread Britton Leo Kerin
Package: gnome Severity: minor Recent GNOME version crashed when you tried to make caps lock an additional control (Desktop-prefereces-keyboard-layout options-Ctrl key position). It doesn't crash now, but it doesn't really work absolutely as expected either. I selected the Make CapsLock an

Bug#365642: gnome: same problem with at least one other Keyboard pref-layout Option

2006-06-18 Thread Britton Leo Kerin
Package: gnome Followup-For: Bug #365642 I have a similar problem with Keyboard Preferences-Ctrl key position-Make CapsLock an additional Ctrl. But since there are at least two settings with this issue seems like a decent chance it may be a more general problem. I'm running the latest nvidia

Bug#359948: vorbis-tools: ogg123 undocumentedly requires -d to preceed -f

2006-03-29 Thread Britton Leo Kerin
Package: vorbis-tools Version: 1.1.1-3 Severity: minor Actually the man page doesn't really even say that -f is going to require -d, and the error message that you get when you try -f alone doesn't say that you need to have the -d preceed the -f, though this requirement probably makes sense. So

Bug#350945: subversion: inscrutable error message while trying to create tag from working copy

2006-02-01 Thread Britton Leo Kerin
Package: subversion Version: 1.2.3dfsg1-3 Severity: normal The svn book (http://svnbook.red-bean.com/en/1.1/ch04s06.html#svn-ch-4-sect-6.2) describes creating a complex tag this way: $ ls my-working-copy/ $ svn copy my-working-copy http://svn.example.com/repos/calc/tags/mytag

Bug#350236: /usr/share/man/man2/kill.2.gz: effect of kill send by process to itself not fully clear

2006-01-27 Thread Britton Leo Kerin
Package: manpages-dev Version: 2.17-1 Severity: normal File: /usr/share/man/man2/kill.2.gz The nots section of the kill man page contains this paragraph: POSIX 1003.1-2003 requires that if a process sends a signal to itself, and that process does not have the signal blocked, and no

Bug#350055: glibc-doc: nanosleep documentation misleading about second (output) argument behavior

2006-01-26 Thread Britton Leo Kerin
Package: glibc-doc Version: 2.3.5-8 Severity: normal The nanosleep info documentation seems to be saying that the second argument (struct timespec *REMAINING in that reference) is filled in with a timespec value of 0 even if the function was not interupted by a signal: -- Function: int

Bug#350076: subversion: svn diff --diff-cmd option fails inscrutably

2006-01-26 Thread Britton Leo Kerin
Package: subversion Version: 1.2.3dfsg1-3 Severity: minor This works: svn diff --diff-cmd=diff sleep_on_option.c | less but this (using fldiff) doesn't: svn diff --diff-cmd=fldiff sleep_on_option.c | less ^^ I see some output in the terminal like this:

Bug#347793: libc6: well the 'most basic pthread program' is in error

2006-01-19 Thread Britton Leo Kerin
Package: libc6 Version: 2.3.5-8 Followup-For: Bug #347793 The pthread_join call is wrong, as the second argument isn't the address of an actual pointer. Get it right: void *return_pointer; return_code = pthread_join (thread, return_pointer); and the complaint goes away. So I guess my bug

Bug#346539: gnucash: account completion remembers old names of renamed accounts

2006-01-08 Thread Britton Leo Kerin
Package: gnucash Version: 1.8.10-12 Severity: minor I renamed an account two levels down an account tree (probably doesn't matter where the account is in the tree, but I haven't confirmed) and then entered some more transactions from that account, and the completion code still wants to complete

Bug#346106: sox: seg fault (probably during command line parsing)

2006-01-05 Thread Britton Leo Kerin
Package: sox Version: 12.17.9-1 Severity: normal Example: greenwood$ touch foo greenwood$ sox -t cdr foo - -t sw foo.raw Segmentation fault (core dumped) Doesn't matter if foo is or isn't actually a cdr file, so I guess this is a problem parsing the command line. The error in the above is the