Re: [Linuxsampler-devel] Problem building package linuxsampler 2.0.0 (2832)

[Christian S. <sch...@li...>]

On Friday 31 July 2015 01:23:30 you wrote:
> Thanks, I also needed to install the lv2-dev package. I suppose these
> dependencies are new but not checked upon configuring. Linuxsampler

The dependencies are old, and they are checked by the configure script as 
optional dependencies for a long time.

What changed is the behavior of the Debian packaging scripts. The 
debian/PACKAGENAME.install files are in general used to declare which files 
should make it into the .deb package and to which directory on the target 
system they shall be unpacked to. On previous Debian versions files listed 
there which did not exist were simply ignored, now the packaging script aborts 
on such cases.

I couldn't figure out yet whether Debian now also allows to add optional files 
there in some way, maybe with some prefix keyword in debian/*.install, or as 
parameter to some of the dh_ calls in debian/rules.

> compiled and installed successfully now! But I ran into a new problem when
> compiling the current qsampler package:
> 
[snip]
> Makefile install make[3]: Entering directory
> `/home/tom/lsampler/qsampler/src'
> mkdir: cannot create directory ‘/usr/src/packages’: Permission denied

Your user running dpkg-buildpackage has no write permission on 
/usr/src/packages, a directory created by you manually. Just change the 
permissions on that directory and it will work.

> Full log here: https://pastee.org/qqs26 (dpkg-buildpackage -rfakeroot -b)
> 
> So dpkg-buildpackage had first complained that a few qt dependencies were
> missing so I installed them, though still it gives me this error and fails
> to create the package.
> 
> The "permission denied" error is because it's trying to run mkdir under
> /usr/, right? And since I'm not running dpkg-buildpackage as root, it's
> failing. I'm not sure I should run it as root, as it already set the
> -rfakeroot parameter. Well I'm hoping you can tell me what's going on or
> how to work around this problem.

No need to run it as root, fakeroot is just fine. Just fix the write 
permissions for the running user, that's it.

CU
Christian