[Bug 1077145] New: [regression] osc build uses wrong changes file
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145 Bug ID: 1077145 Summary: [regression] osc build uses wrong changes file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: adrian@suse.com Reporter: bwiedemann@suse.com QA Contact: qa-bugs@suse.de CC: coolo@suse.com Found By: Development Blocker: --- I found this when working on reproducible builds for openSUSE. Regression occurring since at least 2018-01-19 Using the /usr/lib/build/changelog2spec script from build-20171128-278.1 from openSUSE:Tools repo When building packages like antlr openssh qemu python-pandas that have multiple .changes files sometimes the wrong one will end up in the resulting .src.rpm and binary rpms Steps To Reproduce: osc co openSUSE:Factory/antlr ; cd $_ time osc build --keep-pkg=test.2/ --noservice antlr.spec rpm -qp --changelog test.2/antlr-2.7.7-0.src.rpm|head -2 Actual Result: * Thu Dec 07 2017 dimstar@opensuse.org - Escape the usage of %{VERSION} when calling out to rpm. Expected Result: * Fri Jan 12 2018 tchvatal@suse.com - Add condition about python2 module, the rewrite happened in antlr4 Reproducible: Sometimes on another build host I got build-20171027 and could not reproduce the problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c1
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c2
--- Comment #2 from Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c3
--- Comment #3 from Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c4
Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c5
--- Comment #5 from Bernhard Wiedemann
My two commits probably did not make anything worse than before, maybe they do not fix every case.
actually, the first commit effectively dropped the sort, making things worse than before and the 2nd commit just fixed the case of foo-something.changes but not something-foo.changes (e.g. python-rpm / rpm) and also the intended effect of the first commit was about service generated .changes file and you only sometimes get that depending on hash randomization. In a certain sense 'always broken' is better than 'randomly broken' because you can catch it in testsuites. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c6
--- Comment #6 from Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c7
--- Comment #7 from Stefan Seyfried
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c8
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145
http://bugzilla.opensuse.org/show_bug.cgi?id=1077145#c11
Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com