Bug 1823915 - Method to configure %description section in the %gopkg macro
Summary: Method to configure %description section in the %gopkg macro
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-14 19:14 UTC by Brandon Perkins
Modified: 2020-11-24 18:17 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 18:17:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brandon Perkins 2020-04-14 19:14:05 UTC
Description of problem:
Doing a package review, rpmlint is giving us the error:

golang-github-haproxytech-dataplaneapi-debugsource.x86_64: E: description-line-too-long C This package provides debug sources for package golang-github-haproxytech-dataplaneapi.

which is true:

$ echo -n "This package provides debug sources for package golang-github-haproxytech-dataplaneapi." | wc -c
87

Request is a method to either override the description block or change the format so that the package name is on it's own line.


Version-Release number of selected component (if applicable):
go-rpm-macros-3.0.8-4.fc31


How reproducible:
Always.


Steps to Reproduce:
1. $ /usr/bin/fedora-review -b 1773720
2. $ grep description-line-too-long 1773720-golang-github-haproxytech-dataplaneapi/review.txt 


Actual results:
golang-github-haproxytech-dataplaneapi-debugsource.x86_64: E: description-line-too-long C This package provides debug sources for package golang-github-haproxytech-dataplaneapi.
golang-github-haproxytech-dataplaneapi-debugsource.x86_64: E: description-line-too-long C This package provides debug sources for package golang-github-haproxytech-dataplaneapi.


Expected results:
No error.


Additional info:

Comment 1 Nicolas Mailhot 2020-04-20 09:18:20 UTC
This subpackage is not created by go-rpm-macros, it’s part of the generic Fedora macros (in redhat-rpm-config IIRC)

The debugsource macros should just change line before the package name (that will work as long as no upstream chooses a line-length project name)

Comment 2 Ben Cotton 2020-11-03 16:36:22 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 3 Ben Cotton 2020-11-24 18:17:16 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.