[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I cannot reproduce this.
Is this still an issue for you? Which Ubuntu version do you use? Thank
you for telling us!
** Changed in: xen-common (Ubuntu Hardy)
Status: New => Invalid
** Changed in: xen-common (Ubuntu)
Status: New => Confirmed
** Changed in: xen-common (Ubuntu)
** Changed in: xen-common (Ubuntu)
Importance: Undecided => Low
--
Change in cut behavior breaks scripts
https://bugs.launchpad.net/bugs/211262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
My note above should by qualified by stating that behavior obtained with
"-f,4" in previous versions of cut are the same as "-f4" in old and new
versions of cut.
--
Change in cut behavior breaks scripts
https://bugs.launchpad.net/bugs/211262
You received this bug notification because you are a me
I agree, this change in behavior will affect third party scripts that
were written for generic flavors of Linux. Although the old behavior may
not have been "correct" it was accepted and widely used. I'd also like
to point out that the behavior of -f was changed as well.
This was discovered while
Not a bug in coreutils, marking as such.
Agreed that this should be fixed in any affected scripts for hardy;
which should be a relatively small number, so far only the xen scripts
seem to assume a 0 index is valid.
** Changed in: coreutils (Ubuntu Hardy)
Status: New => Won't Fix
** Change
