The uncrustify build on zani.debian.org filled up the 75G available in
the build directory.

Cheers,
Julien

Hello Julien,

Yep. I got it. Upstream thinks that sizeof(int)==sizeof(size_t) =(

Have to dig through the code to fix this everywhere.

We believe that the bug you reported is fixed in the latest version of
uncrustify, 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 867376@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov <gq@debian.org> (supplier of updated uncrustify 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)
Format: 1.8
Date: Thu, 31 Aug 2017 20:25:06 +0300
Source: uncrustify
Binary: uncrustify
Architecture: source amd64
Version: 0.65+git20170831+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov <gq@debian.org>
Changed-By: Alexander GQ Gerasiov <gq@debian.org>
Description:
 uncrustify - C, C++, C#, D, Java and Pawn source code beautifier
Closes: 867376
Changes:
 uncrustify (0.65+git20170831+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 0.65+git20170831 (Closes: #867376)
   * Bump Standards-Version to 4.1.0 (no additional changes needed).
Checksums-Sha1:
 150d4f10a865daf61397dfc013bfea9574468b31 1744 uncrustify_0.65+git20170831+dfsg1-1.dsc
 5a03e72f4650b37a5989a797f8a36619b9db77bd 708124 uncrustify_0.65+git20170831+dfsg1.orig.tar.xz
 0c8bf4f5333c5179a1feae946c7b9a3a2ca9403a 4236 uncrustify_0.65+git20170831+dfsg1-1.debian.tar.xz
 43ba170fbbdfff511b488b49c0e0bf98765edaf2 2042572 uncrustify-dbgsym_0.65+git20170831+dfsg1-1_amd64.deb
 09f5e626a63cc505a158fc046bce1c4c6def7b0f 6613 uncrustify_0.65+git20170831+dfsg1-1_amd64.buildinfo
 8f55e022dabe3b4d63a7a328844a9d73d080b34d 399674 uncrustify_0.65+git20170831+dfsg1-1_amd64.deb
Checksums-Sha256:
 6cc2450790b5a17471b540d02d52fd7aeb8773b84ad00ffb826ceeebb7faa51a 1744 uncrustify_0.65+git20170831+dfsg1-1.dsc
 ad57d8467cd6b4370046b7b7c73e93a0326e3f07826fbc231fc41246bc0c3ab7 708124 uncrustify_0.65+git20170831+dfsg1.orig.tar.xz
 06263647bc07993d9c2ac18d2d91a467a0c1e79daed952f79addfb531921f929 4236 uncrustify_0.65+git20170831+dfsg1-1.debian.tar.xz
 006848642de6271c2e28b5c0967f417520ff6b87add55f175baa788413ddfdd2 2042572 uncrustify-dbgsym_0.65+git20170831+dfsg1-1_amd64.deb
 4aa0c9c33e614ddb409448d8fa1ecc7ab7d3e85b6d7b05598908e9200be7bca5 6613 uncrustify_0.65+git20170831+dfsg1-1_amd64.buildinfo
 5150389df4d0f924645c59239cc80da5105551dff51488ebe858529d74a184e8 399674 uncrustify_0.65+git20170831+dfsg1-1_amd64.deb
Files:
 b0755a0385dcd08a5f31edc40a0ac50a 1744 devel optional uncrustify_0.65+git20170831+dfsg1-1.dsc
 b1e563ff276e8e6187307260fd01a8cc 708124 devel optional uncrustify_0.65+git20170831+dfsg1.orig.tar.xz
 f7d03a9ccee445054a3d703df1c73767 4236 devel optional uncrustify_0.65+git20170831+dfsg1-1.debian.tar.xz
 5d0d671177dcb34f950598dae85cd0d8 2042572 debug extra uncrustify-dbgsym_0.65+git20170831+dfsg1-1_amd64.deb
 78ea064f870248c929546bc6fa43655f 6613 devel optional uncrustify_0.65+git20170831+dfsg1-1_amd64.buildinfo
 3134929ddb64eaef1c340646fce475d5 399674 devel optional uncrustify_0.65+git20170831+dfsg1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----

iQFCBAEBCAAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAlmoSCcOHGdxQGRlYmlh
bi5vcmcACgkQyofp6CqsM/HoZAf/WkXRZ+OkTXBSSWyWSNvD/nSSQeGpnrOgpzdl
dPDsZxVOx3kJAJ8aRgIefr5gA6bljT37ihehTk+s+URN5n2BLle3rFSJ88jw0abC
Wnp6Lk4ENdwxg8cxxWuLHJ0axhCT/f5/4HLJG+j23QqVVLF9t8nqxOjWhZ/lBBRh
jMwlu5gLZQDTJhwDfMwWC8wizTJGM/RiHdt/EnAfm8TjfbxtPrd9wB1wmJqMLKUU
exLlbwfEBerEhLFwNkEbw8YXIlG2yRz5ljPfNFwv99x5GbnBIXXhCHiuuJoyS09I
DPkbCo5WcjZ6Ov4B+63AGMXBcRCi6FvyqBU/gBsQAQK1KK3sMw==
=2Sd2
-----END PGP SIGNATURE-----

Control: reopen -1

This bug was not a request for packaging a new upstream version, so this
changelog entry isn't appropriate.

Cheers,
Julien

Hello Julien,
Could you please explain your point?

There was several bugs in upstream code which leads to incorrect
behavior on some architectures.
We have fixed them in current upstream code, and current upstream
version was uploaded into archive. This really fixes #867376, you can
see this on https://buildd.debian.org/status/package.php?p=uncrustify

What I mean is that when closing bugs in your changelog entry, it should
actually describe what fixes the bug.  So "New upstream release (closes:
#nnn)" implies that #nnn was about packaging a new upstream release.
"Fix vanilla flavor to not taste like chocolate (closes: #mmm)" implies
that #mmm is about something being wrong with the vanilla flavor of ice
cream.

See also
https://www.debian.org/doc/manuals/developers-reference/ch06.en.html#bpp-changelog-do

Cheers,
Julien

Hello Julien,

On Fri, 1 Sep 2017 17:53:03 +0200 Julien Cristau <jcristau@debian.org> wrote:
Ah, totally lost this mail, so reply just now.

In generally I agree with you, that changelog should be meaningful.
But in this case you're wrong (from my point of view).

We have sigfault in the app.
User reports "%appname segfault when %something"
I look through the code and see pointer dereference, so I create commit
not with "Fix sigfault", but with "Do some checks on pointer
dereference when ... This should fix #issuenumber".

Or may be you mean, that I should write
"New upstream release. Fixes disk overflow on some archs. (Closes:
#number)" There is some good point in this, I agree, but still no
reason to reopen the bug, I think. =)

Yes, that's what I meant.  Thanks.

Cheers,
Julien