Bug 116223 - im-sdk nvr and source name should include the svn revision
Summary: im-sdk nvr and source name should include the svn revision
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: im-sdk
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Yu Shao
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC2Update IIIMF
TreeView+ depends on / blocked
 
Reported: 2004-02-19 07:51 UTC by Jens Petersen
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version: 11.4-46.svn1587
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-26 02:47:19 UTC


Attachments (Terms of Use)

Description Jens Petersen 2004-02-19 07:51:45 UTC
Description of problem:
Since we're currently building from the upstream trunk stable
subversion repository, I think it would be better to include
the head revision number in the source tarball and the package
revision number.

Steps to Reproduce:
1. rpm -ql im-sdk-11.4-13.src.rpm | grep bz2
2. rpm -q iiimf-server
  
Actual results:
1. im-sdk-11.4.tar.bz2
2. iiimf-server-11.4-13

Expected results:
1. say im-sdk-11.4.1568.tar.bz2
2. say iiimf-server-11.4.1568-3

Additional info:
It's nice to now when the source is changes,
and this will also make source maintenance easier I think.

Comment 1 Warren Togami 2004-06-10 06:30:57 UTC
I must suggest a slightly different scheme that would be like fedora
Extras package naming policies, and mharris rules.

Version: 1.4
Release: X.svnY
Where X is the incrementing release number of the package, and Y is
the upstream svn revision.

Including the revision number in the Version tag may potentially
clash, necessitating an Epoch increment.  Just hoping to avoid even
the smallest chance.

Target for FC2 Update on June 14th.

Comment 2 Jens Petersen 2004-06-22 01:44:36 UTC
Yu, thanks for changing the tarball filename. :-)

Can we also have the svn revision at least in pkg release
number as Warren suggested?

Comment 3 Jens Petersen 2004-06-23 14:16:46 UTC
Should be fixed in the update for FC2 and in the next devel build.


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