Bug 1777835 - ocaml-merlin has no %{?dist} in release
Summary: ocaml-merlin has no %{?dist} in release
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ocaml-merlin
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robin Lee
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-28 12:15 UTC by Miro Hrončok
Modified: 2019-12-10 02:54 UTC (History)
1 user (show)

Fixed In Version: ocaml-merlin-3.3.3-1.fc31
Clone Of:
Environment:
Last Closed: 2019-12-10 02:54:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2019-11-28 12:15:49 UTC
Description of problem:
Use of the %{?dist} tag is mandatory in Fedora.
ocaml-merlin doesn't use it.

Version-Release number of selected component (if applicable): 3.3.2-1


Steps to Reproduce:
$ repoquery --repo=rawhide-source ocaml-merlin

Actual results:
ocaml-merlin-0:3.3.2-1.src

Expected results:
ocaml-merlin-0:3.3.2-1.fc32.src

Additional info:
https://docs.fedoraproject.org/en-US/packaging-guidelines/DistTag/

Comment 1 Fedora Update System 2019-12-01 12:50:10 UTC
FEDORA-2019-1f9a8e72a8 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1f9a8e72a8

Comment 2 Miro Hrončok 2019-12-01 13:07:48 UTC
Thanks!

Comment 3 Fedora Update System 2019-12-02 17:37:46 UTC
ocaml-merlin-3.3.3-1.fc31 has been pushed to the Fedora 31 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-1f9a8e72a8

Comment 4 Fedora Update System 2019-12-10 02:54:39 UTC
ocaml-merlin-3.3.3-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.


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