Bug 1146969 - parallel spams stderr every time it is run
Summary: parallel spams stderr every time it is run
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: parallel
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Golo Fuchert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-26 13:18 UTC by David Shea
Modified: 2019-11-27 19:05 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:05:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
remove citation notice (1.29 KB, patch)
2014-09-26 13:18 UTC, David Shea
no flags Details | Diff

Description David Shea 2014-09-26 13:18:02 UTC
Created attachment 941566 [details]
remove citation notice

Description of problem:
When I run parallel, the first thing it outputs it this:

When using programs that use GNU Parallel to process data for publication please cite:

  O. Tange (2011): GNU Parallel - The Command-Line Power Tool,
  ;login: The USENIX Magazine, February 2011:42-47.

This helps funding further development; and it won't cost you a cent.

To silence this citation notice run 'parallel --bibtex' once or use '--no-notice'.


This is completely inappropriate for a non-interactive program, especially one that lends itself to running scripts that are parsed by other programs. Running with --no-notice is obviously an option, but that would cause all scripts that use parallel to depend on a particular version of parallel (for example, the version in F20 rejects this option). Expecting every environment to run parallel --bibtex is infeasible, and also creates a restriction on usage by requiring the user to agree to the terms of citing parallel in publications.

Please remove the citation notice from parallel.

Attached a patch to remove the notice but keeps the --no-notice and --bibtex options intact for compatibility.

Version-Release number of selected component (if applicable):
parallel-20131222-3.fc21.noarch

Comment 1 Golo Fuchert 2014-12-03 22:59:18 UTC
Hi,

I'm sorry you had to wait so long for an answer, I've been very busy for the last months.
I agree that this behavior seems annoying for a non-interactive program. If we find no other solution we may patch parallel. Of course it would be preferable if there would be no need to do that. You say that running parallel --no-notice would not be an option, since scripts would be version depending then. However, what would be wrong with simply putting "--no-notice" in the global config file /etc/parallel/config and ship that with the package? That way user scripts would not have to invoke parallel --no-notice and would stay portable. For me that sounds like a feasible solution, don't you agree?

Comment 2 Jaroslav Reznik 2015-03-03 17:04:10 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora End Of Life 2016-07-19 12:09:58 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Martin Kolman 2018-06-07 11:41:19 UTC
Still valid in F28/Rawhide.

Comment 5 Jan Kurik 2018-08-14 10:24:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 6 Ben Cotton 2019-10-31 20:51:15 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 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 Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2019-11-27 19:05:38 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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