Simon Spero commented on COMPRESS-411:

The mailing list suffers from the billions of duplicated emails from jira
vs github (featuring coveralls).
Wait  - I think I see your point. The volume is such that I have missed
important emails that need reply (eg I need to reply to an email of yours
about how users would identify versions to report in OSGI situations (it
really needs illustration from Kafka /Felix (which in turn requires a faux
compress to add multi versions, and multi issues.)

The conclusolory statement that "its not a problem" is not helpful. Showing
what would be sent is.
The real confusion comes from bad declarations ; other issues comes from
failed resolution. This former can be pom tracing hell ; the latter is
interpreting constraint satisfaction problem errors. Both get better with
more precise versions :) But that's just me saying that.

> TarUtils.formatLongOctalOrBinaryBytes never uses result of formatLongBinary
> ---------------------------------------------------------------------------
>                 Key: COMPRESS-411
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-411
>             Project: Commons Compress
>          Issue Type: Bug
>          Components: Archivers
>    Affects Versions: 1.14
>            Reporter: Simon Spero
>            Priority: Minor
>             Fix For: 1.15
> if the length < 9, formatLongBinary is executed, then overwritten by the 
> results of formatBigIntegerBinary. 
> If the results are not ignored, a unit test would fail.
> Also, do the binary hacks  need to support negative numbers? 

This message was sent by Atlassian JIRA

Reply via email to