Your message dated Tue, 23 Aug 2016 21:34:17 +0200
with message-id <226e642f-4587-0b93-a10c-4621a7e34...@tincho.org>
and subject line already fixed
has caused the Debian Bug report #819452,
regarding golang-fsnotify: not working at all in ppc64el, arm64
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.)
--
819452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-fsnotify
Version: 1.2.9-1
Severity: important
Tags: upstream
As I reported upstream (https://github.com/fsnotify/fsnotify/issues/130),
fsnotify does not seem to work at all in ppc64el. I noticed this when trying to
solve a FTBFS in prometheus, that can be tracked down to this module not
producing any events in that architecture.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Hi all,
It seems I forgot to close the bug in my last upload (from April!). But
this issue was already fixed by a change in x/sys (see the upstream
bug). Closing now.
--
MartÃn Ferrari (Tincho)
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
