On Monday 05 February 2007 21:53, Mark Purcell wrote: > I can't recreate my build environment from Oct 06. > > And I can't reproduce the bug, additionally I don't have the hardware to test. One theory though looking at the time line: asterisk-chan-capi (0.7.1-1) would of been built against asterisk (1:1.2.12.1.dfsg-1) Etch now has asterisk (1:1.2.13~dfsg-2) and asterisk-dev may not be version compatible between 1.2.12 & 1.2.13? This could explain why the binNMU of asterisk-chan-capi now works for etch, and would suggest that asterisk-chan-capi should perhaps have a strict version dependency against asterisk. Mark asterisk-chan-capi (0.7.1-1+b1) testing; urgency=low -- Debian/i386 Build Daemon <buildd_i386-ninsei> Fri, 2 Feb 2007 00:43:31 -0800 asterisk-chan-capi (0.7.1-1) unstable; urgency=low -- Mark Purcell <msp@debian.org> Sun, 22 Oct 2006 20:49:40 +0100 asterisk (1:1.2.13~dfsg-2) unstable; urgency=low -- Mark Purcell <msp@debian.org> Mon, 6 Nov 2006 06:33:19 +0000 asterisk (1:1.2.13~dfsg-1) unstable; urgency=high -- Mark Purcell <msp@debian.org> Wed, 25 Oct 2006 06:46:52 +0100 asterisk (1:1.2.12.1.dfsg-1) unstable; urgency=low -- Mark Purcell <msp@debian.org> Sun, 24 Sep 2006 14:45:58 +0100
Attachment:
pgpf2tiCcLRJW.pgp
Description: PGP signature