Your message dated Sat, 24 Sep 2016 15:37:34 +0200
with message-id <1474724254.32551.0.ca...@debian.org>
and subject line Already fixed in latest upload, but not closed in changelog
has caused the Debian Bug report #831951,
regarding g2p-sk: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: 
binary build with no binary artifacts found; cannot distribute
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.)


-- 
831951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: g2p-sk
Version: 0.4.2-1
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.


The specific error below usually happens there is a binary-indep target in
debian/rules which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released
with jessie, the easy fix is to drop them now. If not, debian/rules should be
modified so that the binary-indep target generates the architecture independent
packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh_testdir
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs
> # Add here commands to install the package into debian/g2p-sk.
> #/usr/bin/make install DESTDIR=/<<PKGBUILDDIR>>/debian/g2p-sk
> cp -v  Trans_morfems.pm /<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/perl5/g2p_sk/
> 'Trans_morfems.pm' -> 
> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/perl5/g2p_sk/Trans_morfems.pm'
> cp -v  Trans_cod.pm /<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/perl5/g2p_sk/
> 'Trans_cod.pm' -> 
> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/perl5/g2p_sk/Trans_cod.pm'
> cp -v -r  Exceptions /<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/g2p_sk/
> 'Exceptions' -> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/g2p_sk/Exceptions'
> 'Exceptions/morfemy.ddat' -> 
> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/g2p_sk/Exceptions/morfemy.ddat'
> 'Exceptions/general_iso.ddat' -> 
> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/g2p_sk/Exceptions/general_iso.ddat'
> 'Exceptions/na_konci_ou.txt' -> 
> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/g2p_sk/Exceptions/na_konci_ou.txt'
> 'Exceptions/priaeu_iso.ddat' -> 
> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/share/g2p_sk/Exceptions/priaeu_iso.ddat'
> cp -v  g2p-sk /<<PKGBUILDDIR>>/debian/g2p-sk/usr/bin/
> 'g2p-sk' -> '/<<PKGBUILDDIR>>/debian/g2p-sk/usr/bin/g2p-sk'
>  dpkg-genchanges --build=all >../g2p-sk_0.4.2-1_all.changes
> dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
> distribute

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/g2p-sk_0.4.2-1_unstable_archallonly.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 ---
Control: fixed -1 0.4.2-2

Already fixed in latest upload, but not closed in changelog.

-- 
tobi

--- End Message ---

Reply via email to