Your message dated Tue, 8 Jan 2019 12:43:31 +0100 with message-id <20190108114331.obwxxp7etgcon...@mail.anaproy.nl> and subject line Re: mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16) has caused the Debian Bug report #917695, regarding mbtserver: FTBFS: unsatisfiable build-dependencies: libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= 3.2.16) 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.) -- 917695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mbtserver Version: 0.11-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20181229 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +------------------------------------------------------------------------------+ > | Install package build dependencies > | > +------------------------------------------------------------------------------+ > > > Setup apt archive > ----------------- > > Merged Build-Depends: cdbs, debhelper (>= 7), pkg-config, dh-autoreconf, > libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= > 3.2.16), libticcutils2-dev (>= 0.13), libxml2-dev > Filtered Build-Depends: cdbs, debhelper (>= 7), pkg-config, dh-autoreconf, > libtimbl4-dev (>= 6.4.8), libtimblserver4-dev (>= 1.11), libmbt1-dev (>= > 3.2.16), libticcutils2-dev (>= 0.13), libxml2-dev > dpkg-deb: building package 'sbuild-build-depends-mbtserver-dummy' in > '/<<BUILDDIR>>/resolver-LNLJQQ/apt_archive/sbuild-build-depends-mbtserver-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-mbtserver-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<<BUILDDIR>>/resolver-LNLJQQ/apt_archive ./ InRelease > Get:2 copy:/<<BUILDDIR>>/resolver-LNLJQQ/apt_archive ./ Release [963 B] > Ign:3 copy:/<<BUILDDIR>>/resolver-LNLJQQ/apt_archive ./ Release.gpg > Get:4 copy:/<<BUILDDIR>>/resolver-LNLJQQ/apt_archive ./ Sources [563 B] > Get:5 copy:/<<BUILDDIR>>/resolver-LNLJQQ/apt_archive ./ Packages [647 B] > Fetched 2173 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install mbtserver build dependencies (apt-based resolver) > --------------------------------------------------------- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-mbtserver-dummy : Depends: libtimbl4-dev (>= 6.4.8) but > it is not going to be installed > Depends: libtimblserver4-dev (>= > 1.11) but it is not going to be installed > Depends: libmbt1-dev (>= 3.2.16) but > it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2018/12/29/mbtserver_0.11-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---Hi Lucas, This issue should be solved by the new release (0.12) that was already prepared but has been uploaded yesterday. It may take a bit for the migration to testing. Kind regards, -- Maarten van Gompel Language Machines research group Centre for Language and Speech Technology Radboud Universiteit Nijmegen proy...@anaproy.nl https://proycon.anaproy.nl https://github.com/proycon GnuPG key: 0x39FE11201A31555C XMPP: proy...@anaproy.nl Matrix: @proycon:matrix.org Telegram: proycon IRC: proycon (freenode) Discord: proycon#8272 Mastodon: https://mastodon.social/@proycon (@proycon@mastodon.social) Twitter: https://twitter.com/proycon ORCID: https://orcid.org/0000-0002-1046-0006 Keybase: https://keybase.io/proycon Bitcoin: 1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd
--- End Message ---
