[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#807789: RFS: 4ti2/1.6.7+ds-1 [New Upstream Release]



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

Hello Mattia:

On 13/12/15 03:19, Mattia Rizzolo wrote:
> control: owner -1 !
> control: tag -1 + pending
> 
> Hi,
> 
> On Sun, Dec 13, 2015 at 02:48:24AM +0100, Jerome Benoit wrote:
>> 	I am looking for a sponsor for the package 4ti2 [1] that
>>  	I am maintaining on behalf of the Debian Science-Team.
>> 	This version is a `New upstream release' that fixes a broken
>> 	test and some cosmetic issues.
> 
> I'm currently building it, and if it will I'll upload it as-is, but I
> have a couple of question for you nontheless:
> 
> * why don't you try to use the git repository in a sane way?  just
>   importing .dsc you build somehow else is not really a good use of it,

It is why I do NOT import dsc material, but I use the same kind of message.
And I group the git-commit to avoid numerous ones.


>   you lost a lot of benefith of git and makes unnecessarily hard for
>   sponsors to review the changes (=> I couldn't use it at all...)
> * I guess
>         - debian/{patches,adhoc}/*:
>           - test walk 344, revive;

In the previous package version, the test named walk failed over a sample input data file
with generic name 344: it was frozen and I sent a report to the upstream maintainer team,
along other minor reports.
This version of 4ti2 mainly fixed the reported issues, see the (upstream) NEWS file for
more details. So I unfrozen this test and I performed some minor changes in the debian
material to reflect the fixes brought by the upstream team. Those changes are minor
in the sense that they mainly concern maintenance, but not end users.


>           - refresh.
>   means something to you, but pretty sure it does mean nothing to me,
>   especially the "test walk 344, revive" line.  At least for the patches
>   next time can you try to be more verbose on what you did?  what you
>   added, what you dropped and why.
> 

I try to be concise. I guess that what you mean is that I should git-commit more often.


Thanks,
Jerome
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWbNykAAoJEIC/w4IMSybj1zwH/1npmQv7jLv/HI8j9ISWDRIP
RZhBiKbpn3EGvD6wZX9Wy04p1o44AXuTM4XcsEbl/ex5C3GWKqWHhmDHc73FTgNX
MxII9xUQ4cdtCuezYCfGM0tsNBvUVpOaHIE4FjZcnz3oJSVyBi5U7quuf+YwXqkF
M55J6r7X1OeyXU9QyLH0zuJyhoxPpLXspdXRQKZIKsTgUkInu4s4h4GJABGQqyiJ
z/1EAkOP4Eop1E+j5xWWS1xUsReih9GFWMs3BWDf6iHZk0UNUz1dkxnhI09R8rb7
KWComjv3wnxSfTkX/hQqQ7PCb9LsvIlYYs2cw4WHb6khJ7wR2qmvcbJ6Nzlb0WI=
=yoZf
-----END PGP SIGNATURE-----


Reply to: