[Bug 211262] Re: Change in cut behavior breaks scripts

[Launchpad Bug Tracker]

[Expired for xen-common (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xen-common (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/211262

Title:
  Change in cut behavior breaks scripts

Status in “coreutils” package in Ubuntu:
  Invalid
Status in “xen-common” package in Ubuntu:
  Expired
Status in “coreutils” source package in Hardy:
  Won't Fix
Status in “xen-common” source package in Hardy:
  Invalid

Bug description:
  Binary package hint: coreutils

  When given a 0 field in cut it used to just treat it as 1; now it
  reports an error.

  Old behavior (Gutsy):

  $ echo foobar | cut -c0-3
  foo

  New behavior (Hardy):

  $ echo foobar | cut -c0-3
  cut: fields and positions are numbered from 1
  Try `cut --help' for more information.
  bash: echo: write error: Broken pipe

  I wouldn't say this is a bug but it will cause problems elsewhere.  I
  noticed the problem in the /etc/init.d/xendomains script.  Treating 0
  as 1 is really harmless so leaving the old behavior doesn't seem to
  present a problem.  If the new behavior remains it might be worth
  trying to find places where it causes problems and fix them prior to
  the release of Hardy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/211262/+subscriptions