Your message dated Wed, 7 Jun 2017 20:43:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#769005: pgloader: FTBFS on armhf
has caused the Debian Bug report #769005,
regarding pgloader: FTBFS on armhf
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 [email protected]
immediately.)
--
769005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769005
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pgloader
Version: 3.1.1+dfsg-1
Severity: important
Justification: FTBFS
Hello,
Your package fails to build from source on Debian autobuilder network.
Please check your package build logs at:
<https://buildd.debian.org/status/package.php?p=pgloader&suite=sid>
Full log at:
https://buildd.debian.org/status/fetch.php?pkg=pgloader&arch=armhf&ver=3.1.1%2Bdfsg-1&stamp=1415212589
Best regards
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (900, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.14-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Re: Hector Oron 2014-11-10
<[email protected]>
> Source: pgloader
>
> Your package fails to build from source on Debian autobuilder network.
>
> Please check your package build logs at:
> <https://buildd.debian.org/status/package.php?p=pgloader&suite=sid>
>
> Full log at:
>
> https://buildd.debian.org/status/fetch.php?pkg=pgloader&arch=armhf&ver=3.1.1%2Bdfsg-1&stamp=1415212589
Hi,
this is (no longer?) a pgloader bug - the necessary sbcl compiler
doesn't exist in unstable for armhf. It used to exist and is still
part of jessie - I can't say why it got removed, but I guess it has to
do with problems of the sort that are visible in these build logs.
Christoph
--- End Message ---
