On Monday, 19 October 2026 08:00:37 British Summer Time Stephen Kitt wrote: > Hi Nick, > > On Sun, 18 Oct 2026 14:35:02 +0100, Nick Bailey <[email protected]> > > wrote: > > Package: libiir-dev > > Version: 1.10.0+dfsg-4+b1 > > Severity: important > > > > Dear Maintainer, > > > > * What led up to the situation? > > > > Attempt to build source and linking lib11r1 > > > > * What exactly did you do (or not do) that was effective (or > > > > ineffective)? > > > > Buiding the library from the upstream source or installing the version in > > testing are both effective remedies. > > > > * What was the outcome of this action? > > > > A small test program builds perfectly when upstream source is used, but > > cmake fails when libiir-dev and libiir1-dev are installed from stable > > > > * What outcome did you expect instead? > > > > It seems that the packaged cmake scripts expect to find a .a file, but > > that > > this file is not included in the package. If this is the case, either it > > should be included, or the cmake files be adjusted to reflect that it is > > not. I can apparently resolve this by installing v.1.10 from testing, but > > am reluctant to mix packaged from different sources on production > > machines. > > Thanks for reporting this. I believe this is the same issue as > https://bugs.debian.org/1125282 but I want to make sure before merging the > bugs. This bug is reported against 1.10.0+dfsg-4+b1; but from the > description, I understand that it affects 1.9.5+dfsg-1 (the version in > stable) and does *not* affect 1.10.1+dfsg-4 (the version in testing), is > that correct? > > I’ve asked for a stable update to fix this in stable too. > > Regards, > > Stephen Yes, sorry to have missed that duplicate report. Bernd (who is the main dev on this library -- i've copied this to him) asked me to check out the stable package because he'd had reports that it would break compilation. Indeed it does. 1.10 in testing is fine. Building from upstream on stable is fine. And installing a downloaded deb from a testing repo on stable with dpkg is also fine.
I'm not sure if you are deciding to remove .a archives from binary packages as a matter of policy? I don't have an axe to grind about that, but the upstream expects it to be there. Hence, I strongly suspect, the cmake error. It essentially stops the dev package in testing being useful to anybody wanting to develop with it. Thanks for getting back so quickly! Nick/.
signature.asc
Description: This is a digitally signed message part.
