Your message dated Sat, 24 May 2025 19:03:19 +0200
with message-id 
<gbcjmvigniwil5of2iedodjs7il4jhbwpv5obhf5vzpiwhu...@tarta.nabijaczleweli.xyz>
and subject line Close: Bug#500248: sloccount does not work with /bin/sh as 
shebang line
has caused the Debian Bug report #500248,
regarding sloccount does not work with /bin/sh as shebang line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
500248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500248
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sloccount
Version: 2.26-2
Severity: important

If you call 'sloccount dir' the programm writes a lot of "could not
change directory" warnings and ends with no result,
but the permissions of these directories are right. 


Fix/Workaround (it works for me...):

Replace in all sloccount related shell-files the shebang line:

< #!/bin/sh
> #!/bin/bash

On my system the /bin/sh is an symbolic link to bash:
lrwxrwxrwx 1 root root 4 2007-01-09 09:45 /bin/sh -> bash

I hope this report helps...

Bye Andreas


-- System Information:
Debian Release: 4.0
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24.4-f4c
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages sloccount depends on:
ii  libc6                  2.3.6.ds1-13etch7 GNU C Library: Shared libraries
ii  perl                   5.8.8-7etch3      Larry Wall's Practical Extraction 

sloccount recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Can't repro this.
Maybe this was #110645 but bash was even worse then than now?

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to