[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1004510: asterisk-opus: Depends on asterisk-1fb7f5c06d7a2052e38d021b3d8ca151 which is gone

Source: asterisk-opus
Version: 13.7+20171009-2
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org, asterisk@packages.debian.org
Tags: sid bookworm
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:asterisk

Dear maintainer(s),

With a recent upload of asterisk the autopkgtest of asterisk-opus fails in testing when that autopkgtest is run with the binary packages of asterisk from unstable. It passes when run with only packages from testing. In tabular form:

                       pass            fail
asterisk               from testing    1:16.23.0~dfsg+~cs6.10.20220309-2
asterisk-opus          from testing    13.7+20171009-2
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of asterisk to testing [1]. Of course, asterisk shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in asterisk was intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from asterisk should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests.

More information about this bug and the reason for filing it can be found on


[1] https://qa.debian.org/excuses.php?package=asterisk


autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) asterisk-opus:amd64 < none -> 13.7+20171009-2 @un puN Ib >
Broken asterisk-opus:amd64 Depends on asterisk-1fb7f5c06d7a2052e38d021b3d8ca151:amd64 < none @un H > Considering asterisk:amd64 10001 as a solution to asterisk-opus:amd64 9999 Broken asterisk-opus:amd64 Depends on libopus0:amd64 < none | 1.3.1-0.1 @un uH > (>= 1.1)
  Considering libopus0:amd64 0 as a solution to asterisk-opus:amd64 9999
  Re-Instated libopus0:amd64
Broken asterisk-opus:amd64 Depends on libopusfile0:amd64 < none | 0.9+20170913-1.1 @un uH > (>= 0.5) Considering libopusfile0:amd64 0 as a solution to asterisk-opus:amd64 9999
  Re-Instated libopusfile0:amd64
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 asterisk-opus : Depends: asterisk-1fb7f5c06d7a2052e38d021b3d8ca151
E: Unable to correct problems, you have held broken packages.
module-loadable      FAIL badpkg
blame: asterisk-opus

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply to: