Bug#839049: /usr/bin/profile-sync-daemon: line 359: ${#DIRArr[@]##*/}: bad substitution

[Brent Clark]

Package: profile-sync-daemon
Version: 6.25-1
Severity: normal

Dear Maintainer,

I first got this message:

bclark@bclark:~$ profile-sync-daemon parse
ERROR! To use overlayfs mode, bclark needs sudo access to /usr/bin/psd-
overlay-helper

Add the following line to the end of /etc/sudoers to enable this
functionality:
bclark ALL=(ALL) NOPASSWD: /usr/bin/psd-overlay-helper

I what was suggested, and then run:

bclark@bclark:~$ profile-sync-daemon parse
/usr/bin/profile-sync-daemon: line 359: ${#DIRArr[@]##*/}: bad substitution

Kind Regards
Brent Clark



-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_ZA.utf8, LC_CTYPE=en_ZA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages profile-sync-daemon depends on:
ii rsync 3.1.1-3

profile-sync-daemon recommends no packages.

Versions of packages profile-sync-daemon suggests:
ii libpam-systemd 231-7
ii systemd-sysv 231-7

-- no debconf information

[Jan Luca Naumann]

Tags: unreproducible

Hey Brent,

I tried to reproduce your problem but at my test system I do not get this
error message. The steps I tried to reproduce the problem are:

1) Install "profile-sync-daemon" on Debian unstable
2) Run "profile-sync-daemon parse" with the resulting message "First time
running psd so please edit /home/jan/.config/psd/psd.conf to your liking
and run again."
3) Enable the usage of overlayfs by uncomment the line
'USE_OVERLAYFS="yes"' in /home/jan/.config/psd/psd.conf
4) Run "profile-sync-daemon parse" again with the resulting message
"ERROR! To use overlayfs mode, jan needs sudo access to
/usr/bin/psd-overlay-helper [...]"
5) Edit the /etc/sudoers file as described
6) Run "profile-sync-daemon parse" again without any error message.

Did you do some other steps I have not done? Do you use "/bin/bash" as
shell or something else?

I hope we find the cause of your problem.

Best regards,
Jan