dogtagpki

#2798 Update development spec file templates
Closed: fixed Opened by mharmsen.

Closed: fixed
Reopen Issue

Update the spec files located under the source directory pki/specs with the new format:

  • Version: 10.5.0
  • Release: 0.0b.%{timestamp}.%{git-commit-id}
NOTE:  The release number is composed as '0.b0.<timestamp>.<git release ID>' to allow
       seamless updating where:
             * the initial ‘0’ is equivalent the previous official release number
               (‘0’ prior to any official releases); allows update from a development
               release to an official release
             * the ‘0.b0’ is equivalent to the previous sprint release number
               (‘0.b0’ prior to any sprint releases); allows update from a development
               release to a sprint release
             * the ‘0.b0.<timestamp>’ is required to be able to update one development
               release to another development release since there is no guarantee that
               the  <git commit ID> at development build time is greater than that of
               a development build that may already be installed on the system

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue priority set to: critical
- Issue set to the milestone: 10.5

Metadata Update from @mharmsen:
- Issue assigned to mharmsen

Author: Matthew Harmsen mharmsen@redhat.com
Date: Sat Sep 2 08:22:50 2017 -0600

Update development spec file templates
Version: 10.5.0
Release: 0.0.<timestamp>.<git commit ID>
The release number is composed as '0.0.<timestamp>.<git commit ID>'
to allow seamless updating where:
    * the initial ‘0’ is equivalent the previous official release
      number (‘0’ prior to any official releases); allows update
      from a development release to an official release
    * the ‘0.0’ is equivalent to the previous stage release
      number (‘0.0’ prior to any stage releases); allows update
      from a development release to a stage release
    * the ‘0.0.<timestamp>’ is required to be able to update one
      development release to another development release since
      there is no guarantee that the  <git commit ID> at
      development build time is greater than that of a development
      build that may already be installed on the system
https://pagure.io/dogtagpki/issue/2798
Change-Id: If8d0d24a1947391dc8ecb19fbd04d9e903b62449

Metadata Update from @mharmsen:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.0 (was: 10.5)
- Issue status updated to: Closed (was: Open)

Commit 1798384de5edc919601d9661dd0c63cd479a4c6a seems to be causing a build break on RHEL 7.4:

Setting 'default_release_value=0'
Setting 'default_stage_value=0'
Setting 'timestamp=20170911065942'
Unknown option: -C
usage: git [--version] [--help] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]
Setting 'git_commit_id='
Setting 'PKI_RELEASE=0.0.20170911065942.'
error: line 86: Illegal sequence ".." in: Release:          0.0.20170911065942..el7

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.5.0)
- Issue status updated to: Open (was: Closed)

In response to this comment, submitted:

https://review.gerrithub.io/#/c/378843/

Commit 1798384de5edc919601d9661dd0c63cd479a4c6a seems to be causing a build break on RHEL 7.4:
Setting 'default_release_value=0'
Setting 'default_stage_value=0'
Setting 'timestamp=20170911065942'
Unknown option: -C
usage: git [--version] [--help] [-c name=value]
[--exec-path[=]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=] [--work-tree=] [--namespace=]
[]
Setting 'git_commit_id='
Setting 'PKI_RELEASE=0.0.20170911065942.'
error: line 86: Illegal sequence ".." in: Release: 0.0.20170911065942..el7

commit 4bc4f9a385f0ad20edfede06e6bf0849da6a26db
Author: Matthew Harmsen mharmsen@redhat.com
Date: Fri Sep 15 16:00:57 2017 -0600

Apply development spec file templates across all platforms
NOTE:  Unfortunately, the "-C" option is not available to the
       native version of 'git' running on all platforms,
       therefore, we must construct a comparable command
       to mimic this behavior on ALL platforms.
https://pagure.io/dogtagpki/issue/2798
Change-Id: Id6c3e7f94a5d50dd0e19fe125a063118c1c4b4aa

Metadata Update from @mharmsen:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to dogtag-pki-10.5.0-1.fc27, dogtag-pki-theme-10.5.0-1.fc27, pki-core-10.5.0-1.fc27, pki-console-10.5.0-1.fc27

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2918

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
Low
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.