Description of problem: The split command does not accept anymore suffix with a length of 2 while it was the default and still written as being so in the man page. Version-Release number of selected component (if applicable): coreutils_8.8-2.mga1 How reproducible: Always Steps to Reproduce: split -a 2 -b 10K /usr/bin/split split_ split: the suffix length needs to be at least 3 split -b 10K /usr/bin/split split_ This will create : -rw-r--r-- 1 eric users 10240 déc. 3 20:12 split_aaa -rw-r--r-- 1 eric users 10240 déc. 3 20:12 split_aab -rw-r--r-- 1 eric users 10240 déc. 3 20:12 split_aac -rw-r--r-- 1 eric users 10240 déc. 3 20:12 split_aad -rw-r--r-- 1 eric users 10240 déc. 3 20:12 split_aae -rw-r--r-- 1 eric users 7880 déc. 3 20:12 split_aaf instead of : split_aa ... split_af Take a 345Mb file : -rw-r--r-- 1 eric users 344707084 déc. 3 17:42 Softs.tar.bz2.gpg split -b 240M Softs.tar.bz2.gpg Softs.tar.bz2.gpg_ This will create : -rw-r--r-- 1 eric users 251658240 déc. 3 17:45 Softs.tar.bz2.gpg_aaaaaa -rw-r--r-- 1 eric users 93048844 déc. 3 17:46 Softs.tar.bz2.gpg_aaaaab Instead of Softs.tar.bz2.gpg_aa and Softs.tar.bz2.gpg_ab
You should report this bug upstream. (and post the link here) http://www.gnu.org/software/coreutils/
Keywords: (none) => UPSTREAMSource RPM: (none) => coreutils
Hi, I 've just sent a bug report to coreutils. I don't know yet if it will be accepted (nor its bug number). Regards. Xuo.
Hi, I have received this mail (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10214). Can the patch be included in the next coreutils update ? Regards. Xuo.
(In reply to comment #3) > Hi, > > I have received this mail (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10214). > Can the patch be included in the next coreutils update ? > > Regards. > > Xuo. tmb is it possible ?
Keywords: (none) => PATCH, TriagedURL: (none) => http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10214Assignee: bugsquad => tmb
(In reply to comment #4) > (In reply to comment #3) > > Hi, > > > > I have received this mail (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10214). > > Can the patch be included in the next coreutils update ? > > > > Regards. > > > > Xuo. > > tmb is it possible ? Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ tmb Please set status to ASSIGNED, if possible
CC: (none) => marja11
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX