3

How to update a RPM version? Shall i just update it in my spec file and re-build the entire package?

Sebastian Mach
  • 38,570
  • 8
  • 95
  • 130
RajSanpui
  • 11,556
  • 32
  • 79
  • 146
  • This isn't really a programming question. Better suited for the super user site, perhaps? –  Jul 06 '11 at 07:57
  • 3
    @Lars: Packaging is part of the programming process. – Ignacio Vazquez-Abrams Jul 06 '11 at 07:58
  • @Lars: After programming comes the RPM packaging so that the end user can use it. – RajSanpui Jul 06 '11 at 08:00
  • @Lars: And that is why i have put the tags as such. Please check the tags. – RajSanpui Jul 06 '11 at 08:01
  • 1
    I vote on this being a topic of programming, too. Imho, it fits less to super user or server fault. Packaging also often needs some scripting. – Sebastian Mach Jul 06 '11 at 08:26
  • @phresnel and Ignacio: Glad there are people like you :) – RajSanpui Jul 06 '11 at 08:52
  • 2
    Packaging is sort-of related to programming, I agree (being a Debian developer for over a decade, I can't really disagree). However, upgrading system software such as RPM is not part of programming, any more than upgrading the compiler, text editor, browser, or shell is, and those are all also integral parts of the programming environment. (But I seem to have misunderstood the question, perhaps.) –  Jul 06 '11 at 09:02

1 Answers1

2

That would be the first step, yes. You may also have to download the new source. And don't forget to reset the Release back to 1.

Ignacio Vazquez-Abrams
  • 776,304
  • 153
  • 1,341
  • 1,358
  • Did not understand, what you mean by: "And don't forget to reset the Release back to 1." I have a package 2.4, have to change it to 2.4_1. – RajSanpui Jul 06 '11 at 07:55
  • Is it required? My first had 2.4-060007. I added a source, and was told to make it to 2.4_1. So can't i make it 2.4_1-060007? – RajSanpui Jul 06 '11 at 07:58
  • The earlier version (before my source update) had that release number. – RajSanpui Jul 06 '11 at 08:00
  • Yeah... if you can't answer *why* then it can't be that important. Reset to 1. – Ignacio Vazquez-Abrams Jul 06 '11 at 08:01
  • ok..thanks, i got ur point. You mean it should continue 2.4_1-00001, 2.4_1-00002..like that. Let me also confirm the same with my lead once before i start :) – RajSanpui Jul 06 '11 at 08:03
  • Last question...Will this also update the version in readme? Or readme needs to be created a patch and all and update? – RajSanpui Jul 06 '11 at 08:04
  • For readme update i saw, we have to untar the tarball in SOURCES, and update there. Because there is no separate patch created for README version update. – RajSanpui Jul 06 '11 at 08:51