Your message dated Tue, 15 Nov 2016 15:56:35 +0100
with message-id <20161115145635.ga11...@diskless.uio.no>
and subject line Re: libelfin: FTBFS everywhere
has caused the Debian Bug report #844369,
regarding libelfin: FTBFS everywhere
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.)
--
844369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libelfin
Version: 0.2-2
Severity: serious
Your package built nowhere:
https://buildd.debian.org/status/package.php?p=libelfin
The previous version didn't build anywhere either, so I'm surprised
this was uploaded to sid without fixing that first...
https://buildd.debian.org/status/logs.php?pkg=libelfin&ver=0.2-1&suite=experimental
Emilio
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500,
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.7.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: 0.2-3
This was fixed in 0.2-3 which was stuck in NEW for unknown reasons.
More build problems were solved in 0.2-4 and 0.2-5.
--
Happy hacking
Petter Reinholdtsen
--- End Message ---
