Your message dated Thu, 30 Jul 2015 11:28:18 +0100
with message-id <55b9fc42.8080...@p10link.net>
and subject line re: apertium: FTBFS on multiple architectures
has caused the Debian Bug report #793425,
regarding apertium: FTBFS on multiple architectures
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 ow...@bugs.debian.org
immediately.)
--
793425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apertium
Version: 3.4.0~r61013-2
Severity: serious
Justification: FTBFS, but did so in the past
The most recent upload of apertium fails to build from source because of
changed symbols:
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libapertium3-3.4-0/DEBIAN/symbols doesn't
match completely debian/libapertium3-3.4-0.symbols
This holds up a (admittedly unco-ordinated) transition. It probably also
triggers one...
-- System Information:
Debian Release: 8.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'proposed-updates'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 3.4.0~r61013-3
The most recent upload of apertium fails to build from source because of
changed symbols:
The -3 upload successfully built on all release architectures.
It probably also
triggers one...
According to the cruft report it looks like this package has a number of
reverse dependencies that need to be dealt with. They all look closely
related to it though.
* source package apertium version 3.4.0~r61013-3 no longer builds
binary package(s): libapertium3-3.1-0 libapertium3-3.1-0-dev
on
amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x
- suggested command:
dak rm -m "[auto-cruft] NBS (no longer built by apertium)" -s unstable -a
amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x
-p -R -b libapertium3-3.1-0 libapertium3-3.1-0-dev
- broken Build-Depends:
apertium-dbus: libapertium3-3.1-0-dev (>= 3.0.2)
apertium-eo-ca: libapertium3-3.1-0-dev
apertium-eo-es: libapertium3-3.1-0-dev
apertium-es-gl: libapertium3-3.1-0-dev (>= 3.1.0)
apertium-es-pt: libapertium3-3.1-0-dev (>= 3.0.1)
apertium-es-ro: libapertium3-3.1-0-dev
apertium-eu-es: libapertium3-3.1-0-dev (>= 3.1.0)
apertium-fr-ca: libapertium3-3.1-0-dev (>= 3.1.0)
apertium-fr-es: libapertium3-3.1-0-dev (>= 3.1.0)
apertium-oc-ca: libapertium3-3.1-0-dev
apertium-oc-es: libapertium3-3.1-0-dev
apertium-pt-ca: libapertium3-3.1-0-dev (>= 3.1.0)
apertium-pt-gl: libapertium3-3.1-0-dev (>= 3.1.0)
apertium-tolk: libapertium3-3.1-0-dev
P.S. I am not a maintainer of this package, just a random dev whose
attention was drawn to it.
--- End Message ---
