Debian Bug report logs - #814968
src:hunspell] hunspell: FTBFS: various tests FAIL

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: submit@bugs.debian.org

Subject: hunspell: FTBFS: FAIL: map.test

Date: Wed, 17 Feb 2016 09:45:03 +0100

[Message part 1 (text/plain, inline)]

Source: hunspell
Version: 1.3.3-3
Severity: serious
Justification: fails to build from source
User: reproducible-builds@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear Maintainer,

hunspell fails to build from source in unstable/amd64:

  [..]

  /usr/bin/make  check-TESTS
  make[4]: Entering directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3/tests'
  make[5]: Entering directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3/tests'
  PASS: affixes.test
  PASS: condition.test
  PASS: condition_utf.test
  PASS: base.test
  PASS: base_utf.test
  PASS: allcaps.test
  PASS: allcaps_utf.test
  PASS: allcaps2.test
  PASS: allcaps3.test
  PASS: keepcase.test
  PASS: i58202.test
  FAIL: map.test
  FAIL: rep.test
  PASS: sug.test
  PASS: sugutf.test
  PASS: phone.test
  PASS: flag.test
  PASS: flaglong.test
  PASS: flagnum.test
  PASS: flagutf8.test
  PASS: slash.test
  PASS: forbiddenword.test
  PASS: nosuggest.test
  PASS: alias.test
  PASS: alias2.test
  PASS: alias3.test
  PASS: breakdefault.test
  PASS: break.test
  PASS: needaffix.test
  PASS: needaffix2.test
  PASS: needaffix3.test
  PASS: needaffix4.test
  PASS: needaffix5.test
  PASS: circumfix.test
  PASS: fogemorpheme.test
  PASS: onlyincompound.test
  PASS: complexprefixes.test
  PASS: complexprefixes2.test
  PASS: complexprefixesutf.test
  PASS: conditionalprefix.test
  PASS: zeroaffix.test
  PASS: utf8.test
  PASS: utf8_bom.test
  PASS: utf8_bom2.test
  FAIL: utf8_nonbmp.test
  PASS: compoundflag.test
  PASS: compoundrule.test
  PASS: compoundrule2.test
  PASS: compoundrule3.test
  PASS: compoundrule4.test
  PASS: compoundrule5.test
  PASS: compoundrule6.test
  PASS: compoundrule7.test
  PASS: compoundrule8.test
  PASS: compoundaffix.test
  PASS: compoundaffix2.test
  PASS: compoundaffix3.test
  PASS: checkcompounddup.test
  PASS: checkcompoundtriple.test
  PASS: simplifiedtriple.test
  PASS: checkcompoundrep.test
  PASS: checkcompoundcase2.test
  PASS: checkcompoundcaseutf.test
  PASS: checkcompoundpattern.test
  PASS: checkcompoundpattern2.test
  PASS: checkcompoundpattern3.test
  PASS: checkcompoundpattern4.test
  PASS: utfcompound.test
  FAIL: checksharps.test
  FAIL: checksharpsutf.test
  PASS: germancompounding.test
  PASS: germancompoundingold.test
  PASS: i35725.test
  PASS: i53643.test
  FAIL: i54633.test
  PASS: i54980.test
  FAIL: maputf.test
  FAIL: reputf.test
  PASS: ignore.test
  PASS: ignoreutf.test
  PASS: 1592880.test
  PASS: 1695964.test
  FAIL: 1463589.test
  FAIL: 1463589_utf.test
  PASS: IJ.test
  PASS: i68568.test
  PASS: i68568utf.test
  PASS: 1706659.test
  PASS: digits_in_words.test
  PASS: colons_in_words.test
  FAIL: ngram_utf_fix.test
  PASS: morph.test
  PASS: 1975530.test
  PASS: fullstrip.test
  PASS: iconv.test
  FAIL: oconv.test
  PASS: encoding.test
  PASS: korean.test
  PASS: opentaal_forbiddenword1.test
  PASS: opentaal_forbiddenword2.test
  PASS: opentaal_keepcase.test
  PASS: arabic.test
  PASS: 2970240.test
  PASS: 2970242.test
  PASS: breakoff.test
  PASS: opentaal_cpdpat.test
  PASS: opentaal_cpdpat2.test
  PASS: 2999225.test
  PASS: onlyincompound2.test
  PASS: forceucase.test
  PASS: warn.test
  ============================================================================
  Testsuite summary for hunspell 1.3.3
  ============================================================================
  # TOTAL: 111
  # PASS:  99
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  12
  # XPASS: 0
  # ERROR: 0
  ============================================================================
  See tests/test-suite.log
  Please report to nemeth@numbertext.org
  ============================================================================
  Makefile:1414: recipe for target 'test-suite.log' failed
  make[5]: *** [test-suite.log] Error 1
  make[5]: Leaving directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3/tests'
  Makefile:1520: recipe for target 'check-TESTS' failed
  make[4]: *** [check-TESTS] Error 2
  make[4]: Leaving directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3/tests'
  Makefile:1611: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  make[3]: Leaving directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3/tests'
  Makefile:1307: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3/tests'
  Makefile:534: recipe for target 'check-recursive' failed
  make[1]: *** [check-recursive] Error 1
  make[1]: Leaving directory '/home/lamby/temp/cdt.20160217092630.ijdNXlcUQQ/hunspell-1.3.3'
  debian/rules:46: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2

  [..]

The full build log is attached.


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

[hunspell.1.3.3-3.unstable.amd64.log.txt.gz (application/octet-stream, attachment)]

Message #16 received at 814968@bugs.debian.org (full text, mbox, reply):

From: Raúl Benencia <rul@kalgan.cc>

To: 814968@bugs.debian.org

Subject: hunspell: diff for NMU version 1.3.3-3.1

Date: Wed, 9 Mar 2016 08:19:49 -0800

[Message part 1 (text/plain, inline)]

Control: tags 814968 + patch
Control: tags 814968 + pending

Dear maintainer,

This FTBFS is caused by a recent update on the grep package that sightly
changes the binary file matching behavior. In this case, the fix consists
in forcing grep to match text. I've prepared an NMU with this changes
(versioned as 1.3.3-3.1).

As I don't have privileges to upload it to DELAYED, I've uploaded it to the
mentors repository. Please visit the following URL:

  http://mentors.debian.net/package/hunspell

Alternatively, one can download the package with dget using this command:

  dget -x http://mentors.debian.net/debian/pool/main/h/hunspell/hunspell_1.3.3-3.1.dsc

Cheers,
Rul

[hunspell-1.3.3-3.1-nmu.diff (text/x-diff, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 814968@bugs.debian.org (full text, mbox, reply):

From: Rene Engelhard <rene@debian.org>

To: Raúl Benencia <rul@kalgan.cc>, 814968@bugs.debian.org

Subject: Re: Bug#814968: hunspell: diff for NMU version 1.3.3-3.1

Date: Wed, 9 Mar 2016 17:43:55 +0100

Hi,

On Wed, Mar 09, 2016 at 08:19:49AM -0800, Raúl Benencia wrote:
> This FTBFS is caused by a recent update on the grep package that sightly
> changes the binary file matching behavior. In this case, the fix consists
> in forcing grep to match text.

Ah, thanks

> I've prepared an NMU with this changes (versioned as 1.3.3-3.1).

Erm, without givinbg the maintainer the chance to add the fix himself? That's not how
NMUs are supposed to work.

> As I don't have privileges to upload it to DELAYED, [...]

I am inclinced to say "thankfully" here.

> I've uploaded it to the  mentors repository. Please visit the following URL:
> 
>   http://mentors.debian.net/package/hunspell
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x http://mentors.debian.net/debian/pool/main/h/hunspell/hunspell_1.3.3-3.1.dsc

Thanks, will get it and/or apply the patch and upload tonight or tomorrow.

Regards,

Rene

Message #30 received at 814968@bugs.debian.org (full text, mbox, reply):

From: Raúl Benencia <rul@kalgan.cc>

To: Rene Engelhard <rene@debian.org>

Cc: 814968@bugs.debian.org

Subject: Re: Bug#814968: hunspell: diff for NMU version 1.3.3-3.1

Date: Wed, 9 Mar 2016 11:08:45 -0800

[Message part 1 (text/plain, inline)]

Hi, 

On Wed, Mar 09, 2016 at 05:43:55PM +0100, Rene Engelhard wrote:
> > I've prepared an NMU with this changes (versioned as 1.3.3-3.1).
> 
> Erm, without givinbg the maintainer the chance to add the fix himself? That's not how
> NMUs are supposed to work.

I'm going to quote the developer reference, section 5.11.1:

| Unless you have an excellent reason not to do so, you must then give some
| time to the maintainer to react (for example, by uploading to the
| DELAYED queue). Here are some recommended values to use for delays:
| 
| (...)
|
| * Upload fixing only release-critical bugs older than 7 days: 2 days

This release-critical bug has been open for more than twenty days, so I
understand that this is how NMUs are supposed to work.

> > As I don't have privileges to upload it to DELAYED, [...]
> 
> I am inclinced to say "thankfully" here.

In hopes of being constructive, would you care to explain why? Section
5.11.3 says:

| Having to wait for a response after you request permission to NMU is
| inefficient, because it costs the NMUer a context switch to come back to
| the issue.

On top of that, section 5.6.2 says:

| It is sometimes useful to upload a package immediately, but to want this
| package to arrive in the archive only a few days later. For example, when
| preparing a Non-Maintainer Upload, you might want to give the maintainer
| a few days to react.

I've used mentors as a replacement of DELAYED in hopes that, if you were
unresponsive for the aforementioned time, another DD could have easily
sponsored the NMU.

Would you care to explain why do you think I shouldn't have hypothetically
used DELAYED in this way?

Thanks in advance,
Rul

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 814968@bugs.debian.org (full text, mbox, reply):

From: Rene Engelhard <rene@debian.org>

To: Raúl Benencia <rul@kalgan.cc>, 814968@bugs.debian.org

Subject: Re: Bug#814968: hunspell: diff for NMU version 1.3.3-3.1

Date: Wed, 9 Mar 2016 21:55:20 +0100

Hi,

On Wed, Mar 09, 2016 at 11:08:45AM -0800, Raúl Benencia wrote:
> On Wed, Mar 09, 2016 at 05:43:55PM +0100, Rene Engelhard wrote:
> > > I've prepared an NMU with this changes (versioned as 1.3.3-3.1).
> > 
> > Erm, without givinbg the maintainer the chance to add the fix himself? That's not how
> > NMUs are supposed to work.
> 
> I'm going to quote the developer reference, section 5.11.1:
> 
> | Unless you have an excellent reason not to do so, you must then give some
> | time to the maintainer to react (for example, by uploading to the
> | DELAYED queue). Here are some recommended values to use for delays:
> | 
> | (...)
> |
> | * Upload fixing only release-critical bugs older than 7 days: 2 days
> 
> This release-critical bug has been open for more than twenty days, so I

Yes, it was open for > 20 days.

But if you actually read the bug carefully you'd have seen that I forwarded
this to upstream _yesterday_. Because I only reached him yesterday given he
wasn't on IRC before.

That was the last action. And you can't expect debugging go that fast for busy
upstreams.

Then today your patch came. Thanks for that :)

> understand that this is how NMUs are supposed to work.

Interestingly, in your above quote you don't quote

- Did you give enough time to the maintainer? When was the bug reported to the BTS? Being busy for a week or two isn't unusual. Is the bug so severe that it needs to be fixed right now, or can it wait a few more days?

and

- If the maintainer is usually active and responsive, have you tried to contact them? In general it should be considered preferable that maintainers take care of an issue themselves and that they are given the chance to review and correct your patch, because they can be expected to be more aware of potential issues which an NMUer might miss. It is often a better use of everyone's time if the maintainer is given an opportunity to upload a fix on their own.

I am active. And see the first paragraph above.

And if that bug is fixed there's other bugs which didn't warrant an other
upload which could be (and were now) fixed with the same upload.

> | It is sometimes useful to upload a package immediately, but to want this
> | package to arrive in the archive only a few days later. For example, when
> | preparing a Non-Maintainer Upload, you might want to give the maintainer
> | a few days to react.
> 
> I've used mentors as a replacement of DELAYED in hopes that, if you were
> unresponsive for the aforementioned time, another DD could have easily
> sponsored the NMU.
> 
> Would you care to explain why do you think I shouldn't have hypothetically
> used DELAYED in this way?

You should have sent the diff and I would have added it quickly. There's
no need to "threaten" with a NMU.

Anyway, thanks for the patch. Told upstream and uploaded the fixed package.

Regards,

Rene

Message #40 received at 814968-close@bugs.debian.org (full text, mbox, reply):

From: Rene Engelhard <rene@debian.org>

To: 814968-close@bugs.debian.org

Subject: Bug#814968: fixed in hunspell 1.3.3-4

Date: Wed, 09 Mar 2016 22:28:21 +0000

Source: hunspell
Source-Version: 1.3.3-4

We believe that the bug you reported is fixed in the latest version of
hunspell, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 814968@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Engelhard <rene@debian.org> (supplier of updated hunspell package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 09 Mar 2016 17:03:11 +0000
Source: hunspell
Binary: libhunspell-dev libhunspell-1.3-0 hunspell hunspell-tools
Architecture: source
Version: 1.3.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers <debian-openoffice@lists.debian.org>
Changed-By: Rene Engelhard <rene@debian.org>
Description:
 hunspell   - spell checker and morphological analyzer (program)
 hunspell-tools - tools for hunspell
 libhunspell-1.3-0 - spell checker and morphological analyzer (shared library)
 libhunspell-dev - spell checker and morphological analyzer (development)
Closes: 780626 798614 811221 814968
Changes:
 hunspell (1.3.3-4) unstable; urgency=medium
 .
   * apply patch from Raúl Benencia: Fix FTBFS caused by new binary
     matching behavior on grep, thanks (Closes: #814968)
 .
   * s/character/characters/ (closes: #811221)
   * apply patch from Matthias Klose:
     - Bump the standards version.
     - Build using dpkg-buildflags. Closes: #780626.
     - Enable parallel builds.
     (closes: #798614)
   * migrate from -dbg to -dbgsym
Checksums-Sha1:
 9ba6508c77a84c3a9db3ffd2230dee2e0ba6cfcb 2101 hunspell_1.3.3-4.dsc
 6d3813dca8dbc9f607cc42928c18310f9cb76c49 21304 hunspell_1.3.3-4.debian.tar.xz
Checksums-Sha256:
 c0744fd296fe6c76ddceed4092c70774aa88bfd86b823bbfd3da8ce2f2191c79 2101 hunspell_1.3.3-4.dsc
 559dc443b36ee472cc2c80292cc5f417efe57afa05ad6d1e5379777c36c660ae 21304 hunspell_1.3.3-4.debian.tar.xz
Files:
 34a05ab053a99f70df09005411f3b5ba 2101 text optional hunspell_1.3.3-4.dsc
 2bad3a594d50e701a0bcca0728b39df7 21304 text optional hunspell_1.3.3-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJW4ItVAAoJEAqgRXHQPj5wCFcP/jFGZaYs+HS/z0WGZTe8iQcU
yqcIZegpM4/z2yWncfC8UMS62Ndvg2cthaNYnnbUlArkKmc0f7RHT/lMVD3zbvVN
jMoJBCUiETKUQmg1iZN9hbsuob9H3vUai9vqToA9S119oCJ5tkLguTQDuTDamog9
qFexsfbLlBB7AQBP7xHw4eAMUSxi3Q5QnCELgisFk0jlt5D8c021s4Fan+z6OwHA
iQCIqy7zYu4SBszugwej6h/t8z7QEkPexofaDJrjhKl3R3GkB5oKzwHHPG8KiZwQ
tGqrqJKpJUGu1hMa6+QCU/iRgtgX9orBnzyensVyCjajAl/PF+N0+cIKOZLzUP5e
QhwpMBuZN1Ta6374qzKO7ue0xLaZQcklCCEJt0OPuRX/OzltDfCJHC3D3sEZzHI6
tImOY8lLY22imbRw6KDh5emgJQNbAN239ReFKV8IDeeGcPKAKwhepF5Cf7wR0xUC
e1NgZVeHJ/APBoApmRfGTd5c5WBLgQalhuVV8UdORuuhnN2a0OZLbaE3GUvlmBaD
P8jhvAQti8SO21T+XjV1T6ZkhJCBJaBuLV4httCz2lhK4iVWzXrNtbqEFI8sJZYQ
/N6yN3KT0sK1DRBgP5y2NpKAFwrYz2vObCiVS15WrzOVxF0cFph87tq9PCOEzQin
mdwBt6JHZYpqYb+c9M0x
=hsXf
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.