On Tuesday 08 November 2005 10:04, Christoph Biedl wrote: [...] > I have been told the package was uploaded by the maintainer, not build > on the Debian buildds. Which would also explain the bug report. [...] > This is not for the i386 architecture. I admit that this build log looks > fine for alpha but cannot verify it (there's only i386 and hppa here).
OK the original asterisk_1:1.0.7.dfsg.1-2 package (i386) and buildds were built against zaptel-source_1:1.0.7-1. In the leadup to the release for sarge asterisk remained the same, however zaptel-source tranisitioned to using modules-assistant and underwent a number of NMU's and was released in sarge as zaptel (1:1.0.7-4.1). The fix as pointed out originally is to update 08_debian-zaptel.dpatch to acount for the new include file location. In fact the patch isn't needed at all as the package compiles correctly without it :-( This is fixed in unstable allready as this patch is no longer used. I have now applied this to svn.debian.org under pkg-voip, to version 1:1.0.7.dfsg.1-2sarge1 Question is? Now the package is fixed how to get an additional upload into stable? Given the guidance in the developers reference, I'm not sure we qualify against the critera: http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-upload-stable Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
