mock questions
 

Hi,
how I can save or get all shell scripts generated by rpmbuild
like /var/tmp/rpm-tmp.Alfd0Z (%build)
I got a build prepare , build compile ,


Thanks in advance.
--
Sérgio M. B.

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

mock questions
 

2011/10/27 Sérgio Basto <sergio@serjux.com>


Hi,

how I can save or get all shell scripts generated by rpmbuild

like /var/tmp/rpm-tmp.Alfd0Z (%build)

I got a build prepare *, build compile ,


man mock*
export MOCKARGS='--no-cleanup-after'


ThanksV!jay
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

mock questions
 

On Thu, 2011-10-27 at 10:37 +0530, Vijay N. Majagaonkar wrote:
>
> 2011/10/27 Sérgio Basto <sergio@serjux.com>
> Hi,
> how I can save or get all shell scripts generated by rpmbuild
> like /var/tmp/rpm-tmp.Alfd0Z (%build)
> I got a build prepare , build compile ,
>
> man mock
>
>
> export MOCKARGS='--no-cleanup-after'

no after mock --rebuild with --no-cleanup-after
the scripts rpm-tmp.something are deleted

find /var/lib/mock/fedora-15-x86_64/ -name "rpm-tmp*"

nothing
>
>
>
> Thanks
> V!jay
> --
> buildsys mailing list
> buildsys@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys

--
Sérgio M. B.

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

mock questions
 

On Thu, 2011-10-27 at 05:38 +0100, Sérgio Basto wrote:
> Hi,
> how I can save or get all shell scripts generated by rpmbuild
> like /var/tmp/rpm-tmp.Alfd0Z (%build)
> I got a build prepare , build compile ,

"If the build process ends in an error, you can take a look at the bash
scripts in /var/tmp/rpm-tmp.*. Looking at these scripts will tell you
exactly what variables are being defined and what is being done. Often
times you can fix an error in the spec file just by looking at the
scripts.
These scripts will be deleted upon termination of a section, preventing
you from looking at them. You can cheat and get a look at them by
forcing an error in that section. Just add "exit 1" to your spec file
in the appropriate section. Another useful thing is to "set; exit 1" in
a spec file. This will exit and spit out a list of defined environment
variables. Finally, you can place "bash -i" in a spec file to stop
rpmbuild and drop to a shell where you can take a look around."

Nothing to stop "these scripts", be deleted upon termination of a
section ?

Thanks in advance
- -
Sérgio M. B.

--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys