Bug 1444941 - bogus date in %changelog
Summary: bogus date in %changelog
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-24 15:04 UTC by Csaba Henk
Modified: 2017-05-30 18:51 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.11.0
Clone Of:
Environment:
Last Closed: 2017-05-30 18:51:22 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Csaba Henk 2017-04-24 15:04:57 UTC
Description of problem:

Building RPM from glusterfs using the shipped spec file produces this warning:

warning: bogus date in %changelog: Wed Feb 7 2017 Kaleb S. KEITHLEY <kkeithle>

Comment 1 Worker Ant 2017-04-24 15:10:00 UTC
REVIEW: https://review.gluster.org/17100 (build: correct bogus date in RPM spec) posted (#2) for review on master by Csaba Henk (csaba)

Comment 2 Worker Ant 2017-04-25 08:18:21 UTC
COMMIT: https://review.gluster.org/17100 committed in master by Niels de Vos (ndevos) 
------
commit d6194de9731ae8f6d97735c7cd5b2434a44c21b5
Author: Csaba Henk <csaba>
Date:   Fri Apr 21 19:43:08 2017 +0200

    build: correct bogus date in RPM spec
    
    In the RPM spec changelog there is an entry
    wth the following date:
    
      Wed Feb 7 2017
    
    However, Feb 7 2017 was Tuesday. In this change
    we correct the day of the date.
    
    BUG: 1444941
    Change-Id: I073bfe878e0a21d446a80c2f4ee045facba3e82b
    Signed-off-by: Csaba Henk <csaba>
    Reviewed-on: https://review.gluster.org/17100
    Tested-by: Kaleb KEITHLEY <kkeithle>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Shyamsundar 2017-05-30 18:51:22 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/


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