Hello,
I noticed some problems with mock, when building tools such as valgrind,
syslinux etc. on x86_64.
The default mock config says to exclude i386 and similar packages.
However, these programs depend on stubs-32.h from the i386 glibc-devel
package.
The x86_64 glibc-devel only brings stubs-6
On Tue, May 16, 2006 at 11:25:43AM +0200, Andreas Thienemann wrote:
> Hello,
>
> I noticed some problems with mock, when building tools such as valgrind,
> syslinux etc. on x86_64.
>
> The default mock config says to exclude i386 and similar packages.
>
> However, these programs depend on stubs
On Tue, 2006-05-16 at 11:33 +0200, Florian La Roche wrote:
> On Tue, May 16, 2006 at 11:25:43AM +0200, Andreas Thienemann wrote:
> > Hello,
> >
> > I noticed some problems with mock, when building tools such as valgrind,
> > syslinux etc. on x86_64.
> >
> > The default mock config says to exclud
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> seth vidal
> On Tue, 2006-05-16 at 11:33 +0200, Florian La Roche wrote:
> > On Tue, May 16, 2006 at 11:25:43AM +0200, Andreas Thienemann wrote:
> > > Hello,
> > >
> > > I noticed some problems with
On Tue, 2006-05-16 at 11:08 -0500, [EMAIL PROTECTED] wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > seth vidal
> > On Tue, 2006-05-16 at 11:33 +0200, Florian La Roche wrote:
> > > On Tue, May 16, 2006 at 11:25:43AM +0200, Andreas T
Title: [PATCH] Fix PS1 prompt for shell
Not quite a brown-paper-bag bug, but I broke the PS1 prompt for the shell command. Not all that earth shattering, but the following trivial patch fixes it.
It was due to using an old mock-helper which didn't have the PS1 in ALLOWED_ENVS and the fact th
Title: [PATCH - RFC] unify config parsing
The recent changes to add default.cfg processing bumped the number of lines in main(). The following patch unifies all config file parsing into one small loop, removing about a dozen redundant lines of code. It also removes an unnecessary variable, co
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> seth vidal
> Sent: Tuesday, May 16, 2006 1:27 PM
> To: Discussion of Fedora build system
> Subject: RE: Multiarch support for mock
>
> On Tue, 2006-05-16 at 11:08 -0500, [EMAIL PROTECTED] wrote:
> >
Title: [RFC] in progress: autocache patch
Here is my current autocache patch for comments. I have two features left to implement: 1) permissions on tarballs, and 2) ability to select compressed/uncompressed tarballs.
Usage:
There are two added command line options. First is
Title: [RFC] in progress: autocache patch
A couple of notes:
Credit should be given to Jochen Schmitt for his original
patch: http://www.redhat.com/archives/fedora-extras-list/2005-November/msg00169.html
My mock-helper changes are straight from Jochen
Schmitt's patch.
All mock.py ch
Title: [PATCH] autocache patch for mock
Here is what I would consider to be a patch ready to check-in to implement automatic caching of the mock buildroot. This feature is disabled by default but can be turned on by the "--autocache" cli option or the "use_cache" config file option.
On Tue, May 16, 2006 at 10:48:39AM -0400, seth vidal wrote:
> On Tue, 2006-05-16 at 11:33 +0200, Florian La Roche wrote:
> > On Tue, May 16, 2006 at 11:25:43AM +0200, Andreas Thienemann wrote:
> > > Hello,
> > >
> > > I noticed some problems with mock, when building tools such as valgrind,
> > >
OK, since I do a bunch of builds I just had to try this out. It took
me a while to get building again after moving from mock 0.4 to 0.5;
I'm still not sure where the buildsys-build package is supposed to
come from, so I just built the spec I found in mock CVS and stuck it
in my local repo.
Basic
Thanks for the feedback!
On Tue, 2006-05-16 at 22:06 -0500, Jason L Tibbitts III wrote:
> OK, since I do a bunch of builds I just had to try this out. It took
> me a while to get building again after moving from mock 0.4 to 0.5;
> I'm still not sure where the buildsys-build package is supposed to
On Tue, 2006-05-16 at 22:18 -0500, Michael E Brown wrote:
> On Tue, 2006-05-16 at 22:06 -0500, Jason L Tibbitts III wrote:
> >
> > I'm building on a dual core quad socket Opteron 880 (2.4GHz) machine
> > with 16GB of RAM; disk is a plain throwaway 250GB Western Digital
> > connected via SATA to an
Attached are timings from various runs with bzip2, gzip, and no
compression. Summary: gzip kicks butt. Mr Tibbitts was correct.
Attached is a diff to change the default to gzip. :)
Here is a summary (warm cache):
No caching: real1m36.247s
build bz2 cache:real4
16 matches
Mail list logo
