21.01.2014 19:05, Oscar C пишет:
El 2014-01-19 17:14, Matwey V. Kornilov escribió:
19.01.2014 20:08, Oscar C пишет:
Looking at this closer, the problem is that the release tag on the .spec
file is changed automatically on every build by OBS. If kernel-sun7i and
kernel-sources have different release number, it's impossible to build a
module for the kernel.
But kernel-$flavor is just a link to kernel-sources. They can not
have different release tags.
Ehm, I'm must be doing something wrong because in my case, they have
different release tags. These are the tests I've done so far:
- Create package kernel-source. Release tag is 1.1
- Branch kernel-sun7i from kernel-source. Release tag is 2.1
- Create package kernel-source. Release tag is 1.1
- Branch kernel-sun7i from kernel-source. Release tag is 2.1
- Commit some modifications to kernel-source. Release tag is 2.1. As
soon as I commit the changes, the kernel-sun7i is rebuilt. Release tag
is then 2.2.
- Create package kernel-source. Release tag is 1.1.
- Commit some modifications to kernel-source. Release tag is 2.1.
- Branch kernel-sun7i from kernel-source. Release tag is 3.1.
All these tests were build in the home:ocurero:arm project. What's wrong?
Usual work-flow is to branch kernel-source and then link kernel-$flavor
to it. Look at
https://build.opensuse.org/project/show/home:matwey:beaglebone
You have to edit kernel-source package, while kernel-$flavor is just a
namekeeper.
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
