How do I build later releases of vim?

English Open Build Service (OBS)
1

Hi,

I’m cautious not to take advantage of this community’s generosity and willingness to help, as I always prefer to do things (like building custom packages) myself as opposed to asking other people to do it for me, but I am kind of stuck and don’t know how to fix this problem myself. What I did was I ran:


osc branch  openSUSE:Factory vim

from ~/OBS/home:fusion809/. This created a folder ~/OBS/home:fusion809/home:fusion809:branches:editors/vim with spec files, patches and assorted other files in it. The spec file was for vim 7.4.1194 and the latest release of vim is 7.4.1294, so I edited the spec file, changing line #20 (%define patchlevel 1194) to

%define patchlevel  1294

. Then I ran

osc build openSUSE_Factory x86_64 vim.spec --noservice > output.txt 2> errors.txt

(output.txt and errors.txt is my way of recording the output so I can share with those that wish to help me). Here is output.txt: http://paste2.org/vKWdJc5k, while errors.txt is empty. I have experience writing PKGBUILDs and ebuilds, with PKGBUILDs merely updating the version defined by the variable pkgver is usually sufficient to update the package version, but with spec files I am beginning to see things are not quite as simple. I am eager to learn how to write spec files correctly, it’s just I am struggling to find any resources that document in detail how to write them in a straightforward and intuitive way. Hence why I am asking for help with specific examples (the previous example I asked for help with, if you missed it was atom.spec https://forums.opensuse.org/showthread.php/513459-Atom-spec-file-is-not-building-an-RPM-or-SRPM-why), so I can learn by example.

Thanks for your time and patience,
Brenton

2

Hi
I wouldn’t pull from factory, always the devel project, I would also copypac rather than branching since this implies your going to possibly send an update back…

In your case it’s maintained in the editors repo (and at the version your building…);
https://build.opensuse.org/package/show?project=editors&package=vim

I would delete the factory one you created, then;


osc copypac editors vim home:fusion809
cd <to you build location if not there>
osc co home:fusion809 vim
cd home:fusion809/vim
osc repos
osc build <repo target from last command>

If you run osc se <some_package> from the list will normally identify the devel project (I’m sure there are osc command options to get this).

3

is what is confusing me, would openSUSE_Factory x86_64 vim.spec be an adequate repo target?

osc repos

returned no output at the command-line, so not sure if you thought it would and meant I should take its output and use that as the input for osc build.

4

Running

osc build editor

(if that is what this repo is meant to be in this example) returns:

no repositories defined for project 'home:fusion809'

if relevant.

5

Hi
Ahh, you haven’t created any in your home project for the package to inherit…

You need to add some… eg Tumbleweed, openSUSE Leap etc…

6

I haven’t created any repos? How do I do this? Have any Wiki links to show me how to? I Googled “osc repositories” as it seemed like the only applicable search that I could think of, but it didn’t give me any useful Wiki links. Sorry, I’m so new to all of this, that some things you’s may consider basic I still need to learn.

7

Hi
Easier to pop onto the webui, login and add;
https://build.opensuse.org/project/repositories/home:fusion809

You may need to also then need to enable at the package level

8

Worked, thanks again!