Bug 1020206 - shar usage output is missing final line-feed
Summary: shar usage output is missing final line-feed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sharutils
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL: http://permalink.gmane.org/gmane.comp...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 09:37 UTC by Petr Pisar
Modified: 2014-03-24 07:51 UTC (History)
1 user (show)

Fixed In Version: sharutils-4.13.3-6.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1020287 (view as bug list)
Environment:
Last Closed: 2014-03-24 07:51:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Pisar 2013-10-17 09:37:19 UTC
Te `shar --help' output is missing final new line:

$ rpm -q sharutils
sharutils-4.13.3-4.fc19.x86_64
petr@dhcp-0-146:~/fedora/sharutils $ LC_ALL=en_US.UTF-8 shar --help | tail -n 1
please send bug reports to:  bug-gnu-utils@dhcp-0-146:~/fedora/sharutils $

Only Fedora 19 is affected, fixed in sharutils-4.13.4.

Comment 1 Fedora Update System 2013-10-17 11:40:03 UTC
sharutils-4.13.3-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/sharutils-4.13.3-5.fc19

Comment 2 Fedora Update System 2013-10-30 01:58:09 UTC
sharutils-4.13.3-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 3 Petr Pisar 2014-03-04 15:02:27 UTC
The fix is wrong. I will apply better one.

Comment 4 Fedora Update System 2014-03-04 15:28:30 UTC
sharutils-4.13.3-6.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/sharutils-4.13.3-6.fc19

Comment 5 Fedora Update System 2014-03-13 05:04:41 UTC
sharutils-4.13.3-6.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.