Bug#1028561: /usr/bin/update-alternatives: Counting mistake in terminal returns

[Daniel B]

Package: dpkg
Version: 1.21.9kali1
Severity: minor
File: /usr/bin/update-alternatives
X-Debbugs-Cc: p2...@icloud.com

Hey there,

when doing "sudo update-alternatives --config x-session-manager" the ruturn is 
(on German, sorry...):

> Es gibt 3 Auswahlmöglichkeiten für die Alternative x-session-manager (welche 
> /usr/bin/x-session-manager bereitstellen).
> 
>   Auswahl  Pfad  Priorität Status
> 
> * 0/usr/bin/startxfce450automatischer Modus
>   1/usr/bin/startplasma-x11   40manueller Modus
>   2/usr/bin/startxfce450manueller Modus
>   3/usr/bin/xfce4-session 40manueller Modus
> 
> Drücken Sie die Eingabetaste, um die aktuelle Wahl[*] beizubehalten,
> oder geben Sie die Auswahlnummer ein: 

It tells me there's 3 choices. But it's 4. It would be 3 *alternatives* to my 
current *choice*.
It should be something like "Es gibt 3 alternative Auswahlmöglichkeiten", 
adding "alternative",
which would translate to "There are 3 alternative choices [...]".

(Freshly installed Kali Linux, was going to switch from xfce to plasma)

Thx for ur work :)


-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

-- System Information:
Distributor ID: Kali
Description:Kali GNU/Linux Rolling
Release:2022.4
Codename:   kali-rolling
Architecture: x86_64

Kernel: Linux 6.0.0-kali3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.36-4
ii  liblzma5 5.2.7-0.1
ii  libselinux1  3.4-1+b3
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4.1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.5.4
pn  debsig-verify  

-- no debconf information

Bug#1015999: emacs: tags-query-replace doesn't start from beginning of already-loaded files

[Daniel B.]

Package: emacs
Version: 1:27.1+1-3.1
Severity: normal

Dear Maintainer,

Doing a tags-query-replace that operates on files that are already opened in
buffers doesn't start searching at the beginning of the file/buffer (as it has
done for years).  (It seems to start at each buffer's point instead.)

(This makes is really difficult to do a series of tags-query-replace commands
on a set of files--one has to do something like deleting all the buffers so a
subsequent tags-query-replace command processes the whole of each file.)

  * Create a TAGS file listing a file.
  * Begin a tags-query-replace that will find something in the file.  (You
don't need to replace anything.)
  * Begin a second tags-query-replace that should find something that is in the
buffer _before_ the last match you went to in the previous step.  Note how
tags-query-replace does not find that something, bu only finds matches
_after_ that previous match.

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs depends on:
ii  emacs-gtk  1:27.1+1-3.1

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information

Bug#1001107:

[Daniel B]

I see that LLVM are now active on GitHub Issues, so I have filed this there
too. Hopefully someone on either side eventually notices it ;-)

https://github.com/llvm/llvm-project/issues/52696

Bug#851864: regression: 2.6.1-5+deb8u1 breaks python-paramiko

[Daniel B]

Oops, forgot to include you.



[Switching to Thread 0x7fffbf5fe700 (LWP 12511)]
PyObject_CallFunctionObjArgs () at ../Objects/abstract.c:2756
2756../Objects/abstract.c: No such file or directory.


#0  PyObject_CallFunctionObjArgs () at ../Objects/abstract.c:2756
#1  0x75f74e49 in _servername_callback (s=,
al=0x7fffbf5fc584,
args=0x73e88a10) at
/home/jmm/scratch/spu/python2.7-2.7.9/Modules/_ssl.c:2975
#2  0x765a9db9 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#3  0x765936cf in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#4  0x76598385 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#5  0x765a31ce in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#6  0x7659ff84 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#7  0x75f77c04 in PySSL_SSLread.lto_priv.39
(self=0x701eb3b0, args=)
at /home/jmm/scratch/spu/python2.7-2.7.9/Modules/_ssl.c:1723
#8  0x004c9196 in call_function (oparg=,
pp_stack=)
at ../Python/ceval.c:4033
#9  PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#10 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#11 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#12 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#13 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#14 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#15 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#16 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#17 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#18 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#19 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#20 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#21 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#22 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#23 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#24 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#25 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#26 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#27 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#28 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#29 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#30 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#31 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#32 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#33 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#34 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#35 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#36 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#37 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#38 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#39 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#40 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#41 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#42 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#43 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#44 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#45 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#46 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#47 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#48 0x004e4518 in PyEval_EvalCodeEx (closure=,
defcount=,
defs=, kwcount=, kws=, argcount=,
args=, locals=, globals=, co=)
at ../Python/ceval.c:3265
#49 function_call.lto_priv () at ../Objects/funcobject.c:526
#50 0x00502ab8 in PyObject_Call (kw=,
arg=, func=)
at ../Objects/abstract.c:2529
#51 instancemethod_call.lto_priv () at ../Objects/classobject.c:2602
#52 0x004d0f2b in PyObject_Call (kw=, arg=(),
func=) at
../Objects/abstract.c:2529
#53 PyEval_CallObjectWithKeywords () at ../Python/ceval.c:3902
#54 0x005bc202 in t_bootstrap () at ../Modules/threadmodule.c:614
#55 0x77bc7064 in start_thread (arg=0x7fffbf5fe700) at
pthread_create.c:309
#56 0x76fd962d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Bug#851864: regression: 2.6.1-5+deb8u1 breaks python-paramiko

[Daniel B]

I'll provide it anyway.

[Switching to Thread 0x7fffbf5fe700 (LWP 12511)]
PyObject_CallFunctionObjArgs () at ../Objects/abstract.c:2756
2756../Objects/abstract.c: No such file or directory.


#0  PyObject_CallFunctionObjArgs () at ../Objects/abstract.c:2756
#1  0x75f74e49 in _servername_callback (s=,
al=0x7fffbf5fc584,
args=0x73e88a10) at
/home/jmm/scratch/spu/python2.7-2.7.9/Modules/_ssl.c:2975
#2  0x765a9db9 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#3  0x765936cf in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#4  0x76598385 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#5  0x765a31ce in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#6  0x7659ff84 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
#7  0x75f77c04 in PySSL_SSLread.lto_priv.39
(self=0x701eb3b0, args=)
at /home/jmm/scratch/spu/python2.7-2.7.9/Modules/_ssl.c:1723
#8  0x004c9196 in call_function (oparg=,
pp_stack=)
at ../Python/ceval.c:4033
#9  PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#10 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#11 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#12 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#13 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#14 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#15 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#16 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#17 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#18 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#19 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#20 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#21 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#22 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#23 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#24 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#25 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#26 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#27 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#28 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#29 0x004c7a59 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265
#30 0x004c96fd in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4129
#31 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#32 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#33 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#34 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#35 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#36 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#37 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#38 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#39 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#40 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#41 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#42 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#43 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#44 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#45 0x004c996a in fast_function (nk=,
na=, n=,
pp_stack=, func=) at ../Python/ceval.c:4119
#46 call_function (oparg=, pp_stack=) at
../Python/ceval.c:4054
#47 PyEval_EvalFrameEx () at ../Python/ceval.c:2679
#48 0x004e4518 in PyEval_EvalCodeEx (closure=,
defcount=,
defs=, kwcount=, kws=, argcount=,
args=, locals=, globals=, co=)
at ../Python/ceval.c:3265
#49 function_call.lto_priv () at ../Objects/funcobject.c:526
#50 0x00502ab8 in PyObject_Call (kw=,
arg=, func=)
at ../Objects/abstract.c:2529
#51 instancemethod_call.lto_priv () at ../Objects/classobject.c:2602
#52 0x004d0f2b in PyObject_Call (kw=, arg=(),
func=) at
../Objects/abstract.c:2529
#53 PyEval_CallObjectWithKeywords () at ../Python/ceval.c:3902
#54 0x005bc202 in t_bootstrap () at ../Modules/threadmodule.c:614
#55 0x77bc7064 in start_thread (arg=0x7fffbf5fe700) at
pthread_create.c:309
#56 0x76fd962d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Bug#851864: regression: 2.6.1-5+deb8u1 breaks python-paramiko

[Daniel B]

Apologies, my issue is not caused by this package.

Bug#828568: [tcpcrypt-dev] tcpcrypt build failures against openssl 1.1.0

[Daniel B Giffin]

thanks for the alert!

i've pushed changes that compile on both 1.0.2 and on
OpenSSL_1_1_0-pre5:

  
https://github.com/scslab/tcpcrypt/commit/1915ddbe678b35d3deb2ea2b2aa2ea7bb476af80

we've got some other work to do on the code to bring it in
line with recent spec changes, so we'll let you know when it
makes sense to re-package.

daniel

Bug#216609: closed by Solveig (Closing old emacs21 bugs)

[Daniel B.]

> I'm closing this bug, since it affected emacs21, and the current
> version is 23.

What?  Just because the current version of Emacs is 23 and a bug was
reported against version 21 is no reason to throw out the bug report.
If the bug still exists in Emacs 23, the report should remain open.

Are you trying to say that you can't reproduce the bug in Emacs 23?


Daniel
--
Daniel B.
d...@smart.net


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#213552: closed by Phillip Susi (mount does not report underlying error - unrecognized mount option "xyz" for -t ext2)

[Daniel B.]

> This is not a bug; ...

How is a bad error message (such a non-specific message) not a usability
problem?

> ... mount tells you to check dmesg for more detailed  error messages.

No, it does not:  From my report, here's what mount says:

   # mount -t ext2  /dev/cdrw /mnt
   mount: block device /dev/cdrw is write-protected, mounting read-only
   mount: wrong fs type, bad option, bad superblock on /dev/cdrw,
  or too many mounted file systems
   #

How do you claim that that tells the user to look at dmesg?  There's
no mention of dmesg, checking logs, or anything similar.


I'm trying to get this usability problem fixed for users that run
into the same problem that I did.

If you don't feel like improving the message, then at least leave
the bug report open so users have a chance that someone will see
the problem and fix it some day.


Daniel


--
Daniel B.
d...@smart.net

--
Daniel B.
d...@smart.net


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700752: modal Privacy... window shown _after_ starting playing; unclear config.

[Daniel B.]

Package: vlc
Version: 1.1.3-1squeeze6
Severity: normal

When I ran vlc with some audio files as command-line arguments, vlc started 
playing that set of files and then displayed the Privacy and Network Policies 
window/dialog.  Because that dialog is modal, I couldn't  control (not even 
pause!) the playback until I finished with that dialog.  


I couldn't finish with that dialog right away because it wasn't clear what
the check box labeled "Allow fetching media information from Internet" 
really meant.  

The phrase "media information" is uselessly ambiguous:  "Media" files are 
information, so the label might refer to retrieving remote audio/video 
files.  On the other hand, "media information" might have been meant to
mean associated information (CDDB-style title/artist/etc. information?), 
so the label might refer to remote lookups of that information.

Note that the "Privacy and Network Warning" text doesn't help.  It says,
in part:

   VLC ... can get informations from the Internet in order to
   get media informations ...

which is next to useless.)




So:

1. VLC should not start playing anything before popping up that (and
   many any other or some other) modal dialog.  (Alternatively, making 
   that dialog non-modal would also solve the problem here.)

2. The wording of that check-box label (and the warning text) should be 
   clear.


Daniel


-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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/dash

Versions of packages vlc depends on:
ii  libaa11.4p5-38   ascii art library
ii  libc6 2.11.3-4   Embedded GNU C Library: Shared lib
ii  libfreetype6  2.4.2-2.1+squeeze4 FreeType 2 font engine, shared lib
ii  libfribidi0   0.19.2-1   Free Implementation of the Unicode
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libgl1-mesa-glx [libg 7.7.1-5A free implementation of the OpenG
ii  libqtcore44:4.6.3-4+squeeze1 Qt 4 core module
ii  libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module
ii  libsdl-image1.2   1.2.10-2+b2image loading library for Simple D
ii  libsdl1.2debian   1.2.14-6.1 Simple DirectMedia Layer
ii  libstdc++64.4.5-8The GNU Standard C++ Library v3
ii  libtar1.2.11-6   C library for manipulating tar arc
ii  libvlccore4   1.1.3-1squeeze6base library for VLC and its modul
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libx11-xcb1   2:1.3.3-4  Xlib/XCB interface library
ii  libxcb-keysyms1   0.3.6-1utility libraries for X C Binding 
ii  libxcb-randr0 1.6-1  X C Binding, randr extension
ii  libxcb-shm0   1.6-1  X C Binding, shm extension
ii  libxcb-xv01.6-1  X C Binding, xv extension
ii  libxcb1   1.6-1  X C Binding
ii  libxext6  2:1.1.2-1  X11 miscellaneous extension librar
ii  ttf-freefont  20090104-7 Freefont Serif, Sans and Mono True
ii  vlc-nox   1.1.3-1squeeze6multimedia player and streamer (wi
ii  zlib1g1:1.2.3.4.dfsg-3   compression library - runtime

Versions of packages vlc recommends:
ii  vlc-plugin-notify1.1.3-1squeeze6 LibNotify plugin for VLC
ii  vlc-plugin-pulse 1.1.3-1squeeze6 PulseAudio plugin for VLC

Versions of packages vlc suggests:
pn  mozilla-plugin-vlc (no description available)
pn  videolan-doc   (no description available)

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4  0.7.4-14   library for decoding ATSC A/52 str
ii  libasound21.0.23-2.1 shared library for ALSA applicatio
ii  libass4   0.9.9-1library for SSA/ASS subtitles rend
ii  libavahi-client3  0.6.27-2+squeeze1  Avahi client library
ii  libavahi-common3  0.6.27-2+squeeze1  Avahi common library
ii  libavc1394-0  0.5.3-1+b2 control IEEE 1394 audio/video devi
ii  libavcodec52  4:0.5.9-1  ffmpeg codec library
ii  libavformat52 4:0.5.9-1  ffmpeg file format library
ii  libavutil49   4:0.5.9-1  ffmpeg utility library
ii  libc6 2.11.3-4   Embedded GNU C Library: Shared lib
ii  libcaca0  0.99.beta17-1  colour ASCII art library
ii  libcddb2  1.3.2-2library to access CDDB data - runt
ii  libcdio10 0.81-4 library to read and control CD-ROM
ii  libdbus-1-3   1.2.24-4+squeeze1  simple interprocess messaging syst
ii  libdc1394-22  2.1.2-3high level programming in

Bug#699551: logrotate: comments don't work in included files

[Daniel B]

Package: logrotate
Version: 3.7.8-6
Severity: normal

It seems that comments don't work in included files.

The manual page for logrotate says:

  Note that comments may appear anywhere in the config file as long as the 
  first non-whitespace character on the line is a #.

and:

  include file_or_directory
Reads the file given as an argument as if it was included inline where 
the include directive appears.  If a directory is given, most of the 
files in that directory are read in alphabetic order before processing 
of the including file continues. ...

(That is, per the current documentation, comments should work in included
files too.)


However, when my /etc/logrotate.d/rsyslog file includes this:

  ...
  
  /var/log/mail.info
  ...
  /var/log/cron.log
  #DSB Configuration:
  #/var/log/debug
  /var/log/debug.log
  #DSB Configuration:
  #/var/log/messages
  /var/log/messages.log
  ...

then running "/usr/sbin/logrotate /etc/logrotate.conf" reports this:

  error: rsyslog:13 duplicate log entry for #DSB
  error: found error in /var/log/mail.info
  ...
  /var/log/cron.log
  #DSB Configuration:
  #/var/log/debug
  /var/log/debug.log
  #DSB Configuration:
  #/var/log/messages
  /var/log/messages.log
  ...
  , skipping
  ...
  error: stat of #DSB failed: No such file or directory
  error: stat of Configuration: failed: No such file or directory
  error: stat of #/var/log/debug failed: No such file or directory

In particular, logrotate is not ignoring all lines whose "first 
non-whitespace character on the line is a #", as the manual page documents 
that it does.


The behavior and the documentation should match.  

At a minimum, if the current behavior actually is as intended, then the 
manual page should document the lack of comments in included files.

However, the fix really should be to fix logrotate's parsing of included 
files to support comments.  (Comments are recognized as being useful (since 
they are already supported in the main configuration file), so they should 
be supported in included files too.)


-- Package_-specific info:
Contents of /etc/logrotate.d
total 60
drwxr-xr-x 2 root root 4096 Jan 30 20:03 RCS
-rw-r--r-- 1 root root  194 Sep 12 22:55 apache2
-rw-r--r-- 1 root root  173 Apr 15  2011 apt
-rw-r--r-- 1 root root   79 Aug 10  2011 aptitude
-rw-r--r-- 1 root root  248 Nov 28  2011 cups
-rw-r--r-- 1 root root  232 Nov 10  2011 dpkg
-rw-r--r-- 1 root root  146 May 12  2011 exim4-base
-rw-r--r-- 1 root root  126 May 12  2011 exim4-paniclog
-rw-r--r-- 1 root root  217 Apr  6  2012 fail2ban
-rw-r--r-- 1 root root  322 Jun 29  2010 ippl
-rw-r--r-- 1 root root   94 Aug  8  2010 ppp
-rw-r--r-- 1 root root 6732 Jan 30 20:04 rsyslog
-rw-r--r-- 1 root root  558 Oct 14 23:04 rsyslog~
-rw-r--r-- 1 root root  322 Apr 30  2012 samba


-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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/dash

Versions of packages logrotate depends on:
ii  base-passwd   3.5.22 Debian base system master password
ii  cron  3.0pl1-116 process scheduling daemon
ii  libc6 2.11.3-4   Embedded GNU C Library: Shared lib
ii  libpopt0  1.16-1 lib for parsing cmdline parameters
ii  libselinux1   2.0.96-1   SELinux runtime shared libraries

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20100314cvs-1 simple mail user agent

logrotate 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#699549: logrotate: _some_ error line numbers off by one (line? token?)

[Daniel B.]

Package: logrotate
Version: 3.7.8-6
Severity: normal

Line numbers reported with some messages appear to be off by one (too 
low).

For example, with /etc/logrotate.d/rsyslog starting as follows (line
numbers added):

 1  /var/log/syslog
 2  {
 3  rotate 7
 4  daily
 5  missingok
 6  notifempty
 7  delaycompress
 8  compress
 9  postrotate
10  invoke-rc.d rsyslog reload > /dev/null
11  endscript
12  }
13  
14  /test
15  /test


running logrotate yields:

  error: rsyslog:13 duplicate log entry for /test

even though there's no test on line 13.


For an error on line 1, logrotate does correctly report line 1 (not line 0),
so the problem does not seem to be in line numbering itself, but instead
in keeping track of the line number corresponding to the parsing state.




-- Package-specific info:
Contents of /etc/logrotate.d
total 60
drwxr-xr-x 2 root root 4096 Jan 30 20:03 RCS
-rw-r--r-- 1 root root  194 Sep 12 22:55 apache2
-rw-r--r-- 1 root root  173 Apr 15  2011 apt
-rw-r--r-- 1 root root   79 Aug 10  2011 aptitude
-rw-r--r-- 1 root root  248 Nov 28  2011 cups
-rw-r--r-- 1 root root  232 Nov 10  2011 dpkg
-rw-r--r-- 1 root root  146 May 12  2011 exim4-base
-rw-r--r-- 1 root root  126 May 12  2011 exim4-paniclog
-rw-r--r-- 1 root root  217 Apr  6  2012 fail2ban
-rw-r--r-- 1 root root  322 Jun 29  2010 ippl
-rw-r--r-- 1 root root   94 Aug  8  2010 ppp
-rw-r--r-- 1 root root 6747 Feb  1 11:02 rsyslog
-rw-r--r-- 1 root root  558 Oct 14 23:04 rsyslog~
-rw-r--r-- 1 root root  322 Apr 30  2012 samba


-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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/dash

Versions of packages logrotate depends on:
ii  base-passwd   3.5.22 Debian base system master password
ii  cron  3.0pl1-116 process scheduling daemon
ii  libc6 2.11.3-4   Embedded GNU C Library: Shared lib
ii  libpopt0  1.16-1 lib for parsing cmdline parameters
ii  libselinux1   2.0.96-1   SELinux runtime shared libraries

Versions of packages logrotate recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20100314cvs-1 simple mail user agent

logrotate 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#697028: not fg/bg: "startx", switch back, then Enter hangs too

[Daniel B.]

I just noticed that the following sequence, which doesn't involve any
job control, causes the same problem:

- in some text virtual console, run "startx"
- (X starts up normally, the window manager (FVWM) responds normally)
- switch back to that text virtual console (with Ctrl-Alt-F)
- press Enter
- switch back to the X virtual console

Now the window manager no longer responds (moving the mouse no longer
moves focus between windows; FVWM's little pager window no longer
repaints).


Daniel
--
Daniel B.
d...@smart.net


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#697028: another case: "startx &", then fg

[Daniel B.]

An additional data point:

"fg" has the same effect on the window manager as "bg".

(No, I'm not intentionally trying to apply job control to
startx.  However, intending to stop, foreground, or background
some other job can lead to accidentally applying the change to
the startx job instead.)

Daniel
--
Daniel B.
d...@smart.net


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#697028: xinit: startx &, then (unneeded) bg freezes window manager

[Daniel B.]

Package: xinit
Version: 1.2.0-2
Severity: normal

After starting X using "startx &" in a shell in a text console, if back in 
that text console I happen to run "bg" on the startx job (which reports 
"... already in background"), then when I go back to the X console, the 
window manager is frozen.  (For example, it doesn't change window focus per 
mouse movement or update its pager.)  The X server is still running otherwise 
(at least enough that whatever window had focus still gets keyboard events).

(Since "bg" reported that the job is already in the background, I wouldn't
expect there to be a change in the status of the job--so I didn't expect
that the job (including the window manager or whatever) would be affected.


I also notice that if I do 'startx &' and then log off of the text console,
the window manager is also frozen.  On Sarge, that didn't happen.  What
changed?



Especially for the "bg" case, is there a bug somewhere in X components, 
especially related to shell job control?


Daniel



-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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/dash

Versions of packages xinit depends on:
ii  coreutils   8.5-1GNU core utilities
ii  libc6   2.11.3-4 Embedded GNU C Library: Shared lib
ii  libx11-62:1.3.3-4X11 client-side library
ii  x11-common  1:7.5+8+squeeze1 X Window System (X.Org) infrastruc
ii  xauth   1:1.0.4-1X authentication utility

Versions of packages xinit recommends:
ii  fvwm [x-window-manager] 1:2.5.30.ds-1F(?) Virtual Window Manager
ii  vnc4server [xserver]4.1.1+X4.3.0-37  Virtual network computing server s
ii  xserver-xorg1:7.5+8+squeeze1 the X.Org X server
ii  xserver-xorg-core [xser 2:1.7.7-14   Xorg X server - core server
ii  xterm [x-terminal-emula 261-1X terminal emulator

xinit 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#685957: locales: dpkg-reconfigure defaults to "None" instead of locale selected in installer

[Daniel B.]

Package: locales
Version: 2.11.3-3
Severity: normal
Tags: d-i


Running "dpkg-reconfigure locales" without making any changes in the user 
interface can 
cause the default system locale to change.

To reproduce:
- Install Debian.  During installation, in the installer, select some locale 
for the 
  default system locale.
- Note that the selected locale is set in /etc/default/locale.
- Run "dpkg-recongigure locales".  
* Note that for the default system locale dialog/page, the dpkg-reconfigure 
list shows 
  "None" as the current default system locale (instead of the previously 
selected locale).
- Without making any changes to the selections, proceed through all 
pages/dialogs (press 
  Enter/Return).
* Note that /etc/default/locale no longer has the same locale setting, even 
though
  you changed nothing in the dpkg-reconfigure dialogs. 


-- System Information:
Debian Release: 6.0.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-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/dash

Versions of packages locales depends on:
ii  debconf [debconf-2.0] 1.5.36.1   Debian configuration management sy
ii  libc6 [glibc-2.11-1]  2.11.3-3   Embedded GNU C Library: Shared lib

locales recommends no packages.

locales suggests no packages.

-- debconf information:
* locales/default_environment_locale: en_US.UTF-8
* locales/locales_to_be_generated: en_US.UTF-8 UTF-8


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535992: sgml-base: uninstalling removes /usr/local/share

[Daniel B.]

Package: sgml-base
Severity: normal

Removing (or maybe removing and purging) package sgml-base removes 
/usr/local/share.

(Isn't there an FHS or Debian policy that packages shouldn't remove things 
from /usr/local?)

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 sgml-base depends on:
ii  perl  5.10.0-19  Larry Wall's Practical Extraction 

sgml-base recommends no packages.

Versions of packages sgml-base suggests:
pn  sgml-base-doc  (no description available)




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535497: linkchecker: hook into URL hierarchy more modularly

[Daniel B.]

Package: linkchecker
Version: 4.9-1
Severity: wishlist


It might be helpful if linkchecker hooked its HTML files and scripts 
into the server's URL hierarchy more modularly/flexibly than simply 
placing files in the file system hierarchy rooted at the default location
(/var/www).

(I don't know that the most advanced or most recommended forms would be 
in Debian, but based on my current knowledge:)

It would probably be most flexible if linkchecker hooked in the 
way package w3c-markup-validator does:  with a file (link) in 
/etc/apache2/conf.d using Alias and ScriptAlias directives specify its 
URIs and to map them to its files.

That way, if the administrator moves the document root to a different 
directory than /var/www, linkchecker would still work with no
adjustment the same way w3c-markup-validator does with no adjustment



-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 linkchecker depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  python2.5.2-3An interactive high-level object-o
ii  python-central0.6.8  register and build utility for Pyt
ii  python2.4 2.4.6-1An interactive high-level object-o

linkchecker recommends no packages.

Versions of packages linkchecker suggests:
ii  apache2-mpm-prefork [htt 2.2.9-10+lenny3 Apache HTTP Server - traditional n
pn  python-geoip   (no description available)
pn  python-optcomplete (no description available)
pn  python-profiler(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#535484: README.Debian: unclear incomplete sentence

[Daniel B.]

Package: linkchecker
Version: 4.9-1
Severity: normal

The file /usr/share/doc/linkchecker/README.Debian says:

  ... you have to for one language XY the file extensions of the
  .html.XY files.


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 linkchecker depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  python2.5.2-3An interactive high-level object-o
ii  python-central0.6.8  register and build utility for Pyt
ii  python2.4 2.4.6-1An interactive high-level object-o

linkchecker recommends no packages.

Versions of packages linkchecker suggests:
ii  apache2-mpm-prefork [htt 2.2.9-10+lenny3 Apache HTTP Server - traditional n
pn  python-geoip   (no description available)
pn  python-optcomplete (no description available)
pn  python-profiler(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#530782: bash: manual page doesn't match "declare ... -p ..." behavior

[Daniel B.]

Package: bash
Version: 3.2-4
Severity: normal


The bash manual page, in its section the declare built-in function, says:

  The -p option will display the attributes and values of each name. 
  When -p is used, additional options are ignored. 

That description is apparently wrong.  Bash does not ignore additional 
options with -p.

Here's one example:

  
  $ declare -p | head -5
  BASH=/bin/bash
  BASH_ARGC=()
  BASH_ARGV=()
  BASH_COMPLETION=/etc/bash_completion
  BASH_COMPLETION_DIR=/etc/bash_completion.d
  $ declare -p -F | head -5
  declare -f _a2dismod
  declare -f _a2dissite
  declare -f _a2enmod
  declare -f _a2ensite
  declare -f _alias
  $ declare -F -p | head -5
  declare -f _a2dismod
  declare -f _a2dissite
  declare -f _a2enmod
  declare -f _a2ensite
  declare -f _alias
  $
  
Here's another:

  
  $ declare -p | head -5
  BASH=/bin/bash
  BASH_ARGC=()
  BASH_ARGV=()
  BASH_COMPLETION=/etc/bash_completion
  BASH_COMPLETION_DIR=/etc/bash_completion.d
  $ declare -p -a | head -5
  declare -a BASH_ARGC='()'
  declare -a BASH_ARGV='()'
  declare -a BASH_LINENO='()'
  declare -a BASH_SOURCE='()'
  declare -ar BASH_VERSINFO='([0]="3" [1]="2" [2]="39" [3]="1" [4]="release" 
[5]="i486-pc-linux-gnu")'
  $ 
  




-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 bash depends on:
ii  base-files5lenny2Debian base system miscellaneous f
ii  debianutils   2.30   Miscellaneous utilities specific t
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libncurses5   5.7+20081213-1 shared libraries for terminal hand

Versions of packages bash recommends:
ii  bash-completion   20080705   programmable completion for the ba

Versions of packages bash suggests:
pn  bash-doc   (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#530655: apticron: doesn't/can't report updates in held packages

[Daniel B.]

Package: apticron
Version: 1.1.27
Severity: normal


Apticron fails to report updates for packages that are installed and
are held, and does not seem to provide an option to change that behavior.

Just because a package is held does not mean that the administrator
does not want to be notified of updates, especially security updates,
for the package.

Apticron should either 1) not ignore packages on hold or 2) provide an
option to control whether to ignore or to report about updates to held
packages.



-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 apticron depends on:
ii  apt0.7.20.2+lenny1   Advanced front-end for dpkg
ii  bsd-mailx  8.1.2-0.20071201cvs-3 A simple mail user agent
ii  debconf [debconf-2 1.5.24Debian configuration management sy
ii  ucf3.0016Update Configuration File: preserv

Versions of packages apticron recommends:
ii  apt-listchanges   2.83   package change history notificatio
ii  iproute   20080725-2 networking and traffic control too

apticron suggests no packages.

-- debconf information:
* apticron/notification: root




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#529631: oops: duplicate (one of 529631 and 529627)

[Daniel B.]

Oops.  One of bug reports number 529631 and 529627 is a duplicate
of the other and can be closed.

(I thought that my first message, which was corrupted into HTML mail by
Microsoft Exchange, was ignored by the BTS and I re-sent the message
(through a different server).)

Daniel







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#529627: bash: nounset treats empty array as unset, contrary to man. page

[Daniel B.]

Package: bash
Version: 3.2-4
Severity: normal


For a reference to the whole array held in an array variable (e.g.,
"${v...@]}"), Bash's nounset option ("set -o nounset") treats a 
reference to a variable bound to an empty array as if the variable were
unset (unbound).


That behavior differs from the behavior that the manual page seemingly 
specifies or documents:

The description of the "nounset" / "-u" option says:

   Treat unset variables as an error when performing parameter 
   expansion.  If expansion is attempted on an unset variable, the 
   shell prints an error message, and, if not interactive, exits 
   with a non-zero status.

Nothing there says that variables that are set to arrays that are
empty are treated as unset variables, and there doesn't seem to be
any other part the manual page that says that.


If by chance the current behavior is intentional (and the manual page
is considered to be the thing that is in error), then take this report
as a bug report about that design intention, and note how the current 
behavior is inconvenient and not orthogonal (not keeping variable
presence and array size separate).

Although a simple case such as this:

possibly_empty_array=( ... )

for i in "${possibly_empty_arr...@}}" ; do
...
done

one can relatively easily wrap an if statement around the loop, 
in cases such as this:


never_empty=( ... )
maybe_empty=( ... )
maybe_empty2=( ... )

somecommand "${never_emp...@}}" "${maybe_emp...@}}" "${maybe_empt...@}}"

working around the irregularity is much more disruptive.


Included below is a script that demostrates the current behavior.  The
output that I see is:

$ ./testNounsetEmptyArray.sh
Test: unset: 
../testNounsetEmptyArray.sh: line 6: arr...@]: unbound variable
UNSET
Test: set, non-empty: 
SET
Test: set, empty: 
../testNounsetEmptyArray.sh: line 6: arr...@]: unbound variable
UNSET
$ 


-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 bash depends on:
ii  base-files5lenny2Debian base system miscellaneous f
ii  debianutils   2.30   Miscellaneous utilities specific t
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libncurses5   5.7+20081213-1 shared libraries for terminal hand

Versions of packages bash recommends:
ii  bash-completion   20080705   programmable completion for the ba

Versions of packages bash suggests:
pn  bash-doc   (no description available)

-- no debconf information

*** testNounsetEmptyArray.sh
#!/bin/sh

set -o nounset

function test ()
{
trap "echo UNSET" EXIT

echo "Test: $1: "
for i in "${arr...@]}" ; do : ; done

echo "SET"

trap - EXIT # ca
}

( unset array;   test "unset"  )
( array=( a b ); test "set, non-empty" )
( array=( ); test "set, empty" )

Bug#529631: bash: nounset treats empty array as unset, contrary to man. page

[Daniel B.]

Package: bash
Version: 3.2-4
Severity: normal


For a reference to the whole array held in an array variable (e.g.,
"${v...@]}"), Bash's nounset option ("set -o nounset") treats a
reference to a variable bound to an empty array as if the variable were
unset (unbound).


That behavior differs from the behavior that the manual page seemingly
specifies or documents:

The description of the "nounset" / "-u" option says:

   Treat unset variables as an error when performing parameter
   expansion.  If expansion is attempted on an unset variable, the
   shell prints an error message, and, if not interactive, exits
   with a non-zero status.

Nothing there says that variables that are set to arrays that are
empty are treated as unset variables, and there doesn't seem to be
any other part the manual page that says that.


If by chance the current behavior is intentional (and the manual page
is considered to be the thing that is in error), then take this report
as a bug report about that design intention, and note how the current
behavior is inconvenient and not orthogonal (not keeping variable
presence and array size separate).

Although a simple case such as this:

possibly_empty_array=( ... )

for i in "${possibly_empty_arr...@}}" ; do
...
done

one can relatively easily wrap an if statement around the loop,
in cases such as this:


never_empty=( ... )
maybe_empty=( ... )
maybe_empty2=( ... )

somecommand "${never_emp...@}}" "${maybe_emp...@}}" "${maybe_empt...@}}"

working around the irregularity is much more disruptive.


Included below is a script that demostrates the current behavior.  The
output that I see is:

$ ./testNounsetEmptyArray.sh
Test: unset:
.../testNounsetEmptyArray.sh: line 6: arr...@]: unbound variable
UNSET
Test: set, non-empty:
SET
Test: set, empty:
.../testNounsetEmptyArray.sh: line 6: arr...@]: unbound variable
UNSET
$


-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 bash depends on:
ii  base-files5lenny2Debian base system miscellaneous f
ii  debianutils   2.30   Miscellaneous utilities specific t
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libncurses5   5.7+20081213-1 shared libraries for terminal hand

Versions of packages bash recommends:
ii  bash-completion   20080705   programmable completion for the ba

Versions of packages bash suggests:
pn  bash-doc   (no description available)

-- no debconf information

*** testNounsetEmptyArray.sh
#!/bin/sh

set -o nounset

function test ()
{
trap "echo UNSET" EXIT

echo "Test: $1: "
for i in "${arr...@]}" ; do : ; done

echo "SET"

trap - EXIT # ca
}

( unset array;   test "unset"  )
( array=( a b ); test "set, non-empty" )
( array=( ); test "set, empty" )





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#528695: libldap-2.4-2: ldap.conf(5) manual page doesn't specify units of limit quantities

[Daniel B.]

Package: libldap-2.4-2
Version: 2.4.11-1
Severity: normal


The ldap.conf(5) manual page doesn't specify the units in the quantities 
specified by configuration options as SIZELIMIT.

For example, the text says:

  SIZELIMIT 
  Specifies  a  size limit to use when performing searches.
  The number should be a non-negative  integer.   SIZELIMIT
  of zero (0) specifies unlimited search size.

Note how the text says nothing about _how_ the integer specifies a limit.
(It doesn't say whether the integer is a number of bytes, megabytes, 
entries, attributes, or even something else.)


The TIMELIMIT documentation is similar:

   TIMELIMIT 
  Specifies  a  time limit to use when performing searches.
  The number should be a non-negative  integer.   TIMELIMIT
  of  zero  (0) specifies unlimited search time to be used.
  VERSION {2|3} Specifies what version of the LDAP protocol
  should be used.

(It doesn't specify whether the integer is the number of seconds--or
maybe milliseconds or something.)


In contrast, for a precedent to follow, notice how the documentation of 
the TIMEOUT configuration option _does_ give the units (seconds):

   TIMEOUT 
  Specifies  a  timeout  (in  seconds) after which calls to
  synchronous LDAP  APIs  will  abort  if  no  response  is
  received.  Also used for any ldap_result(3) calls where a
  NULL timeout parameter is supplied.






-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
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 libldap-2.4-2 depends on:
ii  libc62.7-18  GNU C Library: Shared libraries
ii  libgnutls26  2.4.2-6+lenny1  the GNU TLS library - runtime libr
ii  libsasl2-2   2.1.22.dfsg1-23 Cyrus SASL - authentication abstra

libldap-2.4-2 recommends no packages.

libldap-2.4-2 suggests no packages.

-- no debconf information

Bug#388309: (no subject)

[Daniel B.]

One more thing:  CONFIG_PARPORT_PC_FIFO is marked "EXPERIMENTAL",
at least in kernel 2.6.8, so it had no business being set to Y in 
Sarge's 2.6.8 in the first place.

Daniel
-- 
Daniel Barclay
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#388309: (no subject)

[Daniel B.]

I just found this:

  http://cyberelk.net/tim/parport/archive/current/4542.html

about getting extra bytes at the printer (consistent with the symptoms I'm
getting (see http://lists.debian.org/debian-user/2006/10/msg00133.html))
and "DMA write timed out" and "parport0: FIFO is stuck" errors in code
enabled by CONFIG_PARPORT_PC_FIFO 

Daniel
-- 
Daniel Barclay
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#388309: linux-image-2.6.17-2-686: "DMA write timed out" with "CONFIG_PARPORT_PC_FIFO=y

[Daniel B.]

Is the problem really that CONFIG_PARPORT_PC_FIFO wasn't set to N,
or is it actually that there's a bug in the kernel that only shows up 
when CONFIG_PARPORT_PC_FIFO isn't set to Y (or possibly buggy hardware)?  

I have been unable to print without severe errors 
(http://lists.debian.org/debian-user/2006/10/msg00300.html) 
since I upgraded to Sarge and to kernel 2.6.8 (2.6.8-2-k7-smp, which 
has CONFIG_PARPORT_PC_FIFO set to Y.

Here's my system's lshw information:


dsb
description: Tower Computer
product: System Name
vendor: System Manufacturer
version: System Version
serial: SYS-1234567890
width: 32 bits
capabilities: smbios-2.3 dmi-2.3
configuration: boot=normal chassis=tower
  *-core
   description: Motherboard
   product: A7M266-D
   vendor: ASUSTeK Computer INC.
   physical id: 0
   version: REV 1.xx
   serial: xxx
 *-firmware
  description: BIOS
  vendor: Award Software, Inc.
  physical id: 0
  version: ASUS A7M266-D ACPI BIOS Revision 1010 (03/03/2003)
  size: 64KB
  capacity: 192KB
  capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect 
socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 
int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp
 *-cpu:0
  description: CPU
  product: AMD Athlon(TM) XP
  vendor: Advanced Micro Devices [AMD]
  physical id: 4
  bus info: [EMAIL PROTECTED]
  version: 6.6.2
  slot: SOCKET A
  size: 1200MHz
  capacity: 1600MHz
  width: 32 bits
  clock: 133MHz
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 
3dnow
*-cache:0
 description: L1 cache
 physical id: b
 slot: L1 Cache
 size: 128KB
 capacity: 128KB
 capabilities: synchronous internal write-back data
*-cache:1
 description: L2 cache
 physical id: c
 slot: L2 Cache
 size: 256KB
 capacity: 8MB
 capabilities: pipeline-burst synchronous internal write-back data
 *-cpu:1
  description: CPU
  product: AMD Athlon(TM) XP
  vendor: Advanced Micro Devices [AMD]
  physical id: 5
  bus info: [EMAIL PROTECTED]
  version: 6.6.2
  slot: SOCKET A
  size: 1200MHz
  capacity: 1600MHz
  width: 32 bits
  clock: 133MHz
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 
3dnow
*-cache:0
 description: L1 cache
 physical id: 0
 size: 128KB
*-cache:1
 description: L2 cache
 physical id: 1
 size: 256KB
 *-memory
  description: System Memory
  physical id: 25
  slot: System board or motherboard
  size: 1GB
  capacity: 1GB
*-bank:0
 description: DIMM DRAM Synchronous
 physical id: 0
 slot: DIMM 1
 size: 512MB
 width: 64 bits
*-bank:1
 description: DIMM DRAM Synchronous
 physical id: 1
 slot: DIMM 2
 size: 512MB
 width: 64 bits
*-bank:2
 description: DIMM DRAM Synchronous [empty]
 physical id: 2
 slot: DIMM 3
*-bank:3
 description: DIMM DRAM Synchronous [empty]
 physical id: 3
 slot: DIMM 4
 *-pci
  description: Host bridge
  product: AMD-760 MP [IGD4-2P] System Controller
  vendor: Advanced Micro Devices [AMD]
  physical id: fc00
  bus info: [EMAIL PROTECTED]:00.0
  version: 11
  width: 32 bits
  clock: 66MHz
  resources: iomemory:fc00-fdff iomemory:fb80-fb800fff
*-pci:0
 description: PCI bridge
 product: AMD-760 MP [IGD4-2P] AGP Bridge
 vendor: Advanced Micro Devices [AMD]
 physical id: 1
 bus info: [EMAIL PROTECTED]:01.0
 version: 00
 width: 32 bits
 clock: 66MHz
 capabilities: pci normal_decode bus_master
   *-display
description: VGA compatible controller
product: Riva128
vendor: NVidia / SGS Thomson (Joint Venture)
physical id: 5
bus info: [EMAIL PROTECTED]:05.0
version: 10
size: 16MB
width: 32 bits
clock: 66MHz
capabilities: vga bus_master cap_list
resources: iomemory:f80

Bug#354470: Acknowledgement (misleading message about permissions when real state is non-existent device file)

[Daniel B.]

I wrote:

> ... when the PDA device file does not exist.

Actually, now I'm not sure if it's because the device file (the
filesystem node) does not exist yet, or if it's because the
device isn't ready for reading/writing.  (If it's the latter,
I assume it would be harder to improve the error message.)


Daniel
-- 
Daniel Barclay
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354470: misleading message about permissions when real state is non-existent device file

[Daniel B.]

Package: pilot-manager
Version: 1.107.0pre108-4
Severity: normal

PilotManager reports a misleading error message when the PDA device file
does not exist.

For example, I just got this message:

02/26/2006 10:27:29   Error: Don't have read/write permissions on /dev/pilot!
  (On Solaris owner/group/perms should be root/sys/666)

That wording strongly implies that the device file does exist but the 
permissions aren't set right for PilotManager to have sufficient access.

However, the real problem was that the device file did not exist at all
(because of a udev-related timing problem).

Since PilotManager should avoid giving misleading error messages, it 
should check for the existence of the device file separately from 
checking for access rights and it should issue a different error message 
if the device file doesn't exit.





-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages pilot-manager depends on:
hi  libpda-pilot-perl  0.11.8-10 Perl module to communicate with a 
ii  perl [libdigest-md5-perl]  5.8.4-8sarge3 Larry Wall's Practical Extraction 
ii  perl-tk1:800.025-2   Perl module providing the Tk graph

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354403: [doc] various editorial errors (typos, grammar and punctuation problems)

[Daniel B.]

Package: menu
Version: 2.1.24
Severity: normal

There are a number of editorial errors (typos, grammar errors, and 
punctuation errors) in the documentation.


The update-menus(1) manual page says:

* "update-menus will be ran automatically"

  That should be "... will be run ..."

* "... when Debian packages ... are installed or removed from the 
  system"

  That should be: " ... installed on or removed from ..."

* "(but this can be overruled by the system administrator/user, see 
  below)

  That comma should actually be a semicolon.  (The clauses before
  an after the colon are independent clauses (they could have been
  separate sentences), so they need to be separated with a semicolon
  instead of a comma.)


* "... update-menus execute the menu entry file, and use its stdout"

  That "execute" should be "executes" (and "use" should be "uses").

* "... to the list of directory to search..."

  That should be "... list of directories ..."

* "In these directory ..."

  That should be "these directories ..."

* "files. (if a file ... any more)."

  That should be: 

"files.  (If ... .)"

  or

"files (if ... )."

* "... generated system."$wm"rc files ..."

  The would be clearer as:

"... system.${wm}rc ..."


The menufile(5) manual page says:

* '... you can list several "menu entries", that specify ...'

  That should be 

'... "menu entries" that specify ...'

  or 

'... "menu entries," which specify ...'


* "Each menu entry specifies what package it depends on ..."

  That whould be "... which package ..."


* "Each menu entry specifies what package it depends on, if that package 
  is not installed, the menu entry will be ignored by update-menus(1)."

  The first comma should be a semicolon.


* Similar: 'In a menu entry you can specify pseudo-packages that start 
  with "local.", update-menus will always use those menu entries).'

  That comma should also be a semicolon.


*  "?package(package-name):var1=value var2=varlue2 ..."


* "needs= What type of display will the program run on?"

  That would be better as:

"needs= What type of display the program will run on."

  (because other items (section, icon, etc.) are not described
  with questions).

  (Actually, it would probably be better to say "What type of display
  the program needs" (or "... runs on").


(Also, although this isn't an editorial error:  The FORMAT section
doesn't seem to document that quotes are allowed (or when they are
required).  

Also, that section doesn't document the "hotkey=" option that is
mentioned in the NOTES section.))


* '(icon="none" is also possible, preferably just leave it out)'

  The comma should be a semicolon (and there should be a period 
  right after the word "out").


* "... the X11 one will be used, otherwise the text one will be 
  used..."

  That comma should be a semicolon.

* "... A comma-separated list of  hints  on  how  grouping  menu
  entries, see manual."

  That comma should also be a semicolon (and "see manual" would
  probably be better as "see the manual").


The install-menu(1) manual page says:

* "menu-information" (several times)

  That should be "menu information".

* "menuentries" should be "menu entries".


/usr/share/doc/menu/html/ch2.html says:

* "Basically, you as user don't need to know ...":

  That should be "user as a user don't ..." (or "users don't ...").

* "startupfiles" should be "startup files"

* "Update-menus then reads in all menu files in /etc/menu/ /usr/lib/menu 
and /usr/share/menu/default, ..."

  There should be a comma after "/etc/menu" (between it and 
  "/usr/lib/menu").


/usr/share/doc/menu/html/ch3.html says:

* "Packages provided menu files should be in /usr/lib/menu/."

  That should be "Package-provided ..."


* "The format is"

  That should be:

"The format is:"

* "An entry must be terminated by a newline, however you can use \ to 
  escape a newline."

  That comma should be a semicolon.  Also, that backslash should be
  quoted (although, actually, it would be better to write out the word
  "backslash").

* "... meta-character ... be escaped ..."

  That should be "... meta-characters ..."

* "You can include several entries in the same files."

  I think you mean "... in the same file."

* "The file must be encoded in ASCII 7bit."

  That should be "in 7-bit ASCII."

* "... that do not support 8bit."

  That should be "8-bit" something, probably "8-bit encodings."

* "... not depended by the package ..."

  That should be "... not depended on by the package ..."

* "Users can use pseudo packages names starting by local. which are assumed
  to be always installed.

  In the above:
  - "packages names" should be "package names"
  - "pseudo package..." should probably be "pseudo-package..."
  - "starting by" should be "starting with"
  - the string "local." must be quoted so the period (full stop) doesn't
seem to end the sentence
 
* "menuentry" should be "menu entry"


* "Two entries must not ha

Bug#352304: should depend on nscd for /etc/ppp/ip-up.d/0dns-up's call to /usr/sbin/nscd

[Daniel B.]

Package: pppconfig
Version: 2.3.11
Severity: normal

In package pppconfig, the script /etc/ppp/ip-up.d/0dns-up calls 
/usr/sbin/nscd.  /usr/sbin/nscd is provided by package nscd.  However, 
package pppconfig does not declare a dependency on package nscd.  
Therefore, installing package pppconfig can result in messages like:

  /usr/sbin/nscd: No such file or directory

when /etc/ppp/ip-up.d/0dns-up runs.


It seems that either:
- package pppconfig should declare that it depends on package nscd, or
- the script /etc/ppp/ip-up.d/0dns-up should check for the existence
  /usr/sbin/nscd and avoid trying to execute it if it does not exist.



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-k7-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages pppconfig depends on:
ii  dialog  1.0-20050306-1   Displays user-friendly dialog boxe
hi  ppp 2.4.3-20050321+2 Point-to-Point Protocol (PPP) daem
ii  whiptail0.51.6-20Displays user-friendly dialog boxe

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]