2

I keep running lb build, fixing problem after problem and then running it again, and now i'm getting this message:

dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 1 expected program not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists... Done
Building dependency tree... Done

I then went to check my path and i see

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

This clearly shows /usr/local/sbin, /usr/sbin, and /sbin.

Any suggestions?

**UPDATE 1**

Followed this guide

http://ubuntuforums.org/showthread.php?t=1449322

every command ran fine but still the same error message after running lb build again.

**UPDATE 2 -- Additional Info**

root@kali:~# ls -lA /sbin (Other files) -rwxr-xr-x 1 root root 28208 Aug 12 15:00 start-stop-daemon

Chirality
  • 745
  • 8
  • 22
  • I'm having this same issue, has anybody found a fix? – codesmith Aug 28 '14 at 12:47
  • Sadly, no. I just restarted the whole build process (albeit frustrating as it was, it worked.) The only problem i'm having now is that every time i build it erases all the options i had set in grub/grub2. Also changes the live install screen to a glitchy picture. – Chirality Aug 30 '14 at 03:14

2 Answers2

0

First, you must check the feedback information from the first line (although it is just a warning).

Then， you must have understand that the warning is the key. All the mistakes are caused by this warning. You have to add start-stop-daemon to your pc.

According to the following:

cd /tmp
wget http://developer.axis.com/download/distribution/apps-sys-utils-start-stop-daemon-IR1_9_18-2.tar.gz
tar zxf apps-sys-utils-start-stop-daemon-IR1_9_18-2.tar.gz
cd apps/sys-utils/start-stop-daemon-IR1_9_18-2/
gcc start-stop-daemon.c -o start-stop-daemon
cp start-stop-daemon /usr/local/bin/start-stop-daemon

Now you can help yourself，and others

macfij
  • 3,093
  • 1
  • 19
  • 24
juhengzhe
  • 1
0

I have the same problem, according to https://debianforum.de/forum/viewtopic.php?f=34&t=155279 (in german) the only known solution is to run sudo lb clean before sudo lb build.

centic
  • 15,565
  • 9
  • 68
  • 125