[Touch-packages] [Bug 1799868] Re: seq command has problems near its max integer

2018-11-01 Thread C de-Avillez
Closing INVALID, then, given this is a known, documented limitation. ** Changed in: coreutils (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu.

Re: [Touch-packages] [Bug 1799868] Re: seq command has problems near its max integer

2018-11-01 Thread Kevin O'Gorman
I dont usually read info pages since I have trouble navigating them. But reading what you quoted made clear what happened. I would personally have preferred it if seq would notice when the increment is not doing anything, and instead of producing infinite output, complained and quit as it does

[Touch-packages] [Bug 1799868] Re: seq command has problems near its max integer

2018-10-29 Thread C de-Avillez
Hello Kevin, and thank you for opening this bug and helping make Ubuntu better. The info page for seq (info seq) has the following note: " On most systems, seq can produce whole-number output for values up to at least 2^{53}. Larger integers are approximated. The details differ depending on

[Touch-packages] [Bug 1799868] Re: seq command has problems near its max integer

2018-10-24 Thread Kevin O'Gorman
It's worse than I thought. Increments of 2 fail even when aa factor of 100 away from the limit: kevin@plato-x:~$ seq 170141183460469231731687303715884105721 1 170141183460469231731687303715884105725 | head -10 170141183460469231731687303715884105721 170141183460469231731687303715884105722