Comment 27 for bug 1983794

On Fri, 2023-01-27 at 17:06 +0000, Timo Aaltonen wrote:
> Hello Lindsay, or anyone else affected,
>
> Accepted libcanberra into jammy-proposed. The package will build now
> and
> be available at
> https://launchpad.net/ubuntu/+source/libcanberra/0.30-10ubuntu1.22.04.1
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.

I'll be happy to test this out, but I'm a bit out to sea on building
from source these days. A couple of issues:

First, I received an email about 4 hours after yours which references the
following "excuses":

  libcanberra (0.30-10ubuntu1 to 0.30-10ubuntu1.22.04.1)

      Migration status for libcanberra (0.30-10ubuntu1 to 0.30-
  10ubuntu1.22.04.1): BLOCKED: Rejected/violates migration
  policy/introduces a regression

Is there an issue here about which I should be concerned? is the .deb
in the -proposed repository, or has it gone back to the shop for minor
repairs?

Second, I downloaded libcanberra_0.30-10ubuntu1.22.04.1.debian.tar.xz,
unpacked it, and apparently times have changed. I've built dozens of
packages using the autogen.sh; configure; make; sudo mail install
routine but although this source has an autogen.sh script, it lacks a
configure.in file and autogen.sh fails.

No need to bring me up to speed in public. A private reply re. the
required build technique will do.

Thanks for your work!!!

--
Lindsay Haisley | "The world is full of monsters with friendly
FMP Computer Services | faces and angels with scars."
512-496-7118 |
http://www.fmp.com | - Heather Brewer