On Fri, Jan 04, 2019 at 12:13:20AM +0200, Adrian Bunk wrote:
> The failures all make sense if the result is
> $(currentyear)-11-03 09:23:38.000
> and this is compared with
> 2018-11-03 09:23:38.000
>
> The upstream fix might not work for the complete lifetime of buster...
> https://github.com
Control: tags -1 -help
On Thu, Jan 03, 2019 at 10:24:50PM +0100, Santiago Vila wrote:
> Note: I triggered rebuilds on reproducible-builds and now the failures
> on testing/amd64 and unstable/amd64 are both as follows:
>
> -2018-11-03 09:23:38.000
> -2018-11-03 09:23:38.000
> -2018-11-03 09:23:38.
On Thu, Jan 03, 2019 at 10:22:34PM +0100, Salvatore Bonaccorso wrote:
> Something recent must have now caused that lnav FTBFS,
My guess would be that the test is not well designed and it fails on
certain dates (for example, "at the end or beginning of the year").
Maybe this theory could be tested
Control: tags -1 + confirmed help
Hi Santiago,
On Thu, Jan 03, 2019 at 09:06:05PM +, Santiago Vila wrote:
> Package: src:lnav
> Version: 0.8.4-4
> Severity: serious
> Tags: ftbfs
>
> Hello Salvatore.
>
> I tried to build this package in buster but it failed:
>
> ---
Note: I triggered rebuilds on reproducible-builds and now the failures
on testing/amd64 and unstable/amd64 are both as follows:
-2018-11-03 09:23:38.000
-2018-11-03 09:23:38.000
-2018-11-03 09:23:38.000
+2020-11-03 09:23:38.000
+2020-11-03 09:23:38.000
+2020-11-03 09:23:38.000
Sorry, I believed
Package: src:lnav
Version: 0.8.4-4
Severity: serious
Tags: ftbfs
Hello Salvatore.
I tried to build this package in buster but it failed:
[...]
debian/rules binary-arch
dh binary-arch
dh_update_autotools_config -
6 matches
Mail list logo
