Bug#1014133: asterisk: Asterisk fails to build from source

[Jonas Smedegaard]

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

[Ralf Schlatterbeck]

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

[Jonas Smedegaard]

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.

[Ralf Schlatterbeck]

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).