openSUSE Forums > openSUSE Build Service (OBS) » release version using c_cnt and b_cnt

Go Back   openSUSE Forums > openSUSE Build Service (OBS)
Forums FAQ Members List Search Today's Posts Mark Forums Read


openSUSE Build Service (OBS) Questions about creating packages for openSUSE and using the Build Service

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 05-Aug-2009, 18:11
Puzzled Penguin
 
Join Date: Jan 2009
Location: UK
Posts: 3
sbarbereau hasn't been rated much yet
Default release version using c_cnt and b_cnt

Hello,
I've the feeling I must be missing something simple here but googling and look on forum and ML archive didnt gave me a clear answer.
I would like the Release field from my spec file to be based on the osc build count and commit count. From what i do understand this should be the default behavior but it doesnt seem to be in my packages.
Example spec file header I'm using:
======
Name: iperf
Version: 2.0.4
Release: 3%{?dist}
Summary: Measurement tool for TCP/UDP bandwidth performance
License: BSD
Group: Applications/Internet
URL: http://iperf.sourceforge.net
Source: http://prdownloads.sourceforge.net/iperf/%{name}-%{version}.tar.gz
Patch0: iperf-2.0.4-debuginfo.patch
Patch1: iperf-2.0.4-tcpdual.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
======
I tryed different variations of 'release' fields: "Release: 3","Release: <C_CNT>",no release line .... obvisouly none of it gives me the expected result.

I'm sure it must be very simple to get it to work as it should but if something can give me a hint on what to do I would appreciate.

Thanks,
Seb.
Reply With Quote
Reply

Bookmarks


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2