Bug#1014133: asterisk: Asterisk fails to build from source
On Fri, Jul 01, 2022 at 01:14:28PM +0200, Bernhard Schmidt wrote:
> As Jonas already wrote, please use something like sbuild/cowbuilder. The
> packages for Bullseye have been built from source by the buildd, so
> generally they should work just fine.
I can confirm that the package builds with sbuild.
I was bitten by #725434 #576425 #823651 #856434
my solution was to symlink /tmp to /tmp/user/{1,1000} in the chroot (I
don't have pbuilder installed in the chroot, is probably installed
during build and later removed again).
Ralf
--
Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
Open Source Consulting www: www.runtux.com
Reichergasse 131, A-3411 Weidling email: off...@runtux.com
Bug#1014133: asterisk: Asterisk fails to build from source
Control: severity -1 important Control: found -1 1:16.16.1~dfsg-1 Control: fixed -1 1:16.16.1~dfsg+~2.10-1 Hi Ralf, I am not very familiar with asterisk as packaged for Bullseye - only know that it was pretty unusually done. Maybe try build in a pristine build-environment. What do you mean by this? As Jonas already wrote, please use something like sbuild/cowbuilder. The packages for Bullseye have been built from source by the buildd, so generally they should work just fine. I might have a look later, but since Jonas changed the packaging for Bullseye (in a way I don't grasp anymore :-) ) this is definitely not affecting the next release and it's definitely not stable-update material. So downgrading. Bernhard
Bug#1014133: asterisk: Asterisk fails to build from source
Quoting Ralf Schlatterbeck (2022-06-30 21:18:49) > On Thu, Jun 30, 2022 at 08:28:19PM +0200, Jonas Smedegaard wrote: > > I am not very familiar with asterisk as packaged for Bullseye - only > > know that it was pretty unusually done. > > > > Maybe try build in a pristine build-environment. > > What do you mean by this? Personally I use cowbuilder but some prefer sbuild. Both are mentioned e.g. at https://wiki.debian.org/Packaging#Suggested_tools_to_create_an_environment_for_packaging > > Maybe try get directly in touch with Bernhard Schmidt who prepared the > > work for Bullseye but possibly doesn't follow these bugs nowadays. > > I'll try! > Can you give me a hint how to find his mail address? It is listed in the changelog for the releases he finalized. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1014133: asterisk: Asterisk fails to build from source
On Thu, Jun 30, 2022 at 08:28:19PM +0200, Jonas Smedegaard wrote: > I am not very familiar with asterisk as packaged for Bullseye - only > know that it was pretty unusually done. > > Maybe try build in a pristine build-environment. What do you mean by this? > Maybe try get directly in touch with Bernhard Schmidt who prepared the > work for Bullseye but possibly doesn't follow these bugs nowadays. I'll try! Can you give me a hint how to find his mail address? Thanks for your *very* quick answer! Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: www.runtux.com Reichergasse 131, A-3411 Weidling email: off...@runtux.com
Bug#1014133: asterisk: Asterisk fails to build from source
Hi Ralf, Quoting Ralf Schlatterbeck (2022-06-30 19:58:38) > Package: asterisk > Version: 1:16.16.1~dfsg-1+deb11u1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > I'm trying to build asterisk from source (bullseye) using: > > dpkg-buildpackage -rfakeroot > > Looks like the verification of the needed pjproject sub-project fails. > The last relevant lines from configure: > > configure:9241: checking for embedded pjproject (may have to download) > configure:9243: result: configuring > configure:9310: result: failed > configure:9312: Unable to configure third-party/pjproject > configure:9314: error: Re-run the ./configure command with 'NOISY_BUILD=yes' > appended to see error details. > > If I re-run this, it tries to download the pjproject tarball and fails > to verify the checksum. > If I clean (debian/rules clean) and configure by hand it seems to be > able to verify (but fails later with a different error). > > Let me know if I'm missing some trick here and if you need additional > information. > My plan (why I'm trying to re-build) is to include a simple patch to > res/res_pjsip_messaging.c to allow content-types other than text/plain. > But I'm failing on the unmodified Debian sources. I am not very familiar with asterisk as packaged for Bullseye - only know that it was pretty unusually done. Maybe try build in a pristine build-environment. Maybe try get directly in touch with Bernhard Schmidt who prepared the work for Bullseye but possibly doesn't follow these bugs nowadays. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1014133: asterisk: Asterisk fails to build from source
Package: asterisk Version: 1:16.16.1~dfsg-1+deb11u1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I'm trying to build asterisk from source (bullseye) using: dpkg-buildpackage -rfakeroot Looks like the verification of the needed pjproject sub-project fails. The last relevant lines from configure: configure:9241: checking for embedded pjproject (may have to download) configure:9243: result: configuring configure:9310: result: failed configure:9312: Unable to configure third-party/pjproject configure:9314: error: Re-run the ./configure command with 'NOISY_BUILD=yes' appended to see error details. If I re-run this, it tries to download the pjproject tarball and fails to verify the checksum. If I clean (debian/rules clean) and configure by hand it seems to be able to verify (but fails later with a different error). Let me know if I'm missing some trick here and if you need additional information. My plan (why I'm trying to re-build) is to include a simple patch to res/res_pjsip_messaging.c to allow content-types other than text/plain. But I'm failing on the unmodified Debian sources. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk depends on: ii adduser 3.118 ii asterisk-config 1:16.16.1~dfsg-1+deb11u1 ii asterisk-core-sounds-en 1.6.1-1 ii asterisk-modules 1:16.16.1~dfsg-1+deb11u1 ii libc62.31-13+deb11u3 ii libcap2 1:2.44-1 ii libcrypt11:4.4.18-4 ii libedit2 3.1-20191231-2+b1 ii libjansson4 2.13.1-1.1 ii libpopt0 1.18-2 ii libsqlite3-0 3.34.1-3 ii libssl1.11.1.1n-0+deb11u3 ii libsystemd0 247.3-7 ii liburiparser10.9.4+dfsg-1+deb11u1 ii libuuid1 2.36.1-8+deb11u1 ii libxml2 2.9.10+dfsg-6.7+deb11u2 ii libxslt1.1 1.1.34-4 ii lsb-base 11.1.0 Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1.1 ii asterisk-voicemail [asterisk-voicemail-storage] 1:16.16.1~dfsg-1+deb11u1 ii sox 14.4.2+git20190427-2 Versions of packages asterisk suggests: pn asterisk-dahdi ii asterisk-dev 1:16.16.1~dfsg-1+deb11u1 pn asterisk-doc pn asterisk-ooh323 pn asterisk-opus pn asterisk-vpb -- no debconf information
