I believe I know how to fix this problem: merge IBS and OBS teams!
OBS seems to keep adding new and more restrictive rules, but still IBS
has some rules that OBS does not. And now engineers are expected to
populate both repositories with exactly the same code?
I generally do impossible things only before lunch ... so maybe I can
figure out how to do this tomorrow.
On 09/28/2016 12:57 PM, Lee Duncan wrote:
I maintain several packages in the OBS and in the IBS, and many of them
For example, I am supporting the target-isns package. The newest version
of target-isns is 0.6.3 as was updated in Base:system and then in
Factory Nov 10 2015 (not by me).
So Factory and Base:System have the newest version.
But there are several other versions of this package, and they have
diverged from each other at different times:
openSUSE Base:System 0.6.3
openSUSE Factory 0.6.3
openSUSE Leap 42.1 3 commits behind 0.6.3
openSUSE Leap 42.2 1 commit behind 0.6.3
SLES 12 SP1 1 commit behind 0.6.3
SLES 12 SP2 uses SP1 version
But the problem is that the "target-isns.changes" files has 4 versions
now! There are 3 versions in OBS (for openSUSE) and one other version in
IBS (for SLES).
On top of this, the new "interlocking" rules seem to require that the
version in Leap 42.2 exactly match the version in SLES 12 SP2, including
meta-data such as the SPEC file and the *.changes file.
My only problem is that I understood there was a rule that the *.changes
file for any project be strictly chronological. If that's true, then
once two *.changes file diverge, they can never be exactly the same
again, as no old entries are ever supposed to be lost.
Can anyone help me with this "catch 22"?
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org