Your message dated Sun, 28 Feb 2010 12:48:26 +0100
with message-id <[email protected]>
and subject line libalog_0.1-4(mips/unstable): Probably wrong control file.
Architectures for runtime, dev and dbg packages should be the same
has caused the Debian Bug report #514789,
regarding libalog_0.1-4(mips/unstable): Probably wrong control file.
Architectures for runtime, dev and dbg packages should be the same
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
514789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514789
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libalog
Version: 0.1-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of libalog_0.1-4 on ball by sbuild/mips 99.99
> Build started at 20090206-1103
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 7), gnat, libahven-dev (>= 1.3), libaws-dev (>=
> 2.5~124785)
[...]
> dpkg-shlibdeps: warning: symbol unicode__ccs___elabs used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol ahven__temporary_output___elabs used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol aws__smtp__statusDI used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol aws__smtp__receiverDF used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol aws__net__poll_events___elabs used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol ahven_E used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol unicode__ces___elabs used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol ahven__listeners_E used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: symbol aws__net___elabs used by
> debian/libalog0/usr/lib/libalog.so.0.1 found in none of the libraries.
> dpkg-shlibdeps: warning: 154 other similar warnings have been skipped (use -v
> to see them all).
> dh_gencontrol
> dpkg-gencontrol: error: current host architecture 'mips' does not appear in
> package's architecture list (alpha amd64 i386 ia64 powerpc s390 sparc)
> dh_gencontrol: command returned error code 65280
> make: *** [binary-arch] Error 1
> dpkg-buildpackage: failure: /usr/bin/sudo debian/rules binary-arch gave error
> exit status 2
A full build log can be found at:
http://buildd.debian.org/build.php?arch=mips&pkg=libalog&ver=0.1-4
--- End Message ---
--- Begin Message ---
I believe this problem has been resolved by the debian version 0.3-1 by
setting the Architectures in the controle file to "any" for all
packages. I forgot to include a close directive in the changelog so I am
closing this bug manually.
-Adrian
--- End Message ---
