On 7/6/11 3:10 AM, "Li, Yan I" <[email protected]> wrote:

>On Wed, 2011-07-06 at 16:07 +0800, Nashif, Anas wrote:
>> As long as you are using a link you should not worry about it, since
>> obs adds the build number from the origin to that of the destination
>> of the link, If you are not using links, then the proposed solution
>> below should also work.
>> 
>Thanks. I'm importing an old package so I have to manually set the
>Release number. Didn't know such a good trick before. :)

What are you doing specifically?  I'm a bit worried about you changing the
release number, as the version/release in the .spec should be
corresponding to the version/release of the actual code you're packaging.

Here's a good reference btw:

http://wiki.meego.com/Packaging/Guidelines#Version_and_Release


Thanks,

rs

>
>
>> On Wed, Jul 6, 2011 at 9:01 AM, Zhang, Vivian <[email protected]>
>> wrote:
>>         How about defining "Release: 8" in spec file?
>>         It will make sure the <CI_CNT> of the generated rpm starting
>>         from 8.
>>         
>>         Thanks
>>         vivian
>>         
>>         
>>         -----Original Message-----
>>         From: [email protected]
>>         [mailto:[email protected]] On Behalf Of Yan Li
>>         Sent: Wednesday, July 06, 2011 2:40 PM
>>         To: David Greaves
>>         Cc: [email protected]
>>         Subject: Re: [meego-packaging] Changing package's Release
>>         number in OBS?
>>         
>>         On Wed, 2011-07-06 at 02:53 +0800, David Greaves wrote:
>>         > > but since OBS guarantees that it only goes up... I don't
>>         think the situation
>>         > > that you mention can actually happen
>>         >
>>         > It can't happen to us in MeeGo, but if you are a customer
>>         who, for some reason
>>         > needs to rebuild a package then it most certainly can. I'd
>>         like us to be more
>>         > supportive of letting MeeGo be used in ways it's not
>>         "expected" to be used.
>>         >
>>         > There are other issues around this too but to answer the
>>         OP's question, yes you
>>         > can do this using the <SPEC_REL> macro.
>>         >
>>         > https://bugs.meego.com/show_bug.cgi?id=10910
>>         
>>         Thanks. But, no, I don't want to override the default naming
>>         schema. I'm
>>         importing an old package called foo-5.1-7.1 into OBS so I want
>>         the
>>         <CI_CNT> to start with 8 so I can get foo-5.1-8.1. I'm looking
>>         for a way
>>         to boost to the <CI_CNT>...  :)
>>         
>>         --
>>         Best regards,
>>         Li, Yan
>>         
>>         MeeGo Team, Opensource Technology Center, SSG, Intel
>>         Office tel.: +86-10-5751-1695 (inet: 8-751-1695)
>>         OpenPGP key: 5C6C31EF
>>         IRC: yanli on network irc.freenode.net
>>         
>>         _______________________________________________
>>         MeeGo-packaging mailing list
>>         [email protected]
>>         http://lists.meego.com/listinfo/meego-packaging
>>         _______________________________________________
>>         MeeGo-packaging mailing list
>>         [email protected]
>>         http://lists.meego.com/listinfo/meego-packaging
>>         
>> 
>> 
>
>-- 
>Best regards,
>Li, Yan
>
>MeeGo Team, Opensource Technology Center, SSG, Intel
>Office tel.: +86-10-5751-1695 (inet: 8-751-1695)
>OpenPGP key: 5C6C31EF
>IRC: yanli on network irc.freenode.net
>
>_______________________________________________
>MeeGo-packaging mailing list
>[email protected]
>http://lists.meego.com/listinfo/meego-packaging

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to