Bug 1706169 - Expletive words found in package names
Summary: Expletive words found in package names
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-repos
Version: 29
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-03 17:30 UTC by jeffj1101
Modified: 2019-05-03 18:17 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-03 18:17:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screen grab (98.81 KB, image/png)
2019-05-03 17:30 UTC, jeffj1101
no flags Details

Description jeffj1101 2019-05-03 17:30:06 UTC
Created attachment 1562619 [details]
Screen grab

Description of problem:

Searching for steam on dnf, amongst the results, I saw this:


python2-fuckit.noarch : The Python Error Steamroller
python3-fuckit.noarch : The Python Error Steamroller

I think the use of expletives should be removed from packaging as this is seen as unprofessional and could result in uncomfortable situations in the workplace. 
These packages are part of the 'fedora' repo. 


Version-Release number of selected component (if applicable):
Fedora 29 


How reproducible:
Everytime 

Steps to Reproduce:
1.Open terminal
2.Do 'dnf search steam'
3.Observe the results

Actual results:

Result include packages with profanity in it. I.e. 

the words 'fuck'. 

Expected results:

A less profane package names. e.g. 

python2-fixit.noarch : The Python Error Steamroller
python3-fixit.noarch : The Python Error Steamroller

Additional info:

Comment 1 Peter Robinson 2019-05-03 18:17:46 UTC
I don't believe it's in violation of the packaging guidelines and should probably be taken to the Fedora Packaging Committee or FESCo (Fedora Engineering Steering Committe, it can't be resolved in this bug as the fedora-repos package is purely for fedora repository configuration data so it's not actually a bug in a package per se but a policy decision which can't be solved here.


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