Your message dated Sun, 21 Oct 2018 14:28:37 +0200 with message-id <b5248434-f109-7040-d720-ab20898bf38a@debian.org> and subject line Re: Bug#911522: ghostscript: FTBFS on amd64, i386 has caused the Debian Bug report #911522, regarding ghostscript: FTBFS on amd64, i386 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 owner@bugs.debian.org immediately.) -- 911522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911522 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: ghostscript: FTBFS on amd64, i386
- From: Ivo De Decker <ivodd@debian.org>
- Date: Sun, 21 Oct 2018 10:08:43 +0000
- Message-id: <[🔎] 20181021100843.bkaxvjuwu5uakytz@debian.org>
package: src:ghostscript version: 9.25~dfsg-4 severity: serious tags: ftbfs Hi, The latest version of ghostscript in unstable fails on amd64, i386: https://buildd.debian.org/status/package.php?p=ghostscript Cheers, Ivo
--- End Message ---
--- Begin Message ---
- To: Samuel Thibault <sthibault@debian.org>, Jonas Smedegaard <jonas@jones.dk>, 911522-done@bugs.debian.org
- Subject: Re: Bug#911522: ghostscript: FTBFS on amd64, i386
- From: Ivo De Decker <ivodd@debian.org>
- Date: Sun, 21 Oct 2018 14:28:37 +0200
- Message-id: <b5248434-f109-7040-d720-ab20898bf38a@debian.org>
- In-reply-to: <[🔎] 20181021110616.efbx3pspyl6pirvk@function>
- References: <[🔎] 20181021100843.bkaxvjuwu5uakytz@debian.org> <[🔎] 20181021100843.bkaxvjuwu5uakytz@debian.org> <[🔎] 154011936206.1793.13237445545646406723@auryn.jones.dk> <[🔎] 20181021110616.efbx3pspyl6pirvk@function>
Hi, On 10/21/18 1:06 PM, Samuel Thibault wrote:Jonas Smedegaard, le dim. 21 oct. 2018 12:56:02 +0200, a ecrit:I am clueless why that happens. Not sure, but I suspect it is a spurious error happening occationally and if so that a workaround is to simply request a binNMU. Help dearly appreciated either requesting a binNMU (by someone understanding the - to me - strange language to do that),I have done so (actually it's a buildd give-back, binNMU is when you rebuild a new binary version of an existing package)It builds now. Closing! Thanks, Ivo
--- End Message ---