Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1764123 - Make the package available for Fedora 30
Summary: Make the package available for Fedora 30
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: golang-x-xerrors
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert-André Mauchin 🐧
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-22 09:45 UTC by Maciek Borzecki
Modified: 2020-05-26 18:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:02:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Maciek Borzecki 2019-10-22 09:45:53 UTC 
Description of problem:

golang-x-xerrors is currently only available for Fedora 31 and Rawhide. With the next release of snapd, we'd like to start using the package internally.

Additional info:

I have prepared a commit with an update to the spec so that it builds on F30. The relevant commit is right here in my fork: https://src.fedoraproject.org/fork/bboozzoo/rpms/golang-x-xerrors/c/ddd8489cad5035a3ad33fc5852fbb81aa5ae9224?branch=bboozzoo%2Ff30

The scratch build was successful as well: https://koji.fedoraproject.org/koji/taskinfo?taskID=38462437
Comment 1 Fedora Update System 2019-12-14 11:02:10 UTC 
FEDORA-2019-f1e35483d5 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f1e35483d5
Comment 2 Maciek Borzecki 2019-12-14 16:13:17 UTC 
Thank you!
Comment 3 Fedora Update System 2019-12-15 01:41:00 UTC 
golang-x-xerrors-0-0.1.20190916gita985d34.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f1e35483d5
Comment 4 Ben Cotton 2020-04-30 20:37:57 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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 30 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 5 Ben Cotton 2020-05-26 18:02:15 UTC 
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.