[PD] trying to build puredata 0.46-2 .deb package (was: compile pd-0.45-5 on Linux with autogen.sh)

katja katjavetter at gmail.com
Sun Nov 30 12:56:51 CET 2014

On Wed, Nov 12, 2014 at 8:00 PM, IOhannes m zmölnig <zmoelnig at iem.at> wrote:
> On 11/09/2014 10:57 PM, katja wrote:
> > Hello, I'm unsuccessful in building the puredata 0.46-2 .deb package for
> > Raspberry Pi as per IOhannes' description:
> >
> > On Wed, Jun 25, 2014 at 9:56 AM, IOhannes m zmölnig <pd-list at lists.iem.at>
> > wrote:
> >
> >>
> >> if your distro ships an older version you can do:
> >> $ dget
> >> http://ftp.de.debian.org/debian/pool/main/p/puredata/puredata_0.45.4-2.dsc
> >> $ cd puredata-0.45.4/
> >> $ sudo aptitude install devscripts
> >> $ sudo mk-build-deps -i -r debian/control
> >> $ dpkg-buildpackage -rfakeroot
> >>
> >> this will create the puredata package(s) using the autotools method.
> >> you can then install it using:
> >> $ sudo dpkg -i ../puredata*_0.45.4-2_*.deb
> >>
> >
> > Devscripts had to be installed first to use dget.
> >  After downloading the
> > files with dget I got the error:
> > "gpg: Can't check signature: public key not found
> > Validation FAILED"
> well, probably a problem with the debian keyring for jessie not being
> available on the raspberry.
> $ man dget
> reveals the "-u" flag, that allows you to download even if the signature
> could not be verified (if you are worried about the integrity of the
> dgetted files, you should of course *not* do that and instead search the
> web on how to properly solve the problem)

Thanks for the hints. Indeed the jessie key is missing on my system,
Raspbian wheezy. I was looking in the wrong place anyway because
Raspbian has it's own repository. A recent version of
raspbian-archive-keyring exists (2014-10-19) and it probably has the
jessie key, however this keyring version is not available in Raspbian
wheezy without at least a partial upgrade to jessie. Rather than
experimenting with mixed sources, I preferred to build and install
puredata without verification. The whole procedure (if I noted
everything correctly):

First make sure to have packages devscripts and fakeroot installed.
Then on command line:

$ dget -u -x http://archive.raspbian.org/raspbian/pool/main/p/puredata/puredata_0.46.2-1.dsc
$ cd puredata-0.46.2
$ sudo mk-build-deps -i -r debian/control
$ dpkg-buildpackage -rfakeroot
$ sudo dpkg -i ../puredata*_0.46.2-1_*.deb


Each command must be on a single line (layout may be perverted in the
mail transfer). The mk-builds-deps step removes the following packages
which came with Raspbian: jackd jackd2 libjack-jackd2-0 qjackctl
sonic-pi supercollider supercollider-server. Build dependency
libjack-dev depends on libjack0, which in turn can not coexist with
libjack-jackd2-0. IOhannes has explained the reason for this build
dependency earlier on pd-list
(http://lists.puredata.info/pipermail/pd-list/2013-10/104620.html). It
should be no problem to reinstall jackd2 after building puredata.

Building puredata on Raspberry Pi takes a long time, maybe an hour or
so. While building, I accidentally removed the .dsc file. At the end
of the build process there were errors from gpg about the secret key
being not available. These things did not prevent dpkg from installing
the packages. I'm happy to have bleeding edge puredata installed on
Raspberry Pi.

Thanks IOhannes, for keeping puredata packages up to date.


More information about the Pd-list mailing list