[Touch-packages] [Bug 1769941] Re: grep fails to match an empty line using perl regexp if it's the last line in a file
I can't identify when it was fixed, but can confirm this is not happening any more in grep 3.1-2build1 in Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1769941 Title: grep fails to match an empty line using perl regexp if it's the last line in a file Status in grep package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center grep: Installed: 2.25-1~16.04.1 Candidate: 2.25-1~16.04.1 Version table: *** 2.25-1~16.04.1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.24-1 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen (echo 123; echo; ) | grep -P '^$' $ # output contains one empty line $ (echo 123; echo;) | grep -P '^$' $ 4) What happened instead $ # output contains no line $ (echo 123; echo;) | grep -P '^$' $ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: grep 2.25-1~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 18:49:45 2018 InstallationDate: Installed on 2018-02-13 (83 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: grep UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1769941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1113597] Re: --rsyncable option not documented in man page
Thanks for reporting this. This was fixed back in gzip version 1.6-1, and the oldest version of gzip in a supported version of Ubuntu is 1.6-3ubuntu1. Closing! ** Bug watch added: Debian Bug tracker #688305 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688305 ** Also affects: gzip (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688305 Importance: Unknown Status: Unknown ** Changed in: gzip (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1113597 Title: --rsyncable option not documented in man page Status in gzip package in Ubuntu: Fix Released Status in gzip package in Debian: Unknown Bug description: ## Package Information Description: Ubuntu 12.10 Release: 12.10 gzip/quantal uptodate 1.5-1.1ubuntu1 ## Bug Description `man 1 gzip` does not contain any information about the `--rsyncable` option. However, the output of `gzip -h` explains the option as follows: --rsyncable Make rsync-friendly archive The option should be documented in the man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1113597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1168049] Re: gunzip ignores 'n' when asked to overwrite file
Fixed in gzip 1.6-1. Oldest version in a supported version of Ubuntu is 1.6-3ubuntu1 (in Trusty). ** Changed in: gzip (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1168049 Title: gunzip ignores 'n' when asked to overwrite file Status in gzip package in Ubuntu: Fix Released Status in gzip package in Debian: Unknown Bug description: Steps to repro: % echo overwritten > test % gzip test % echo clean > test % cat test clean % gunzip test.gz gzip: test already exists; do you wish to overwrite (y or n)? n % cat test overwritten % This bug seems to have been reported in several other places as a compiler optimization bug (saw one reference to GCC 4.7 x86-64 -O2). It's possible that it's been fixed in upstream already. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gzip 1.5-1.1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Apr 11 12:45:38 2013 InstallationDate: Installed on 2012-04-13 (363 days ago) InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: gzip UpgradeStatus: Upgraded to quantal on 2012-11-09 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1168049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1168049] Re: gunzip ignores 'n' when asked to overwrite file
** Bug watch added: Debian Bug tracker #704689 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704689 ** Also affects: gzip (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704689 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1168049 Title: gunzip ignores 'n' when asked to overwrite file Status in gzip package in Ubuntu: Fix Released Status in gzip package in Debian: Unknown Bug description: Steps to repro: % echo overwritten > test % gzip test % echo clean > test % cat test clean % gunzip test.gz gzip: test already exists; do you wish to overwrite (y or n)? n % cat test overwritten % This bug seems to have been reported in several other places as a compiler optimization bug (saw one reference to GCC 4.7 x86-64 -O2). It's possible that it's been fixed in upstream already. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gzip 1.5-1.1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Apr 11 12:45:38 2013 InstallationDate: Installed on 2012-04-13 (363 days ago) InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: gzip UpgradeStatus: Upgraded to quantal on 2012-11-09 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1168049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 91175] Re: cut gets confused with UTF-8 characters
*** This bug is a duplicate of bug 875713 *** https://bugs.launchpad.net/bugs/875713 ** This bug has been marked a duplicate of bug 875713 cut fails to handle correctly utf-8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/91175 Title: cut gets confused with UTF-8 characters Status in coreutils package in Ubuntu: Triaged Bug description: Binary package hint: coreutils GNU cut gets confused about character boundaries with UTF-8 encoded files. An example, as they (almost) say, is worth a thousand words: nslater@hinata: ~ $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= nslater@hinata: ~ $ cat foo.txt She said “I think I found a bug.” nslater@hinata: ~ $ cat foo.txt | cut --characters 10- “I think I found a bug.” nslater@hinata: ~ $ cat foo.txt | cut --characters 11- ��I think I found a bug.” nslater@hinata: ~ $ cat foo.txt | cut --characters 12- �I think I found a bug.” nslater@hinata: ~ $ cat foo.txt | cut --characters 13- I think I found a bug.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/91175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414316] Re: cut() does not handle unicode properly
*** This bug is a duplicate of bug 875713 *** https://bugs.launchpad.net/bugs/875713 ** This bug has been marked a duplicate of bug 875713 cut fails to handle correctly utf-8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1414316 Title: cut() does not handle unicode properly Status in coreutils package in Ubuntu: New Bug description: Hi, $ echo 哈哈 哈哈 $ echo 哈哈 | cut -c 2- ��哈 Apparently, Red Hat patched this in or before FC15. http://unix.stackexchange.com/questions/15961/coreutils-that-are-utf-aware [patches@holocene ~]$ rpm -q coreutils coreutils-8.10-2.fc15.x86_64 [patches@holocene ~]$ echo 哈哈 | cut -c 2- 哈 The patch is here: http://pkgs.fedoraproject.org/cgit/coreutils.git/tree/coreutils- i18n.patch?id=6e10f376996b64f538259091a524df2249b653fb;id2=HEAD ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: coreutils 8.21-1ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 24 10:06:25 2015 InstallationDate: Installed on 2013-05-22 (611 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) SourcePackage: coreutils UpgradeStatus: Upgraded to trusty on 2015-01-04 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1414316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1179487] Re: wrong output of command /usr/bin/seq
Upstream bug (marked "Done") shows this is a bug in coreutils 8.20: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13227 Since the affected version of coreutils is no longer in a supported release of Ubuntu, I'm marking this bug as Fix Released. Thanks! ** Changed in: coreutils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1179487 Title: wrong output of command /usr/bin/seq Status in coreutils package in Ubuntu: Fix Released Bug description: The command seq return wrong output when parameter -s is used $ seq --help ... -s, --separator=STRING use STRING to separate numbers (default: \n) ... Example: On Ubuntu (wrong): $ /usr/bin/seq -s , 10 1 2,3,4,5,6,7,8,9,10, On Debian (all right): $ /usr/bin/seq -s , 10 1,2,3,4,5,6,7,8,9,10 More info: $ lsb_release -rd Description:Ubuntu 13.04 Release:13.04 $ dpkg -l coreutils ii coreutils 8.20-3ubuntu5 amd64GNU core utilities ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: coreutils 8.20-3ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon May 13 14:27:36 2013 MarkForUpload: True SourcePackage: coreutils UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1179487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997093] Re: stat does not display ext4 crtime
** Bug watch added: Debian Bug tracker #793831 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793831 ** Also affects: coreutils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793831 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/997093 Title: stat does not display ext4 crtime Status in coreutils package in Ubuntu: Confirmed Status in coreutils package in Debian: Unknown Bug description: This is an Oneiric install which was upgraded to Precise. -(cmsj@kiryo)-(~)- mount | head -1 /dev/sda1 on / type ext4 (rw,noatime,errors=remount-ro) Note that / is mounted as ext4 -(cmsj@kiryo)-(~)- rm /tmp/statlol -(cmsj@kiryo)-(~)- date Wed May 9 13:50:18 BST 2012 -(cmsj@kiryo)-(~)- touch /tmp/statlol -(cmsj@kiryo)-(~)- stat -c "%w" /tmp/statlol - This should have shown the current time as the "birth" time of the file. -(cmsj@kiryo)-(~)- stat /tmp/statlol File: `/tmp/statlol' Size: 0 Blocks: 0 IO Block: 4096 regular empty file Device: 801h/2049dInode: 396056 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/cmsj) Gid: ( 1000/cmsj) Access: 2012-05-09 13:50:21.927574000 +0100 Modify: 2012-05-09 13:50:21.927574000 +0100 Change: 2012-05-09 13:50:21.927574000 +0100 Birth: - Full stat output shows that all other time fields are shown, but "Birth" (crtime) is not. -(cmsj@kiryo)-(~)- sudo debugfs -R 'stat /tmp/statlol' /dev/sda1 Inode: 396056 Type: regularMode: 0664 Flags: 0x8 Generation: 4155105282Version: 0x:0001 User: 1000 Group: 1000 Size: 0 File ACL: 0Directory ACL: 0 Links: 1 Blockcount: 0 Fragment: Address: 0Number: 0Size: 0 ctime: 0x4faa680d:dd269fc0 -- Wed May 9 13:50:21 2012 atime: 0x4faa680d:dd269fc0 -- Wed May 9 13:50:21 2012 mtime: 0x4faa680d:dd269fc0 -- Wed May 9 13:50:21 2012 crtime: 0x4faa680d:dd269fc0 -- Wed May 9 13:50:21 2012 Size of extra inode fields: 28 EXTENTS: -(cmsj@kiryo)-(~)- Calling stat() directly with debugfs shows that crtime is indeed populated correctly, which suggests that coreutils' stat(1) is not able to display it correctly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: coreutils 8.13-3ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu6 Architecture: i386 Date: Wed May 9 13:49:31 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: Upgraded to precise on 2012-04-11 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/997093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1169580] Re: "tail -f file" with "mv file file2" does not show changes to file2
Upstream bug (marked "Done") is at http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19760 ** Changed in: coreutils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1169580 Title: "tail -f file" with "mv file file2" does not show changes to file2 Status in coreutils package in Ubuntu: Confirmed Bug description: The manual page of tail states the following: With --follow (-f), tail defaults to following the file descriptor, which means that even if a tail'ed file is renamed, tail will continue to track its end. However, the following command sequence does not behave like that: touch file tail -f file & mv file file2 echo "text" >> file2 In this case, tail does not show any output. However, tail shows the "text" properly when run on a Solaris server. This indicates that tail does behave like its manual page states in some versions. System version: Ubuntu 12.04.2 LTS touch version: touch (GNU coreutils) 8.13 tail version: tail (GNU coreutils) 8.13 mv version: mv (GNU coreutils) 8.13 bash version: GNU bash, version 4.2.24(1)-release (x86_64-pc-linux-gnu) On the Solaris server that behaves correctly, each are '(GNU coreutils) 6.7' except bash which is 'GNU bash, version 3.2.25(1)-release (sparc-sun-solaris2.11)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1169580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 289535] Re: date returns the wrong day (DST problem?)
This bug was fixed many years ago, although it seems it wasn't backported to Dapper. Closing as Fix Released. ** Changed in: coreutils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/289535 Title: date returns the wrong day (DST problem?) Status in coreutils package in Ubuntu: Fix Released Bug description: Binary package hint: coreutils In Dapper, the "+1 week" relative time specification seems to be wrong. ~$ date Sun Oct 26 12:39:09 EDT 2008 ~$ date --date="next Saturday" Sat Nov 1 00:00:00 EDT 2008 ~$ date --date="next Saturday + 1 week" Fri Nov 7 23:00:00 EST 2008 However, the same commands return the correct information on a Hardy machine: ~$ date Sun Oct 26 12:41:27 EDT 2008 ~$ date --date="next Saturday" Sat Nov 1 00:00:00 EDT 2008 $ date --date="next Saturday + 1 week" Sat Nov 8 00:00:00 EST 2008 So it looks like something that has been fixed upstream. Could the fix be included in Dapper? It bit me pretty badly this week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/289535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
