On Sun, Aug 21, 2016 at 11:27:14PM +0300, Adrian Bunk wrote:
> On Sun, Aug 21, 2016 at 09:55:26PM +0200, Santiago Vila wrote:
> > On Sun, Aug 21, 2016 at 10:49:22PM +0300, Adrian Bunk wrote:
> > > On Sun, Aug 21, 2016 at 09:05:19PM +0200, Santiago Vila wrote:
> > > > When a package fails to build from source, there are no runtime
> > > > problems at all, because the binary package does not even exist.
> > > 
> > > That is only true when the build always fails (see my next email).
> > 
> > Indeed. When I wrote that I was still confused about why "FTBFS"
> > was in the subject of this report.
> > 
> > Maybe he meant that the package made others packages to FTBFS (?).
> > I don't know.
> 
> golang-fsnotify builds only binary-all packages.
> 
> golang-fsnotify contains testcases.
> 
> This is not a normal FTBFS that you would see on the autobuilders
> (no autobuilder ever tried to build golang-fsnotify),
> but if you would try to build golang-fsnotify on ppc64el I assume
> the build would fail due to failing testcases.

Aha, so the subject could have been like this:

(FTBFS and not working at all) in ppc64el

and this is what I understood:

FTBFS and (not working at all in ppc64el)

Thanks for the claritication.

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to