Bug 2105093 - prometheus package does not follow naming guidelines
Summary: prometheus package does not follow naming guidelines
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: golang-github-prometheus
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Mark E. Fuller
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-07 21:52 UTC by nilskemail
Modified: 2023-08-16 08:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:20:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description nilskemail 2022-07-07 21:52:31 UTC
Description of problem:

The package containing the popular prometheus monitoring tool is namen golang-github-prometheus. However the packaging/naming guidelines explicitly state the following:

"Source packages that provide a well-known application such as etcd MUST be named after the application. End users do not care about the language their applications are written in. But do not name packages after an obscure utility binary that happens to be built by the package."

(Capitalization of "MUST" was NOT added by me.)
The current name is rather confusing and makes this package hard to find.
There is no double that prometheus falls into the category of such well known packages given the popularity in enterprise deployments for monitoring.

Additional info:

* Guidelines:
  https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/#_source_packages_src_rpm
* Bug to track packages which are not following packaging guidelines (though no recent activity there)
  https://bugzilla.redhat.com/show_bug.cgi?id=1731683

Comment 1 Ben Cotton 2023-04-25 17:34:15 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ludek Smid 2023-05-25 19:20:25 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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

Comment 3 Fedora Admin user for bugzilla script actions 2023-06-11 00:40:03 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Fedora Admin user for bugzilla script actions 2023-06-23 00:15:20 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Fedora Release Engineering 2023-08-16 08:08:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


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