how to build a scratch build of an older version of my package ?

[Development discussions related to Fedora]

In trying to track down when a bug began showing up, I'd like to build
an earlier version of my package eg from 9 months ago (hence earlier
upstream release and different spec/patches). How can that be achieved
on the builder ?

Does the build system keep the build logs of old packages, ie that shows
what build requires-version was installed, and which gcc compiler
version was used ?

[Richard Shaw]

On Tue, Sep 17, 2013 at 2:30 PM, David Timms <dtimms(a)iinet.net.au&gt; wrote:

>  In trying to track down when a bug began showing up, I'd like to
> build
>  an earlier version of my package eg from 9 months ago (hence earlier
>  upstream release and different spec/patches). How can that be achieved
>  on the builder ?
>
>  Does the build system keep the build logs of old packages, ie that shows
>  what build requires-version was installed, and which gcc compiler
>  version was used ?
>
>  I'm not sure if you can build from a previous commit in git with fedpkg 
but you
can pretty much build whatever you want with a source RPM so if
could get a hold of the older source RPM (perhaps from an older Fedora
release) then you can submit it to koji.

Richard

[Mikolaj Izdebski]

On 09/17/2013 09:30 PM, David Timms wrote:
>  In trying to track down when a bug began showing up, I'd like to
> build
>  an earlier version of my package eg from 9 months ago (hence earlier
>  upstream release and different spec/patches). How can that be achieved
>  on the builder ? 
koji build --scratch <target>
'git://pkgs.fedoraproject.org/<pkgname>?#<hash>'

You just need to substitute Koji target you want to build for, component
(source package) name and git commit hash that you want to build.  For
example:

koji build --scratch f19-candidate
'git://pkgs.fedoraproject.org/javapackages-tools?#4a755d42fa884cacdb373ac05c8b3b9e62751994'


>  Does the build system keep the build logs of old packages, ie that
> shows
>  what build requires-version was installed, and which gcc compiler
>  version was used ? 
Unreferenced builds are garbage collected, which means build logs will
eventually be removed.

-- 
Mikolaj Izdebski
IRC: mizdebsk

[Paul Howarth]

On 17/09/13 20:30, David Timms wrote:
>  In trying to track down when a bug began showing up, I'd like to
> build
>  an earlier version of my package eg from 9 months ago (hence earlier
>  upstream release and different spec/patches). How can that be achieved
>  on the builder ?
>
>  Does the build system keep the build logs of old packages, ie that shows
>  what build requires-version was installed, and which gcc compiler
>  version was used ? 
Note that old builds (source and binary RPMs, plus logs) can be found 
at: http://kojipkgs.fedoraproject.org/packages/<pkgname>/

Paul.

difference between F18 and F19 ? was: how to build a scratch build of an older version of my package ?

[Development discussions related to Fedora]

On 18/09/13 20:45, Paul Howarth wrote:
>  On 17/09/13 20:30, David Timms wrote: 
...
>  Note that old builds (source and binary RPMs, plus logs) can be
> found
>  at: http://kojipkgs.fedoraproject.org/packages/<pkgname>/ 
Thanks Richard, Mikolaj and Paul. These were all useful and helpful
responses.

With the info links, I downloaded older builds of audacity, installed
and tested a particular feature (Effect|Equalization), and found that
packages built on F19 or later produce a segmentation fault before the
wxDialog is shown on screen.

The builds in the build system use the same spec and sources. The built
for F18 rpm runs on my F19 machine, and the feature showing the bug
works fine, no crash. The same issue was noted on Arch linux build (with
recent builds some months), but not on an Ubuntu build (might be an
older release).

Reviewing mock logs:
- state.log: mock v 1.1.22 both F18 and F19.
- root log: most packages are very similar versions, usually just
    a few -releases later. (I can show complete diffs if that would help).
- gcc-c++:  fc18 (4.7.2-8)   fc19 (4.8.1-1).
- wxGTK:    fc18 (2.8.12-5)  fc19 (2.8.12-8).


build.log:
gcc-cc FLAGS:
- fc18(a heap of them)  fc19 (same heap plus -grecord-gcc-switches)

The .configure line ends of with multiple copy of
above grecord-gcc-...items (f19 only).

- fairly new spec code:
++++
# ensure we use the system headers for these, note we do this after
# configure as it wants to run sub-configures in these dirs
for i in ffmpeg libresample libsoxr libvamp portaudio-v19; do
   rm -rf lib-src/$i
done
++++


On build f18, this is not logged. The f19 build does log this removals.

Does any of this ring any "oh yeah, build system could cause this issue"
scenarios ? [https://bugzilla.redhat.com/show_bug.cgi?id=999145]

Thanks, David.