Bug 1237176 - release field does not include dist tag
Summary: release field does not include dist tag
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pacman
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1237153
TreeView+ depends on / blocked
 
Reported: 2015-06-30 13:57 UTC by Kamil Páral
Modified: 2015-06-30 15:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 15:04:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kamil Páral 2015-06-30 13:57:11 UTC
Description of problem:
This package does not include a dist tag (e.g. '.fc23') in its release field, even though it is mandatory according the packaging guidelines:
https://fedoraproject.org/wiki/Packaging:DistTag

Our automated testing efforts are beginning to rely on having a dist tag in RPM file names:
https://lists.fedoraproject.org/pipermail/packaging/2015-June/thread.html#10693

Please adjust the package spec file and add '%{?dist}' at the end of the release field. Do this for all supported Fedora releases.

It is not necessary to build a new package version immediately, but it should be prepared in the spec file so that a new package build in the future will contain the dist tag.

Thank you.


Version-Release number of selected component (if applicable):
libalpm-0:4.2.1-1.i686
libalpm-0:4.2.1-1.x86_64
libalpm-devel-0:4.2.1-1.i686
libalpm-devel-0:4.2.1-1.x86_64

Comment 1 Kamil Páral 2015-06-30 14:00:35 UTC
Version-Release number of selected component (if applicable):
pacman-0:4.2.1-1.x86_64
pacman-filesystem-0:4.2.1-1.noarch

Comment 2 Zbigniew Jędrzejewski-Szmek 2015-06-30 15:04:32 UTC
Oops, it seems I dropped it when going from a git snapshot to a released version. Fortunately only in rawhide. I'll rebuild the package, to be able to close this immediately.


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