Regression: seq -s broken

Bug #1199878 reported by Stephan Diestelhorst
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
coreutils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The 'seq' command is broken 8.13 -> 8.20.

VERSION="13.04, Raring Ringtail"
$> apt-cache policy coreutils
coreutils:
  Installed: 8.20-3ubuntu5
  Candidate: 8.20-3ubuntu5
  Version table:
 *** 8.20-3ubuntu5 0
        500 http://ch.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status
$> seq -s ' ' 0 7
0

VERSION="12.04.2 LTS, Precise Pangolin"
>$ apt-cache policy coreutils
coreutils:
  Installed: 8.13-3ubuntu3.2
  Candidate: 8.13-3ubuntu3.2
  Version table:
 *** 8.13-3ubuntu3.2 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     8.13-3ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
$> seq -s' ' 0 7
0 1 2 3 4 5 6 7

Revision history for this message
Stephan Diestelhorst (syon) wrote :

Just looking at this some more. The expected behaviour is (with marked new lines):

$> seq -s " " 0 7
"0 1 2 3 4 5 6 7\n"

Broken behaviour:
$> seq -s " " 0 7
"0\n1 2 3 4 5 6 7"

Going to bisect upstream. Seems a silly bug to me.

Revision history for this message
Stephan Diestelhorst (syon) wrote :

This has been fixed upstream with coreutils 8.21, and is acknowledged as a regression introduced with 8.20. I would suggest to update the package, what is the process to request an update?

http://lists.gnu.org/archive/html/coreutils-announce/2013-02/msg00000.html

tags: added: raring
Changed in coreutils (Ubuntu):
status: New → Confirmed
Revision history for this message
Stephan Diestelhorst (syon) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.