Bug#948895: neomutt: FTBFS: test failure

2020-03-12 Thread Andreas Henriksson
Hello,

On Thu, Mar 12, 2020 at 05:25:50PM -0700, Stefano Rivera wrote:
> Control: reopen -1
> Control: notfixed -1 20191207+dfsg.1-1
[...]

If you're going to claim neomutt still FTBFS despite what
https://buildd.debian.org/status/package.php?p=neomutt
says, then I think you could atleast provide a build log backing up your
claim. (And even with that I'd personally likely not agree with your
claim that FTBFS on anything but official buildd is RC severity, but
that's up to the neomutt maintainers to finally decide on I guess.)

(IOW Please don't repurpose old bug reports when new ones are free.)

Regards,
Andreas Henriksson



Bug#948895: neomutt: FTBFS: test failure

2020-03-12 Thread Stefano Rivera
Control: reopen -1
Control: notfixed -1 20191207+dfsg.1-1

> This is fixed by:
> https://github.com/neomutt/neomutt/commit/6a98d598bf0443516146c6a856b965f5e0fb35a1#diff-80e4b64ac703024c17f04c3d0d014e40
> 
> In other words updating to the latest release (20191207) would
> fix this issue.

That is just one of the failures here.

Here's another one:
https://github.com/neomutt/neomutt/commit/26a6b07c728aa88414057cff257cdebfd2967907

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Bug#948895: neomutt: FTBFS: test failure

2020-02-09 Thread Andreas Henriksson
Control: tags -1 + fixed-upstream

Hello,

This is fixed by:
https://github.com/neomutt/neomutt/commit/6a98d598bf0443516146c6a856b965f5e0fb35a1#diff-80e4b64ac703024c17f04c3d0d014e40

In other words updating to the latest release (20191207) would
fix this issue.

Regards,
Andreas Henriksson



Bug#948895: neomutt: FTBFS: test failure

2020-01-14 Thread Mattia Rizzolo
Source: neomutt
Version: 2019+dfsg.1-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid chroot:

test/neomutt-test
Test test_mutt_addr_cat...  [ OK ]
Test test_mutt_addr_cmp...  [ OK ]
Test test_mutt_addr_copy... [ OK ]
...
Test test_mutt_date_gmtime...   [ OK ]
Test test_mutt_date_is_day_name...  [ OK ]
Test test_mutt_date_localtime...[ FAILED ]
  Case December, 2000:
mutt_date_localtime.c:36: Check tm.tm_hour == 12... failed
  Case June, 2000:
mutt_date_localtime.c:48: Check (tm.tm_hour == 12) || (tm.tm_hour == 11)... 
failed
  hour = 23
mutt_date_localtime.c:51: Check tm.tm_mday == 25... failed
mutt_date_localtime.c:54: Check tm.tm_wday == 0... failed
mutt_date_localtime.c:55: Check tm.tm_yday == 176... failed
  Case Today:
mutt_date_localtime.c:61: Check tm.tm_yday >= 119... failed
Test test_mutt_date_localtime_format... [ FAILED ]
  mutt_date_localtime_format.c:49: Check result == true... failed
Test test_mutt_date_local_tz... [ OK ]
Test test_mutt_date_make_date...[ OK ]
Test test_mutt_date_make_imap...[ FAILED ]
  mutt_date_make_imap.c:43: Check result == true... failed
Test test_mutt_date_make_time...[ FAILED ]
  Case {0,0,0,1,0,1,0} = 9223372036854775807:
mutt_date_make_time.c:74: Check result == 946684800... failed
Test test_mutt_date_make_tls... [ OK ]
Test test_mutt_date_normalize_time...   [ OK ]
Test test_mutt_date_parse_date...   [ OK ]
...
Test test_url_tobuffer...   [ OK ]
Test test_url_tostring...   [ OK ]
FAILED: 4 of 377 unit tests have failed.
make[1]: *** [Makefile:1150: test] Error 1
make[1]: Leaving directory 
'/build/1st/neomutt-2019+dfsg.1/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j15 test VERBOSE=1 returned exit 
code 2
make: *** [debian/rules:20: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature